1 「軟體採購程序改善計畫 sapip 」 - 由 “section 804” 大法說起 cmmi-am 2006 年...

1

「軟體採購程序改善計畫 SAPIP 」 - 由“ Section 804” 大法說起 CMMI-AM

2006 年 11 月

國防工業發展協會科技顧問尹守紀

E-mail:[email protected]

2

內容

A. CMMI-AM （ CMMI-ACQ ）之緣由：源起於國會之不滿

B. 美國採購缺失之實例：肇因於軟體複雜性劇增與系統工程能力不足

C. 美國採購單位之改善措施：歸向於改善系統工程能量D. 美國 SEI 規劃配套 CMMI-AM 之教育重點E. 國內之可行方式由系統工程檢視軟體採購之需求定

義程序a) 由系統工程 (ISO/IEC-15288) 確認需求b) 由 (IEEE/EIA-12207) 進行程序書規劃c) 以 Products 角度建立 Program WBSd) 由 WBS 撰述 RFP 架構

3

A. CMMI-AM 之緣由：源起於國會之不滿

1. 2001 年美國政府管考辦公室或國家審計總署 (GAO) 針對國防部有關系統與軟體改善提出建議報告，該報告中建議採用 SEI 之 IDEAL Models 並列舉 SW-CMM 之相關內容以改善專案品質；但美國國防部企圖以改進 DOD 5000.2R( 已更名為 Defense Acquisition Guidebook) 方式達成 SW-CMM Level-3( 或相近似 models) 以滿足 Software Process Improvement 部分 ( 但僅針對研發案金額超過美金$3.65 億或採購金額超過美金 $21.9 億之計劃 ) ；在 DOD 5000.2R 增列 Software Management 章節，並明述承約商須具有 SEI 所發展或由採購單位認可同等 Model 之 Level-3 能力，若承約商無法達到前述目標應提出 Risk Mitigation Plan ，前述之 Level-3 appraisement 效期為 2 年；GAO 在報告之 page 35 頁亦提到“ Software Capability Maturity Model® (SW-CMM®), was designed to assist organizations in improving software development and maintenance processes.” ，未提到 Acquisition Phase之適當方法；

4

CMMI-AM 之緣由 ( 續 )

2. 由於前述建議報告未得到國防部正面回應， 2002 年 12月 2 日通過之美國國會 2003 年度國防授權法案（ National Defense Authorization Act for Fiscal Year 2003 ）針對前述之缺失提出 SEC. 804. Improvement of Software Acquisition Processes ，責令 (mandate) 國防部執行重大武器系統採購計畫 (Major Defense Acquisition Program) 須進行軟體採購過程改善，同時在 Section 804 附註Major Defense Acquisition Program 之定義應參用美國聯邦法典 section 139(a)(2)(B) of title 10, United States Code 之解釋，意即研發案金額超過美金 $3 億或採構金額超過 $18 億者；

5

CMMI-AM 之緣由 ( 續 )

3. Section 804 條列應執行事項有1)對於 (1)software acquisition planning, (2)req

uirements development and management, (3)project management/ oversight, 及 (4)risk management. 等程序應有文件紀錄；

2)對於計劃執行效能應進行度量評估暨進行持續改善；

3)採購專案之關鍵執行工程人員應具有適當之經驗與軟體採購訓練；

4)每一軍事採購單位應確實遵循既訂採購程序與需求執行軟體相關專案採購；

2002.12.02國會於 Section 804 提出四項改

善領域

6

採購單位之程序改善承諾：美國國防部針對 Section 804 的改善措施

1. 美國國防部針對 Section 804 的要求，擬定了 8 項改善領域；2. Section 804 責令國防部應於該法案生效日起 120 天內開始執

行，因此國防部各採購單位配合 Section 804 完成下列措施：1) 成立 Software Acquisition Process Improvement Program

