Doel vakAfter taking this course, you will...
• understand the key concepts of RE and its relevance for system and
• know how to properly elicit and evaluate requirements;
• know how to properly specify and document requirements;
• know how to create goal models for the purpose of capturing functional
and non-functional goals;
• know how to create UML class diagrams for the purpose of capturing the
structure and the in- ter-relations between the conceptual objects
manipulated in the system;
• know how to create operational models and behavioral models for the
purpose of capturing the operational and behavioral aspects of the
Inhoud vakRequirements engineering (RE) is concerned with the identification of
the goals that need to be achieved by an envisioned system, the
operationalization of these goals into services and constraints, and the
assignment of responsibilities for the resulting requirements to agents
such as humans, devices, and software. The processes involved in RE
include domain analysis, elicitation, specification, assess- ment,
negotiation, documentation, and evolution. Getting high-quality
requirements is difficult and crit- ical. Recent surveys have confirmed
the growing recognition of RE as an area of utmost importance in
software engineering research and practice.
Within this course, we put an emphasis on requirements elicitation,
specification, and modeling. The overall goal is to teach the key
concepts related to RE and to create an awareness for the importance of
this topic in practice. The various lectures and instructions will be
devoted to the following topics:
• Introduction to Requirements Engineering: In this lecture, you will
learn what RE is all about, its aim and scope, its critical role in
system and software engineering, and its relationship to other
disciplines. You will also learn what requirements are, what they are
not, and what good re- quirements are.
• Requirements Elicitation and Evaluation: In this lecture (and the
corresponding exercise session), you will learn a variety of techniques
that we may use for understanding the domain in which a software project
takes place and for eliciting the right requirements for a new system.
What is more, you will learn how to evaluate the elicited requirements.
• Requirements Specification and Documentation: In this lecture (and the
corresponding exercise session), you will learn how to specify
requirements in a proper way. Among others, we will dis- cuss templates
in natural language, diagrammatic notations, and formal specification
methods for critical aspects of the to-be system.
• Modeling System Objectives: In this lecture (and the corresponding
exercise session), you will learn how to model the functional and
non-functional goals of the to-be system. The models you will learn to
create are referred to as goal models.
• Modeling Conceptual Objects: In this lecture (and the corresponding
exercise session), you will learn how to capture the structural
perspective of the system. More specifically, you will learn how to use
UML class diagrams to characterize, structure, and inter-relate the
conceptual ob- jects manipulated in the system.
• Modeling System Operations and Behaviors: In this lecture (and the
corresponding exercise ses- sion), you will learn how to model the
functional and the behavioral perspectives of the system. To this end,
you will learn how to create operational models and behavioral models.
|Faculteit||Faculteit der Bètawetenschappen|
|Vakcoördinator||dr. H. Leopold MSc|
|Examinator||dr. H. Leopold MSc|
dr. H. Leopold MSc
Voor dit vak moet je zelf intekenen.
Voor dit vak kun je last-minute intekenen.
Dit vak is ook toegankelijk als: