Requirements reviews revisited: Residual challenges and open research questions
Author:
- 1 July 2013
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 1090705X,p. 250-255
Abstract
It is widely accepted that early reviews on requirements specifications (RS) are an effective and efficient quality assurance technique. So why are they still not applied all over the software industry? In this paper we pinpoint that this is due to five major challenges: 1) Software requirements are based on flawed `upstream' requirements and reviews on RS are thus in vain. 2) The impact of sociological issues related to reviews is underestimated. 3) Important quality aspects of RS escape reviews. 4) The goal of applying reviews is not made clear and different review approaches are mixed. 5) Incremental software development poses specific challenges to applying reviews on RS. In this paper we argue that in order to solve these five challenges research on reviews must take a more holistic approach, stretching to pre-project phases and incorporating various other disciplines in order to add more value for the software industry. The paper also offers preliminary solutions to the discussed challenges and sketches open research questions of high relevance for the software industry.Keywords
This publication has 14 references indexed in Scilit:
- Assessments in global software development2010
- Inspection effectiveness for different quality attributes of software requirement specifications: An industrial case study2009
- Requirements in the 21st Century: Current Practice and Emerging Trends2009
- Risk Themes Discovered through Architecture Evaluations2007
- Understanding the product life cycle: four key requirements engineering techniquesIEEE Software, 2006
- Keynote: Just Enough Requirements Management for Web EngineeringLecture Notes in Computer Science, 2005
- How perspective-based reading can improve requirements inspectionsComputer, 2000
- Practical programmer: inspections—some surprising findingsCommunications of the ACM, 1999
- Persistent Software ErrorsIEEE Transactions on Software Engineering, 1981
- Design and code inspections to reduce errors in program developmentIBM Systems Journal, 1976