EXTREME: EXecuTable Requirements Engineering, Management, and Evolution

EXTREME: EXecuTable Requirements Engineering, Management, and Evolution

Ella Roubtsova (Open University of The Netherlands, The Netherlands)
Copyright: © 2013 |Pages: 25
DOI: 10.4018/978-1-4666-4217-1.ch003


Requirements engineering is a process of constantly changing worlds of intentions, goals, and system models. Conventional semantics for goal specifications is synchronous. Semantics of conventional system modeling techniques is asynchronous. This semantic mismatch complicates requirements engineering. In this chapter, we propose a new method EXTREME that exploits similarities in semantics of goal specification and executable protocol models. In contrast with other executable modelling techniques, the semantics of protocol modelling is based on a data extended form of synchronous CSP-parallel composition. This synchronous composition provides advantages for relating goals and system models, reasoning on models, requirements management, and evolution.
Chapter Preview

Goal Modelling

Goal-Oriented Requirements Engineering (GORE) is a well-established group of approaches (Kavakli, 2002; van Lamsweerde, 2004; Darimont & Lemoine, 2006; Regev & Wegmann, 2012). The aim of a goal-oriented approach is to justify requirements by linking them to higher-level goals.

The notion of a goal is used as a partial description of a system state being a result of an execution of the system. The authors of the GORE methods emphasize the similarity between goals, requirements, and concerns and propose to combine them in one tree structure. Goals are refined by requirements and concerns. The goal models are used to keep the business motivation in mind of requirement engineers and to elaborate the strategic goals with requirements and concerns.

An example of a goal tree is shown in Figure 1. The top nodes of Figure 1 present business goals of a simplified system supporting insurance business. The goals are

Figure 1.

Goal tree of an insurance business

  • A product is composed.

  • A policy is bought by a registered customer.

  • A claim of a client with a bought policy is handled.

Complete Chapter List

Search this Book: