Author(s):  
Badariah Solemon ◽  
Shamsul Sahibuddin ◽  
Abdul Azim Abd Ghani

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.


IEEE Access ◽  
2020 ◽  
Vol 8 ◽  
pp. 53374-53393 ◽  
Author(s):  
Muhammad Azeem Akbar ◽  
Ahmed Alsanad ◽  
Sajjad Mahmood ◽  
Abeer Abdulaziz Alsanad ◽  
Abdu Gumaei

2020 ◽  
Author(s):  
Andreas Drechsler ◽  
S Breth

© 2019 Elsevier Ltd and Association for Project Management and the International Project Management Association We employ design science research to develop a process model for the management of globally distributed software development (GDSD) projects. The model provides guidance for transforming established project frameworks in organizations to cope with additional challenges that a global project scale entails. The model integrates extant GDSD project management knowledge and makes it actionable for project managers, especially those with limited GDSD experience. The model was evaluated and found to be effective in transforming an actual GDSD project with teams in Germany, Poland, and India. Interviews with project managers with and without GDSD experience support the model's wider applicability to other contexts and IT project types. The model can also be used in GDSD project retrospectives to identify areas for improvement. In a research perspective, our model constitutes a novel type and instance of a social meta-artefact intended to transform existing social artefacts to retain their usefulness in evolving contexts.


Author(s):  
Claudia S. Litvak ◽  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn

It is a usual practice to use natural language in any document intended for clients and users in the requirements engineering process of a software development. This facilitates the comprehension of the requirements engineer's proposals to clients and users. However, natural language introduces some drawbacks, such as ambiguity and incompleteness, which attempt against a good comprehension of those documents. Glossaries help by reducing ambiguity, though they introduce their own linguistic weaknesses. The nominalization of verbs is one of them. There are sometimes appreciable differences between using a verb form or its nominal form, while in other cases they may be synonyms. Therefore, the requirements engineer must be aware of the precise meaning of each term used in the application domain, in order to correctly define them and properly use them in every document. In this chapter, guidelines about treatment of verb nominalization are given when constructing a specific glossary, called Language Extended Lexicon.


Sign in / Sign up

Export Citation Format

Share Document