MDRE: The Requirements Engineering Process

2022 ◽  
pp. 75-84
Author(s):  
James A. Crowder ◽  
Curtis W. Hoff
Keyword(s):  
Requirements Engineering ◽  
Engineering Process ◽  
Requirements Engineering Process

A Requirements Engineering process for Software Product Lines

2010 ◽  
Author(s):  
Danuza Neiva ◽  
Fernando Cesar de Almeida ◽  
Eduardo Santana de Almeida ◽  
Silvio Lemos Meira
Keyword(s):  
Requirements Engineering ◽  
Software Product Lines ◽  
Engineering Process ◽  
Product Lines ◽  
Requirements Engineering Process ◽  
Software Product

Requirements Engineering Process Improvement and Related Models

2011 ◽  
pp. 18-33
Author(s):  
Badariah Solemon ◽  
Shamsul Sahibuddin ◽  
Abdul Azim Abd Ghani
Keyword(s):  
Requirements Engineering ◽  
Process Improvement ◽  
Process Model ◽  
Good Practice ◽  
Capability Maturity Model ◽  
Maturity Model ◽  
Engineering Process ◽  
Principal Characteristics ◽  
Capability Maturity ◽  
Requirements Engineering Process

Requirements Engineering (RE) is a key discipline in software development, and several standards and models are available to help assess and improve RE processes. However, different standards and models can also help achieve different improvement goals. Thus, organizations are challenged to select these standards and models to best suit their specific context and available resources. This chapter presents a review of selected RE-specific and generic process improvement models that are available in the public domain. The review aims to provide preliminary information that might be needed by organizations in selecting these models. The chapter begins with analyses of how RE maturity is addressed in the Capability Maturity Model Integration (CMMI) for Development. Then, it describes the principal characteristics of, and the assessment and improvement framework applied in four RE-specific process assessment and improvement models: the Requirements Engineering Good Practice Guide (REGPG), the Requirements Engineering Process Maturity(REPM), the Requirements Capability Maturity Model (R-CMM), and the Market-Driven Requirements Engineering Process Model (MDREPM). This chapter also examines the utility and lesson learned of these models.

Towards eGovernment in the Large

2011 ◽  
pp. 227-243
Author(s):  
Thomas Matheis ◽  
Jörg Ziemann ◽  
Peter Loos ◽  
Daniel Schmidt ◽  
Maria Wimmer
Keyword(s):  
European Union ◽  
Requirements Engineering ◽  
Local Level ◽  
Evaluation Framework ◽  
European Research ◽  
The European Union ◽  
Engineering Process ◽  
Research Project ◽  
Requirements Engineering Process ◽  
European Research Project

An increasing level of cooperation between public administrations nowadays on national, regional and local level requires methods to develop interoperable eGovernment solutions and leads to the necessity of an efficient evaluation and requirements engineering process that guides the establishment of systems and services used by public administrations in the European Union. In this chapter, the authors propose a framework to systematically gather and evaluate requirements for eGovernment in the large. The evaluation framework is designed to support requirements engineers to develop a suitable evaluation and requirements engineering process with respect to interoperable eGovernment solutions. The methodology is motivated and explained on the basis of a European research project.

A Security Requirements Engineering Tool for Domain Engineering in Software Product Lines

2011 ◽  
pp. 73-92
Author(s):  
Jesús Rodríguez ◽  
Eduardo Fernández-Medina ◽  
Mario Piattini ◽  
Daniel Mellado
Keyword(s):  
Requirements Engineering ◽  
Software Product Lines ◽  
Product Line ◽  
Security Requirements ◽  
Engineering Process ◽  
Product Lines ◽  
Requirements Engineering Process ◽  
Security Requirements Engineering ◽  
Software Product ◽  
Automated Support

The concepts of Service-Oriented Architectures and Software Product Lines are currently being paid a considerable amount of attention, both in research and in practice. Both disciplines promise to make the development of flexible, cost-effective software systems possible and to support high levels of reuse, and may sometimes be complementary to each other. In both paradigms, security is a critical issue, although most of the existing product line practices do not comprise all the security requirements engineering activities or provide automated support through which to perform these activities, despite the fact that it is widely accepted that the application of any requirements engineering process or methodology is much more difficult without a CARE (Computer-Aided Requirements Engineering) tool, since it must be performed manually. Therefore, this chapter shall present a tool denominated as SREPPLineTool, which provides automated support through which to facilitate the application of the security quality requirements engineering process for software product lines, SREPPLine. SREPPLineTool simplifies the management of security requirements in product lines by providing us with a guided, systematic and intuitive manner in which to deal with them from the early stages of product line development, thus simplifying the management and the visualization of artefact variability and traceability links and the integration of security standards, along with the management of the security reference model proposed by SREPPLine.

Sign in / Sign up

Export Citation Format

Share Document