China
Africa
Explore chapters and articles related to this topic
Context Modelling for Variability-intensive Systems During Requirements Engineering
Published in Ivan Mistrik, Matthias Galster, Bruce R. Maxim, Software Engineering for Variability Intensive Systems, 2019
Nelufar Ulfat-Bunyadi, Maritta Heisel
Context modelling is performed during requirements engineering. Requirements engineering is the activity of eliciting, documenting, negotiating, validating, and managing requirements for a system [21]. Context modelling is an important activity during requirements engineering due to the following dependency. Each system is developed for a certain context. Requirements for the system are defined based on assumptions about this context. Satisfaction of the system requirements can only be guaranteed if the developed system is integrated into this context. If it is integrated into another context, it is possible that the set of system requirements is no longer satisfied. Due to this dependency between system and context, it is not sufficient to elicit and document only system requirements during requirements engineering. The underlying assumptions about the context, or more generally, the underlying knowledge about the context (i.e. facts and assumptions) needs to be documented as well during requirements engineering.
Introduction to Requirements Engineering
Published in Phillip A. Laplante, Requirements Engineering for Software and Systems, 2017
Requirements engineering is the branch of engineering concerned with the real-world goals for, functions of, and constraints on systems. It is also concerned with the relationship of these factors to precise specifications of system behavior and to their evolution over time and across families ofrelated systems.
Integrating Visualization Tools into the Requirements Engineering Process: An Empirical Study
Published in Engineering Management Journal, 2018
Bradford Logan, Jason Dever, Steven M.F. Stuban
Kossmann (2013) defines requirements engineering as “the discipline concerned with elaborating the requirements for a given project, program or system to be developed in a given context, based on the needs of all relevant stakeholders, analyzing and negotiating these requirements, tracing them, validating them with the relevant stakeholders, and managing their change over time.” Requirements engineering research was driven by the “practitioner’s need for more disciplined software development” to address the issues associated with software complexity in the mid-1970s (Jarke & Lyytinen, 2015). The enormous growth in software complexity over the last four decades further emphasizes the importance of improving the requirements engineering practice and its relationship to organizational success.