c-17 software development process · life cycle data contractual process documented in c-17...

21
1 JRA 20 October 2005 C-17 Software Development Process Hafez M. Lorseyedi Director C-17 Systems Architecture The Boeing Company John R. Allen Senior Manager C-17 Systems Architecture Mission Assurance The Boeing Company

Upload: doanthuy

Post on 10-Jun-2018

219 views

Category:

Documents


0 download

TRANSCRIPT

1 JRA20 October 2005

C-17 SoftwareDevelopment Process

Hafez M. LorseyediDirector

C-17 Systems ArchitectureThe Boeing Company

John R. AllenSenior Manager

C-17 Systems ArchitectureMission Assurance

The Boeing Company

2 JRA20 October 2005

Introduction

� The C-17 airlifter is a software intensivesystem with an ongoing avionics upgradeprogram

� Software process is inseparable fromSystems engineering process—Robust avionics systems and software

engineering processes are critical to success—Process improvement is an essential

component of performance improvement

3 JRA20 October 2005

Topics

� C-17 Program� Avionics Systems and Software

Engineering Process� Challenges, Lessons Learned and

Improvement Strategies� Summary

4 JRA20 October 2005

Over 898,750 Flight Hours!USAF Fleet – 872,885 UK Fleet – 23,085

Over 898,750 Flight Hours!USAF Fleet – 872,885 UK Fleet – 23,085

As of 3 August 2005

C-17: A High Performance Program

4

M E E T I N G O U R C O M M I T M E N T S M E E T I N G O U R C O M M I T M E N T S

� Excellent Quality� Ahead of Schedule� On Price� 180 Aircraft Program

�� Excellent QualityExcellent Quality�� Ahead of ScheduleAhead of Schedule�� On PriceOn Price�� 180 Aircraft Program180 Aircraft Program

� 141 USAF Aircraft - 6 Bases� Worldwide Operations� Best Fleet Reliability� 4 UK C-17s Delivered

�� 141 USAF Aircraft141 USAF Aircraft -- 6 Bases6 Bases�� Worldwide OperationsWorldwide Operations�� Best Fleet ReliabilityBest Fleet Reliability�� 4 UK C4 UK C--17s Delivered17s Delivered

5 JRA20 October 2005

Delivers Heavy and OutsizeCargo into

Short RunwaysSemi-prepared

RunwaysSmall Ramps

or Narrow Body Slots

Direct Deliveries OverIntercontinental Distances into

Small Austere Airfields

Carries Airborne Troops Anywhere:“Long Flight, Ready to Fight”

Reduces Manpower: 3-PersonAircrew; Breaks Less and

is Easier to Fix

throughand/or

Unique C-17 Capability

6 JRA20 October 2005

C-17 Bed Down Locations

145 of 184 Delivered

Elmendorf ABAlaska8 A/C2007

Travis AFB13 A/C2007

C-17 Bases

Next Base

Future Bases

Brize Norton4 A/C2001

Charleston AFB50 A/C2003

C-17 SG Dover AFB13 A/C2008

McChord AFB44 A/C2004

Altus/Training15 A/C2007

Jackson ANG8 A/C2004

McGuire AFB13 A/C2005

March ARB8 A/C2006

Hickam AB8 A/C2006

7 JRA20 October 2005

C-17 Flight Software Summary

� Over 2 million source lines of code� Mix of military and commercial software� Software development/maintenance

—Approximately 50%-50% Boeing/Supplier split—Over 20 suppliers

� Many software languages—Migrating to Ada 95 and C/C+ as equipment is

modernized

8 JRA20 October 2005

Avionics Systems and SoftwareEngineering Process

9 JRA20 October 2005

Systems and Software Engineering Process

Software Code

SYSTEMS

SOFTWARE

Software Design

Configuration Audit andDelivery

System Requirements

Software Requirements

Concept of OperationsReview with Customers

System Analysis,Operational Concept,

Top level designAircraft Certificate of

Conformance

Detailed System Design

Flight Test

Unit/Integration Test

Software QualificationTest

System Test

10 JRA20 October 2005

Software Development Process

SoftwareRequirements

Analysis

SoftwareUnitTest

SoftwareImplementation

(coding)

SoftwareArchitectural

Design

SoftwareQualification

Test

SoftwareUnit

Integration

SoftwareDetailedDesignDO-178B

Mil-Std-498

Software

Life Cycle Data

