Recent Trends in DoD Systems
and Software Engineering
Processes
Bruce Amato
Acting Deputy Director, Software Engineering and Systems
Assurance
Office of the Deputy Under Secretary of Defense
(Acquisition and Technology)
28 October 2008
AT&L Organization
USD, Acquisition
Technology & Logistics
DUSD, Acquisition &
Technology
Dir, Joint Advanced
Concepts
Defense Procurement
and Acquisition Policy
Dir, Systems and
Software Engineering
Industrial
Programs
Dir, Portfolio
Systems Acquisition
Small Business
Programs
Defense Acquisition
University
Defense Contract
Management Agency
2
SSE Functions
Acquisition Program Support
Decision Support to Senior DoD Leadership
Mentoring Acquisition Programs
Technical Reviews of Key Program Documentation
Policy, Guidance, Best Practices
Acquisition Workforce Education and Training
SE, Test, Product Quality Management, Software
Systemic Root Cause Analysis
“Discipline” Expertise
✫
✫
✫
✫
Risk
Reliability
Architectures
Test/Eval
✫
CMMI
✫ Software
✫ Energy
✫ Safety
✫
Modeling/Simulation
✫ Assurance/Cyber
✫ Comm/Networking
✫ System of Systems
3
SSA FY08/09 Thrust Areas
Software Engineering Competency
Human Capital
Software Metrics
Software Engineering
Early Software Engineering
Competitive Prototyping
Milestone B after Preliminary Design Review
Systemic Root Cause Analysis
Systems of Systems
System Assurance
4
Human Capital Initiatives
Graduate Software Engineering Reference
Curriculum
Version .5 on the street
Version 1.0 to be taken over by IEEE
Defense Acquisition University
Competencies
Using GSwERC competency efforts
In-house Training Course
To be expanded to organizations outside OSD
5
Software Metrics Initiatives
Software Cost Estimation
Continuous PSR efforts
Work Breakdown Structure
MIL HDBK 881 recommendations
Earned Value Management
Field pilots underway
Quality Metrics
Software Metrics Database
6
Software Engineering Initiatives
Software and Systems Engineering
Integration Framework (continuing effort)
Incremental Commitment Model
Guidebook (Barry Boehm)
Architecture Guidance (Q2/3 FY09)
Software Engineering Guidance
Input from multiple studies/research
Milestone A to B (or how to produce an
effective Request for Proposal)
Milestone B to C (follow on)
7
Early Software Engineering
New Acquisition Policy focused on
“buying down” risk
Competitive Prototyping
Movement of Milestone B (Approval
for Development to Proceed) after
Preliminary Design Review
Start-up Support (Continuous
Engineering)
8
Questions/Discussion
Contact Information:
Bruce Amato
ODUSD(A&T) Systems & Software Engineering
Deputy Director, Software Engineering and System Assurance
bruce.amato@osd.mil
9
Backup Slides
10
A word on CMMI…
DoD does not place significant emphasis on
capability level or maturity level ratings
CMMI is a tool for internal process improvement
Levels should not be a source selection consideration
Lack of emphasis on ratings is prudent
Findings that not all programs exhibit behavior consistent
with supplier attained CMMI maturity level rating
Further findings that achievement of levels has little impact
on program cost and schedule performance
Essential that DoD and industry use CMMI
capability in the right manner, with appropriate
measure, in order to realize benefits
11