This January 2012 webinar discusses SEI efforts to improve acquisition program staff decision making in order to reduce program cost, schedule, and quality failures.
12/30/2011The information in this report is intended to help program managers reason about actions they may need to take to adapt and comply with the Section 804 NDAA for 2010 and associated guidance.
10/31/2011This technical note addresses some of the key issues that either must be understood to ease the adoption of Agile or are seen as potential barriers to adoption of Agile in the DoD acquisition context.
10/05/2011This technical note focuses on software acquisition and development practices related to the evaluation of products before, during, and after implementation. From engagements with numerous DoD acquisition programs, it has been observed that a number of recurring issues reduce the effectiveness of how software-reliant products are evaluated. An acquisition effort consists of identifying the customer’s needs, selecting or developing a product that is responsive to those needs, and then evaluating the product to determine if it properly addresses the identified needs. This technical note describes the Product Evaluation (verification, validation, and certification) process including test, reviews, and formal methods. It also makes the argument that Product Evaluation should not be deferred until after a product has been built, but should begin as soon as the customer’s needs have been identified and should continue throughout the acquisition effort
07/20/2011This report describes standard noncommercial software licensing alternatives as defined by U.S. government and Department of Defense (DoD) regulations. It also suggests an approach for objectively identifying agency needs for license rights and the appropriate license type for systems with noncommercial computer software or as standalone software in the DoD environment.
02/28/2011This report explores the interdependencies among common language, business goals, and soft-ware architecture as the basis for a common framework for conducting evaluations of software technical solutions.
12/17/2010This report synthesizes presentations, discussions, and outcomes from the "Beyond Technology Readiness Levels for Software" workshop from August 2010.
11/11/2010This report explores the value of enhancing typical strategic planning techniques with the CSF method and scenario planning.
09/30/2010This report describes key elements in systems thinking, provides an introduction to general systems archetypes, and applies these concepts to the software acquisition domain.
09/30/2010This report documents ideas and recommendations for improving the overall acquisition process and presents the actions taken by project managers in several programs to develop, staff, and obtain approval for their systems.
09/30/2010This report provides suggestions for documenting service-oriented architecture-based systems based on the Views & Beyond (V&B) software documentation approach.
08/18/2010This report details a framework that documents best practices for risk management and an approach for evaluating a program’s risk management practice in relation to this framework.
06/17/2010This 2010 report explores the questions: Can Agile be used in the DoD environment? If so, how?
06/07/2010This report examines how data rights issues were addressed in the TSAT program, reviews additional concerns posed by the use of commercial software in the TSAT program’s Space Segment, and reviews data rights concerns for software incorporated in the GPS program.
05/25/2010In this 2010 paper, Grady Campbell - delivered at the 7th Acquisition Research Symposium - argues that a new approach to acquisition is needed that recognizes that hiding uncertainty is detrimental to success.
05/25/2010presentation given at the 7th Annual Acquisition Research SymposiumNaval Postgraduate School, Monterey, CA, May 2010
05/04/2010one hour overview presented as a DoD and NDIA System-of-Systems Engineering Collaborator’s Information Exchange (SoSECIE) Webinar on May 18, 2010
05/04/2010Keynote presentation by Donald Firesmith at SESS’10, as part of the 32nd ACM/IEEE International Conference on Software Engineering (ISCE’2010) in Cape Town, South Africa.
05/04/2010presentation given at the 22nd Annual Systems and Software Technology Conference (SSTC 2010) in Salt Lake City, Utah on April 26-29, 2010.
05/04/2010presentation given at the 32nd International Conference on Software Engineering 4 May 2010
04/30/2010presentation given by William Novak and Ray Williams at the 2010 Systems and Software Technology Conference (SSTC) on April 29, 2010
04/30/2010In this 2010 presentation, Michael Bandor and Suzanne Garcia-Miller focus on software issues and shortfalls observed during the DoD Technology Readiness Assessment (TRA) processes.
04/30/2010Bryce Meyer and James Wessel provide a 10-step method for planning/assessing software performance, allowing for respective improvement of architecture and test processes.
04/30/2010James Wessel focuses on software measurement practices that Army acquisition organizations find useful for software issue identification, tracking, and active control of programs.
04/30/2010Terry Roberts addresses why R&D in cyber and software engineering is different, how to research the federal lab landscape for opportunities, and how focus our R&D initiatives.
04/06/2010presentation made by Patricia Oberndorf Thomas Merendino, & Soumya Simanta at the at the Systems and Software Technology Conference, Salt Lake City, UT, April 26, 2010
04/06/2010presentation made by Patricia Oberndorf & Carol Sledge at the Systems and Software Technology Conference, Salt Lake City, UT, April 27, 2010
04/06/2010This presentation was given by Patricia Oberndorf and Carol A. Sledge of the Software Engineering Institute (SEI) on April 6, 2010 at the IEEE Systems Conference in San Diego, CA.
01/18/2010When problems are detected in programs, everyone needs to listen and work together towards a solution. Shooting the messenger only delays the process, and hurts program morale.
12/31/2009Criteria and standards to certify an organization as a COE are presented in this Carnegie Mellon Software Engineering Institute preliminary report.
11/17/2009This report explores the lack of agreement among SCAMPI Lead Appraisers about what “artifact quality” means in the SCAMPI process context.
11/17/2009This report explores the lack of agreement among SCAMPI Lead Appraisers about what “process quality” means in the SCAMPI process context.
10/26/2009Presented at the NDIA Systems Engineering Conference 2009 by Audrey Dorofee and Christopher Alberts.
10/15/2009This April 2009 whitepaper focuses on the problems of underspending, which can result in funds being shifted from one acquisition program to another.
10/15/2009When time and budget are tight, it's tempting to follow the "happy path" in testing. But be careful: it may be a path that brings your program great unhappiness.
09/30/2009This 2009 report contains a series of observations and their associated lessons learned from a large, multi-segment, software-intensive system.
06/30/2009This paper explores how continued use of the acquisition roadmaps opens up the potential for running into program pitfalls (programmatic IEDs) that aren’t acknowledged on the map at hand.
06/01/2009This report summarizes the findings of a study conducted for the Army to find and describe software measurement practices that are being used successfully.
06/01/2009The 2009 report defines and communicates software engineering and management events necessary to support the successful acquisition of software-intensive systems.
04/24/2009A technical overview of systemic risk and opportunity management for distributed environments.
04/23/2009This April 2009 whitepaper is one in a short series of acquisition failures. This paper focuses on the problems of underspending, which can result in funds being shifted from one program to another.
04/23/2009Planning for a long development period doesn't always solve acquisition scheduling problems. Sometimes it makes them worse.
04/20/2009Donald Firesmith of the SEI presented a one-day tutorial in the Method Framework for Engineering Systems Architectures (MFESA) at the 2009 SSTC in April 2009.
03/24/2009This presentation was given by Joe Wickless of the Software Engineering Institute (SEI) in March 2010 at SEPG North America 2009, held in San Jose, CA.
03/23/2009Tutorial: The Method-Framework for Engineering System Architectures (MFESA). Delivered by Donald Firesmith at the IEEE International Systems Conference, March 23-26, 2009.
03/23/2009This March 2009 presentation, An Innovative Requirements Solution, was presented by Ira Monarch, Dennis Goldenson, and Robert W. Stoddard at SEPG North America 2009.
03/23/2009This brief tutorial of the Method Framework for Engineering System Architecture was delivered in March 2009 at the IEEE International Systems Conference by Donald Firesmith.
03/23/2009presented in San Jose, California, at the 21st Annual SEPG North America 2009 conference March 23-26, 2009
03/06/2009When projects attempt to please too many customers, complexity mounts, schedules slip, costs expand ... and no one is happy.
12/10/2008A tutorial on the Method Framework for Engineering System Architectures (MFESA) delivered at ICSSEA 2008 on December 10, 2008.
12/01/2008This survey quantifies the relationship between the application of Systems Engineering (SE) best practices to projects and programs, and the performance of those projects and programs.
11/15/2008Presentation by Kenneth Nidiffer, Director of Strategic Plans for Government Programs (SEI), from the 8th Annual CMMI Technology Conference and User Group, November 2008.
11/12/2008A presentation made by Rick Barbour and Barbara Tyson at the 8th Annual CMMI Technology and Users Conference in November 2008. The Last Phase of Process Change - Deployment
10/18/2008Kenneth Nidiffer delivered this presentation at the 11th Annual Systems Engineering Conference in October 2008.
10/10/2008Presented: October 2008
09/22/2008Applying more pressure on staff can temporarily increase productivity, but burnout soon sets in.
09/22/2008From the Acquisition Support Program, one in a series of short papers on acquisition patterns of failure. Acquisition Archetype: Underbidding the Contract
09/08/2008Renewing the Product Line Vision was presented by Brady Campbell (SEI) at the 12th International Software Product Line Conference in September 2008.
08/01/2008The purpose of this 2008 document is to preview a core set of activities and outputs that define a MAAP assessment.
06/11/2008In this podcast, Brian Gallagher, former director of the Acquisition Support Program at the SEI, discusses what business leaders need to know when acquiring or purchasing software, along with implications for security.
06/04/2008presentation from the Second Annual Systems Engineering Conference of the National Reconnaissance Office on June 4, 2008
04/08/2008This presentation was given by Linda Levine and Bill Novak of the SEI’s Acquisition Support Program at the IEEE Systems Conference in April 2008.
03/17/2008presented at SEPG 2008, March 17-20, 2008 Tampa, Florida
03/12/2008Presented by Don Firesmith on March 12, 2008
03/10/2008All hands on deck helps put out the immediate blazes threatening projects, but falling into a routine of constant firefighting is not the way to guide a project across the finish line.
03/04/2008Everyone intends the best in project-driven marriages of PMOs and contractors, but good intentions can't overcome the hostility generated by loss of trust and squabbles in poorly developed relationships.
03/04/2008Some programs take on a life of their own--privileged, and woven into an organization's existence. But when "sacred cow" projects begin to go wrong, that privilege and protection makes fixing them even more difficult.
03/01/2008This technical note describes the adaptation of the Mission Diagnostic (MD) necessary for a customer and the lessons we learned from its use.
03/01/2008This 2008 document describes the core set of activities and outputs that defines mission diagnostic protocol (MDP).
12/01/2007This 2007 document is a draft in progress of a technology vision and roadmap to improve the ability of the DoD and industry to deliver needed SiS capability in a timely, cost-effective, and predictable manner.
11/01/2007This survey quantifies the relationship between the application of systems engineering best practices to projects and the performance of those projects.
10/25/2007From the Acquisition Support Program, one in a series of short papers on acquisition patterns of failure.
10/01/2007This 2007 report presents a COTS and Reusable Software Management Plan that can serve as a guide for how to manage multiple COTS and other reusable software components in complex systems.
05/31/2007Full day tutorial presented in May 2007
03/15/2007Presented: March 2007
03/01/2007This 2007 report provides an overview of the concepts and foundations of MOSAIC, a suite of advanced, risk-based analysis methods for assessing complex, distributed programs, processes, and information-technology systems.
02/27/2007presentation given at the 6th IEEE International Conference on COTS-Based Software Systems (ICCBSS) 2007, Alberta, Canada (February-March 2007)
10/27/2006A tutorial presented by Donald Firesmith at the 9th Annual Systems Engineering Conference, October 23-27, 2006, in San Diego, California.
10/26/2006presentation made at International Council on Systems Engineering (INCOSE) 2007, San Diego, June 24-29, 2007
10/26/2006Presented: March 2007
10/26/2006Presentation by Donald Firesmith (SEI) on QUASAR, V3.0 (February 2008).
10/26/2006Presented: March 2007
10/26/2006Presented: May 2006
10/26/2006Presentation by Brian Gallagher, Director, Acquisition Support Program (SEI) on acquisition support. Provides a number of real-world examples relevant to the defense industry.
10/26/2006Presented: March 2007
10/26/2006Presentation by Brian Gallagher which discusses acquisition archetypes and how they can be used to detect acquisition problems in an organization (April 2008).
10/26/2006Presentation by Neal London, Dr. Carl Sunshine, and Dr. Charles Hammons on using the TSAT approach to service identification, classification, and definition (October 2006).
10/26/2006Presented by Donald Firesmith at SEPG 2006.
10/26/2006presentation given at the 6th IEEE International Conference on COTS-Based Software Systems (ICCBSS) 2007, Alberta, Canada (February-March 2007)
10/26/2006Presented: October 2006
10/26/2006presentation made at the SEPG 2006 symposium, March 6-9, 2006, Nashville, Tennessee
10/26/2006Presented: September 2007
10/26/2006Presented: June 2006
10/26/2006Presented: October 2006
10/26/2006In this 2007 presentation, Brian Gallagher discusses the state of acquisition support and offers advice for better implementing acquisition support programs in an organization.
10/26/2006Peter Capell (SEI) discusses QUASAR, a method of assessing system architecture, and MFESA, a method framework that enables the development of system-specific architecture (2008).
10/26/2006presentation given at the 2007 SEPG Conference, March 2007, Austin, Texas
10/26/2006This SEI presentation – “Using System Archetypes to Identify Failure Patterns in Acquisition” – was delivered by Diane Gibson, Linda Levine, and William E. Novak on May 2, 2006.
09/01/2006This 2006 report describes methods for selecting candidate commercial off-the-shelf packages for further evaluation, possible methods for evaluation, and other factors besides requirements to be considered.
08/01/2006This report addresses interoperable risk management: the interoperability of organizations that engage in risk management in the context of a system of systems.
08/01/2006This 2006 handbook documents the QUASAR (QUality Assessment of System ARchitectures) method for assessing the quality of the architecture of a software-intensive system.
06/13/2006This book isn't an official guide to best practice, and it certainly isn't a textbook. But in a kind of off-beat way, it's an entertaining yet insightful look at some of the things that can really happen in software acquisition.
06/01/2006This 2006 report presents definitions of IDR and FDR, their context in the acquisition life cycle, a comparison of engineering emphasis during IDR and FDR, IDR and FDR pre- and post-conditions, and IDR and FDR criteria and how to apply it.
05/31/2006presentation delivered at the Systems & Software Technology Conference (SSTC): Transforming: Business, Security, Warfighting, in Salt Lake City, Utah, 1-4 May 2006
05/31/2006presentation delivered at the Systems & Software Technology Conference (SSTC): Transforming: Business, Security, Warfighting, in Salt Lake City, Utah, 1-4 May 2006
05/31/2006presentation delivered at the Systems & Software Technology Conference (SSTC): Transforming: Business, Security, Warfighting, in Salt Lake City, Utah, 1-4 May 2006
05/01/2006This report, published in 2006, discusses questions about sustaining new and legacy systems; the report presents definitions, related issues, future considerations, and recommendations for sustaining software-intensive systems.
04/01/2006This 2006 report explores the questions, "What constitutes risk?" and "What factors put operational missions at risk?"
03/09/2006In this 2006 presentation, Brian Gallagher, Director of the Software Engineering Institute’s (SEI) Acquisition Support Program (ASP) provides an overview of the ASP.
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/06/2006Presented: March 2006
03/01/2006Presented: March 2006
12/01/2005This 2005 handbook presents guidance for acquisition planning and strategy topics in a condensed form, and references the primary resources available for each topic.
11/17/2005Presented: November 2005
11/01/2005Presented: November 2005
11/01/2005The OPEN Process Framework (or OPF) is an appropriate focused requirements engineering method (REM) that facilitates the search for a mechanism that will support the flexible creation of a number of tailored REMs from a single base.
09/02/2005Presented: September 2005
09/01/2005This 2005 report attempts to fill in these gaps in knowledge and experience by presenting an overview of the operational diagnostic life cycle of a system.
09/01/2005This report presents a taxonomy-based method for identifying and classifying risks to operational aspects of an enterprise.
07/01/2005This 2005 report provides an overview of a generic FPGA firmware design process and identifies the resulting work products that may be suitable for reuse in future development efforts.
05/21/2005In this MPEC 2005 presentation, Donald Firesmith of the Software Engineering Institute (SEI) discusses how to achieve quality requirements with reusable software.
05/11/2005Presented: May 2005
05/01/2005What are the drivers for the burgeoning interest in agile methods? Have these drivers stimulated a similar rethinking on other fronts? What have we discovered? In this 2005 paper, the author takes a reflective stance in order to look at these larger issues and patterns.
05/01/2005This paper addresses the problems associated with a lack of a clear security taxonomy by identifying four different types of security-related requirements, providing them with clear definitions, and placing them within an organizing hierarchical taxonomy.
05/01/2005This position paper argues that a successful COTS evaluation process should be based on the principles of method engineering (ME).
04/01/2005This 2005 technical note provides guidance and procedures for performing robustness testing as part of DoD or federal acquisition programs that have a software component.
03/01/2005Software Acquisition Survival Skills: Helping the DoD and Government Program Offices Improve Acquisition of Software and Systems
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005A presentation about software acquisition made in January 2005 by Mary Catherine Ward and Joseph P. Elm
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
01/01/2005Presented: January 2005
11/17/2004Presented: November 2004
11/17/2004Presented: November 2004
09/28/2004This paper describes a taxonomy of these different kinds of safety-related requirements, and clearly and briefly defines and describes each of the above categories of safety-related requirements.
09/01/2004The SEI has constructed a tentative "roadmap" for personnel involved in the systems and software acquisition community. This report describes the characteristics that determine whether a risk diagnostic method qualifies for the roadmap.
05/26/2004Social networks play a key role in the adoption and diffusion of software process improvement as a networked technology. This panel addressed actual examples of SPI networks and identified key characteristics of and roles in these emergent networks.
05/26/2004This paper summarizes the scope of patent protection in the European Union, the United States, and Japan. In doing so, it examines the patentability of computer software as inventions allowed under E.U. and U.S. patent law.
05/01/2004Presented: May 2004
03/01/2004Benchmarking for Improvement in Army Acquisition
03/01/2004This report analyzes a survey that covered four areas of the acquisition system: the acquirer's environment, the developer's environment, communication between the acquirer and developer, and external factors that could affect the acquisition system.
02/01/2004This 2004 paper documents some of the challenges and risks facing programs or organizations trying to help small manufacturing enterprises (SMEs).
01/28/2004A presentation made during the 2004 SIS Conference: Improving Acquisition through COTS Risk Identification.
01/28/2004This 2004 presentation on Software Acquisition Process Improvement was delivered by Donald R. Beyron, Debra Borden (NAVAIR), Gerry Imai (STSC), and John Kennedy (MITRE).
01/28/2004This 2004 presentation on reconsidering the role of systems engineering in DoD software problems was delivered by Grady Campell of the Software Engineering Institute (SEI).
01/28/2004“Acquisition Modeling: The Key to Managing Acquisition Complexity?” was delivered at the 3rd OSD Conference on the Acquisition of Software-Intensive Systems in January 2004.
01/28/2004This 2004 presentation was delivered at the 3rd OSD Conference on the Acquisition of Software Intensive Systems by Richard J. Adams and others of the Aerospace Corporation.
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004A presentation in January 2004 to survey the U.S. railroad industry to benchmark best practices in the acquisition of software-intensive systems.
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/28/2004Presented: January 2004
01/27/2004This 2004 presentation on Guidelines for Acquisition Planning was delivered by Cecilia A. Albert and three others of the Software Engineering Institute (SEI).
01/27/2004In this 2004 presentation, Barry Boehm of the University of California (Los Angeles) discusses early warning indicators in the acquisition of software-intensive systems.
01/27/2004This 2004 presentation on iterative RFP project management was delivered by Chris Armstrong and Bobbi Underbakke of Adaptive Team Collaboration (ADC).
01/01/2004This paper outlines a successful effort to apply COTS-based engineering principles to a software acquisition by various groups at the SEI.
09/12/2003presentation from RE'2003 RHAS'03 Workshop, September 12, 2003
09/01/2003presentation from RE'2003 RHAS'03 Workshop, September 12, 2003
09/01/2003This 2003 report describes the development of an approach to reduce the number of program failures attributable to COTS software: the COTS Usage Risk Evaluation (CURE).
09/01/2003A system cannot have high assurance if it has poor security, and thus, requirements for high assurance systems will logically include security requirement as well as availability, reliability, and robustness requirements.
08/01/2003Acquisition Support Program Director answers the question: What is the SEI's long-term strategy for cross-functional integration across the various SEI competencies.
07/01/2003This 2003 report documents a recent investigation which characterized the technical and programmatic risks in reusing significant quantities of legacy Ada code in a new system.
03/01/2003The Acquisition Support Program
01/29/2003This January 2003 presentation – “SA-CMM in a Large Complex Program” – was delivered by Lloyd Anderson and Hugh Gray at a Software Engineering Institute (SEI) conference in Washington, D.C.
01/29/2003This presentation was delivered by Jonathan D. Addelston at the Conference on the Acquisition of Software Intensive Systems on January 29, 2003.
01/28/2003This 2003 presentation on reducing system acquisition risk with software architecture analysis and evaluation was delivered by J.K. Bergey, Matt Fisher, and Lawrence G. Jones of the Software Engineering Institute (SEI).
01/28/2003This page contains the keynote presentation by Claude M. Bolton at the Acquisition of Software-Intensive Systems Conference, held from January 28-30, 2003.
01/28/2003In this 2003 presentation, V. Basili and Barry Boehm provide an overview of complex systems of systems, discussing the software benefits, risks, and strategies associated with them.
01/28/2003Presented: January 2003
01/28/2003presentation at the Conference on the Acquisition of Software-Intensive Systems, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003presentation at the Conference on the Acquisition of Software-Intensive Systems, January 28-30, 2003
01/28/2003presentation at the Acquisition of Software-Intensive Systems Conference, January 28, 2003, in Arlington, Virginia
01/28/2003Presented: January 2003
01/28/2003presentation from the Acquisition of Software-Intensive Systems Conference, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003presentation from the Acquisition of Software-Intensive Systems Conference, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003presentation from the Acquisition of Software-Intensive Systems Conference, January 28-30, 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003Presented: January 2003
01/28/2003IPresented: January 2003
01/28/2003Presentation by Dr. Dave Thombs, Pricing & Forecasting Group (PFG), made on January 2003.
01/28/2003Presented: January 2003
01/28/2003This presentation on the experiences and lessons learned in applying the Tri-Service Assessment Initiative Process was delivered by William Bail of MITRE on January 28, 2003.
01/28/2003This 2003 presentation was delivered by Charles R. Armstrong of the Customs Modernization Office at the Conference on the Acquisition of Software-Intensive Systems.
01/27/2003This 2003 presentation was delivered by Melanie Benhoff of Integrity Applications, Inc., in which she presents a number of lessons learned on cooperative government/industry appraisals.
01/26/2003“They Keep Moving the Cheese: A Framework for the Evolutionary Acquisition of Large Software Intensive Systems” was delivered by Cecilia Albert and Lisa Brownsword in 2003.
01/01/2003Presented: January 2003
12/01/2002This 2002 report provides information to help guide decisions about when COTS products are an appropriate solution—and when they are not.
11/01/2002This 2002 document is the first release of a full description of the EPIC framework along with its activities and artifacts.
09/01/2002This 2002 report outlines the early results of an approach to support software migration planning that focused on deriving actionable plans for focus areas that were identified in an initial increment of an overall migration plan.
06/01/2002This 2002 report focuses is on the use of Earned Value in the context of a COTS-Based System (CBS).
03/01/2002This 2002 version of the SA-CMM incorporates change requests that have been received, as well as the results of lessons learned from conducting appraisals and from the use of Version 1.02.
12/01/2001This special report provides a bibliography of books, articles, and other literature concerning the PSP and TSP methodologies.
07/10/2001Presentation from July 2001 on the IDEAL model, an organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions.
05/01/2001DoD Instruction 5000.2 introduced innovations throughout the acquisition cycle. To address this, a workshop was held September 2000. This 2001 report summarizes the workshop and presents its recommendations.
08/01/2000The SEI surveyed senior acquisition managers about the performance of their organizations, especially on skills and competencies, and issues surrounding the training needed to develop them. The results of the survey are presented in this report.
10/01/1999This report provides guidelines for implementing a software acquisition risk management program that satisfies the goals of the ARM KPA of the SA-CMM.
07/01/1998This 1998 document discusses rationale behind the need for the Software Acquisition Improvement Framework (SAIF), the elements constituting the SAIF, and the intended operational usage of the SAIF.
08/01/1997This 1997 report contains a software acquisition process maturity questionnaire, intended for those interested in learning about and performing software acquisition process appraisals.
12/01/1996This 1996 version of the SA-CMM incorporates the results of lessons learned from the use of Version 1.0.
01/01/1996This book describes the underlying principles, concepts, and functions of risk management and provides guidance on how to implement it as a continuous practice in your projects and organization.
06/01/1987This 1987 report offers several recommendations for achieving a balanced policy as to government funded software, privately funded software, and mixed funding software that will meet the mission needs of the DoD while enabling contractors to protect their proprietary interests, and commercialize their software products.
01/01/1987This 1987 report summarizes the significant technical and managerial considerations that affect the maintenance and enhancement of software.
09/01/1986This report 1986 recommends regulatory strategies for addressing difficulties the DoD has experienced with respect to legal issues related to software acquisitions.
04/01/1986For more information
Email: info@sei.cmu.edu
Call: 412-268-2358