Abstract | ||
---|---|---|
Abstract: Evolutionary prototyping focuses on gathering a correct and consistent set of requirements. The process lends particular strength to building quality software by means of the ongoing clarification of existing requirements and the discovery of previously missing or unknown requirements. Traditionally, the iterative reexamination of a system 's requirements has not been the panacea that practitioners sought, due to the predisposition for requirements creep and the difficulty i n managing it. This paper proposes the combination of evolutionary prototyping and an aggressive risk- mitigation strategy. Together, these techniques support successful requirements discovery and clarification, and they guard against the negative effects of requirements creep. We embody these techniques in a comprehensive software development model, which we call the EPRAM (Evolutionary Prototyping with Risk Analysis and Mitigation) model. The model was intentionally designed to comply with the Level 2 Key Process Area of the Software Engineering Institute 's Capability Maturity Model. Validation is currently underway on several software development efforts that employ the model to support the rapid development of electronic commerce applications. |
Year | DOI | Venue |
---|---|---|
2001 | 10.1109/ISRE.2001.948548 | RE |
Keywords | Field | DocType |
capability maturity model,evolutionary prototyping,key process area,comprehensive software development model,successful requirements discovery,ongoing clarification,rapid development,evolving beyond requirements creep,requirements creep,software development effort,risk-based evolutionary prototyping model,building quality software,risk mitigation,risk management,programming,risk analysis,software development,application software,software quality,creep,electronic commerce,prototypes,system requirements,software engineering | Systems engineering,Computer science,Requirements engineering,Requirements analysis,Software prototyping,Requirements management,Requirement,Business requirements,Requirement prioritization,Software requirements specification | Conference |
Citations | PageRank | References |
15 | 1.13 | 12 |
Authors | ||
4 |
Name | Order | Citations | PageRank |
---|---|---|---|
Ryan A. Carter | 1 | 82 | 7.48 |
Annie I. Antón | 2 | 1557 | 142.50 |
Laurie Williams | 3 | 4033 | 473.64 |
Aldo Dagnino | 4 | 194 | 21.07 |