Article thumbnail
Location of Repository

838 Regulations Modelling and their Validation and Verification 1. GORE Goal-oriented Analysis of Regulations

By Robert Darimont, Michel Lemoine, Cediti B and Dprs/sae F


Abstract This paper explains how goal-oriented requirements engineering can be transposed into regulation modelling. It motivates also why this way of modelling regulations is worthwhile for people responsible for preparing regulations. In addition, the paper recounts how the approach has been applied to model ICAO Security Regulation for Civil Aviation in the context of the SAFEE project. Goal-Oriented Requirements Engineering (GORE) is an approach advocating the identification and analysis of goals as a prerequisite for writing of complete and consistent requirements documents. One of the most prominent GORE methodologies is KAOS [1, 2]. In KAOS, the requirements engineer is prompted to build a requirements model before writing the requirements document by exploiting various information mines, such as interviews, documentation, observations, etc. The requirements model to build consists of four main integrated sub-models: ─ The goal model captures the intentional view shared by all implied stakeholders. Goals are declarative properties on the system and its environment. Goals describe the problem to solve and are prescriptive. Goals are refined from highlevel strategic intentions (i) into technical, low-level requirements on the system and (ii) into expectations on its environment. Conflicts between goals and obstacles preventing goals from being achieved are also recorded in the model. ─ The object model captures the terminology needed to express the problem to solve (that is, the goals). ─ The agent model provides an agent-centered view on the system-to-be. ─ The operation model describes how agents have to cooperate to achieve the goals. KAOS has been successfully used in many industrial or service contexts mainly to produce requirements documents, to define strategies and refine them into IT plans, to reengineer requirements on top of existing systems. It is supported by a tool

Year: 2009
OAI identifier: oai:CiteSeerX.psu:
Provided by: CiteSeerX
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • (external link)
  • http://sunsite.informatik.rwth... (external link)
  • Suggested articles

    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.