scispace - formally typeset
Journal ArticleDOI

Story card Maturity Model (SMM): A Process Improvement Framework for Agile Requirements Engineering Practices

Chetankumar Patel, +1 more
- 07 Jan 2009 - 
- Vol. 4, Iss: 5, pp 422-435
Reads0
Chats0
TLDR
This paper 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.
Abstract
This paper 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 nonfunctional 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. We 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.

read more

Content maybe subject to copyright    Report

Citations
More filters

Software engineering economics

Barry Boehm
TL;DR: In this article, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
Journal ArticleDOI

Improving agile requirements: the Quality User Story framework and tool

TL;DR: The Quality User Story (QUS) framework is proposed, a set of 13 quality criteria that user story writers should strive to conform to and a software tool, based on QUS, is presented, which relies on natural language processing techniques and suggests possible remedies.
Journal ArticleDOI

Using CMMI together with agile software development: A systematic review

TL;DR: Agile methodologies can be used by companies to reduce efforts in getting to levels 2 and 3 of CMMI, however, agile methodologies alone, according to the studies, were not sufficient to obtain a rating at a given level.
Journal ArticleDOI

Enterprise maturity models: a systematic literature review

TL;DR: This study investigates the literature that presents assessment models for classifying maturity levels as well as the development of the research area to update the state of the art on MM and identify gaps that may prompt future research.
Journal ArticleDOI

A systematic literature review on quality criteria for agile requirements specifications

TL;DR: A systematic literature review is conducted to investigate what quality criteria for assessing the correctness of written agile requirements exist and categorize and analyze these criteria and compare them with those from traditional requirements engineering.
References
More filters
Book

Extreme Programming Explained: Embrace Change

Kent Beck
TL;DR: You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.

Software engineering economics

Barry Boehm
TL;DR: In this paper, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
Book

Agile Software Development with SCRUM

Ken Schwaber, +1 more
TL;DR: This book describes building systems using the deceptively simple process, Scrum, a new approach to systems development projects that cuts through the ocmplexity and ambiguity of complex, emergent requiremetns and unstable technology to iteratively and quickly produce quality software.
Book

Requirements Engineering: Processes and Techniques

TL;DR: Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones and are all based on real systems descriptions to demonstrate the applicability of the approach.