Advances in software inspections
IEEE Transactions on Software Engineering
Experience with evolutionary prototyping in a large software project
ACM SIGSOFT Software Engineering Notes
Managing the development of large software systems: concepts and techniques
ICSE '87 Proceedings of the 9th international conference on Software Engineering
N-Fold inspection: a requirements analysis technique
Communications of the ACM
A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
Measuring software reliability
IEEE Spectrum
Design and code inspections to reduce errors in program development
IBM Systems Journal
Operational Prototyping: A New Development Approach
IEEE Software
| Hi-index | 0.00 |
Defects are introduced into a software product during every phase of software development. A major source of defects that is often overlooked is requirements generation. Requirement errors discovered in later phases of the software development process are the most costly to correct because all phases of software development are usually impacted. Requirement defects can be categorized into two main types: 1) specification generation errors; and 2) unwanted/unnecessary/incorrect user functionality. This experience report presents the results of incorporating a two‐step methodology which combines Operational Demonstrations of the user interface and Requirement Inspections on software requirement specifications. The two‐step methodology addresses and corrects both types of requirement defects. Results from this experience support the premise that cost reduction and quality improvement can be obtained using a combined Operational Demonstration and Requirement Inspection development methodology for software requirements.