1Colorado Space Grant Consortium

Gateway To SpaceASEN / ASTR 2500

Class #14

2

Announcements:

3

Announcements:

- 20th year report to NASA is DONE!

- Thanks for your patience…

- If you want a copy

4

Proposals:

- I have completed my very thorough review of your proposals

- Comments given back at the end of class.

- It is only the end of the world if you don’t do anything

5

Proposals:

- Process used…

6

Proposals:

Histogram

0

0.2

0.4

0.6

0.8

1

1.2

30 36 42 48 54 60 66 72 78 84 90 96

Bin

Freq

uenc

y

7

Design Document:

- Design Document template has been posted on the website

- DD Rev B must include items from Rev A

- DD Rev A is not due Thursday

- DD Rev B is due 10/14/08 along with your CDR Slides

8

CDR:

- Conflicts with review time if at…1. 6:00 – 8:00 PM2. 5:00 – 7:00 PM

- Template is on-line

- All presentations are due at 4:00 PM via email or in person if larger than 15 MB

- Order announced Thursday.

9

Today…

- Sign-in sheet with attached letter…please sign both

- Password problem, should be fixed by Thursday

- Meeting with Kyle tonight at 5:30 PM

- If you are doing a sky brightness mission, plan on attending or sending a rep from your team with questions.

- Some hardware is here, see me after class.

10

Questions?

11

Today…

We have our first guest lecturer of the semester.

Topic is System Engineering

Let’s welcome…

Julia Chu from Lockheed Martin

12

Introduction toIntroduction toSystems Engineering Systems Engineering

Julia Chu Julia Chu October 7, 2008October 7, 2008

Some material developed by P. Robitaille and INCOSESome material developed by P. Robitaille and INCOSE

13

How Would You Define SE?

14

Systems Engineering…

• Is a systematic, interdisciplinary approach that transforms customer needs into a total system solution

• Is led by systems engineers

-But all functions play a role; Integrated via clear roles & responsibilities

•Must be rigorously applied across program

• Is the technical "glue" which makes separate design disciplines and subsystems function together to provide an integrated system which performs a specific job.

Systems Engineering is a PROCESS -Not an organization

15

The Systems Viewpoint

• The Design Engineer has the specialist's viewpoint. Views the system from the inside.

- Concerned with other system elements only as they affect their own design task; but not necessarily how theirs may affect others

• The Systems Engineer has the systems viewpoint. Views the system from the outside.

- Concerned with the effect of all system elements as they affect overall system design / performance / cost / schedule

16

Systems Engineering must focus on the entire problem: optimize the whole, not the parts!

Why Systems Engineering?

17

Systems Engineering Objectives

• Systematic elimination of less desirable concepts and early selection of a single preferred system approach.

• Early identification and resolution of critical problem areas.

• Focusing of technical expertise to match program needs.

• Maintaining compatibility among separate but interrelated technical activities.

• Maintaining technical oversight and configuration control throughout concept definition, design, implementation, and support phases.

Key objective: achieve a balanced, affordable design that meets stakeholder needs

18

Integrated Product Teams (IPTs)

Systems Engineering Integration Team (SEIT)

Program Business Support

IPT

The SEIT Provides SE Guidance & Support to other The SEIT Provides SE Guidance & Support to other IPTs which apply SE Process to their activities.IPTs which apply SE Process to their activities.

CustomerCustomer

Product 2 IPT

Product 1 IPT

Product 3IPT

Product N IPT

CustomerCustomer

CustomerCustomer CustomerCustomer CustomerCustomerCustomerCustomer

Program Management

Integrated Product Team (IPT)

19

Systems Engineering TasksState the problem Design the system Produce documentation

Understandcustomer needs

Do sensitivityanalyses

Lead teams

Discoverrequirements

Assess & managerisk

Assess performance

Validaterequirements

Do reliabilityanalyses

Prescribe tests

Investigatealternatives

Integrate systemcomponents

Conduct reviews

Define quantitativemeasures

Design & manageinterfaces

Verify requirements

Define the systemmodel

Executeconfigurationmanagement

Perform totalsystem test

Perform functionaldecomposition

Integrate projectmanagement

Re-evaluate &Improve quality

Source: UA and LM Sandia LabsNo temporal flow is intended for performing these tasks

20

Requirement Decom

position and DefinitionIn

tegr

atio

n an

d Ve

rific

atio

n

HWDrawings,

Design DocsProcurement SpecificationsMake-Buy decisions

SWSDDs,UML,

etc

Inspectionsbench test

Inspect, unittest, integrate

units into CSCs(CSC I&T)

SystemSpecs

Requirement/Integration/Verification Roadmap Systematic Build-Up of Orion Capabilities

“design to”

“design to”

ElementSpecs

SubsystemSpecs

Component, CSCISpecs

“design to”

“design to”

CSCI, Comp.T&V

Plans,Procedures,

Reports

Verify to requirements in Section 4 of Component, CSCI Specs

