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. Later in the semester, they alternate between regular meetings with the client (for interviews, planning, and review of software product deliverables) and the delivery and presentation of the initial and improved versions of a process playbook.

The lab classes are dedicated to progress meetings with the professor, addressing both the development of the project and the evolution of the playbook.

Work is carried out weekly in groups of 5 to 7 students, both inside and outside the classroom, 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 and the planning, organization, and monitoring of all phases of the software development lifecycle.

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

They also develop a software project, following the defined processes and engaging in all activities such as project management, requirements analysis, architecture, development, and quality assurance. Issues related to communication, team dynamics, and professional practice are also covered. This project involves the participation of an external client.

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

1. Analyze, select, and justify an appropriate software lifecycle and development processes in a project context.
2. Establish measurable process performance baselines, monitor progress and adapt the processes based on evidence.
3. Plan, develop, and deliver a software product while controlling scope, schedule, cost, quality, and risk through disciplined practices and data-driven monitoring.
4. Collaborate effectively as a team, managing roles, communication, and professional practices responsibly.
5. Engage responsibly with clients and stakeholders to understand needs build trust and deliver value.

1. Definition, evaluation, and improvement of software processes

• Disciplined Agile Delivery
• Way of Working
• Playbook
• Continuous improvement

2. Agile development of a software project

• Planning
• Project management
• Quality management
• Delivery
• Evaluation

NAO