Welcome to the InfoSci Platform
Best Practices Guidelines for Agile Requirements Engineering Practices

Best Practices Guidelines for Agile Requirements Engineering Practices

Chetankumar Patel, Muthu Ramachandran
Copyright: © 2012 |Pages: 14
ISBN13: 9781613504567|ISBN10: 161350456X|EISBN13: 9781613504574
DOI: 10.4018/978-1-61350-456-7.ch602
Cite Chapter Cite Chapter

MLA

Patel, Chetankumar, and Muthu Ramachandran. "Best Practices Guidelines for Agile Requirements Engineering Practices." Computer Engineering: Concepts, Methodologies, Tools and Applications, edited by Information Resources Management Association, IGI Global, 2012, pp. 1403-1416. https://doi.org/10.4018/978-1-61350-456-7.ch602

APA

Patel, C. & Ramachandran, M. (2012). Best Practices Guidelines for Agile Requirements Engineering Practices. In I. Management Association (Ed.), Computer Engineering: Concepts, Methodologies, Tools and Applications (pp. 1403-1416). IGI Global. https://doi.org/10.4018/978-1-61350-456-7.ch602

Chicago

Patel, Chetankumar, and Muthu Ramachandran. "Best Practices Guidelines for Agile Requirements Engineering Practices." In Computer Engineering: Concepts, Methodologies, Tools and Applications, edited by Information Resources Management Association, 1403-1416. Hershey, PA: IGI Global, 2012. https://doi.org/10.4018/978-1-61350-456-7.ch602

Export Reference

Mendeley
Favorite

Abstract

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.