Go to:
Logótipo
You are here: Start > M.EIC014

Requirements Engineering

Code: M.EIC014     Acronym: ER

Keywords
Classification Keyword
OFICIAL Software Engineering

Instance: 2024/2025 - 2S Ícone do Moodle

Active? Yes
Web Page: https://moodle2425.up.pt/course/view.php?id=5327
Responsible unit: Department of Informatics Engineering
Course/CS Responsible: Master in Informatics and Computing Engineering

Cycles of Study/Courses

Acronym No. of Students Study Plan Curricular Years Credits UCN Credits ECTS Contact hours Total Time
M.EIC 22 Syllabus 1 - 6 39 162

Teaching Staff - Responsibilities

Teacher Responsibility
António Manuel Lucas Soares

Teaching - Hours

Recitations: 3,00
Type Teacher Classes Hour
Recitations Totals 1 3,00
António Manuel Lucas Soares 3,00
Mais informaçõesLast updated on 2025-02-10.

Fields changed: Objectives, Resultados de aprendizagem e competências, Métodos de ensino e atividades de aprendizagem, Fórmula de cálculo da classificação final, Bibliografia Complementar, Melhoria de classificação, Programa, Componentes de Avaliação e Ocupação, Bibliografia Obrigatória, Avaliação especial

Teaching language

English

Objectives

This course unit aims to endow students with the ability to analyse a complex problem situation and plan and manage a requirements engineering process to lead to the design of a new system where one or more digital sub-systems are fundamental. It is assumed that software systems (digital systems) are considered socio-technical systems that can be designed to optimize both the technical and social dimensions of the broader system they belong to.

Learning outcomes and competences

By the end of the course, students should be able to:

  1. explain the importance of requirements and the RE process in the success of an information system;
  2. describe the RE process as well as identify and explain the roles and actors in the process according to a specic conceptual framework;
  3. describe and know how to apply the requirements elicitation techniques: problem solving, systemic and design thinking, requirements workshops, focus groups, and scenarios;
  4. explain what is the importance of requirements analysis and negotiation and describe the associated techniques;
  5. describe and know how to apply the various requirements documentation techniques, in particular the use-cases technique, the requirements document and its communication and negotiation functions;
  6. explain the importance of requirements validation and associated techniques;
  7. describe the activities and tools for requirements management; 
  8. know scientic literature that studies project cases involving requirements engineering;

Working method

Presencial

Program


  1. Requirements Engineering Fundamentals and Framework - Importance, requirements fundamentals; requirements engineering framework, System Context

  2. Requirements Engineering Artefacts - Goals, Scenarios, Solution-oriented requirements

  3. Requirements Engineering Core Activities - Elicitation, Documentation, Negotiation

  4. Requirements Validation - Fundamentals, Techniques.

  5. Requirements Management - Fundamentals, Traceability, Prioritization, Change Management.

Mandatory literature

Pohl , Klaus; Requirements engineering : fundamentals, principles, and techniques. ISBN: 978-3-642-12577-5

Complementary Bibliography

Laplante, Phillip A., and Mohamad Kassab; Requirements engineering for software and systems, Auerbach Publications, 2022. ISBN: 0367654520
Neill, Colin J., and Philip A. Laplante; Antipatterns: identification, refactoring, and management, CRC Press, 2005. ISBN: 978-0849329944

Teaching methods and learning activities

The CU is structured in three learning dimensions: research and innovation, technical and methodological, and societal and professional. The classes will be based on the flipped classroom instructional strategy. Most of the classes will have students led debates about scientific and technical papers, case studies, research methods, reflection about technical/professional roles, impact on organisations, etc.. Project-based learning will drive students group project to develop a vision for a new software system to solve a complex problem situation.

Evaluation Type

Distributed evaluation without final exam

Assessment Components

Designation Weight (%)
Trabalho prático ou de projeto 35,00
Participação presencial 20,00
Apresentação/discussão de um trabalho científico 15,00
Trabalho escrito 30,00
Total: 100,00

Amount of time allocated to each course unit

Designation Time (hours)
Elaboração de projeto 33,00
Estudo autónomo 63,00
Frequência das aulas 42,00
Apresentação/discussão de um trabalho científico 8,00
Trabalho escrito 16,00
Total: 162,00

Eligibility for exams

Students have to attend at least 75% of the scheduled classes;

Calculation formula of final grade

20% - Paper reading sheets (individual)
30% - Final essay (individual)
15% - Presentation and discussion of articles (group)
35% - Project (group)

Special assessment (TE, DA, ...)

All components are mandatory for all students. Students exempt from attending classes (student workers, etc.) must carry out group work and be present at their presentation. 

Classification improvement

It is possible to improve the final essay.

Observations

1. Permitted Use of AI tools

1.1 Ethical and Scientific Principles.
AI use is allowed under strict adherence to ethical and scientific standards. Students must ensure proper handling of sources and maintain transparency about AI use in their work.

1.2 Permitted Use of AI.
All types of generative models for image, text, or sound creation are permissible, but transparency in their use and thus documentation in the appendix of the reports is required.

1.3 Creation of Text Material.
AI should be used as tool, a powerful but also fallible one, and thus a critical engagement with AI-generated text and other content is necessary.

1.4 Creation of Images
Use of generative models for image creation is allowed. Images created using AI must be properly credited and documented.

1.5 Documentation in the Appendix.
The use of AI in academic writing must be documented in a table in the appendix, specifying the AI tools used, their application, the critical review process, and the location in the manuscript this applies to.


2 Prohibited Use of AI

Directly using texts from AI (copy/paste) as part of academic work is forbidden. This applies to all forms of writing, and any violation will be treated at the same level as with plagiarism.
Recommend this page Top
Copyright 1996-2025 © Faculdade de Engenharia da Universidade do Porto  I Terms and Conditions  I Accessibility  I Index A-Z  I Guest Book
Page generated on: 2025-06-16 at 06:58:59 | Acceptable Use Policy | Data Protection Policy | Complaint Portal