Story Card Process Improvement Framework for Agile Requirements

2010 ◽  
pp. 61-54 ◽  
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Process Improvement ◽  
Agile Software Development ◽  
Assessment Method ◽  
Engineering Process ◽  
Knowledge Based ◽  
Requirements Engineering Process ◽  
Agile Software ◽  
Software Development Environments

This chapter describes an ongoing process to define a suitable process improvement model for story cards based requirement engineering process and practices at agile software development environments. Key features of the SMM (Story card Maturity Model) process are: solves the problems related to the story cards like requirements conflicts, missing requirements, ambiguous requirements, define standard structure of story cards, to address non-functional requirements from exploration phase, and the use of a simplified and tailored assessment method for story cards based requirements engineering practices based on the CMM, which is poorly addressed at CMM. CMM does not cover how the quality of the requirements engineering process should be secured or what activities should be present for the requirements engineering process to achieve a certain maturity level. It is difficult to know what is not addressed or what could be done to improve the process. The authors also presents how can be the identified areas of improvement from assessment can be mapped with best knowledge based story cards practices for agile software development environments.

scholarly journals A Supporting Tool for Requirements Prioritization Process in Agile Software Development

2020 ◽  
Vol 5 (1) ◽  
pp. 15-27
Author(s):  
Khaled AbdElazim Muhammad ◽  
◽  
Ramadan Moawad ◽  
Essam Elfakharany ◽  
◽  
...  
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Agile Software Development ◽  
Continuous Growth ◽  
Requirements Prioritization ◽  
Prioritization Process ◽  
Development Life Cycle ◽  
Supporting Tool ◽  
Growth Change ◽  
Agile Software

Requirements engineering is a crucial phase of software engineering, and requirements prioritization is an essential stage of requirements engineering particularly in agile software development. Requirements prioritization goals at eliciting which requirements of software need to be covered in a particular release. The key point is which requirement will be selected in the next iteration and which one will be delayed to other iterations for minimizing risk during development and meeting stakeholders’ needs. There are many existing techniques for requirement prioritization, but most of these techniques do not cover continuous growth, change of requirements, and requirements dependencies. The prioritization techniques need to be more continuous, scalable, implemented easily and integrated with software development life cycle. This paper introduces a supporting tool for a proposed framework to prioritize requirements in agile software development. This framework tries to find solutions for the challenges facing this prioritization process such as how to make this prioritization continuous and scalable and how to deal with rapidly requirement changes and its dependencies. The proposed framework is validated in a real case study using its supporting tool, and the results are promising

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.

scholarly journals A Systematic Study to Improve the Requirements Engineering Process in the Domain of Global Software Development

IEEE Access ◽  
2020 ◽  
Vol 8 ◽  
pp. 53374-53393 ◽  
Author(s):  
Muhammad Azeem Akbar ◽  
Ahmed Alsanad ◽  
Sajjad Mahmood ◽  
Abeer Abdulaziz Alsanad ◽  
Abdu Gumaei
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Systematic Study ◽  
Global Software Development ◽  
Engineering Process ◽  
Requirements Engineering Process

Nominalizations in Requirements Engineering Natural Language Models

2018 ◽  
pp. 5127-5135 ◽  
Author(s):  
Claudia S. Litvak ◽  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn
Keyword(s):  
Software Development ◽  
Natural Language ◽  
Requirements Engineering ◽  
Language Models ◽  
Application Domain ◽  
Engineering Process ◽  
Usual Practice ◽  
Precise Meaning ◽  
Requirements Engineering Process ◽  
Nominal Form

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.

Teaching Agile Software Development Quality Assurance

2009 ◽  
pp. 2700-2713
Author(s):  
Orit Hazzan ◽  
Yael Dubinsky
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Specific Teaching ◽  
Quality Issues ◽  
Agile Software ◽  
Software Development Environments ◽  
The Way

This chapter presents a teaching framework for agile quality—that is, the way quality issues are perceived in agile software development environments. The teaching framework consists of nine principles, the actual implementation of which is varied and should be adjusted for different specific teaching environments. This chapter outlines the principles and addresses their contribution to learners’ understanding of agile quality. In addition, we highlight some of the differences between agile software development and plan-driven software development in general, and with respect to software quality in particular. This chapter provides a framework to be used by software engineering instructors who wish to base students learning on students’ experiences of the different aspects involved in software development environments.

Sign in / Sign up

Export Citation Format

Share Document