Program Considerations

It’s a Toaster

The "stuff" we work on is big and complex, but the principles are simple and basic. To keep the thinking simple, think of "the system" as a toaster. The same basic SE principles hold true for a toaster as any highly complex system, but we can conceptualize the application to the development of a toaster without getting lost in "interesting" technical problems.

Basic Questions

What are we doing?

What is the objective of the program?

This should be very simply and straightforwardly stated. What Designing

Complex Systems with Models and Objects calls "the essential elements of

design". Typically less than 10.

Who is the Customer?

Who is the System operator?

Who is the System's User (the user of the system's product)?

What is the System?

Physical & Logical Architecture

Key (driving) requirements "the essential elements of design".

Key Use Cases

Install

Init

Operate (and Maintenance)

FD/FI/FR

Disposal

Programmatic

What is the administrative structure of the program?

Should align with physical logical architecture

What is the Period of Performance?

What are the deliverables?

What is the schedule for deliverables?

Spec tree

Should align with physical logical architecture and administrative structure

Should include Specs (including SRS), conops documents, and ICDs

Processes & Procedures

Documented in a Systems Engineering Management Plan (SEMP)

A SEMP is important from a communication with the team perspective but even more so for being forced, by generating the SEMP, to think about and coordinate within the management team, an implementable process understood and supported by the management team. Process is essential, but fight unnecessary bureaucracy.

SEMP Content (not exhaustive)

Program phases and schedule (defines actions and products)

Products (with descriptions, include cmd media and/or DID references)

Technical Review process (with entrance and exit criteria)

CM/DM process

Change process

Tools & Techniques

Systems Engineer F&Rs

Functions: Analysis, Design, Review, Audit, Approve

Responsibilities:

Phases

Systems Engineering emphasis varies over the lifetime of the program

Program Phase Chart

SFR

- We understand what the objective is

PDR

- We have derived a notional system design

• Requirements

• Architecture

• Conops

CDR

- We have Synthesized the viable system design

Construction

- Build

- Test

• Assembly testing

• System behavior testing

• Requirement testing (Verification)

Delivery

- Training, Users Manuals

- Sell-off

Operations & Maintenance

- Field Repairs

- Upgrades