(SAPIP) ，2) 重新訂定諸如 Acquisition Guideline 之採購指引，3) 參用實獲值工程 ANSI/EIA-748-A-1998 EVMS 進行效能監控，4) 各單位依據需要分別選用 CMMI、 SA-CMMR、 FAA-ICMM、

或混合使用以配合 SAPIP 執行 Acquisition Process Improvement ， ( 所選用類型極為繁雜；因此國防部認為有必要規劃 CMMI-based acquisition model ，此即後續 CMMI-ACQ 之發軔；先期規劃有 CMMI Module for Acquisition (http://www.sei.cmu.edu/news-at-sei/features/2005/1/feature-1-2005-1.htm) ，其對象係針對 system project offices/program managers (http://www.sei.cmu.edu/acquisition/acquisition.html)) ；

2003.03,21美國國防部增列為八項改善

領域

http://www.sei.cmu.edu/news-at-sei/features/2005/1/feature-1-2005-1.htm

http://www.sei.cmu.edu/news-at-sei/features/2005/1/feature-1-2005-1.htm

http://www.sei.cmu.edu/acquisition/acquisition.html)



FY03 Defense Authorization Act Section 804

• Requires Services and applicable Agencies establish “software acquisition process improvement programs” within 120 days (March 2003)

• Army, Navy, Air Force• MDA, DISA, DLA, DFAS, and Health Affairs

• Requires ASD(NII) and USD(AT&L) to…• Prescribe uniformly applicable guidance• Ensure compliance by Service/Agency Components

• Section 804 approach to Component implementation identified eight process improvement areas:

1) Acquisition Planning2) Requirements Development and Management3) Configuration management4) Risk Management5) Project Management and Oversight6) Test and Evaluation7) Integrated Team Management8) Solicitation and Source Selection

• Past performance, Process maturity, Product maturity

2003.03,21揭示採購單位必須改善之 8項領域

： Section 804 要求領域

：美國國防部另增領域

© 2005 by Carnegie Mellon University CMMI Acquisition Module - Page M2-8

CMMI ®

CMMI-AM and Project Management v0.1

CMMI Acquisition ModuleV 1.1

Engineering SupportProject

Management

• Project Planning• Project Monitor and Control• Integrated Project

Management• Risk Management• Solicitation and Contract

Monitoring

• Requirements Management

• Requirements Development

• Verification• Validation

• Measurement and Analysis

• Decision Analysis and Resolution

• Transition to Operations and Support

CMMI-AM Structure

KeyNew for CMMI-AM

： Section 804 要求領域

：美國國防部另增領域

2005.05.15SEI 配合 Section 804 規劃之 CMM

I-AM 的架構

9

B. 採購缺失之實例：肇因於軟體複雜性劇增

C-17 運輸機 Boeing 公司設計（ 2003.

12.04取得 CMMI SW/SE/IPPD/SS Level 5 ）

1985 年計畫開始規劃有 4項軟體相關系統，估計有 164,000 lines-of-code.

1990 年檢討時軟體相關系統遞增為 56 項，總計有 1,356,000 lines-of-code, 內含新增功能 643,000 lines-of-code,

© Copyright Lockheed Martin Corporation 2003Joan Weszka -

10

1 1 / 1 9 / 0 3© C o p y r i g h t L o c k h e e d M a r t i n C o r p o r a t i o n 2 0 0 3

J o a n W e s z k a - 2 3

L M M a r i t i m e S y s t e m s & S e n s o r s – U n d e r s e a S y s t e m sP r o c e s s I m p r o v e m e n t R e t u r n - o n - I n v e s t m e n t S u m m a r y

N o t e : O t h e r i n i t i a t i v e s u n d e r w a y d u r i n g t h i s p e r i o d i n c l u d e

• I S O 9 0 0 1 r e g i s t r a t i o n , f o l l o w e d b y A S 9 0 0 0• I n t e g r a t e d T e a m i n g , a n d c r e a t i o n o f a n I n t e g r a t e d P r o c e s s L i b r a r y• I n t e g r a t i o n o f S y s t e m s E n g i n e e r i n g a n d S W E n g i n e e r i n g

