Lessons Learned are those experiences in the past that can be used in the future to prevent mistakes or perform a task or job better. A lesson is not learned until it is put into practice or until behavior changes. The DoD has a few sources of lessons learned for Software that can be used to prevent the software mistakes of the past. The DAU Acquisition Center of Excellence (ACE) is a good source of lessons learned. – See Lessons Learned
Some additional sources of lessons learned are:[1]
- Defense Acquisition University (DAU)
- Defense Technical Information Center (DTIC)
- Air Force Knowledge Now (AFKN) (CAC Card Needed)
- Communities of Practice (CoPs) (CAC Card Needed)
- Software Technology Support Center (STSC)
- Air Force Institute of Technology Software Professional Development Program (SPDP)
- USAF Weapon Systems Software Management Guidebook
- Other service guidebooks and handbooks
- Other Government agency guidebooks and handbooks
AcqLinks and References:
- USAF Weapon Systems Software Management Guidebook
- Open Technology Development (OTD): Lessons Learned & Best Practices for Military Software, – 16 May 2011
- Mil-STD-498 “Software Development and Documentation” – 5 Dec 1994
- MIL-STD-498 “Application and Reference Guidebook” – 3 Jan 1996
- Defense Acquisition Guidebook (DAG) – Chapter 4
- Software Development Plan Information Outline
- Joint Software Systems Safety Engineering Handbook (JSSSEH) – 27 Aug 2010
- Template: Software Development Plan – SPAWAR
- Website: MIL-STD-498 Software Documentation
- Journal: Journal of Software Technology
Defense Cost Resource Center (DCRC)
