Programme
Positioning (day 1)
With references to models like INCOSE, IEEE 1471 and RUP the discipline of requirements modeling is discussed extensively. The role of the requirements engineer is discussed explicitly as well as the limitations of its responsibilities and its consequences. Skills in expert-interviews are important in Requirements Engineering and therefore these are practised in a workshop.
Context (day 2)
During this session the context in which requirements engineering takes place is discussed. This focuses on the position of the system within the business in relation to the business processes. Business modeling is about the Universe of Discourse and we will learn about the terminology that is used in the domain. The possibilities of UML in this kind of modeling will be discussed. In process modeling we discuss languages for process models and modeling principles for processes. Subjects such as workflow modeling and orchestration will also be discussed.
System Modeling (day 3)
This session focuses on system modeling. Use Cases are an important tool for modeling a system’s functional requirements. Besides approaches to describe Use Cases we also study the relationship between Use Cases and business processes. Use case modeling is associated with object oriented modeling. This approach to modeling is compared to traditional modeling. Strong and weak points of the two are discussed. Also the object oriented modeling language UML is compared to traditional modeling languages such as ER-Diagrams and functional decomposition.
Quality & Patterns (day 4)
In this session of the Masterclass Requirements Engineering the Quint model for the specification of quality requirements is central. The part on requirements patterns focuses on the question whether standard solutions can be found for typical situations. We discuss for a number of ‘typical systems’ and ‘typical processes’ the QUINT attributes that are found to be important. For a number of standards, the relationship with the QUINT model is discussed.
Reviews & testing (day 5)
In this session a number of aspects are discussed that are related to reviewing and testing software and other products such as documents. The well known V-model for testing is studied and a link is created with use cases. We also refer back to the QUINT model and it is shown which test strategies are available to test different aspects of a system. Finally the importance of executing Fagan inspections is discussed.
Process & new developments (day 6)
In this last session we study the effects of new developments on requirements engineering such as agile development, test-driven development and Model Driven Architecture (MDA). We will also discuss modeling requirements in the context of an iterative process. When is the requirements engineer ready for modeling? At which moments and with which roles does the requirements engineer communication?
Target Audience
Requirements Engineers with experience in the traditional way of specifying (experience with elicitation techniques) orRequirements Engineers who are familiar with OO techniques and agile development, but lack experience in requirements elicitation.
Prerequisites
Elementary knowledge of OO and UML on the level of the course OO & UML Essentials.