Software acquisition management involves a wide variety of topics ranging from general management theory to special is-sues regarding software testing, contract types, risk manage-ment, etc. It isn’t possible for a single document to cover any of these topics completely. Therefore, the reader probably needs to study texts that cover these topics in depth to gain a better un-derstanding on how to carry out a successful software
acquisi-7 Results and summary
© Daniel Svennberg 2001 123
However, the following are some suggestions for future re-search on software acquisition management that could be based upon this thesis:
• It could be further investigated how to customize and adapt the different processes and artifacts. Perhaps two customization levels are sufficient?
• Are there more customization factors? Which factors are important for which process?
• Similar guidelines for the acquisition of COTS software could be made.
• Can an expert system or other tools be made for assisting software acquisition management?
• How can the guidelines be adapted to match common software development methodologies?
8 Bibliography
Assmann, Danilo (2000), MASS – a Method for Assessing Soft-ware Subcontractors, Kaiserslautern, Fraunhofer IESE
Beck, Kent (1999), Embracing Change with eXtreme Programming, Computer, Vol. 32, No. 10, Oct 1999, pp.70-77,
IEEE 0018-9126/99
Breu, Michael (1995), A Concise Guide to Euromethod, European Software Institute, ESI-1995-CG004.01
Brooks, Frederick P., Jr (1995), The Mythical Man-Month: essays on software engineering, Anniversary ed., Reading, Addi-son-Wesley, ISBN 0-201-83595-9
Brown, Norm et al. (1998), The Program Manager’s Guide to ware Acquisition Best Practices version 2.2, Arlington, Soft-ware Program Managers Network
Brown, Norm et al. (1999), The Guidebook of Software Acquisition Questions version 1.0, Arlington, Software Program Manag-ers Network
Carr, Marvin J. et al. (1993), Taxonomy-Based Risk Identification, Pittsburgh, Software Engineering Institute, CMU/SEI-93-TR-6
Christel, Michael G. and Kang, Kyo C. (1992), Issues in Re-quirements Elicitation, Pittsburgh, Software Engineering
In-8 Bibliography
© Daniel Svennberg 2001 125
CMMI (2000), Capability Maturity Model Integration,
http://www.sei.cmu.edu/cmmi/ (15 September 2000) Cockburn, Alistair (n.d.), Balancing Lightness with Sufficiency,
http://members.aol.com/acockburn/papers/barelysuffici ent.htm (2 August 2000)
DAD (2000), Defense Acquisition Deskbook,
http://web2.deskbook.osd.mil/default.asp (1 September, 2000)
D.I.R. (2000), Tailoring the Guidelines,
http://www.dir.texas.gov/eod/qa/tailor.htm (1 August 2000)
Duncan, William R. (1996), A Guide to the Project Management Body of Knowledge, Newtown Square, Project Management Institute, ISBN 1-880410-12-5
Euromethod (1996), Euromethod version 1, Euromethod Project FAA-iCMM (1997), The Federal Aviation Administration
Inte-grated Capability Maturity Model (FAA-iCMM) Version 1.0, U.S. Federal Aviation Administration
Fleming, Quentin W. and Koppelman, Joel M. (1996), Earned value project management, Newtown Square, Project Man-agement Institute, ISBN 1-880410-38-9
Gallivan, Michael J. (1999), Analyzing IT Outsourcing Relation-ships as Alliances among Multiple Clients and Vendors, Pro-ceedings of the 32nd Hawaii International Conference on System Sciences
Ganssle, Jack G. (1998), The Seven Habits of Highly Defective Pro-grammers, Embedded Systems Programming – July 1998
Haimes, Yacov Y. et al. (1997), A Holistic Management Framework for Software Acquisition, Acquisition Review Quarterly – Winter 1997, Defense Systems Management College, pp.
55-86
IEEE 982.1 (1988), IEEE Standard Dictionary of Measures to Pro-duce Reliable Software, New York, The Institute of Electrical and Electronics Engineers, Inc.
IEEE 1062 (1998), IEEE Recommended Practice for Software Acqui-sition, New York, The Institute of Electrical and Electronics Engineers, Inc., ISBN 0-7381-1514-2
IEEE/EIA 12207.0 (1996), Standard for information technology – Software life cycle processes, New York, The Institute of Elec-trical and Electronics Engineers, Inc., ISBN 1-55037-077-4 ISO/IEC 9126 (1991), Information technology – Software product
evaluation – Quality characteristics and guidelines for their use, ISO/IEC
ISO/IEC 15504 (1998), Information technology – Software process assessment, ISO/IEC
Kar, Pradip and Bailey, Michelle (1996), Characteristics of Good Requirements, 1996 INCOSE Symposium
Kerth, Norman L. (n.d.), An Approach to Post Morta, Post Parta, and Post Project Reviews, Beaverton, Elite Systems
Marciniak, John J. and Reifer, Donald J. (1990), Software Acqui-sition Management, New York, John Wiley & Sons, Inc., ISBN 0-471-50643-5
Mosemann, II, Lloyd K. (1996), Guidelines for Successful Acquisi-tion and Management of Software-Intensive Systems, U.S. De-partment of the Air Force, Software Technology Support Center
8 Bibliography
© Daniel Svennberg 2001 127
Oskarsson, Östen (2000), interviewed by author at Östen Oskarsson’s home, Linköping, 21 April 2000
Oskarsson, Östen (n.d. a), Tutorial – Acquisition and Supply of Software Development,
http://www.oskarsson.se/useful_info/acqtutorial.html (4 April 2000)
Oskarsson, Östen (n.d. b), Example of Software Contract Require-ments,
http://www.oskarsson.se/useful_info/Contract.html (3 May 2000)
Oskarsson, Östen and Glass, Robert L. (1996), An ISO 9000 Approach to Building Quality Software, Upper Saddle River, Prentice-Hall, Inc., ISBN 0-13-228925-3
Paulk, Mark C. et al. (1993), Capability Maturity Model for Soft-ware, Version 1.1, Pittsburgh, Software Engineering Insti-tute, CMU/SEI-93-TR-24
Ran, Mats (2000), interviewed by author at Q-Labs AB, Linköping, 3 May 2000
Reeves, Jack W. (1992), What is Software Design?, C++ Journal Vol. 2, Nr. 2 1992
Reifer, Donald J. (1997), Software management, New York, The Institute of Electrical and Electronics Engineers, Inc., ISBN 0-8186-8001-6
Salwin, Arthur E. (1998), The Road to Successful ITS Software Ac-quisition, Washington, U.S. Department of Transportation, Report No. FHWA-JPO-98-035
SS-ISO 9000-3 (1992), Kvalitetssystemstandarder – Del 3: Riktlinjer för tillämpning av SS-9001 vid utveckling, leverans och under-håll av programvara, SIS – Standardiseringskommissionen i Sverige
The Standish Group (1995), The Standish Group Report Chaos, http://www.scs.carleton.ca/~beau/PM/Standish-Report.html (28 August 2000)
Urmi, Jaak (2000), interviewed by author at Ericsson AB, Kista, 14 April 2000
Wideman, R. Max (1992), Project and program risk management: a guide to managing project risks and opportunities, Project Management Institute, ISBN 1-880410-06-0
Wilson, Peter B. (2000), Sizing Software with Testable Require-ments, Systems Development Management, Auerbach Pub-lications
129
A Frameworks coverage
This chapter shows that the processes in the guidelines covers most issues in the main frameworks that have comparable processes or sections.