Saltar al contingut Menu
Map
  • Home
  • Information
  • Contact
  • Map

Syllabus

Requirements Engineering ( ER )

Change to no-tab version

ECTS Credits Department Type Requirements Teaching Languages
6.0 ESSI
  • Specialization Compulsory (Information Systems)
  • Specialization Compulsory (Software Engineering)
Pre-requisit EEE
Pre-requisit IES
  • Catalan   
Correu
Center where the class is given Facultat d'Informàtica de Barcelona (FIB) - Universitat Politècnica de Catalunya - BarcelonaTECH

Description

The most difficult task of building an information system or, in general, a software system, consists of determining which system should be built. This task is called Requirements Engineering. No other work has a such negative economic and social impact as if done wrong. Many of the systems development failures are attributed to not do correctly their engineering requirements. This course presents the concepts, activities and artifacts of requirements engineering. Emphasis is placed on aspects that are essential to ensure the success of projects, especially the definition of the objectives of stakeholders, the correct formulation of the requirements and satisfaction of the argument. The teaching method of the course is of the family of PBL (Project Based Learning) and the centerpiece is a project (which varies each year) for which students, working in groups, have to make ​​the complete engineering requirements.

Professors

Person in charge

Maria Ribera Sancho Samso (ribera@essi.upc.edu)

Other

Ernest Teniente Lopez (teniente@essi.upc.edu)
Sergio Morales Garcia (smorales@essi.upc.edu)
Weekly hours dedication
T: 2.0 P: 0.0 L: 2.0 AA: 6.0 AD: 0.0



Generic Competences

Transversal Competences

  • SOLVENT USE OF THE INFORMATION RESOURCES

  • G6 - To manage the acquisition, structuring, analysis and visualization of data and information of the field of the informatics engineering, and value in a critical way the results of this management.
  • G6.3 - To plan and use the necessary information for an academic essay (for example, the final project of the grade) using critical reflection about the used information resources. To manage information in a competent, independent and autonomous way. To evaluate the found information and identify its deficiencies.


Technical Competences

  • INFORMATION SYSTEMS SPECIALIZATION

  • CSI3 - To determine the requirements of the information and communication systems of an organization, taking into account the aspects of security and compliance of the current normative and legislation.
  • CSI4.1 - To participate actively in the specification of the information and communication systems.
  • CSI3.5 - To propose and coordinate changes to improve the operation of the systems and the applications.
  • CSI4 - To participate actively in the specification, design, implementation and maintenance of the information and communication systems.
  • SOFTWARE ENGINEERING SPECIALIZATION

  • CES2 - To value the client needs and specify the software requirements to satisfy these needs, reconciling conflictive objectives through searching acceptable compromises, taking into account the limitations related to the cost, time, already developed systems and organizations.
  • CES2.1 - To define and manage the requirements of a software system.

Goals

  1. Understanding the need, objectives and contexts in which engineering requirements activities are performed

    Related Competences
  2. Knowing defining the objectives of a project.

    Related Competences
  3. Knowing identifying stakeholders of a porject.

    Related Competences
  4. Understanding what isthe system context, the boundary of the system and the use cases.

    Related Competences
  5. Knowing defining a business process in a particular language.

    Related Competences
  6. Understanding the need to perform a detailed state of the art of the professional practice within the scope of a project.

    Related Competences
  7. Knowing performing a detailed state of the art of professional practice within the scope of a project.

    Related Competences
  8. Understanding what are the scenarios and use cases of a system and what are the relations among them.

    Related Competences
  9. Knowing defining the use cases of a system by using a particular template.

    Related Competences
  10. Knowing what are the software system requirements and into what types are classified.

    Related Competences
  11. Knowing the methods to specify the requirements and contexts in which they are useful.

    Related Competences
  12. Knowing what the conflicts of requirements engineering, how to analyze them and how to solve them.

    Related Competences
  13. Understanding the need for argumentation satisfaction of goals on a project.

    Related Competences
  14. Knowing performing argumentation satisfaction of goals.

    Related Competences
  15. Knowing writing the requirements specification by using a particular template.

    Related Competences
  16. Knowing the methods to validate the requirements and in which contexts they are useful.

    Related Competences
  17. Knowing validating a requirements specification through inspection.

    Related Competences
  18. Understaing the need of performing the conceptual schema.

    Related Competences
  19. Knowing developing the conceptual schema from the requirerments of a project.

    Related Competences
  20. Knowing writing a conceptual schema in an executable language.

    Related Competences
  21. Understanding the relations among the artifacts of requirements engineering, and the need to keep the traceability and consistency.

    Related Competences
  22. Knowing validating a conceptual schema through inspection.

    Related Competences