Verify to requirements in Section 4 of Subsystem Specs

Verify to requirements in Section 4 of Module Specs

Verify to requirements in Section 4 of Module Specs

Assemble & integrate component

Integrate CSCs into CSCI

Perform informal integration activities (tests, demos)

System T&VPlans,

Procedures,Reports

Element T&VPlans,

Procedures,Reports

Subsystem T&VPlans,

Procedures,Reports

Perform I&T & T&V according to plan

Perform formal verification & qualification

activities according to test procedures

Prepare reports documenting all formal

verification activities

Integration

21

Develop/Acquire Item2.3.6-T1-DesEng-1.0-P

Design System 2.3.4-T1-SysEng-1.0-P

Bi-directional RequirementsTraceability Bi-directional RequirementsTraceability Flow [System to Item Overview]Flow [System to Item Overview]

Traceability Flow

Task 3.5 Establish and maintain bi-directional traceability between system requirements and their allocated element…

System Requirements/Design

Element Requirements/Design

Item Requirements/Design

Task 2.5 Establish and maintain bi-directional traceability between item requirements and the higher level element requirements.

Computer Models

Part lists/Specs

Schematics

Drawings

Task 2.3 Establish and maintain… bi-directional traceability between the allotted element requirements, the detailed derived requirements and the work products…

Develop/Acquire Element2.3.5-T1-DesEng-1.0-P

Analyze System Requirements 2.3.3-T1-SysEng-1.0-P

Task 4Step 4.2

…Document…traceability to mission requirements. System requirements are flowed down to lower level requirements….

Item Requirement Database2.3.6-T1-DesEng-1.0-P W1Sect 4 The Item reqmt Database shall include

…Traceability from a reqmt to its source reqmt……Traceability from a reqmt to its derived reqmt…

Requirements/Architecture

Flowdown

22

Bi-directional Requirements Traceability Bi-directional Requirements Traceability Flow [Verification Activity]Flow [Verification Activity]

Traceability Flow

System Product/Verification

Element Product/Verification

Item Product/Verification

Computer Models

Part lists/Specs

Schematics

Drawings

Verify system2.3.8-T1-SysEng-1.0-P

Task 1.1.7

Document Verification Requirements Traceability

Task 1.4.1

The SVP (Sys Verif Plan) shall contain or reference as a minimum:•A verification matrix that provides the map from system requirements( specs and interface docs) to the verification program activities.• The SVP shall identify component configurations that shall be subject to each verification activities.

Task 1.7

…The requirements shall show the bi-directional traceability between the system requirements and their associated verification…ensuring that every product requirement is assigned at least one verification activity.

Verifi

catio

n Roll

-up

Task 1: Perform Verification Planning

Task 2.2

The procedures shall contain, as a minimum, the elements defined below:•Identification of the item and specific requirement being verified•Traceability to the requirement identifier, including references to governing plans

Task 2: Prepare for Verification Activities

Task 3.1.1

Qualification tests, design analyses, demonstrations and inspections shall be conducted to…have resulted in a product that conforms to specification requirements.

Task 3: Executing Verification

23

SE throughout Product Life Cycle

Program Life-Cycle Phases

SE Effort

SE begins with program or proposal, whichever comes first, and continues throughout a program’s life cycle

Production &Deployment

Pre-Concept

ConceptExploration &

Definition

Engineering &ManufacturingDevelopment

Disposal

Operation& Support

Demonstration& ValidationDoD 5000.2

Pre 2002

15 to 20 Percent of total engineering effort on complex development programs

Concept &Technology

Development

SystemDevelopment &Demonstration

Production &Deployment

Operations & SupportDoD 5000.2

2002-2003

SystemDevelopment &Demonstration

ConceptRefine-ment

Production &Deployment

Operations & Support

DoD 5000.22003

TechnologyDevelopment

24

Requirements TasksRequirements Tasks

• Ensure clear, consistent requirementsEnsure clear, consistent requirements• Decompose requirements from highest to lowest Decompose requirements from highest to lowest levellevel- completecomplete- unambiguousunambiguous- verifiableverifiable

• Understand constraintsUnderstand constraints- costcost- scheduleschedule- technical capabilitytechnical capability

25

• Ensure that engineers understand problem to be solved

• Provide contractual basis for verification and acceptance

• If requirements are wrong, so is everything else- architecture, design, tests

Poor Requirements yield Wrong Products!

Why are Requirements Important?Why are Requirements Important?

26

As Contracts Specified It

Why are Requirements important?

As Engineering Designed It As Materiel Ordered It

As Manufacturing Assembled It As Test Verified It What the Customer Wanted

Clearly communicating requirements is essential

27

One RequirementsRepository/Toolfor ALL Data and Disciplines

Requirements and Design

Stakeholder Needs &Mission Requirements

OperationalConcepts

System Requirements

System Architectural Design

Element Requirements

Element Design

Repeat to lowest item level Items

Q: Where do requirements end and design begin?

Proposed Changes