S W - C M M ® L e v e l 3



C M M I ® L e v e l 5

I m p r o v e m e n t M e t r i c 1 9 9 0 1 9 9 5 1 9 9 9 2 0 0 2Q u a l i t y D e f e c t s / M D S S 6 0 0 3 0 0 1 5 0 5 1P r o d u c t i v i t y E S S / L a b o r M o n t h 2 2 0 2 8 0 3 4 0 3 7 9C o s t & S c h e d u l e + - V a r i a n c e 1 5 % 1 0 % 8 % 8 %R e w o r k e x p r e s s e d a s a %

o f i n d u s t r y a v g 6 % 3 % 2 % 2 %R e u s e P e r c e n t 6 8 % 7 5 % 8 2 % 8 2 %

2003年由 LM Martine所分享之 CMM/CMMI效益

11

2006 年 GAO 對 6 項合約成效之檢討

檢討結論：預算超支、時程落後


CMMI ®

•M1-Background v0.1

KS

LO

C

F/A-18C/D SMUG/RUG 14268K

F/A-18E/F17101K

F/A-18C/D XN-86629K

F/A-18 Night Attack3054k

F/A-18C/D 2130K F-14D416K F-14B 2866K

A-7E16K

F-14 80K

A-4 (ARBS) 16K

A-6E 64K

F/A-18A/B 943K

F-14B 364K

AV-8B NightAttack 1780K

AV-8B Radar 3748K

AH-1 NTS 1000KAH-1 764KA-E SWIP 364KAV-8B 764K0

3000

6000

9000

12000

15000

18000

66 70 74 78 82 86 90 94 98 02Aircraft IOC, Year

EA-6B ICAP2BLK 89 2203K

E-A6B ICAP148K



06 10

•JSF•UAVs•NCW•Inter-System Operability

Increasing System Complexity

造成預算超支、時程落後原因之ㄧ為軟體複雜性劇增

複雜性為人月神話所歸類於固有性軟體問題


CMMI ®

•M1-Background v0.1

Functionality Provided by Software in DoD Systems is Increasing

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

1960 1964 1970 1975 1982 1990 2000

% o

f fu

nc

tio

na

lity

SW

pro

vid

es

Ref: Defense Systems Management College

F-4 A-7

F-111

F-15F-16

B-2

F-22

造成預算超支、時程落後原因之二為軟體比重遽增

如人月神話之“ No silver bullets”所敘述將因為 Project Team的溝通問題導致 Cost overruns and schedule delay

14

Industry Views - Current SE Issuesbased on Performance Factors Summit, June 2 & 3, 2004

• Despite high maturity prime contractors (i.e. CMMI Level 5) there are still significant problems on major DoD programs

• Systems Engineering is often not performed because:– PM will not fund (viewed as “overhead”)– Programs tend to be “back-loaded”, insufficient front-end funds– PM voids contractor process maturity by tailoring critical items out of a

program– PM typically feels need to start coding/designing immediately– Many major primes will not engage their subs in the top-level SE process

(believing this to be sole responsibility of the prime)• And yet Boeing only builds 38% of F/A-18 E/F, Lockheed 36% of F/A-

22, etc

• PM and contractor often unable to distinguish between real requirements and implied requirements (often driven by user representative) Requirements not properly interpreted/followed

• Many of the “software problems” on programs are not really rooted in software or software engineering, but are really software “content” issues (algorithms, operational flows, functional analysis) which is related to systems engineering

15

C. 採購單位之改善措施：歸向於改善系統工程能量

Software Process Improvement Roadmap

Public Law 107-314,

Section 804

OSD Software Acquisition

Process Improvement

IIPT

Air Force Software Intensive Systems

Strategic Improvement

Program (AFSSIP)

Tailored Application by PEOs/Centers

Policy

Guidance

Training

AFSSIP Products

美國國防部執行軟體採購程序改善 SAPIP 之架構

