Development Cycle, Reviews, and Deliverables

Question 1

Stage-Gate Model

Answer 1

Used to represents the development cycle of a product

‘Stage’ - No different than a phase
- Represented by rectangles
‘Gate’ - Usually a “Technical Review” or test where you have to show your work and justify your design decisions
- Represented by triangles

The idea is that you do some work, pause and check to make sure to was done right and that you are on the right track, then continue the project.

In order to pass on to each stage, you need to meet the criteria of the gate

Each gate has one of four outcomes
1) Go: means the project continues as planned
2) Hold: Basically purgatory, you’re not ready to ‘go’ but the project hasn’t
3) Recycle:
4) Kill: The project is over

Question 2

“Good Idea Fairy”

Question 3

DOD5000 System Lifecycle

Answer 3

Question 4

Lifecycle Standards

Answer 4

Most of the big companies have a generic standard that they use for all project

Question 5

Wasson Lifecycle

Question 6

DOD5000 v. Wasson Lifecycle

Answer 6

Question 7

NASA Lifecycle

Answer 7

Question 8

Iridium Case Study

Question 9

CDO/Housing Market Case Study

Question 10

Importance of the ‘gates’ and periodic reviews

Answer 10

Helps you catch problems earlier

No different than going to the doctor to make sure that your health is good and that there’s nothing about your diet/lifestyle you need to change

Question 11

Importance of continuously revisiting the purpose

Answer 11

Helps prevent you from diverging from what you set out to do (or what the customer asked you to do)
- This helps prevents mistakes when it comes to system validation

Question 12

Two main things that can blow up the costs for a project

Answer 12

1) Diverging from the actual purpose of the project (if you don’t catch it early, it could be very expensive to get it back on track… that’s why you constantly compare the implications to the purpose)
2) Small problems early in the design that don’t get discovered until testing (can cause you to basically startover)

Question 13

System Thinking attitude towards iteration and recursion

Answer 13

Iteration is possible in ALL phases of the design

Question 14

Technical Reviews

Answer 14

A formal Presentation where have to show your work and justify your design decisions
- Represented by triangles on the
- Commonly Referred to as ‘Gates’

• Technical Reviews always come with artifacts that you need to have ready for the presentation

Question 15

“Horseblanket”

Answer 15

Refers to the visual representation of the schedule in the form of a gate-stage model:
- Stages represented as rectangles
- Gates represented as triangles

*Can sometimes have multiple layers, like a Gantt chart

Question 16

Exit Criteria

Question 17

Technology Development Strategy (TDS)

Question 18

Test & Evaluation Strategy (TES)

Question 19

Program Protection Plan (PPP)

Question 20

Item Unique Identification (IUID) Implementation Plan

Question 21

Component Cost Estimate (CCE)

Question 22

Systems Engineering Plan (SEP)

Question 23

Systems Engineering Management Plan (SEMP)

Question 24

Test and Evaluation Master Plan (TEMP)

Question 25

Technical Reviews in DOD5000

Answer 25

Question 26

Parts of a Technical Review

Answer 26

1) Program Background
2) Program Schedule
3) Membership
4) Entry Criteria
5) Sucess Criteria
6)

[view Juan’s powerpoints for more]

Question 27

Request for Action (RFA) at the closeout of a Technical Review

Question 28

Request for Information (RFI) at the closeout of a Technical Review

Question 29

Importance of Templates

Question 30

Deliverable Templates

Question 31

Presentation Templates

Question 32

Initial Technical Review

Question 33

Alternative System Review

Question 34

System Requirements Review (SRR)

Question 35

Integrated Baseline Review

Question 36

System functional Review

Question 37

Preliminary Design Review

Question 38

Software Specification Review

Question 39

Critical Design Review

Question 40

Flight Readiness Review

Question 41

Integrated Readiness Review

Question 42

Operational Test Readiness Review

Question 43

System Verification Review

Question 44

Production Readiness Review

Question 45

Physical Configuration Audit

Question 46

In-Service Review

Question 47

Interface Control Document

Question 48

Interface Requirements Document

Question 49

“Scoping”

Answer 49

One of the first things that happen on the project.

The short version:
researching the project, talking with customers, sharing the information with stakeholders (with an emphasis on what should be included)

Project teams explore the project’s boundaries, objectives, and requirements. The goal is ensuring that all stakeholders have a clear understanding of what the project will entail and what will be delivered.

This step involves clarifying project goals, establishing initial requirements, identifying constraints, and estimating resources, which forms a foundation for project planning and design