Contents

1. Overview of requirements engineering

2. Project goals

3. Stakeholders

4. The system and its context

5. Scenarios and use cases

6. Software requirements

7. Satisfaction argument of goals.

8. Requirements engineering activities: Determination of requirements, documentation, negotiation and validation

9. Conceptual modeling in requirements engineering

10. Development of the conceptual schema

11. Traceability of requirements engineering artifacts

12. Validation of conceptual schemas

Activities

Legend

Activity
Evaluative Activity
Theory hours
Problem hours
Lab hours
Independent Learning Hours
Directed Learning Hours


Introduction
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 1. Overview of requirements engineering
Goals project
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 2. Project goals
  • 3. Stakeholders
E1
T      P      L      AA    AD    Total 
- - 0.0 0.0 - 0.0

Exercise on project goals.

Week 2
Type of exam: Laboratory exam

Goals:
Requirements
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 2. Project goals
  • 3. Stakeholders
  • 6. Software requirements
  • 7. Satisfaction argument of goals.
E2
T      P      L      AA    AD    Total 
- - 0.0 0.0 - 0.0

Exercise on satisfaction argument

Week 3
Type of exam: Laboratory exam

Goals:
Introduction to requirements engineering
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 1. Overview of requirements engineering
  • 8. Requirements engineering activities: Determination of requirements, documentation, negotiation and validation
Delivering state of the art
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Week 4
Type of exam: Theory exam

Goals:
System, context, use cases
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 4. The system and its context
E3
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Modeling business processes

Week 5
Type of exam: Theory exam

Goals:
Determining requirements
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 8. Requirements engineering activities: Determination of requirements, documentation, negotiation and validation
E4
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Exercise on essential and real use cases

Week 6
Type of exam: Theory exam

Goals:
Negotiating requirements
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 8. Requirements engineering activities: Determination of requirements, documentation, negotiation and validation
D1
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Preliminary delivery on requirements specification

Week 7
Type of exam: Theory exam

Goals:
Validation requirements
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 8. Requirements engineering activities: Determination of requirements, documentation, negotiation and validation
E5
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Exercise on validation requirements

Week 8
Type of exam: Theory exam

Goals:
Recap on requirements
T      P      L      AA    AD    Total 
1.0 0.0 2.0 6.0 0.0 9.0

Alumn: (-)

Goals:

Contents
  • 2. Project goals
  • 3. Stakeholders
  • 4. The system and its context
  • 5. Scenarios and use cases
  • 6. Software requirements
  • 7. Satisfaction argument of goals.
  • 8. Requirements engineering activities: Determination of requirements, documentation, negotiation and validation
  • 12. Validation of conceptual schemas
Q1
T      P      L      AA    AD    Total 
1.0 - - 0.0 - 1.0

Questionnaire on basic concepts of requirements engineering. The questionnaire will be answered online within the class. Each student must bring a laptop or similar to access and respond to the questionnaire.

Week 9
Type of exam: Theory exam

Goals:
D2
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Final delivery of the requirements specification

Week 9
Type of exam: Final exam

Goals:
Conceptual modeling in requirements engineering
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 9. Conceptual modeling in requirements engineering
  • 10. Development of the conceptual schema
E6
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Exercise on the executable OCL

Week 10
Type of exam: Final exam

Goals:
The structural scheme
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 10. Development of the conceptual schema
E7
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Exercise making structural scheme

Week 11
Type of exam: Theory exam

Goals:
The scheme behavior
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 9. Conceptual modeling in requirements engineering
  • 10. Development of the conceptual schema
D3
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Preliminary delivery of conceptual schema of the project

Week 12
Type of exam: Theory exam

