Overview
ABSTRACT
The design and implementation of a new system relies on both a definition phase where user requirements are identified, and a demonstration that the system meets the user requirements. During the definition phase, a key step is to identify the different users, the systems in interface and their interaction with the system to be designed. Several approaches have been developed to identify the needs, relying on textual notation and modeling tools. The expected output is a list of requirements. This paper describes the overall requirements of the engineering process to acquire, formalize and demonstrate that the needs are met.
Read this article from a comprehensive knowledge base, updated and supplemented with articles reviewed by scientific committees.
Read the articleAUTHOR
-
Jean-Louis BOULANGER : Evaluator-Certifier - Certifer (Anzin, France)
INTRODUCTION
Requirements engineering is a necessity that appears in all industry standards (aeronautics, automotive, railways, nuclear, electrical equipment, space and defense). One difficulty is that no industry standard (DO 178, CENELEC, IEC 61508, etc.) provides an unambiguous, shared definition of a requirement, although there are dedicated standards such as ISO/IEC 29148. Industry standards introduce the notion of traceability (link between different elements) and the notion of level (in aeronautics we have the notion of HLR and LLR for High Level Requirement and Low Level Requirement).
This article presents the activities involved in requirements engineering and their implementation. The activities identified cover the field from the analysis of the user need to its realization. The term "realization" covers all activities from the acquisition of the requirement to the provision of the system meeting it.
Requirements engineering is the discipline of establishing and documenting requirements. The various associated activities are elucidation (translation of the word elicitation), specification, analysis, verification and validation, and management.
As a general rule, a project starts with a requirements definition phase, which aims to build a technical specification with associated performance levels. Based on the technical specification, the second phase consists of building a system that satisfies all the requirements.
It should be noted that some projects start with functional specifications or technical specifications supplied by the client (who may be a prime contractor in the case of an organization relying on several companies to build the final system). This does not mean that there has been no prior analysis of the requirements: in reality, this will have been carried out by the client, and only the technical specifications will have been supplied, which serve to control the coherence of the whole.
Exclusive to subscribers. 97% yet to be discovered!
Already subscribed? Log in!
KEYWORDS
Requirement | Railway transportation | Realization
Requirement Engineering
Bibliography
Also in our database
Events
ERTSS Embedded Real Time Software and System
ESREL
LambdaMU
Qualita
Standards and norms
- CENELEC, Applications ferroviaires. Spécification et démonstration de la fiabilité, de la disponibilité, de la maintenabilité et de la sécurité (FMDS). - NF EN 50126 - janvier 2000
- ISO, Quality management systems – Requirement. - ISO 9001 :2008 - Décembre 2000
- IEC, Sécurité fonctionnelle des systèmes électriques électroniques programmables relatifs à la sécurité, norme internationale. - IEC 61508 - 2008 ...
Directory
Manufacturers – Suppliers – Distributors (non-exhaustive list)
APTE
Organizations – Federations – Associations (non-exhaustive list)
AFIS
CERTIFY
Exclusive to subscribers. 97% yet to be discovered!
Already subscribed? Log in!
Article included in this offer
"Control and systems engineering"
(
149 articles
)
Updated and enriched with articles validated by our scientific committees
A set of exclusive tools to complement the resources