Teaching Methodologies
The curricular unit is based on theoretical-practical classes. The teaching methods (ME) to be used are balanced between traditional and active and are the following:
ME1 – Presentation of content by the teacher (compatible with learning objectives 1, 2, 4, 6)
ME2 – Application of content learned by students (compatible with learning objectives 3, 5)
ME3 – Problem solving by students (compatible with learning objectives 3, 5, 7)
ME4 – Interaction and sharing of ideas by students (compatible with learning objectives 7)
ME5 – Development of critical thinking by students (compatible with learning objectives 7)
ME6 – Research carried out by students (compatible with learning objectives 5, 7)
ME7 – Project-based learning (compatible with learning objectives 7)
The classes include the presentation of concepts and methodologies and proceed with their discussion, as well as the demonstration of applied problem solving. In the classes, concepts and methodologies are presented, content is discussed and problem-solving is demonstrated. There will also be practical worksheets for students to complete, which allow them to test the content they have learned. The content is taught and discussed in a classroom environment.
In addition to the traditional lecture method, the methodology will include project-based learning. As the name suggests, this is an active learning methodology that aims to associate learning with doing. This method is based on the collective construction of knowledge, moving away from the conventional classroom model where the teacher teaches a subject and the students demonstrate how much they have learned through a final assessment activity. The project that is proposed to be developed, ideally carried out in a group, aims to present a proposal and feasibility study for a project to develop an information system (IS) for a specific organization that operates in a specific area of activity, complemented by the respective vision, objectives, business requirements, modeling and specification of software requirements related to this information system. This project will encourage problem solving by students, interaction and sharing of ideas by students in the same project group, the development of their critical thinking and will also promote research carried out by them in order to enhance the solution based on the functionalities and requirements of the proposed system.
Learning Results
Students should understand the role of IS in organizations and be able to identify, analyze and implement technological solutions to improve organizational processes. The Learning Objectives are:
LO1 – Identify requirements for computer systems and formulate appropriate technological solutions
LO2 – Know good practices for analysis, management and development of software requirements
LO3 – Understand and be able to use IS analysis techniques in practice
LO4 – Understand the UML modeling principles
LO5 – Understand and be able to use the most common UML diagrams in practice
LO6 – Raise awareness of software development processes according to ISO 12207
LO7 – Know how to apply the knowledge in a practical project
The teaching method, based on theoretical-practical classes, promotes the development of theoretical knowledge and practical skills and analytical competences. The teaching methodology includes several pedagogical methods (expository, demonstrative and project-based learning).
Program
Software requirements development
1. Principles of software requirements
2. Elicitation
3. Analysis
4. Specification
5. Validation
B. Software requirements management
1. Best practices
2. Change and version management
C. Information systems analysis techniques
1. Decision tables
2. Decision trees
3. Flowcharts
4. Structured language
6. Other analysis techniques
D. UML modeling language
1. Introduction
2. Modeling abstractions
3. Concepts used
4. Types of diagrams
E. Processes in information system development (ISO 12207)
1. Primary processes
– Acquisition
– Supply
– Development
– Operation
– Maintenance
2. Support processes
3. Organizational processes
Internship(s)
NAO
Bibliography
Belfo, Fernando. (2012). Especificação de Requisitos de Software. Instituto Superior de Contabilidade e Administração de Coimbra.
Coimbra.
Booch, G., Rumbaugh, J., & Jacobson, I. (2006). UML: Guia do Usuário (4a). Elsevier Editora.
Borges, J., Cunha, J. e Dias, T. (2015). Modelação de Dados em UML: Editora FCA
International Organization for Standardization and International Electrotechnical Commission (1995). ISO-IEC 12207 Standard – Software Life Cycle Processes, Joint Technical Committee Kimmel, P. (2005). Uml Demystified. McGraw Hill.
Koç, H., Erdo?an, A. M., Barjakly, Y., & Peker, S. (2021). UML diagrams in software engineering research: A systematic literature review. Proceedings, 74(1), 13.
Mauro, N. e O´Neil, H. (2004). Fundamental de UML: Editora FCA.
O´Neil, H., Mauro, N. e Ramos, P. (2010). Exercícios de UML: Editora FCA.
Wiegers, K. E., & Beatty, J. (2013). Software requirements. Pearson Education.