21 st century processes for acquiring 21 st century software-intensive systems of systems

CrossTalk

Volumn 19, Issue 5, 2006, Pages 4-9

  Boehm, Barry ^a,b,c   Lane, Jo Ann ^a,c  

^a UNIVERSITY OF SOUTHERN CALIFORNIA   (United States)

^b Department of Software Engineering ^*  (United States)

^c University of Southern California   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPLEX INTERACTIONS; EXTERNAL SYSTEMS; RISK-DRIVEN SPIRAL MODELS; SOFTWARE-INTENSIVE SYSTEMS OF SYSTEMS (SISOS);

LEGACY SYSTEMS; MATHEMATICAL MODELS; RISK ASSESSMENT; SOFTWARE ENGINEERING; TELECOMMUNICATION TRAFFIC;

COMPUTER SOFTWARE;

EID: 33745190286     PISSN: None     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (24)

1. International Organization for Standardization. Information Technology Software Life Cycle Processes. ISO/IEC 12207: 1995. Geneva, Switzerland: ISO, 1995.
2. International Organization for Standardization. Systems Engineering System Life Cycle Processes. ISO/ IEC 15288: 2002. Geneva, Switzerland: ISO, 2002.
3. Zachman, J. "A Framework for Information Systems Architecture." IBM Systems Journal 26.3 (1987): 276-292.
4. Putman, J. Architecting With RM-ODP. Prentice Hall, 2001.
5. Federal Chief Information Officer Council. A Practical Guide to Federal Enterprise Architecture Vers. 1.0. Washington, D.C.: FCIO, Feb. 2001.
6. Harned, D., and J. Lundquist. "What Transformation Means for the Defense Industry." The McKinsey Quarterly 3 Nov. 2003: 57-63.
7. Lane, J., and R. Valerdi. "Synthesizing System-of-Systems Concepts for Use in Cost Estimation." IEEE SMC, 2005.
8. Boehm, B., A.W. Brown, V. Basili, and R. Turner. "Spiral Acquisition of Software-Intensive Systems of Systems." CROSSTALK May 2004: 4-9 〈www.stsc.hill.af.mil/crosstalk/2004/05/0405boehm.html〉.
9. U.S. Air Force-Scientific Advisory Board. Information Architectures Study. Washington, D.C.: U.S. Air Force, 1994.
10. Boehm, B. "Some Future Trends and Implications for Systems and Software Engineering Processes." USC-CSE-TR-2005-507. Los Angeles, CA: University of Southern California, 2005.
11. Royce, WE. Software Project Management. Addison-Wesley, 1998.
12. Ehn, Pelle. Work-Oriented Design of Computer Artifacts. Lawrence Earlbaum Assoc., 1990.
13. Checkland, P. Systems Thinking, Systems Practice. 2nd ed. Wiley, 1999.
14. Womack, J., and D. Jones. Lean Thinking: Banish Waste and Create Wealth in Your Corporation. Simon & Schuster, 1996.
15. Deck, M., M. Strom, and K. Schwartz. "The Emerging Model of Co-Development." Research Technology Management Dec. 2001.
16. Rational, Inc. Driving Better Business With Better Software Economics. Rational Software Corp., 2001.
17. Elssamadisy, A., and G. Schalliol. Recognizing and Responding to 'Bad Smells' in Extreme Programming. Proc. of the 24th International Conference on Software Engineering, Orlando, FL, May 2002: 617-622.
18. Collins, J. Good to Great. Harper Collins, 2001.
19. Rubey, J.R., J.A. Dana, and P.W Biché. "Quantitative Aspects of Software Validation." IEEE Transactions on Software Engineering June 1975: 150-155.
20. Cusumano, M., and R. Selby. Microsoft Secrets. Harper Collins, 1996.
21. Beck, K. Extreme Programming Explained. Addison-Wesley, 1999.
22. Christensen, C. The Innovator's Dilemma (Harper Business Essentials). Harper Collins, 2000.
23. Chesbrough, H. Open Innovation: The New Imperative for Creating and Profiting from Technology. Harvard Business School Press, 2003.
24. Boehm, B., A. Egyed, J. Kwan, D. Port, A. Shah, and R. Madachy. "Using the WinWin Spiral Model: A Case Study." IEEE Computer July 1998: 33-44.