Base Knowledge
Students must master advanced software engineering development skills.
It is recommended the completion of the following curricular units:
– Applied Programming;
– Database;
– Internet Programming I & II;
– Software Engineering;
– User Interaction.
Teaching Methodologies
The curricular unit is strongly based on the experimental and active methods, where students actively explore and develop their skills in managing a common software engineering project of considerable size. In this way, the curriculum unit follows a dynamic methodology PBL (Project-Based Learning).
The project integrates several students who interact in the various phases and procedures in a group dynamic, being autonomous and responsible in decision-making, under the guidance of the teacher.
Although there is occasional exposition of theoretical foundations and concepts, learning is encouraged through the practical resolution of real problems.
Learning Results
At the end of the curricular unit the student will be able to:
1. Plan and manage software projects;
2. Plan and schedule tasks and deadlines;
3. Implement a change control process;
4. Implement a quality assurance plan;
5. Identify risks;
6. Estimate and manage costs and resources;
7. Identify and resolve social and organizational issues in large groups.
Program
1. Software design techniques and methodologies (traditional waterfall methodology and agile methodologies); Project management standardization;
2. Project phases: Software Concept; Requirements Development; Architectural Design; Detailed Design; Coding and debugging; and Software Release;
3. Planning, estimating and scheduling tasks (Gantt diagram);
4. Change control and project life cycle;
5. Quality management: Document and code review and inspection process;
6. Risk management;
7. Control of the execution of a project;
8. Project management support tools;
9. Social, organizational and ethical issues in large groups.
Curricular Unit Teachers
Marco António Morais VelosoGrading Methods
Regarding the evaluation, the following methods are considered:
1. Periodic Evaluation:
a) a group project, with three iterations (presentation moments) over the duration of the semester.
The final grade corresponds to the evaluation of the project, after submission at the end of the semester.
2. Exam Evaluation (Normal Period, Resit Period, Special Period):
a) a group project, with three iterations (presentation moments) over the duration of the semester, corresponding to the project developed during the academic semester;
The final grade corresponds to the evaluation of the project, after submission at the end of the semester.
General rules:
a) the evaluation is individual, although students work in groups.
b) the group project must be carried out exclusively during the academic semester, and it is not possible to develop the project them during the exam evaluation.
c) access to the different evaluations depends on prior enrolment via the academic management platform.
Internship(s)
NAO
Bibliography
Kerzner, H. (2017). Project management: A systems approach to planning, scheduling, and controlling (12th ed.). Wiley.
Layton, M., Morrow, D. (2018). Scrum for dummies. For Dummies.
Layton, M., Ostermiller, S., and Kynaston, D. (2020). Agile project management for dummies (3rd ed.). For Dummies.
McConnell, S. (2000). Software project survival guide. Microsoft Press. (Bibliografia complementar).
Miguel, A. (2015). Gestão de projectos de software (5th ed.). FCA. (Bibliografia complementar).
Miguel, A. (2024). Gestão moderna de projectos – Melhores técnicas e práticas (9th ed.). FCA.
Murray, P. (2016). The complete software project manager: Mastering technology from planning to launch and beyond. Wiley.
Pinto, J. and Tscharf, C. (2019). Scrum – A gestão ágil de projectos. FCA.
Sutherland, J. (2016). Scrum – A arte de fazer o dobro do trabalho em metade do tempo. Lua De Papel.
Wysocki, R. (2019). Effective project management: Traditional, agile, extreme, hybrid (8th ed.). Wiley.