16

重點在 Pre-Acquisition Process

1

Acquisition Process Model

Cross-reference Matrix

RFP

ProgramObjectives

(SOO)

ACQUISITION STRATEGY

Contract Type/LengthMajor Milestones/EventsCompetition ApproachBudget/Reqmt Refinement

EvalCriteria

ITO

RD

Proposals

Proposals

So

urc

e

Se

lec

tio

n

CONTRACTAWARD &

EXECUTION

SSP Factors

Proposals

RFP DEVELOPMENT

ModelContract

ASP PRAG

POST AWARD PLANNING& RISK MITIGATION

Resources

Schedule

Industry Base

Direction

Technology

Requirements Document

User

Funding

Program Office Size/IMP/IMS/WBSSAMP/Acq PlanEarned Value ManagementDCMC OversightTest Planning/Tech Program MeasuresCDRLs/MetricsIncentive/Disincentive Eval

RiskAssess-

ment

美國國防部執行軟體採購之程序

17

Operational Concept

MNS

STAR

TRD Scenario

GovernmentUsers/Operators

GovernmentAcquisition

Contractor

System SpecVerification

Plan

Seg X Spec Seg Y Spec Seg Z Spec

Sub X-1 Documentation Sub Z-1 Documentation

Sub Y-1 Documentation

CONOPS

SPG

TEMP ORD

Government & Contractor Responsibilities

CRD

參考 CMMI 之 Requirements Development [PA157.N101]

參考 CMMI 之 Requirements Development [PA157.N108]

有標準規範可參考

無標準規範可參考 (TEMP除外 )

18

Acquisition 在 Life Cycle 之程序關係 (1)

Disciplined

Flexible

Maturity Level

Maturity Level?????

19

Acquisition Process (based on 12207)

• Initiation• describe needs• define system reqr• define software reqr (?)• prepare acquisition plan• define acceptance strategy

• Tender (RFP)• document acquisition reqr• determine processes• define references to

contract• set review milestones

• Contract Preparation and Update• establish supplier selection

procedures• select supplier• tailor 12207 and involve

parties• negotiate contract

• Supplier Monitoring• monitor in accordance

with joint review and audit process

• supplement with verification and validation

• Acceptance and Completion• prepare for acceptance

including tests• conduct acceptance

review/testing• accept deliverables• assume configuration

management

目前並無 Standards敘述”Needs” 之 activity ， CJCAI-3170 以外

可參考美國採購法 FAR 15.203

可參考採購部門之程序書

20

美國國防部執行 SAPIP 之改善事項

1. 修定國防部之採購規範 Policy/Guidance1) 採購管理部份： (1)DFARS 、 (2)DoD Directive 5000.1 Def

ense Acquisition System、 (3)DoD Instruction 5000.2 Operation of the Defense Acquisition System、 (4)Defense Acquisition Guidebook

2) 需求管理部份： (1)CJCSI 3170.01E Joint Capabilities Integration and Development System、 (2)CJCSM 3170.01B Operation of the Joint Capabilities Integration and Development system

3) 各執行單位自行修訂相關之程序書2. 針對 8 項 process area 進行流程改善且均一化各單

位之 Guidance3. 補強採購程序之教育訓練4. 有效監控各採購單位是否落實 Acquisition Guidance

21

美國國防部執行 SAPIP 之改善事項 ( 續 )

5. 選商必須考量廠家 Past performance並評估 Product maturity與 Process maturity（方法可包括 CMMI、 ISO-9001、 EIA-731、 SDCE、 J-STD-016、 ISO/IEC-12207、… . ，統稱之為“ best practices” ）

6. 建立 software development and acquisition之 best practices的資料交換中心 (clearinghouse)

7. 強化 Life Cycle Cost 之 Acquisition Model ： Evolutional Acquisition Spiral Development model

8. 採用實獲值工程 (Applying Earned Value Management to Software) ：有助於了解軟體專案之“健康”狀態

