Knowledge, abilities and skills to be acquired by the students:
Identify the key topics in the activities related to requirements engineering of software systems;
Raise awareness of the importance of requirements engineering processes;
Present the major activities of the requirements development processes;
Describe the major tasks of an analyst;
Suggest ways of organizing a requirements document;
Write a software requirements specification;
Adopt a few best practices for writing requirements;
Learn the difference perspective of software systems modeling;
Framing the different diagrams of UML in the software development cycle;
Know the modeling elements of UML;
Modeling software efficiently and properly using UML diagrams.
Programme
IT Engineering
Level of Qualification|Semesters|ECTS
| Semestral | 6
Year | Type of course unit | Language
2
|Mandatory
|Português
Code
ULP452-7343
Recommended complementary curricular units
Software Engineering
Programming Languages
Databases
Professional Internship
Não
Syllabus
Theoretical part:
Introduction to requirements engineering;
engineering processes;
Requirements elicitation;
analysis and negotiation;
Requirements specification;
Best practices for writing requirements;
Requirements validation;
Requirements management;
Requirements development: an example of methodology.
Practical part:
Introduction to the UML;
use cases diagrams;
class diagrams;
object diagrams;
UML activity diagrams;
UML state diagrams;
component diagrams;
distribution diagrams;
sequence diagrams;
UML collaboration diagrams.
Objectives
Provide awareness of the importance of the requirements engineering process in the software development cycle.
Analyze and design systems and their components using the Unified Modeling Language (UML).
Teaching methodologies and assessment
Expository method in theory part lectures, complemented with application examples;
Expository methods in practical part lectures interspersed with solving practical problems by students;
Two tests, worth 25%;
Writing of a software requirements specification document, worth 25%;
Presentations in the theoretical classes, worth 25%;
It is necessary for approval to obtain a minimum of 8 points in each component.
References
- Kotonya, Gerard; Sommerville, Ian - Requirements Engineering: Processes and Techniques, John Wiley & Sons, 1998
- Booch, Grady; Rumbaugh, James; Jacobson, Ivar - The Unified Modeling Language User Guide, Addison Wesley, 1998
