Projeto de Software

Students must have fundamental knowledge and practice of software programming.

The theoretical classes are used initially for the presentation and discussion of software processes and process models, including Disciplined Agile Delivery (DAD) and the responsible use of AI. Later in the semester, they are dedicated to regular meetings with the client (first interview, Kick-Off Meeting, MVP presentation, and Final Delivery), weekly presentations of the Process Charter’s evolution, and regular presentations of novel practices experimented with by the teams.

The lab classes are dedicated to weekly thirty-minute progress meetings with the professor, per team, addressing both the development of the project and the evolution of the Process Charter.

Work is carried out weekly in groups of about 5 students, both inside and outside the classroom. Teams may contact the client at any time, in addition to the four formal engagement points (first interview, Kick-Off Meeting, MVP, and Final Delivery), with support from the professor throughout the week, either in person or via chat and video call tools.

In exceptional circumstances, some group members may participate remotely via video call, reflecting practices increasingly common in the software industry.

The Software Project course addresses software development processes in a context increasingly shaped by Artificial Intelligence (AI), as well as the planning, organization, and monitoring of all phases of the software development lifecycle.

Students participate in the definition, analysis, and continuous improvement of their own software processes.

Students also develop a software project for a client external to ISEC, engaging in all activities such as project management, requirements specification, architecture, AI-assisted development, and quality assurance. Issues related to communication, team dynamics, responsible AI use, and professional practice are also covered.

By completing this course, students are expected to have acquired the following competencies:

1. Analyze, select, and justify a software development lifecycle and processes, using Disciplined Agile Delivery (DAD) as a reference framework, appropriate to a software project context.
2. Define and use Objectives and Key Results (OKRs) to monitor project and process progress based on evidence.
3. Practice requirements specification as a first-class engineering competency (user stories, acceptance criteria, ADRs), as a primary driver of AI-assisted development quality.
4. Apply critical verification practices to AI-generated artefacts, including code review, testing, and documentation of AI usage decisions.
5. Plan, develop, and deliver a software product, controlling scope, quality, and risk through disciplined practices and data-driven monitoring.
6. Collaborate effectively as a team, managing roles, communication, and professional practices responsibly.
7. Engage responsibly and continuously with clients and stakeholders to understand needs, build trust, and deliver value incrementally.
8. Identify, document, and share innovative engineering practices experimented with throughout the project.

1. Definition, evaluation, and improvement of software processes in an AI context

• Disciplined Agile Delivery (DAD) as a mandatory framework
• Way of Working and Process Charter
• AI Integration Policy and AI Decision Log
• Objectives and Key Results (OKRs)
• Requirements specification (user stories, acceptance criteria, ADRs)
• Continuous improvement and sharing of novel practices across teams

2. Milestone-oriented software project development

• Milestone-based planning (Kick-Off Meeting, MVP, Final Delivery)
• Project and risk management
• Verification and quality assurance in an AI-assisted development context
• Delivery
• Evaluation

The final grade consists of two components:

• Definition of software Processes (Process Charter) - 40%
• Development of the software Project - 60%

The grades for both the Project and the Processes are based on the group assessment, adjusted by an individual factor that reflects each student's performance throughout the semester and peer evaluation, resulting in an individual grade.

Both components are assessed continuously, combining weekly assessment with formal milestone assessment.

The Processes (Process Charter) are assessed as follows:

• Continuous weekly assessment (weekly Process Charter presentations and novel practice presentations) - 40%
• Kick-Off Meeting review - 20%
• MVP review - 20%
• Final review - 20%

The Project is assessed as follows:

• Continuous weekly assessment (weekly progress meetings with the professor) - 20%
• Kick-Off Meeting - 20%
• MVP Delivery - 25%
• Final Delivery - 35%

Assessment is exclusively continuous: there is no exam and no possibility of grade improvement.

A minimum of 40% in each component is required to pass the course.

NAO