Contractual process documented in C-17 Software Development Plan

11 JRA20 October 2005

Quality Journey

*CAPE = California Awards for Performance Excellence

MalcolmBaldrige

Win

MalcolmBaldrige

Win

MalcolmBaldrige

Applicant

MalcolmBaldrige

Applicant

BestPracticeExchange

BestPracticeExchange

InternalAssessment

InternalAssessment

InternalAssessment

InternalAssessment

CAPE*Applicant

CAPE*Applicant

IndustryWeek

Top 25Finalist

IndustryWeek

Top 25Finalist

IndustryWeek

Top 10Finalist

IndustryWeek

Top 10Finalist

1998 2002 2003 20042000 20011999

Incorporationof high-leverage

actions intostrategicplanning

TrainedExaminersdevelopedin-house

Deploymentof best

practicesto new

sitetenants

Quest forExcellence

andspeaking

engagements

ISOISO

InternalAssessment

InternalAssessment

Use CAPEfeedback to

improve usinginternal

Examiners

CCETeam

ExcellenceApplicant

CCETeam

ExcellenceApplicant

CMMILvl 5CMMILvl 5

CCETeam

ExcellenceApplicant

CCETeam

ExcellenceApplicant

2005

CMMLvl 3CMMLvl 3

Software process improvement is a key component in the quality journey

CMMLvl 5CMMLvl 5

12 JRA20 October 2005

C-17 Software Process Evolution

1999 2001 2002 2003 2004 2005 20062000

CMMLevel 3

CMMLevel 5

CMMIReassessment

CMMILevel 5

Airlift and Tankers Organizational ProcessC-17 Tailored Process

Process Compliance Artifacts

CMM to CMMITransition

MIL-STD-498 MIL-STD-498/DO-178B

13 JRA20 October 2005

Challenges, Lessons Learned andImprovement Strategies

14 JRA20 October 2005

Challenges and Lessons Learned

� Supplier SW management� Documentation� Managing overlapping development� Maintaining process discipline

15 JRA20 October 2005

Supplier Software Management

� Approximately half of C-17 software is developedand maintained by suppliers

� Boeing-Supplier teamwork is essential for success� Supplier Software Management Team

—Software engineering experience—Software acquisition experience

Supplier Selectionand Monitoring Processes

Software acquisition tools-Lifecycle data/product review checklists-Template Statement of Work

Repository for review artifacts

Supplier Software Metrics

16 JRA20 October 2005

Documentation

� Capturing and verifying airborne software life cycledata is a complex task—Thousands of requirements—Thousands of pages—Traceability—Milestone review entry criteria

� Solutions— Implemented DOORS— Improved product evaluations

Air VehicleRequirements

AvionicsSystem/

SubsystemRequirements

AvionicsSystem/

SubsystemDesign

AvionicsSoftware

Requirements

AvionicsSoftwareDesign

AvionicsSoftware

Code

AvionicsSoftware

Test Plans andProcedures

17 JRA20 October 2005

Overlapping Development

� Multiple Software block upgrades occursimultaneously with different effectivity

� Challenges—Laboratory Capacity—Flight Test Capacity—Manpower availability

� Solutions—Integrated block planning—Block Integration—Alternate test resources—Staff versatility—Earlier error detection –reducing late phase rework

18 JRA20 October 2005

Maintaining Process Discipline

CorrectiveAction

ProcessMonitoring

ProcessImprovements

Monitoring Methods

Training Methods

Monitoring Discipline

Training Content

MetricsAudits

19 JRA20 October 2005

Strategic Process Improvement

Continuous Improvement

SystemsEngineering

Processes

SoftwareEngineering

Processes

Value Stream/ProcessMapping

Next GenerationStrategic

ImplementationPlan

IncreasedProcess

Commonalityand efficiency

•Eliminate Redundancy•Eliminate Non valueadded steps

•Product processes•Monitoring processes•Tools

•Reduced developmentcosts•Increased staff“portability”•Reduced trainingcosts/learning curves•Reduced processmanagement costs

20 JRA20 October 2005

Summary

21 JRA20 October 2005

Summary

� Systems and software processes are inseparable—Both directly affect product delivery—Both directly affect product quality

� C-17 Software process has evolved through theBoeing quality journey—Current plans are to further optimize systems and

software processes for improved commonality andefficiency

� Process discipline is an integral part of the C-17software mission assurance strategy