Copyright © 2002, Software Productivity Consortium NFP, Inc.

Systems Engineering
Started in the Middle of a Program

Jim Armstrong
Software Productivity Consortium
July 9, 2002

1
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

SCAMPI Version 1.1 Changes

Agenda

• Bahill and Briggs Process

• Alternative method
• Examples
• Summary

2
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

Bahill and Briggs Process

Analyze the Detailed WBS…
To Identify…
System

xxxx xxxx xxxx xxxx

1 2 3 4 5 6 7 8
xxxx
Project Mgt & System Test Operations & xxxx
System System Eng Integration Logistics & Evaluation Data Training Maintenance xxxx

1.1 1.2 1.3 1.4 1.5 xxxx

Product Auxiliary Spares and
Product Integration Equipment Repair Parts
Support
Equipment
Process Functions
& Test

1.1.1 1.1.2 1.1.3 1.1.4

Work Package
Infer… Generate…
Subsystem Subsystem Subsystem Subsystem

1.1.4.1 1.1.4.2 1.1.4.3 1.1.4.4 1.1.4.5

Mission
Subsystem Subsystem Subsystem Subsystem Statement
Requirements Architecture Detailed Subsystem Integration
Analysis Design Design Fabrication and Test
Requirements

Use WBS Deliverables to Define Interfaces…

And WBS Blocks

to Find Assumptions…

????

3
Copyright © 2002, Software Productivity Consortium NFP, Inc.

But What If…?

WBS?? Users??

SE?? What’s an
ICD??

4
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

Alternatively – First Understand the Big

Picture

• Who is using this product for what? Stakeholders?

• What is the intended function?

CONOPS

End Users and Environment

• What’s the intended architecture and how do the
pieces fit?
System Boundaries
(SW)

(SW)

5
Copyright © 2002, Software Productivity Consortium NFP, Inc.

Forest or Trees?

…Or Bark?

6
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

Compare and Evaluate Holes in SE

What SE should have been done..

… with what SE has been done…

… and assess risks of missing pieces

7
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

Missing Pieces

• Concept of Operations
— “…but how does it help me fight the war?”
— Radio need for anti-jam
— Any mode but the one to be used
• Requirements
— How far have you gone without a baseline?
— “anywhere in” vs “over the”
• Functionality Definition
— Launch sequence

8
 Copyright © 2002, Software Productivity Consortium NFP, Inc.
• Allocations
— Design to cost failure mode
— Undocumented allocations exist anyway
FFF uuu nnn ccc ttti iiooo nnn
DDD eee sss tttrrr ooo yyy TTT aaa rrr ggg eee ttt
GGG ooo tttooo TTT aaa rrr ggg eee ttt
PPP rrr ooo ppp eee l ll BBB uuu l lll lleee tttsss
SSS tttaaa bbb i iil lli iizzz eee BBB uuu l lll lleee tttsss
AAA i iimmm GGG uuu nnn
CCC ooo nnn tttrrr ooo l ll aaa i iirrr ccc rrr aaa fffttt
GGG uuu i iiddd eee aaa i iirrr ccc rrr aaa fffttt
P r o v id e a e r o d y n a m ic s
PP rr oo vv i i dd ee aa ee rr oo dd yy nn aa mm i i cc ss
More Missing Pieces
RRR eee qqq uuu i iirrr eee mmm eee nnn ttt CCC ooo mmm ppp ooo nnn eee nnn ttt
XXX %%% ddd aaa mmm aaa ggg eee ///hhh i iittt BBB uuu l lll lleee tttsss
+++ ///--- XXX ddd eee ggg rrr eee eee sss BBB uuu l lll lleee tttsss
+++ ///--- XXX fffppp sss GGG uuu nnn
+++ ///--- XXX bbb uuu lllllleee ttt sss ///sss eee ccc ooo nnn ddd
+++ ///--- XXX ddd eee ggg rrr eee eee sss
+++ ///--- XXX RRR PPP MMM GGG uuu nnn
+++ ///--- ddd eee ggg rrr eee eee sss MMM ooo uuu nnn ttt///aaa i iirrr fffrrr aaa mmm eee
+++ ///--- sss ttt aaa bbb iiillliiittt yyy FFF l lli iiggg hhh ttt ccc ooo nnn ttt rrr ooo l ll
+++ ///--- ccc ooo nnn tttrrr ooo l ll aaa ccc ccc uuu rrr aaa ccc yyy PPP i iil llooo ttt
+ / - s t a b ilit y & r e s p o n s e A ir fr a m e
++ // -- ss tt aa bb ii l l i i tt yy && rr ee ss pp oo nn ss ee AA i i rr ff rr aa mm ee
9
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

And more

• Traceability
• Interfaces
— Holes in walls
— Switch parity checks
— “Whats an ICD?”
• Modeling
— Behavior
— Loading analysis

10
 Copyright © 2002, Software Productivity Consortium NFP, Inc.

SCAMPI Version 1.1 Changes

Summary

• Understand the program from a systems view

• Know what should have been done
• Compare to what was done
• Determine risk of missing pieces
• Fix the high risk areas, e.g.
— CONOPS
— Requirements
— Functionality
— Interfaces

11