Requirements engineering

Résumé

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference. In the waterfall model, requirements engineering is presented as the first phase of the development process. Later development methods, including the Rational Unified Process (RUP) for software, assume that requirements engineering continues through a system's lifetime. Requirements management, which is a sub-function of Systems Engineering pract

Source officielle

https://en.wikipedia.org/wiki/Requirements_engineering

À propos de ce résultat

Cette page est générée automatiquement et peut contenir des informations qui ne sont pas correctes, complètes, à jour ou pertinentes par rapport à votre recherche. Il en va de même pour toutes les autres pages de ce site. Veillez à vérifier les informations auprès des sources officielles de l'EPFL.

Publications associées (17)

Publications associées

Chargement

Personnes associées (2)

Personnes associées

Chargement

Unités associées (1)

Unités associées

Chargement

Concepts associés (16)

Concepts associés

Chargement

Cours associés (7)

Cours associés

Chargement

Séances de cours associées (13)

Séances de cours associées

Chargement

During the design phase of an aircraft manufacturing system, different industrial scenarios need to be evaluated according to key performance indicators to achieve the optimal system performance. It is a highly complex process involving multidisciplinary stakeholders, various digital tools and protocols. To address the digital discontinuity challenge during this process, this paper proposes a tradespace framework based on semantic technology and model-based systems engineering. It aims at functionality integration of requirement management, architecture definition, manufacturing system design, solution verification and visualization. An application ontology is developed to integrate assembly system domain knowledge, industrial requirements and system architecture model information. The proposed framework is implemented in a case study to support the fuselage orbital joint process design, which is part of the aircraft final assembly line. A toolchain is presented to support the implementation, which consists of a set of enabling software corresponding to the functional modules of the framework. Different manufacturing system architectures are first designed by industrial system engineers supported by the application ontology stored in a graph database. They are then analyzed through Discrete Event Simulations and 3D simulations. The simulation results are presented through a web-based portal to show the key performance values of each architecture. This study serves as a part of the proof-of-concept of the recently proposed Cognitive Digital Twin concept.

SPRINGER2022

Chargement

The Integration of an RE Method and AHP: A Pilot Study in a Large Swiss Bank

Arash Golnam, Sofia Kyriakopoulou, Gil Regev, Alain Wegmann

This paper reports on a pilot study of the integration between the Systemic Enterprise Architecture Method (SEAM) and the Analytic Hierarchy Process (AHP) in a requirements engineering project. The objective of the project, conducted in one of the major banks in Switzerland, was to select a common SOA tool that could satisfy the needs of two of the bank’s main business units, investment and private banking. SEAM provided help in identifying stakeholders, eliciting their requirements, and analyzing these requirements. The resulting requirements were then grouped and translated into selection criteria for the alternative SOA tools. Based on these criteria, the stakeholders chose the tool to be purchased using AHP. We describe the project, the challenges we faced and the lessons learned. These relate to the nature and traceability of requirements, to the requirements elicitation process and to the relations between the bank’s business units.

IEEE2013

Chargement

Precise Graphical Representation of Roles in Requirements Engineering

Pavel Balabko, Alain Wegmann

Modeling complex systems can not be done without considering a system from multiple views. Using multiple views improves model understandability. However the analysis of models that integrate multiple views is difficult. In many cases a model can be evaluated only after its implementation. In our work we describe a visual modeling framework that allows for the evaluation of multiview models. We give an overview of our framework using a small case study of a Simple Music Management System. For each view in our framework we specify a separate role of the system. The whole system is specified as a composition of smaller roles. Each role, as well as the whole model of a system, can be evaluated by means of the analysis of possible instance diagrams (examples) that can be generated automatically. Instance diagrams are generated based on the formalization of visual models using the Alloy modeling language.

2003

Chargement