asee workshop 2006 february 25, 2006 battle of the bulge: the software challenge of the mission...
TRANSCRIPT
ASEE Workshop 2006
February 25, 2006
Battle of the Bulge: The Software Challenge of the Mission System Integrator
Dennis Frailey, Raytheon, Network Centric Systems, Ground Sensor Integrator [email protected] (972-344-8366)
2/25/2006 Slide 2
Program Tiers - What is a Mission System Integrator?
Tier5
Tier4
Tier3
Tier2
Tier1
Component
Subsystem
System
MSI
LSI
$1M-$50M
$50M-$100M
>$100M
>$100M
>$300M
Value ($)
Co
mp
lexi
ty
Mission
System
Integrator
2/25/2006 Slide 3
Communication Flow
Our Customer (Lead System
Integrator)
Ultimate Customer (US Army)
GSDsGSDsGSDsGSDs (Our Suppliers)
GSI (Mission System
Integrator)
Our Internal
SW teams
2/25/2006 Slide 4
Sensors, Suites and Vehicles
V1
Radar 1
S1
S2Dev3
EO 3
EO 2
EO 1
Detector
SPEC Sensors
S6
S7
V3
V4
V5
V7
V8
V9
V6
S5
S4
S3
V2
Dev4
Dev1
Dev2
Sensors(what our suppliers do)
Suites(what we do)
Vehicles (our customers)
2/25/2006 Slide 5
Software Development and Management
Each GSD produces multiple products containing software.
GSI Software Team (Integration into Suites)GSI Software Team
(Integration into Suites)
Lab ToolsLab
Tools
SimulatorsSimulators
Special System Models
Special System Models
V&E IPT I&T IPTGSD #1
SimulatorSimulator
EmulatorEmulator
SensorSensor
WrapperWrapper
WrapperWrapper
Sensor Suite
Control
Sensor Suite
Control
Make/Buy
Delivery to Vehicles
GSD #2
SimulatorSimulator
EmulatorEmulator
SensorSensor
…GSD #n
SimulatorSimulator
EmulatorEmulator
SensorSensor
SW
Ov
ers
igh
t a
nd
Ma
na
ge
me
nt
SW
De
ve
lop
me
nt
The GSI produces or acquires other software needed for integration.
Non-deliverable SW
2/25/2006 Slide 6
ExpandedRisk/Opportunity Management
All ProgramsHonest assessment of risk or opportunity with a solid quantitative impact (technical, schedule, cost)
Integrated risk/opportunity assessment and tracking
Mitigation plans resourced in program execution plan with customer buy-in
List of Watch Items with well defined trigger points
Balanced opportunity plan
+
MSI AdditionsIntegrated risk/opportunity plan with all program partners
Multi Level Risk/Opportunity Boards with elevation process
Automated Tool (ARM) that allows easy integration from all levels is essential
2/25/2006 Slide 7
ExpandedCustomer Relations
All Programs
Honest timely communication
No surprises
Mutual Problem Solving
Constant focus on Performance Assessment
Quality Presentation
Collaborative execution environment is valuable
+
MSI Additions
Multi Level communication plan is critical
Lower Level customer / contractor communication up to the top levels are aligned (good and bad)
Open forum to address bureaucracy issues (One Team Partner Council)
Peer partner relationships are equally important
Collaborative execution environment is mandatory
2/25/2006 Slide 8
ExpandedChange Management
All Programs
Baseline definition and management Requirements Contract SOW Interfaces Architecture and Standards
Traceability interfaces and impact analysis
Balanced Cost/benefit process for derived requirements
Robust Engineering Review Boards and Configuration Control Boards
+
MSI Additions
Automated workflow configuration management processes and tools
Streamlined Holistic Multi Level decision process
Balanced Cost/benefit Process
Horizontal / Vertical
2/25/2006 Slide 9
ExpandedProcess Requirements
All ProgramsIntegrated ProcessCMMISix Sigma
Local Tailoring of Processes
+MSI Additions
Need processes that reflect MSI type program i.e. multi-level integration, multi-level requirements management, multi-level risk management, multi-level configuration control, and many suppliers.
2/25/2006 Slide 10
Why This Isn't Enough
Gaps:Our processes assume one
program, not multiple tiers of
programs
CMMI
Standards and Best Practices
6 sigmaProcess for
Improvement
Integrated Product
Development System
How we do business
2/25/2006 Slide 11
Gap Analysis Process
Organizational Processes
MSI Requirement
s
Prioritized List of New
Artifacts Needed for
an MSI Program
Prioritized List of New
Artifacts Needed for
an MSI Program
An MSI would need many new artifacts in addition to the organizational processes already in place
–Work Instructions, Tools, Procedures Well established estimating process
use to determine the development costs
MSI Process Improvement Project
The Bulge
2/25/2006 Slide 12
Some Examples of New Work Instructions Needed How to Review and Evaluate Supplier Bids, Plans,
Deliverable Documents and Software How to Control Changes in a Multi-level Hierarchy How to Manage Software Suppliers How to Establish Architectural and Design Standards for
Multiple Suppliers that Enable Effective Integration but Allow Each Supplier to Use its Own Processes
How to Define Metrics that Each Supplier can Provide within their existing process and can be Consolidated into Meaningful Assessments of Supplier and Program Health
How to Assess “ilities” (safety, supportability, maintainability, etc.) at an overall system level when each supplier has its own systems for defining these things.
How to gain maximum benefit from Reuse when the existing reusable assets are highly diverse
2/25/2006 Slide 13
Example: Change ManagementConsider the Possibilities …
V1
Radar 1
S1
S2Dev3
EO 3
EO 2
EO 1
Detector
SPEC Sensors
S6
S7
V3
V4
V5
V7
V8
V9
V6
S5
S4
S3
V2
Dev4
Dev1
Dev2
Sensors(what our suppliers do)
Suites(what we do)
Vehicles (our customers)
2/25/2006 Slide 14
CMMI Experience Gave Us Leverage
EstimationProcess
EstimationProcess
MetricsBaseline
MetricsBaseline
ContinuousImprovementIngrained in
theOrganization
ContinuousImprovementIngrained in
theOrganization
ConfigurationControl
Infrastructure
ConfigurationControl
Infrastructure
Peer ReviewProcess and
Tools forWork
Instructions
Peer ReviewProcess and
Tools forWork
Instructions
Templates for Work
Instructions
Templates for Work
Instructions
MetricsCollection,Analysis
AndStorage
MetricsCollection,Analysis
AndStorage
• Our CMMI and Process foundation gave us many tools to approach this challenge
• They provided a baseline approach for metrics, work instruction development and review, configuration control, estimation and improvement
• Thus we were able to focus on solving the problem rather than defining the approach
2/25/2006 Slide 15
Multi-Year Approach
Program Needs
New Org Artifacts
New Program Artifacts
Program Needs
New Org Artifacts
New Program Artifacts
Year 1 Year 2
Program Needs
New Org Artifacts
New Program Artifacts
Year 3 Year 4
• We employed a phased approach to tackling this problem First identify and prioritize emerging program needs Then develop new, organization-level artifacts Finally, tailor those to program needs
• Artifacts arrive “just in time” to meet program needs
2/25/2006 Slide 16
Future
Our organizational processes are enriched as we flow MSI Improvement Project artifacts back into the organizational process.
Enhanced Integrated Product
Development System
MSI Process Improvement Project
OrganizationalProcess
Enhancements
2/25/2006 Slide 17
Questions
2/25/2006 Slide 18
Biography Dennis J. FraileyDennis J Frailey is a Principle Fellow assigned to the Future Combat Systems Ground Sensor Integrator team in Plano, TX. He is currently responsible for many roles on the program such as development and maintenance of the software development plan, chair of the software configuration control board, and sundry duties associated with selection and evaluation of software suppliers.
Dr. Frailey, who earned a PhD in Computer Science from Purdue in 1971, has been with Raytheon (and previously with Texas Instruments) for 32 years. His career includes positions ranging from college professor to developer of real-time operating systems, scientific applications, and user interfaces to speechwriter for corporate executives to software process improvement specialist. He has been head of an SEPG and was the software lead on numerous proposals.
Dennis is an ACM Fellow and Distinguished Lecturer; an IEEE Senior Member and Distinguished Visitor; and an Engineering Accreditation Evaluator. He served as vice president of ACM, conference chair and program chair for over two dozen major computing conferences, and is the author of over 100 published technical papers. In addition, he serves as an adjunct professor at Southern Methodist University, UCLA and the University of Texas at Austin. Dennis has spoken at many conferences, including keynote addresses at the SIGADA national conference, the Conference on Software Engineering Education, the Euromicro Software Engineering Workshop, and several regional conferences.
Dennis can be reached at: 972-344-8366 or [email protected]