Development of the ibm.com Interactive Solution Marketplace (ISM): A systems engineering case study

Systems Engineering

Volumn 8, Issue 1, 2005, Pages 78-92

  Hole, Eirik ^a   Verma, Dinesh ^a,c   Jain, Rashmi ^a   Vitale, Vito ^b   Popick, Paul ^b  

^a STEVENS INSTITUTE OF TECHNOLOGY   (United States)

^b IBM   (United States)

^c Department of Outreach and Executive Education ^*  (United States)

Author keywords

Case study; Requirements management; Systems engineering management; Technical reviews

Indexed keywords

INTERACTIVE SOLUTION MARKETPLACE (ISM); STAKEHOLDERS; SYSTEM ENGINEERING AND ARCHITECTURE;

COMPUTER SOFTWARE; HARDWARE; PROJECT MANAGEMENT; SCHEDULING; WEBSITES;

SYSTEMS ENGINEERING;

EID: 24944521607     PISSN: 10981241     EISSN: 15206858     Source Type: Journal    
DOI: 10.1002/sys.20022     Document Type: Article

References (24)

1. I.F. Alexander, Being clear: Requirements are EITHER needs OR specifications, Requirements Quart, Requirements Eng Specialist Group Br Comput Soc 25 (January 2002), 10-12.
2. I.F. Alexander and R. Stevens, Writing better requirements, Addison-Wesley, London, 2002.
3. B.G. Barker and D. Verma, System engineering effectiveness: A complexity point paradigm for software intensive systems in the information technology sector, Eng Management J 15(3) (2003), 29-38.
4. B.S. Blanchard and W.J. Fabrycky, Systems engineering and analysis, 3rd edition, Prentice Hall, Englewood Cliffs, NJ, 1998.
5. B. Boehm, Software engineering economics, Prentice Hall, Englewood Cliffs, NJ, 1981.
6. B. Boehm, W. Brown, L. Huang, and D.N. Port, Schedule as independent variable process for acquisition of software-intensive systems, INCOSE 2004, 14th Int Symp Proc, Toulouse, 2004.
7. K.B. Clark and T. Fujimoto, Product development performance strategy, organization and management in the world auto industries, Harvard Business School, Boston, MA, 1991.
8. Capability Maturity Model® Integration (CMMISM), Version 1.1, CMMI-SE/SW/IPPD, V1.1 Staged Representation, Software Engineering Institute, Pittsburgh, 2001, http://www.sei.cmu.edu/cmmi/.
9. E. Fricke, B. Gebhard, H. Negele, and E. Igenbergs, Coping with changes: Causes, findings and strategies, Syst Eng 3(4) (2000), 169-179.
10. G. Friedman and A.P. Sage, Case studies of systems engineering and management in systems acquisition, Syst Eng 7(1) (2004), 84-97.
11. A.M. Graziano and M.L. Raulin, Research methods - a process of inquiry, 5th edition, Allyn & Bacon, Boston, MA, 2002.
12. I.F. Hooks and F.A. Farry, Customer-centered products, AMACOM, New York, 2001.
13. IBM (IBM Internal), ISM 2.0 Project Proposal, IBM Global Services (internal document), Bethesda, MD, 2002.
14. INCOSE, Systems engineering handbook, INCOSE-TP-2003-016-02, Version 2a, Seattle, Washington, June 2004.
15. A. Kossiakoff and W.N. Sweet, Systems engineering principles and practice, Wiley, New York, 2002.
16. R. MacLachian, Regeneration X, People Management 4(7) (1998), 34-40.
17. M.S. MacNealy, Towards better case study research, IEEE Trans Professional Commun 40(3) (1997), 182-196.
18. A. Odlyzko, Current state and likely evolution of the Internet, Global Telecommun Conf (GLOBECOM), 1999, Vol. 3, pp. 1869-1876.
19. L.G. Roberts, Beyond Moore's law: Internet growth trends, Computer 33(1) (2000), 117-119.
20. A.P. Sage, Systems management for information technology and software engineering, Wiley, New York, 1995.
21. A.P. Sage and A.E. Armstrong, Jr., Introduction to systems engineering, Wiley, New York, 2000.
22. Standish Group, CHAOS reports, http://www.standishgroup. com/sample_research/index.php, 1994, 1999, 2001.
23. J. Teresko, Driving success at New Blue, Industry Week 248(2) (December 1999), 56-67.
24. D. Verma and W.J. Fabrycky, Systematically identifying system engineering practices and methods, IEEE Trans Aerospace Electron Syst 33(2) (1997), 587-595.