Skip Ribbon Commands
Skip to main content

Software Development

Agile Development​

Topic Area
ACC Topic
Summary Description
red book.pdf
EngineeringArmy; DoDReferenceSoftware Development
The "little red book" is divided into seven sections: general precepts about COTS products, requirements, evaluation and design, maintenance, business processes, testing and debugging, and IPTs.
5/18/2017 7:44 PM
EngineeringDoDReferenceSoftware Development
Interest in COTS products requires examination both in terms of its causes and effects, and also in terms of its benefits and liabilities. In this paper we offer some observations on all of these, and voice some specific concerns and criticisms. We stress that our observations are essentially cautionary, not condemnatory: it is obvious to almost any observer that the huge growth in software costs will continue, not abate, and that appropriate use of commercially-available products is one of the remedies that might enable us to acquire needed capabilities in a cost-effective manner.  Where use of an existing component is both possible and feasible, it is no longer acceptable for the Government to specify, build, and maintain a comparable product; clearly an existing commercial solution is called for.
5/18/2017 7:44 PM
COTS Gotchas.pdf
ReferenceSoftware Development
The presentation provides information on assumptions and errors in COTS procurement that can deleteriously affect the process.
5/18/2017 7:44 PM
25 p822.pdf
EngineeringNavyLearning MaterialSoftware Development
Software infrastructure plays a crucial role in adopting industry advances for mission-critical systems. This presentation will explain software infrastructure's role, problem domain, and challenges. In addition, this presentation will describe an approach to determine the merits of emerging technologies. Discussed are the software infrastructure layers, related technologies, and practical experiences; as well as the operating system layer, the middleware layer, the component framework layer, and the data tier.
5/18/2017 7:47 PM
SEI Management Practices.aspx
ReferenceSoftware Development
This website is a listing of the software engineering management practices, software engineering management, SEI projects, and software engineering. Topics include: CMM, CMMI, SEI Appraisal program, IDEAL, Risk Management, Personal Software Process (PSP), Team Software Process (TSP), Software Acquisition CMMR, Software Acquisition Guidebooks, Software Risk Evaluation Service, Software Engineering Measurement & Analysis (SEMA), Software Engineering Information Repository (SEIR), and links to SEI Initiatives, Publications and Training.
5/18/2017 7:47 PM
Acquiring All You Need to Maintain Your Software.pdf
Contracting; EngineeringNavyLearning MaterialSoftware Development
by Al Kaniss from Defense AT&L; March-April 2005
The government doesn't automatically own software that is produced on a government contract, even if the government paid for 100 percent of its development.
5/18/2017 7:47 PM
Engineering; Program ManagementDoDLessons LearnedSoftware Development; PM Technical Management
Experience in identifying and evaluating project risks in large-scale software systems acquisition and development programs has led to development of a risk database. This database was analyzed and seven predominant characteristics were identified that provided insight into causes of dysfunctional software projects: failure to apply essential project management practices; unwarranted optimism/unrealistic management expectations; failure to implement effective software processes; premature declarations of victory; lack of program management leadership; untimely decision-making; and lack of proactive risk management.
6/26/2017 8:51 AM
Acquiring and Enforcing the Government s Rights in Technical Data and Computer Software Under Department of Defense Contrac.aspx
ReferenceSoftware Development; PM Technical Management
This handbook is designed to provide you with a practical "cradle-to-grave" handbook to acquiring technical data and computer software rights.
6/26/2017 8:57 AM
CMMI Institute.aspx
ReferenceKitchen Sink; Software Development; PM Technical Management
As part of its mission to transition mature technology to the software community, the SEI has transferred CMMI-related products and activities to the CMMI Institute, a 100%-controlled subsidiary of Carnegie Innovations, Carnegie Mellon University’s technology commercialization enterprise. The CMMI Institute will conduct CMMI training and certification, sponsor conferences and classes, and provide information about CMMI process improvement models and appraisals.
The SEI will continue to pioneer and advance new research in the field of software process management. More information about our current work is available at
6/27/2017 8:36 AM
104EXSAM 450 COTS Issues.ppt
Engineering; Information TechnologyArmy; DoDPresentationSoftware Development
Definition of COTS and what makes COTS challenging.
7/25/2017 3:30 PM
Clinger Cohen Act.pdf
Contracting; Information Technology; Program ManagementDoD; Joint StaffReferencePM Policies and Guidance; PM Technical Management; Software Development
The Clinger-Cohen Act of 1996 that shapes DoD's and other Federal Agencies' approaches to IT acquisition and management;
- The House of Representatives Report 104-450, National Defense Authorization Act for Fiscal Year 1996, Conference Report, that provides an historical legislative perspective for the Act;
- Title 10, United States Code, Section 2223 that gives additional responsibilities to the DoD CIO and the CIOs of the Military Departments;
- Executive Order 13011, "Federal Information Technology," that provides policy guidance for significantly improving the acquisition and management of IT by implementing the Clinger-Cohen Act and the Paperwork Reduction Act of 1995;
- Secretary of Defense Cohen's Memorandum, "Implementation of Subdivision E of the Clinger-Cohen Act of 1996 (Public Law 104-106)," June 2, 1997, that defines and clarifies how the Act will be implemented in DoD, and the responsibilities of the DoD Chief Information Officer (CIO) vis--vis those of the Military Department CIOs;
- Deputy Secretary of Defense Hamre's Memorandum, "DoD Chief Information Officer Executive Board," March 31, 2000, and DoD CIO Executive Board Charter; and
- Deputy Secretary of Defense Hamre's Memorandum, "DoD Chief Information Officer (CIO) Guidance and Policy Memorandum No. 8-8001 - March 31, 2000 - Global Information Grid," March 31, 2000. 
2/12/2020 8:35 AM