A: There is no dividing line. Design work at one level generates requirements for the next lower level.

28

Why is it Important to Why is it Important to Manage Requirements?Manage Requirements?

• To ensure that there is a stable, consistent requirements baseline

• To avoid requirements growth - “Better is the enemy of good” - Voltaire

• To ensure everyone is working to the same set of requirements

• To get appropriate cost impact assessments for proposed changes from all stakeholders

29

Integration TasksIntegration Tasks

• Optimize system designOptimize system design- the best solution for a subsystem may not be the best solution for a subsystem may not be the best system solutionthe best system solution

• Ensure elements, subsystems, Ensure elements, subsystems, components will all work togethercomponents will all work together- validate requirementsvalidate requirements- identify and resolve technical inconsistenciesidentify and resolve technical inconsistencies- identify and resolve interface issuesidentify and resolve interface issues

• Manage program riskManage program risk• Manage program plansManage program plans

30

Why is Integration Important?Why is Integration Important?

• Plans allow the program to execute successfully- plan the technical effort, delineate roles & responsibilities

- define tasks and schedules to accomplish the work

- allow for changes along the way• Identify problems early enough to mitigate them at low cost- What is risk? “A potential event that would be “A potential event that would be detrimental to the program as related to system detrimental to the program as related to system performance, cost, or schedule”performance, cost, or schedule”

31

Impact of SE on Program Cost

Defense Systems Defense Systems Management College - 9/1993Management College - 9/1993

Cum

ulat

ive

Perc

enta

ge L

ife C

ycle

Cos

tC

umul

ativ

e Pe

rcen

tage

Life

Cyc

le C

ost 100%100%

90%90%

80%80%

70%70%

60%60%

50%50%

40%40%

30%30%

20%20%

10%10%

0%0%

ConceptConceptPhasePhase

DesignDesignPhasePhase

Develop-Develop-mentment

Prod/TestProd/TestPhasePhase

OperationsOperationsThroughThroughDisposalDisposal

8%8% 15%15% 20%20%

100%100%

Committed CostsCommitted Costs

70%70%

85%85%95%95%

3-6X3-6X

20-100X20-100X

500-1000X500-1000X

TimeTimeFull Program ExpendituresFull Program Expenditures

50%50%

Cost to Extract Defects

Cost to Extract Defects

Typically, by the time system level design is complete, around 85% of the costs have been committed and the cost to extract defects goes up exponentially

32

Verification TasksVerification Tasks

• Ensure that the design meets the requirementsEnsure that the design meets the requirements- done at every level (component to system)done at every level (component to system)

• Start with planningStart with planning- how should each requirement be verified?how should each requirement be verified?- test, analysis, inspection, demonstration?test, analysis, inspection, demonstration?- how much is enough?how much is enough?- what is cost-effective?what is cost-effective?

• Ensure verifications are completeEnsure verifications are complete- inspection of test conditions and results, inspection of test conditions and results, analysis reports, etc.analysis reports, etc.

33

Why is Verification Important?Why is Verification Important?

• To ensure the system as built will work as planned before it becomes operational

• Customers and designers love test- some test is always needed – the key is to choose wisely- test is often the most expensive verification method- cases that are difficult to test may be better to verify by analysis

• Choosing the “wrong” verification methods may result in a failure- INTELSAT

34

Characteristics of SEs - Ability to focus on complex problemsAbility to focus on complex problems- Ability to balance risk and opportunityAbility to balance risk and opportunity- Ability to facilitate problem solving Ability to facilitate problem solving (involving various domain (involving various domain

experts)experts)- Good interpersonal communications skills Good interpersonal communications skills (to elicit (to elicit

requirements, etc.)requirements, etc.)- Excellent logic capability and disciplined work habitsExcellent logic capability and disciplined work habits- Decision making capability Decision making capability (process data and come to conclusion in (process data and come to conclusion in

a timely manner)a timely manner)- Ability to work in teams across functional boundaries Ability to work in teams across functional boundaries - Process awareness and applicabilityProcess awareness and applicability

A Systems Engineer needs to be disciplined, balance risk and opportunity, and work across functional boundaries

35

In summary, Systems Engineering:In summary, Systems Engineering:

- Focuses on defining customer needs and required Focuses on defining customer needs and required functionality early in the development cycle, functionality early in the development cycle, documenting requirements, then proceed with design.documenting requirements, then proceed with design.

- Provides early IV&V to reduce cost, schedule, and riskProvides early IV&V to reduce cost, schedule, and risk

- Integrates all the disciplines and specialty groups into a Integrates all the disciplines and specialty groups into a team effort forming a structured development process team effort forming a structured development process that proceeds from concept to production to operation.that proceeds from concept to production to operation.

- Provides confidence that a design will operate Provides confidence that a design will operate successfully.successfully.

- Considers both the business and the technical needs of Considers both the business and the technical needs of all customers with the goal of providing a quality product all customers with the goal of providing a quality product that meets the user needs.that meets the user needs.