9. 可考量採用 Best Practice (CMMI-AM 為其中之一 ) 對於採購單位與專案計畫之 SAPIP 成效進行 measurement

SDCE: Air Force Aeronautical System Center’s Software Development Capability Evaluation

CDSC-PM , 17 July 03 - 22

DOTMLPF

MS A

Analysis of Materiel

Approaches

Demo

Demo

Demo

AoATechnology

Development

DABJROC

MS B

MS B MS C

MS C

- -MaterielProcess

DOTLPFChange

FunctionalArea

Analysis

Functional AreaFunctional Concept

Integrated Architecture

Overarching Policy

NSS/NMS/Joint vision

Joint Capstone Policy

Feedback

ICD ConceptRefinementCD

Oversight

RequirementsAcquisitionIntegrated Decision MeetingsIntegrated Decision Meetings

Increment 1

New

MS B

CDD

DABJROC

MS C

CPD

DABJROC

Increment 2

Increment 3

Fig. 2, DoDI 5000.2

Requirements & Acquisition Process Requirements & Acquisition Process

DoDI 5000.2 文件規範採購程序

23

Working Against the Plan• As Work Is Performed, Earned Value

Is Claimed and Actual Dollars Are Expended

– earned value = budgeted cost of work performed (BCWP)

– actual cost = actual cost of work performed (ACWP)

• Cost Variance (CV)– CV = BCWP - ACWP

• Schedule Variance (SV)– SV = BCWP - BCWS– units of dollars, NOT time!– INDICATOR of being “on plan”

• Percent Complete, Percent Spent– % complete = BCWP / BAC– % spent = ACWP / BAC

Time

Schedule End

BAC

BCWS

ACWP

BCWP

CVSV

Dol

lars

Now

實獲值工程EVMS

24

Work Instructions

Applying Best Practices

TailoringRecords

Process DeploymentContinuous

ProcessImprovement

Process Baseline

Framework Standards

Tailoring

Validation

Evaluation

Performance

Supporting Standards

Standards-Based Knowledge Products

IEEE/EIA 12207

ISO/IEC 15288

IEEE 830

IEEE 830IEEE

830

TrainingMaterials

IEEE Standards-

Based Training

P&P

PAL Action Plans

Process Improvement

Plan

TrainingMaterials

Management Plans

Performance

Findings

EvaluationReports

* From work by Paul Croll, Chairman of IEEE CS Software Engineering Standards Committee (SESC), 2002

25

D. 美國 SEI 規劃配套 CMMI-AM 之教育重點

a) 由 IDEAL Model轉入 CMMI-AMb) PM自行依據 SEI’s questions 執行 CMMI-AM Self-

Assessmentc) 強化 PM 與 Contractor 之間的 Information Exchan

ge、 Products Evaluation & Measurement、 Schedule/Cost Evaluation & Measurement

d) 強化需求工程以完成 Customer’s requirementse) 強化 Acquisition Method ： Evolutional Acquisitio

n-Spiral Development


CMMI ®

M6-Process Improvement v0.1

Using IDEAL to adopt CMMI-AM 1

IDEAL:Initiate, DiagnoseEstablish, Act, Learning

Set Context

Stimulusfor Change

Set Priorities

Plan Actions

Create Solution

Analyze & Validate

Learning

Acting

EstablishingDiagnosing

InitiatingCharact-

erizeCurrent

& Desired State

Develop Recom- endations

Pilot/TestSolution

RefineSolution

Implement Solution

Propose Future Actions

Build Sponsorship

Charter Infra-

structure

SM IDEAL is a service mark of Carnegie Mellon University.

a) 由 IDEAL Model轉入 CMMI-AM


CMMI ®

M6-Process Improvement v0.1

CMMI-AM Self-Assessment

To guide the PM in assessing the acquisition program, the CMMI-AM includes a series of questions focused on:

• Acquisition Strategy

• Acquisition Planning

• Cost Schedule and Performance Baselines

