This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Broad, Quantitative Model for Making Early Requirements Decisions
March/April 2008 (vol. 25 no. 2)
pp. 49-56
Martin S. Feather, Jet Propulsion Laboratory
Steven L. Cornford, Jet Propulsion Laboratory
Kenneth A. Hicks, Jet Propulsion Laboratory
James D. Kiper, Miami University
Tim Menzies, West Virginia University
During the early phases of project life cycles, detailed information is scarce, yet developers frequently need to make key decisions, especially concerning trade-offs among quality requirements. Such trading among competing concerns occurs in many fields, including systems, hardware, and software engineering. The defect detection and prevention model aids in requirements decision making in all such fields. The DDP model uses coarse quantification of relevant factors. Examples from studies of software technology requirements analyses illustrate this approach.

1. S.L. Cornford, "Managing Risk as a Resource Using the Defect Detection and Prevention Process," Proc. 4th Int'l Conf. Probabilistic Safety Assessment and Management, Springer, 1998, pp. 1609–1614.
2. M.S. Feather et al., "Applications of Tool Support for Risk-Informed Requirements Reasoning," Computer Systems Science and Eng., vol. 20, no. 1, Jan. 2005, pp. 5–17.
3. D.M. Tralli, "Programmatic Risk Balancing," Proc. IEEE Aerospace Conf., IEEE Press, 2003, pp. 2775–2784.
4. M.S. Feather and S.L. Cornford, "Quantitative Risk-Based Requirements Reasoning," Requirements Eng., vol. 8, no. 4, 2003, pp. 248–263.
5. P. Zave and M. Jackson, "Four Dark Corners of Requirements Engineering," ACM Trans. Software Eng. and Methodology, vol. 6, no. 1, 1997, pp. 1–30.
6. W. Swartout and R. Balzer, "On the Inevitable Intertwining of Specification and Implementation," Comm. ACM, vol. 25, no. 7, 1982, pp. 438–440.
7. J. Karlsson and K. Ryan, "A Cost-Value Approach for Prioritizing Requirements," IEEE Software, vol. 14, no. 5, 1997, pp. 67–74.
8. A. Van Lamsweerde and E. Letier, "Integrating Obstacles in Goal-Driven Requirements Engineering," Proc. 20th Int'l Conf. Software Eng (ICSE), IEEE CS Press, 1998, pp. 53–62.
9. E.M. Knorr and R.T. Ng, "Finding Intensional Knowledge of Distance-Based Outliers," Proc. 25th Very Large Database Conf., ACM Press, 1999, pp. 211–222.
10. M.S. Feather, J. Kiper, and S. Kalafat, "Combining Heuristic Search, Visualization, and Data Mining for Exploration of System Design Spaces," Proc. 14th Int'l Symp., Int'l Council on Systems Eng. (INCOSE), CD-ROM, Int'l Council on Systems Eng., 2004.
11. T. Menzies and H. Singh, "Many Maybes Mean Mostly the Same Thing," Soft Computing in Software Eng., E. Damiani, L.C. Jain, and M. Madravio, eds., Springer, 2003, pp. 125–150.
12. M.S. Feather and T. Menzies, "Converging on the Optimal Attainment of Requirements," Proc. IEEE Int'l Conf. Requirements Eng, IEEE CS Press, 2002, pp. 263–270.
13. R. Balling, "Design by Shopping: A New Paradigm," Proc. 3rd World Congress of Structural and Multidisciplinary Optimization (WCMSO-3), Optimization Soc., 1999, pp. 295–297.
14. Y. Akao, Quality Function Deployment, Productivity Press, 1990.

Index Terms:
decision support, requirements analysis, requirements elicitation, management, cost estimation, risk management, information visualization, optimization, data mining
Citation:
Martin S. Feather, Steven L. Cornford, Kenneth A. Hicks, James D. Kiper, Tim Menzies, "A Broad, Quantitative Model for Making Early Requirements Decisions," IEEE Software, vol. 25, no. 2, pp. 49-56, March-April 2008, doi:10.1109/MS.2008.29
Usage of this product signifies your acceptance of the Terms of Use.