Base Knowledge
Programming knowledge, preferably in the object-oriented paradigm
Teaching Methodologies
Theoretical classes
– presentation of concepts
– illustration of concepts through examples
Practical classes
– application of concepts through guided exercises
– eventual exposure of additional concepts
Monitoring the development of practical work
Learning Results
Upon completing this course, students should be able to:
– Identify and correctly represent the requirements using appropriate diagrams.
– Perform an object-oriented analysis of a software system
– Create UML diagrams
– Describe and understand the evolution of analysis and software construction paradigms
– Assess the implications of architectural options for software development.
Program
1. Introduction to UML
2. Use Cases
3. Activity diagrams
4. Object Oriented Modeling
5. Class diagrams
6. Object diagrams
7. State Machine Diagram
8. Sequence diagrams
9. Communication diagrams
10. Component diagrams
11. Installation diagrams
12. Software Design Patterns
13. Software development methodologies
Curricular Unit Teachers
Leonor Isabel de Albuquerque MeloGrading Methods
The final grade will be calculated based on the following 2 evaluation components:
1. Written test with a weight of 50% of the final grade:
a. With a 35% minimum rating.
b. The test corresponds to the exam to be carried out in one of the planned evaluation periods.
c. The written test is carried out without consultation.
2. Practical work with a weight of 50% of the final grade:
a. No minimum rating.
b. Divided into three phases with the following provisional delivery dates:
i. goal 1 (12.5% of the final grade): 4th week of classes
ii. goal 2 (12.5% of the final grade): 8th week of classes
iii. goal 3 (25% of the final grade): 12th week of classes
c. Practical work is done in groups of 3 students each. The group's constitution must remain fixed along the semester. One of the goals of the curricular unit is improving the communication and teamwork skills. As such, groups of a single students will have a 20% penalty and groups of 2 students will have a 10% penalty.
d. Each phase of practical work is subject to a mandatory defense. The defenses will be carried out in the period after the delivery date of each phase, being subject to scheduling in a model to be announced later.
e. During defenses, in addition to discussing the work delivered, additional questions may be asked to be answered by a specific member of the group.
f. Each goal of the practical work can only be delivered once and on the dates indicated.
g. The grade obtained is valid for all assessment periods in the current academic year and cannot be improved.
h. Any component of the evaluation may be subjected to oral defence
Internship(s)
NAO
Bibliography
Main Bibliography
Booch, G., Rumbaugh, J., & Jacobson, I. (2000). UML : guia do usuário. Rio de Janeiro: Editora Campus. Localização: 1A-7-42 (ISEC) – 11118
Fowler, M. (2003). UML distilled : a brief guide to the Standard Object Modeling Language. Boston: Addison-Wesley. Localização: 1A-7-66 (ISEC) – 14417
Larman, C. (2007). Applying UML and patterns : an introduction to object-oriented analysis and design and iterative development (3rd ed.). Upper Saddle River, NJ: PTR, Prentice Hall. Localização: 1A-7-76 (ISEC) – 14711
Nunes, M., & O’Neill, H. (2004). Fundamental de UML (5th ed.). Lisboa: FCA – Editora de Informática. Localização: 1A-7-63 (ISEC) – 14307; 1A-7-64 (ISEC) – 14308
Silva, A., & Videira, C. (2001). UML, metodologias e ferramentas CASE. Lisboa: Edições Centro Atlântico. Localização: 1A-7-45 (ISEC) – 11543
Sommerville, I. (2011). Software engineering (9th ed.). Boston: Pearson, cop. Localização: 1A-7-107 (ISEC) – 15872
Additional Bibliography:
Miles, R., & Hamilton, K. (2006). Learning UML 2.0. O’Reilly Media, Inc.
Pilone, D., & Pitman, N. (2005). UML 2.0 in a Nutshell. O’Reilly Media, Inc.