The purpose of the Requirements discipline is: (1) To establish and maintain agreement with the customers and other stakeholders on what the system should do. (2) To provide system developers with a better understanding of the system requirements. (3) To define the boundaries of (delimit) the system. (4) To provide a basis for planning the technical contents of iterations. (5) To provide a basis for estimating cost and time to develop the system and (6) To define a user-interface for the system, focusing on the needs and goals of the users.
In this subject we will focus on describing the requirements engineering process following the Unified Process methodology and using its artifacts for the treatment of requirements: Vision Document, Supplementary Specification, Use Case Model, Conceptual Domain Diagram, etc.
We will also consider how to develop requirements in agile methodologies like Scrum, comparing these techniques with those of the Unified Process.
(*)The teaching guide is the document in which the URV publishes the information about all its courses. It is a public document and cannot be modified. Only in exceptional cases can it be revised by the competent agent or duly revised so that it is in line with current legislation.