Embed Size (px)
Citation preview
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Headquarters U.S. Air Force
As of: 1
George R. Winters, PETechnical Director, AFPEO/C2&CS
January 28, 2003
The Software Maturity Matrix;A Software Performance Metric
As of: 2I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Overview
n Introductionn Software Metricsn Software Maturity Matrix (SwMM)n SwMM Relationship to CMM-based Improvementn Summary & Conclusion
As of: 3I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Introduction
n Backgroundn Visionn Status
As of: 4I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Background
n Portfolio of the PEO for Command and Control &Combat Support contains the greatest concentrationof software intensive programs of any PEO portfolio.
n Software development issues are among the mostcritical in the AFPEO/C2&CS portfolio.
n Software metrics now reported to PEO as part ofperiodic execution plan reviews.
As of: 5I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Vision
n Identify incipient software problems and mitigatethem early.
n Franchise the AFPEO/C2&CS processes andprocedures to other organizations.
As of: 6I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Status
n Metrics are in third spiral of development.n Software Maturity Matrix started early and will end
last.n Introduction of statistical controls is months away.
As of: 7I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Software Metrics
n Why Measure?n Measurement Principlesn AFPEO/C2&CS Reportable Software Metrics
As of: 8I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Why Metrics?
Objective measurements are the key to objectivecommunication.
As of: 9I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Measurement Principles
n Focus on a Key Fewn Keep Them Simplen Insure Reliability and Repeatabilityn Measurements are for Managingn Use Them!
n Unused measurements have the same value as lastnight’s unused hotel room or an empty airline seat.
n Be Prepared to Change or Modify Them
As of: 10I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Software Metrics for AFPEOC2&CS
n Size Growthn Workforce Size and Qualificationsn Requirements Fulfillment (Software Maturity Matrix)n Quality Trendsn Selected Earned Value Information
As of: 11I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Why Requirements Fulfillment?
n Meeting Requirements Is How We Will Be Measuredn Controlling Requirements Is the First Step to Cost
and Schedule Controln Mutual Understanding of Requirements Is the
Foundation of a Successful Integrated ProductDevelopment Team
As of: 12I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Software Maturity Matrix(SwMM)
n Purposen Descriptionn Evolutionn Implementation
As of: 13I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Purpose
n Forces Developer Requirements Capture (User,Derived, & External)
n Forces Developer Analysis of Maturation Over Timen Identifies Areas of Non/Under/Over Performancen Basis of Objective Discussion of Statusn Flags Areas Needing Management Attention
As of: 14I n t e g r i t y - S e r v i c e - E x c e l l e n c e
What is an SwMM?
n Formatn Expected Values Over Timen Actual Values at Selected Milestones
n At Least Four Milestones per Year
n Application and Tailoringn Evolution
As of: 15I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Format
RQT n
RQT 3
RQT 2
RQT 1
MS nMS 3MS 2MS 1
As of: 16I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Initial Entries: ExpectedValues
/ms nr n EV
/ms 1r n EV
RQT n
/ms 3r 3 EV
RQT 3
RQT 2
/ms nr 1 EV
/ms 2r 1 EV
/ms 1r 1 EV
RQT 1
MS nMS 3MS 2MS 1
As of: 17I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM MS Entries: ActualValues
AV n/EV n
RQT n
AV 3/EV 3
RQT 3
RQT 2
AV n/EV n
AV 1/EV 1
RQT 1
MS nMS 3MS 2MS 1
As of: 18I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Analysis
RQT n
/100%/125% 130%/150%
180%/175%
200%/200%
SpareMem.
RQT 2
RQT 1
MS nMS 3MS 2MS 1
As of: 19I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Evolution
RQT n
/100%/125±10%
130%/150±25%
180%/175±30%
200%/200±50%
SpareMem.
RQT 2
RQT 1
MS nMS 3MS 2MS 1
As of: 20I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Implementation
This example is at an early stage of development.
As of: 21I n t e g r i t y - S e r v i c e - E x c e l l e n c e
GCSS-AF Software MaturityMatrix - CINC 57 (1)
n Strategic Cargo and Personnel Movementn Intratheater Cargo and Personnel Movementn Equipment and Supplies Asset Visibilityn Personnel and Equipment Deployment Visibilityn Prepositioned Equipment and Material Availabilityn Location and Status of Class IX: Repair Partsn Location and Status of Class VII: Major End Itemsn Location and Contents of Prepositioned Stocks and
Suppliesn Location of LOCs and PODsn Projected Arrival of Forces, Supplies, and
Equipmentn Location and Status of Class V: Ammunitionn Decision Tools and Logistics Estimate Capabilityn Inter- and Intra-theater forces, equipment, and
supplies movementn Prepositioned WRMn Notional TPFDDn LOC/POE informationn Logistics Analysis for an Operational Missionn Transportation Asset Location and Availabilityn Transportation Infrastructure Informationn Munitions Requirements by Phase
n LSA of COAn Timely, near real time, accurate informationn Location and Status of Class III: POLn LSA for Each Supply Class by Mission Phasen Transportation Asset Availability and Node Throughput
Capabilityn Status and Location of POLn POL Requirements by Mission Phasen Unit and Personnel Location and Status Trackingn Logistics units, stockage locations, LOCn Logistics units status in AORn Project lift and transportation requirementsn Compare time-phased requirements vs available
resourcesn Predict POD and POE requirementsn Conduct operational mission logistics analysis
n Assess transportation infrastructure shortfallsn Reliable and current secure communicationsn Status of laterally distributed logistics assetsn Determine POL movement and theater capabilitiesn Simplify JOPES TPFDD processn Project POL consumption with usagen Project Munitions consumption with usage
As of: 22I n t e g r i t y - S e r v i c e - E x c e l l e n c e
GCSS-AF Software MaturityMatrix - CINC 57 (2)
n Project class of supply consumption from historicaldata
n Project Medical supplies consumption with usagen Provide theater combat and civil engineering statusn Project support requirements for incoming
personnel and forcesn Project water and subsistence consumption with
usagen Plan, manage and track retrograde cargon Conduct real-time medical supportability analysis of
a COAn Provide battle space picturen Project POL consumption with usage
n Provide engineering supportability analysis of aCOA
n Provide ground LOC analysisn Conduct real-time medical supportability
analysis of a COAn Compare medical support requirements with
available resourcesn Project Individual Equipment consumption with
usagen Project construction material consumption with
usagen Track NEO and humanitarian requirements with
lift requirements
As of: 23I n t e g r i t y - S e r v i c e - E x c e l l e n c e
GCSS-AF Software MaturityMatrix-FY03
Dec-02 Jan-03 Mar-03 May-03 Jun-03 Jul-03 Sep-03Integration Framework/Air Force Portal CapabilitiesApplications on IF 15 (goal), 10
(threshold)Single Sign-on Applications 60 (goal), 30
(threshold)Operate IF at more than one site Engineering
approach delivered2nd NIPRNet site operational
Deploy IF releases Version 5 fieldedDevelop Deployed Operations support approach Deployed CS
approach definedImplement .com access .com access for
current usersDocument Management AFP document
management fielded
Verity Search Implementation Verity search engine fielded on AFP
Warfighter innovations TBD by user
Integration Framework/Air Force Portal CharacteristicsAvailability NIPRNet-99% NIPRNet-99.99%
Enterprise Data Warehouse SpiralsCapability/Data Acquisition – Maintenance Spiral 1 complete Spirals 2-5 complete
Capability/Data Acquisition – Supply Wholesale and Deport Supply
Requirements Forecasting
Base Supply, DLA
Analysis & Capability/Data Acq – Finance Plan complete Data acquisition complete
Analysis & Capability/Data Acq - Contracting Plan complete Data acquisition complete
As of: 24I n t e g r i t y - S e r v i c e - E x c e l l e n c e
GCSS-AF Software MaturityMatrix-FY04
Dec-03 Mar-04 Jun-04 Sep-04Integration Framework/Air Force Portal CapabilitiesApplications on IF 45
Single Sign-on Applications 100
Operate IF at more than one site 2 SIPRNet sites operational
3rd NIPRNet site operational
Deploy IF releases Version 6 fieldedDevelop Deployed Operations support approach
Implement .com access
Document Management
Verity Search Implementation
Warfighter innovations
Integration Framework/Air Force Portal CharacteristicsAvailability SIPRNet-99.99% NIPRNet-99.99%
As of: 25I n t e g r i t y - S e r v i c e - E x c e l l e n c e
GCSS-AF Software MaturityMatrix-FY05
Dec-04 Mar-05 Jun-05 Sep-05Integration Framework/Air Force Portal CapabilitiesApplications on IF 100
Single Sign-on Applications 200
Operate IF at more than one site
Deploy IF releases Version 7 fieldedDevelop Deployed Operations support approach
Implement .com access
Document Management
Verity Search Implementation
Warfighter innovations
As of: 26I n t e g r i t y - S e r v i c e - E x c e l l e n c e
SwMM Relationship to CMM-based Improvement
As of: 27I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Areas Addressed by the SwMMat ML2-Repeatable
n Requirements must be defined and agreed to.n Project plans must incorporate appropriate
milestones and estimates.n Project tracking is built in at milestones.n Measurement is implicit.n Verification is implicit.n Requirements changes must be controlled and
mapped into updates, and an audit trail must bemaintained.
n If outside suppliers are involved, their efforts shouldbe tracked in the same way.
n Conformance to requirements is implicit.
As of: 28I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Areas Addressed by theSwMM at ML 3 - Defined
n The SwMM technique requires a process ownern The SwMM Technique requires organization process
assets and data basen The organizational standard SwMM technique must
be tailored for projectsn The SwMM can be a focus for integrated product
teamsn Organization standard measurements are implicitn Organization standard verification is implicitn Organization standard SMM training can be the
basis of an organization training programn Product Engineering efforts are focussed on
meeting the requirements delineated in the SwMM
As of: 29I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Areas Addressed by the SwMM atML 4 - Quantitatively Managed
n Quantitative decision making is implicit
n Quantitative product characteristics are implicit
n SwMM data identifies areas for corrective action
n Satisfaction of direct and derived customerrequirements is driven by the SwMM
As of: 30I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Areas Addressed by the SwMM atML 5 - Optimizing
n Continuous improvement culture is fosteredby the need to continuously improve the“planned” values for the maturity profile.
n New technologies and processes canchange the “Planned” values in a favorableway.
As of: 31I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Summary
n AFPEO/C2&CS imposed software metrics set acrossportfolio.
n One metric, the Software Maturity Matrix, tracksrequirements satisfaction.
n Applying the SwMM is compatible with CMM-basedimprovement efforts.
As of: 32I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Conclusion
The Software Maturity Matrix, in conjunction withother metrics and as part of periodic reviews,provides useful management insight into softwareand software-intensive development programs.