• User Requirements

• Product Engineering

• Acquisition Processes

• Risk Identification and Management

Questions are linked to the CMMI-AM Process Areas

b) PM自行依據 SEI’s questions 執行CMMI-AM Self-Assessment


CMMI ®

M4 – CMMI-AM and Support v0.1

Roles and Information Exchange

Status Information

• Monitor & oversee progress

• Quality of tangibles

Develop,customize,integrate

• Software• Systems• COTS

PMO Contractor

Directions, Corrections

Deliverables

Interim Documents, Tangibles

Functional RequirementsPre-award

activities

Post-award activities

• RFP prep.• Contract Award

Sub-contractors

c1)強化 PM與 Contractor 之間的 Information Exchange


CMMI ®


Evaluate Quality of Deliverables

PMO’s Inspection or Review Process

Measurable Results (Examples)

Products• defects discovered

– description, severity, class, type

• size of the work product

Process• effort invested in the inspection

process• time spent during the inspection

activitiesPMO’s Evaluation

Criteria

Documents to review

• SRD• SDP• Meas Plan• SDD• Etc.

Indicators

Final Deliverables

c2)強化 PM 與 Contractor 之間的 Products Evaluation & Measurement


CMMI ®


Monitor and Oversee

PMO’s Analysis &

Review Process

Measurable Results (Examples)• contractor effort actual vs. plan• contractor schedule actual vs.

plan• defects reported

• description, severity, class, type

• size, complexity of the work product

Status Information

• schedule progress

• budget status

• test results

• process results, e.g. inspections

• Process compliance

• etc.

Indicators

PMO's Evaluation

Criteria

c3)強化 PM 與 Contractor 之間的 Schedule/Cost Evaluation & Measurement


CMMI ®

CMMI-AM and Engineering v0.1

Requirements and DoD Acquisition 2

Operational Need

AoAJCIDS

Users

JROC ICD CDD

PMO Supplier

Requirements Development

RFP, SOW, SOO, etc.

User validation

User input Analyze requirementsDerive requirements

Allocate requirements

System

Sub-systems

Component

Sub-systems

Component

Component

d1)強化需求工程：找出 Needs


CMMI ®


Overly simplistic elicitation

Failure to identify / validate “root” of the requirement

Lack of attention to stakeholder requirements

Failure to involve all stakeholders

Develop Customer Requirements

• Collect stakeholder needs• Elicit needs• Develop customer requirementsTypical Work Products

•Customer requirements

•Customer constraints on the conduct of verification

•Customer constraints on the conduct of validation

Sample Key Issues

d2)強化需求工程：找出 Requirements


CMMI ®


Requirements Must be Balanced

Adapted from COTS-Based Systems for Program Managers

Marketplace

Stakeholder Needs / Business Processes

Programmatics/ Risks

Architecture / Design

Simultaneous Definition & Tradeoffs

d3)強化需求工程：找出平衡點


CMMI ®


Acquisition MethodMethod Req’ts Technology Schedule Comments Example

Single Step All known at start

All Mature at start

No need for early deployment

Software requirements must also be stable

New utility truck

Evolutionary - Incremental

All known at start

Technology for first increment mature

May be a need for early deployment

Could have incremental software and single-step hardware

Missile with improved range over 2-3 increments

Evolutionary - Spiral

Req’ts for first spiral known at start

Technology for first spiral mature


Spirals may also be for risk reduction – not deployment

A communi-cation system with new interfaces yet to be defined

e1)EASD


CMMI ®


Single-Step and Evolutionary Acquisition

100%

Based on AF Program Manager Workshop presented by Mr Little

Single-Step

Time

Known increment

‘Deliverable’ Capability

100% of requirements known at start

100% of requirements known at start

Known increment

Partially known

increment Unknown increment Unknown

increment

Only first increment requirements known at start

Incremental

Spiral

Known increment Known increment

User, developer, tester, sustainer “use and learn”

e2)EASD


CMMI ®


