GSAW 2007
Software Acquisition Best Practices for Ground Systems Suellen Eslinger Software Engineering Subdivision Computers and Software Division The Aerospace Corporation March 27, 2007
© 2003-2007 The Aerospace Corporation.
The Big Issues and Challenges in Acquiring Ground Systems
Software!
Mission Assurance
Executability
2
Example DoD and NSS Acquisition Models Tailored for Software-Intensive Systems without Production NSS Space Acq Policy 03-01 (Adapted) Pre-Systems Acquisition Key Decision PHASE A PHASE B Points: Approval Approval
A
Pre KDP-A Concept Studies
Systems Acquisition PHASE C Approval
C
B PHASE A Concept Development SRR
Build Approval
PHASE B Preliminary Design
SDR
Follow On Buy Approval
PHASE C Complete Design
PDR
Sustainment
1st Launch IOC
Upgrade Decision
FOC
PHASE D Build & Operations
CDR
Concept Decision
Technology Development
A
C PD R
System Development & Demonstration Approval
CD R
B
SR R
Technology Development Milestones: Approval
Deployment
System Development & Demonstration
SF R
Concept Refinement
Design Readiness Review
Limited Deployment Approval
DoDI 5000.2 (12 May 2003) (Adapted) 3
IOC
Operations & Support
Full Deployment Approval
FOC
Reducing Space System Acquisition Risk with Software Acquisition Best Practices NSS Space Acq Policy 03-1 Pre-Systems Acquisition Key Decision Points:
Systems Acquisition
PHASE A Approval
PHASE B Approval
PHASE C Approval
A
B
C
Pre KDP-A Concept Studies
PHASE A Concept Development SRR
Software Product & Process Risk Reduction
SoftwareInclusive System Requirements
SoftwareInclusive System Architecture
SDR
PHASE B Preliminary Design PDR
Sustainment 1st Launch IOC
PHASE C Complete Design
FOC
PHASE D Build & Operations
CDR
Robust Software Test Program
Contractor Capability Evaluation Robust Software Architecture
Realistic Software Size, Cost and Schedule Estimates
SoftwareInclusive Technical Reviews Key Software Technical and Management Deliverable Data
Pro-Active Quantitative Management
Contractually Compliant Software Standards
Software Acquisition “Best Practice” Contract
SOW
• • • •
Contract Reqs
Deliverable Data
Comply with SDP • Software-inclusive • Do COTS SW trade studies system requirements • Hold SW technical reviews • COTS software • Undergo periodic software support requirements • process appraisals • Special Provisions • Electronic access to all software products • Access to prime & subcontractor software technical & mgmt data
Compliance Docs • Full life cycle software standard • Other softwarerelated standards 5
Software plans Reqs & architecture Test documentation Metrics reports O&M documentation Award Fee Plan
• Software quality • SW architecture for evolution and legacy transition
Best Practices that Span the Acquisition Life Cycle Software Acquisition Risk Management Software Systems Acquisition Pre KDP-A
PHASE A
PHASE B/C/D
Software Acquisition Risk Management
Software Systems Acquisition
• Continuous software acquisition risk management • Across the entire acquisition life cycle • Program level risk management and contractor development risk management are necessary but not sufficient
• Integrate software acquisition with the system acquisition process • From capability needs identification through system retirement • Especially during early life cycle and pre-contract award activities 6
Conclusion
• Software acquisition best practices do not guarantee success They are not a panacea!
• Using best practices, however, can reduce risk in complex software-intensive ground system acquisitions
7
References • • •
•
•
•
• •
L. A. Abelson, R. J. Adams, and S. Eslinger, Metrics-Based Software Acquisition Management, Aerospace Report No. TOR-2004(3909)-3405, May 2004. R. J. Adams and S. Eslinger, A Framework for Software Products Within a System Context (2nd Edition), Aerospace Report No. TR-2002(8550)-3, May 2002. R. J. Adams and S. Eslinger, COTS-Based Systems: Lessons Learned from Experiences with COTS Software Use on Space Systems, Aerospace Report No. TR-2001(8550)-1, September 2001. R. J. Adams, S. Eslinger, P. Hantos, K. L. Owens, L. T. Stephenson, J. M. Tagami, and R. Weiskopf, Software Development Standard for Space Systems, Aerospace Report No. TOR-2004(3909)-3537, Revision B, March 2005. R. J. Adams, S. Eslinger, K. L. Owens, and M. A. Rich, Software Acquisition Best Practices: Experiences from the Space Systems Domain, Technical Report No. TR2004(8550)-1, September 2004. R. J. Adams, S. Eslinger, K. L. Owens, and M. A. Rich, Reducing Software Acquisition Risk: Best Practices for the Early Acquisition Phases, Technical Report No. TR-2006(8550)-1, January 2006. R. J. Adams, S. Eslinger, K. L. Owens, and M. A. Rich, Software Acquisition Best Practices Tutorial, Technical Report No. TR-2005(8550)-1, September 2005. P. Hantos, Evolutionary Acquisition and Spiral Development Tutorial: Revision B, Technical Report No. TR-2006(8550)-2, 30 October 2006 8
Author Contact Information
•
Suellen Eslinger Distinguished Engineer Software Engineering Subdivision, The Aerospace Corporation (310) 336-2906
[email protected]
9
Acronyms and Abbreviations Acq CDR COTS Docs DoD DoDI FOC GSAW IOC KDP Mgmt NSS O&M PDR Reqs SDP SDR SFR SOW SRR SW
Acquisition Critical Design Review Commercial Off-the-Shelf Documents Department of Defense DoD Instruction Full Operational Capability Ground Systems Architecture Workshop Interim Operational Capability Key Decision Point Management National Security Space Operations and Maintenance Preliminary Design Review Requirements Software Development Plan System Design Review System Functional Review Statement of Work System Requirements Review Software 10