Goals:
Validating conceptual schema
T      P      L      AA    AD    Total 
2.0 0.0 2.0 6.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 10. Development of the conceptual schema
  • 11. Traceability of requirements engineering artifacts
  • 12. Validation of conceptual schemas
E8
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Exercise on schema validation

Week 13
Type of exam: Final exam

Goals:
Recap subject
T      P      L      AA    AD    Total 
1.0 0.0 2.0 6.0 0.0 9.0

Alumn: (-)

Goals:

Contents
  • 11. Traceability of requirements engineering artifacts
  • 12. Validation of conceptual schemas
Completion of the final delivery of the conceptual scheme
T      P      L      AA    AD    Total 
0.0 0.0 0.0 10.0 0.0 10.0

Alumn: (-)

Goals:

Contents
  • 10. Development of the conceptual schema
  • 12. Validation of conceptual schemas
D4
T      P      L      AA    AD    Total 
0.0 - - 0.0 - 0.0

Final delivery of conceptual schema

Week 15-18
Type of exam: Theory exam

Goals:
Q2
T      P      L      AA    AD    Total 
1.0 - - 0.0 - 1.0

Questionnaire on basic concepts of conceptual modeling in requirements engineering. The questionnaire will be answered online within the class. Each student must bring a laptop or similar to access and respond to the questionnaire.

Week 14
Type of exam: Theory exam

Goals:
Total per type
T      P      L      AA    AD    Total 
28.0 0.0 28.0 94.0 0.0 150.0

Teaching methods

The course will primarily (but not completely) be taught using the teaching method PBL (Problem Based Learning).

There is a class (conventional) two hours a week in which the teacher presents very general topics (eg what is the requirements engineering) or aspects that are not sufficiently covered by other activities. Almost half the class is devoted to discussion and work in small groups on issues raised by the teacher. Typically, the class also provides a good solution to the exercise of the previous week.

La second main activity of the course is the determination of the requirements of a particular software system. The teacher sketches a specific situation (different from one course to another), for which students have to determine and specify the requirements of a software system, using some methods and languages ​​to be learned previously. This work is performed in group. The number of people and the composition of the group is defined at the beginning of the course (no more than five/six). Each group appoints a coordinator and a secretary. Each group meets at least once a week for two hours, the hours of laboratory classes. The group submits its work in five deliverables during the course, within limits fixed at the beginning of the course.

Before starting the meeting of the project groups, its members have posted what they have done during the week. Each meeting consists of three parts: The first part explains what each student has made during the week, the second consolidates the work done by members of the group, the third is planing what will be done in next week, and who will. At the end of each meeting, the Secretary publishes the minutes in the forum.

The third major activity is the course exercises. The teacher asks at least eight exercises during the course. Each student must submit (via Athena) his own solution to the exercises, within the specified deadline. The completion of the exercise requires learning new skills. The exercises are corrected soon, and if possible they will be discussed in class of the next week.

Note: The teaching method used in the course requires students to acquire new knowledge independently, using bibliographic sources that are normally in English. It is essential that the student has a sufficient level of English without much difficulty assimilating the literature (technical).

Assessment

In addition to the mark of the course, there will be a grade for the generic competence assigned to the course, with values A, B, C, D, where:
· A indicates that the competence has been accomplished with a level of excellence
· B indicates that the competence has been accomplished with the desired level
· C indicates that the competence has been accomplished with a sufficient level
· D indicates that the competence has not accomplished
This grade comes from the evaluation of the first assigment of the group (Context analysis.

Generic competences weight in the evaluation specific part

  • 0.0 % - To plan and use the necessary information for an academic essay (for example, the final project of the grade) using critical reflection about the used information resources. To manage information in a competent, independent and autonomous way. To evaluate the found information and identify its deficiencies.

Basics bibliography

Complementary bibliography

Prior learning

- An overview of software engineering, and the role it plays in Requirements Engineering
- Basic elements of conceptual modeling in UML / OCL
- Organizations, economic environment, decision-making.
- English reading level.

Compartir

 
logo FIB © Barcelona school of informatics - Contact - RSS
This website uses cookies to offer you the best experience and service. If you continue browsing, it is understood that you accept our cookies policy.
Classic version Mobile version