Evolutionary Approach

CR TD SDD PD OS

B

Increment 2

Increment 3

A C

B C

B C

Increment 1

Adapted from dod5000.dau.mil

= Contractor Spiral Development

= Contractor Incremental Development

e3)EASD


CMMI ®


Evolutionary Approach (Space)

PreKDP-A

Phase AStudy Phase

Phase BDesign Phase

Phase C (Build, Test Launch)

B

Increment 2

Increment 3

A C

B C

B C

Increment 1

Adapted from NSS 03-01 and dod5000.dau.mil

= Contractor Spiral Development

= Contractor Incremental Development

e4)EASD


CMMI ®


Acquisition & Development Methods

= fielded system

Acquisition of a New Utility truck

Single Step Acquisition, Contractor Incremental Development

Increment 1 – Hard to produce brakes

Increment 2 – Easier to produce brakes

Inc 3 – Develop new interfacesSpiral 1 – Prototype 1

Spiral 2 – Prototype 2

Spiral 3 – Prototype 3

Inc 2–SW radios for existing interfacesIncrement 1- Interface 1

Increment 2- Interface 2

Inc 1 – HW UpgradesSingle Step Development

Evolutionary Acquisition (Spiral), Contractor Mixed Development– Comms System

e5)EASD

39

AFSPC- SMC “Customer-Supplier”

KeyKeyDecisionDecision

Points:Points:

Draft USECAF Space Acq Policy 02-1

Pre-Pre-AcquisitionAcquisitionApprovalApproval

PHASE BPre-AcquisitionSys Def & Risk

Reduction

Acquisition & Acquisition & OperationsOperationsApprovalApproval

PHASE AConcept

DefinitionStudies

ConceptConceptDefinitionDefinitionApprovalApproval

PHASE CAcquisitions

andOperations

CBA

SRRSRR SDRSDR PDRPDR CDRCDR

1st Launch1st Launch

Pre-Systems Acquisition Systems Acquisition Sustainment & Disposal

EVOLUTIONARY REQUIREMENTS DEFINITIONS

NEED ANALYSISSUPPORT

TECHNOLOGYOPPORTUNITY

ALTERNATIVECONCEPTS

REDUCEDRISK

ALTERNATIVES

DETAILEDDESIGN

PRODUCTION & REFINED

FINALDESIGN

PRODUCTIMPROVEMENT

MNS

ORD

1

ORD

2

PPBSPhase

APhase

BPhase

C

APPROVALAS

REQUIRED

MOD

REQ

Responsibility of AF/DoD/AFSPCResponsibility of SMC and any contractor

40

E. 國內之可行方式

a) 由系統工程檢視軟體採購之需求定義程序b) 由 IEEE-12207 之 Acquisition process 進行程序

書規劃c) 建立 CM、 V&V、 Performance Monitor、 Revi

ew/Audit、 Risk Management 之專業工程d) 以 Products 角度建立 Program WBSe) 由 WBS 撰述 RFP 架構f) 需求不明確之計畫應採用 Evolutional Acquisitio

n – Spiral Development modelg) 新開發需求軟體專案應採用成本計價 (Costing)

41Slide 41

System/Subsystem Design Description (SSDD)System Specification (SS) (MIL-STD-961D)

Requirements

Requirement: “Noun shall verb.” Example: The car shall stop within 100 feet at 50 mph.

Functional PerformanceFunction: “Verb Noun.” Example: Stop Car or “Verb-ing.” Example: Stopping.

Component: “Noun.” Example: Brake.

Functions Components

System/Subsystem Specification (SSS)System Requirements Document (SRD)System Requirements Specification (SRS)

(SSDD/SS)

What is Systems Engineering? (cont)

JOCKey Terms and Relationships

由系統工程檢視軟體採購之需求定義程序

42

由 IEEE-12207 之 Acquisition process 進行程序書規劃

由 IEEE-12207 之 Acquisition process 進行程序書規劃

WBS/ 43/9180

