Implementing risk management on software intensive projects

IEEE Software

Volumn 14, Issue 3, 1997, Pages 83-89

  Conrow, Edmund H ^b,c,d,e,f   Shishido, Patricia S ^a,g,h  

^a NORTHROP GRUMMAN CORPORATION   (United States)

^b Acq and Technology Associates

^c UNIVERSITY OF ARIZONA   (United States)

^d OKLAHOMA STATE UNIVERSITY   (United States)

^e RAND CORPORATION   (United States)

^f IEEE   (United States)

^g UNIVERSITY OF REDLANDS   (United States)

^h KANSAI UNIVERSITY   (Japan)

Author keywords

[No Author keywords available]

Indexed keywords

RISK MANAGEMENT; TRW ADA PROCESS MODEL;

ADA (PROGRAMMING LANGUAGE); COMMAND AND CONTROL SYSTEMS; COMPUTER AIDED DESIGN; COMPUTER ARCHITECTURE; DATA PROCESSING; PROJECT MANAGEMENT; REAL TIME SYSTEMS; STORAGE ALLOCATION (COMPUTER); USER INTERFACES;

SOFTWARE ENGINEERING;

EID: 0031145733     PISSN: 07407459     EISSN: None     Source Type: Journal    
DOI: 10.1109/52.589242     Document Type: Article

References (18)

1. The Standish Group International, Charting the Seas of Information Technology, Dennis, Mass., 1994.
2. L.K. Mosemann, Guidelines for Successful Acquisition and Management of Software Intensive Systems, Dept. of Defense, Version 1.1 - Vol. 1, Feb. 1995.
3. E.H. Conrow, "The Use of Ordinal Scales in Defense Systems Engineering," Proc. 1995 Acquisition Research Symp., Defense Systems Mgt. College, 1995, pp. 455-463.
4. Air Force Systems Command, "Software Risk Management," AFSC Pamphlet 800-45, Sept. 1988.
5. B.W. Boehm, "A Spiral Model of Software Development and Enhancement," Computer, May 1988, pp. 61-72.
6. R.N. Charette, Software Engineering Risk Analysis and Management, McGraw-Hill, New York, 1989.
7. M. Evans, "Thread of Failure: Project Trends That Impact Success and Productivity," NetFocus, No. 203, Software Program Managers Network, Naval Information System Management Center, Mar. 1994.
8. C. Jones, "Assessment and Control of Software Risks," Proc. 2nd Software Eng. Inst. Conf. Software Risks, SEI, Carnegie Mellon Univ., Pittsburgh, 1993.
9. C. Jones, "Risks of Software System Failure or Disaster," American Programmer, Mar. 1995, pp. 2-9.
10. F.J. Sisti and S. Joseph, "Software Risk Evaluation Method," Tech. Report CMU/SEI-94-TR-19, SEI, Carnegie Mellon Univ., Pittsburgh, 1994.
11. E.H. Conrow, "Some Long-Term Issues and Impediments Affecting Military Systems Acquisition Reform," Acquisition Review Quarterly, Summer 1995, pp. 199-212.
12. Dept. of Defense, "Defense Acquisition," DoD Directive 5000.1, Mar. 1996.
13. Dept. of Defense, "Software Development and Documentation," MIL-Standard-498, Dec. 1994.
14. E.H. Conrow and M.A. Fredrickson, "Some Considerations for Implementing Risk Management in Defense Programs," Program Manager, Defense Systems Mgt. College, Jan.-Feb. 1996, pp. 6-11.
15. Dept. of Defense, Defense Acquisition Deskbook, Version 1.3, Dec. 31, 1996.
16. B.W. Boehm, Software Risk Management, IEEE Comp. Soc. Press, Los Alamitos, Calif., 1989.
17. W. Royce, "TRW's Ada Process Model for Incremental Development of Large Software Systems," Proc. ICSE 12, Mar. 1990, pp. 2-11.
18. D.L. Parnas, "Designing Software for Ease of Extension and Contraction," IEEE Trans. Software Eng., Mar. 1979, pp. 128-137.