“Family tree“ 是一種圖示表達方式，輔助讀者易於了解下層 Components 如何組成上層 Compo

nents。“Major

Element”, or “Prime Mission

Equipment”, or “Prime Mission

Product”

Common WBS

Elements

Aircraft SystemsWork Breakdown Structure 範例

Aircraft System

Air Vehicle Training Peculiar Support

Equipment

SystemT&E

Sys Eng./ Program

Mgmt

Data Opn'l/SiteActivation

CommonSupport

Equipment

IndustrialFacilities

InitialSpares

& RepairParts

Level 1(Program Level)

Level 2(Project Level)

Equipment

Services

Facilities

DT&E

OT&E

Mockups

T&ESupport

TestFacilities

Construction/Conversion/Expansion

EquipmentAcquisitionor Mod

Maintenance

Level 3(System Level)

Airframe

Propulsion

Application Software

System Software

Comm's/Identification

Navigation/Guidance

Central Computer

Fire Control

Data Display & Controls

Survivability

Reconnaissance

Automatic Flight Control

Central IntegratedCheckout

Antisubmarine Warfare

Armament

Weapons Delivery

Auxiliary Equipment

Test &MeasurementEquipment

Support &HandlingEquipment

TechPubs

EngData

SupportData

ManagementData

DataDepository

Test &MeasurementEquipment

Support &HandlingEquipment

Sys Assembly,Installation &Checkout onSite

ContractorTech Support

SiteConstruction

Site/ShipVehicleConversion

“Major Program

”

44

由 Requirements/WBS/SOW轉換為專案之 IMP 以及 IMS

Requirement WBS Elements SOW Task

System Specification

1000 Air Vehicle

1100 Airframe

1110 Wing

1000 Air Vehicle

1100 Airframe

1110 Wing••

1189 Landing Gear

3.1 Air Vehicle (WBS 1000)

Design, develop, produce and verify, complete air vehicles, defined as airframe propulsion, avionics and other installed equipment.

Integrated Master Plan

Management Plan Events Accomplishment Criteria

1.Preliminary Design Review PDR 1.a. Duty Cycle Defined

b. Preliminary Analysis Complete

Integrated Master Schedule

Detailed Tasks 20XX

Program Events

1. Preliminary Design complete

Duty Cycle Defined

20XX 20XX

PDR CDR

20XX 20XX

Requirement WBS Elements SOW Task

System Specification

1000 Air Vehicle

1100 Airframe

1110 Wing

1000 Air Vehicle

1100 Airframe

1110 Wing••

1189 Landing Gear

3.1 Air Vehicle (WBS 1000)

Design, develop, produce and verify, complete air vehicles, defined as airframe propulsion, avionics and other installed equipment.

Integrated Master Plan

Management Plan Events Accomplishment Criteria

1.Preliminary Design Review PDR 1.a. Duty Cycle Defined

b. Preliminary Analysis Complete

Integrated Master Schedule

Detailed Tasks 20XX

Program Events

1. Preliminary Design complete

Duty Cycle Defined

20XX 20XX

PDR CDR

20XX 20XX


CMMI ®


Acquisition MethodMethod Req’ts Technology Schedule Comments Example

Single Step All known at start

All Mature at start

No need for early deployment

Software requirements must also be stable

New utility truck

Evolutionary - Incremental

All known at start

Technology for first increment mature


Could have incremental software and single-step hardware

Missile with improved range over 2-3 increments

Evolutionary - Spiral

Req’ts for first spiral known at start

Technology for first spiral mature


Spirals may also be for risk reduction – not deployment

A communi-cation system with new interfaces yet to be defined

需求不明確者應選用 Evolutionary-Spiral model

1 「 軟體採購程序改善計畫 sapip 」 - 由 “section 804” 大法說起 cmmi-am 2006 年...

Documents

1 「軟體採購程序改善計畫 sapip 」 - 由 “section 804” 大法說起 cmmi-am 2006 年...