Mission Analysis - Applying Systems Engineering - Lecture Slides, Slides of Systems Engineering

Download Mission Analysis - Applying Systems Engineering - Lecture Slides and more Slides Systems Engineering in PDF only on Docsity!

Mission Analysis

Objectives

• Discuss key terminology

• Discuss the importance of Mission Analysis

(the SE function or process)

• Understand what constitutes a “good” Mission

Definition

• Understand how to establish System

Boundaries

• Develop a Mission Plan or Mission Statement

(the SE product)

Key Terminology

• Customer Needs
• Customer Set
• Inputs
• Interfaces
• Measures of Performance
• Milestones
• Mission
• Mission Definition
• Mission Goals / Objectives
• Mission Statement
• Outputs
• Products
  • Program
  • Project
  • Requirements (top-level)
  • Resources
  • Stakeholder
  • System
  • System Boundary
  • Tailored Approach
  • Task
  • Technical Performance Measures

Where Missions Come From

The DOE Business Environment

• DOE mission’s are implemented at the Program level
• Projects are established to fulfill individual mission objectives.

"We don't have time to do all this stuff. We have to hurry up and start coding... because we have so much debugging to do!!"

Why Do Mission Analysis?

• Provides understanding and agreement of:
  • External requirements and constraints
  • Resources
  • External interfaces; understand how this “system” (project) fits into the enterprise
  • Basis for system development
  • Basis for determining success
  • Overview of problem and solution.
• The result of Mission Analysis is a good Mission Definition and

a good Mission Statement or Plan

Mission Definition

A good Mission Definition includes:

• Definition of the potential customer set

• Analysis of customers’ needs

• Description of a perceived problem/opportunity

• Initial mission description or statement

• Definition of system boundaries

• Identification of driving (system) requirements

• Initial technical performance measures

The Customer Connection

• Interest in, or influence over, your activities

and output.

• Origination of requirements

• Operants must understand the system

“customer set”

• Belief in the existence of a customer for your

system is fundamental

Omitting the Customer Examples from the INEEL

• Settlement Agreement to receive fuel shipments at the INEEL was negotiated between the State of Idaho, the U.S. Navy, and DOE
• The shipments must pass through Shoban lands, but the Shoban Tribe was not included in the negotiations.
• Shoban police parked a car on the tracks and halted the first fuel shipment pending inclusion in further negotiations.

Needs Analysis Examples

Boeing 777 Jetliner

Potential Customer Expectations Requirements Issues Constraints Assumptions Assertions Airlines Profitable airplane Safe airplane Servicing frequency Available air routes No new routes Must fit at existing airports Flying Public Safe airplane Reliable air service Cost of ticket The plane, route, time, cost, airports offered by airlines FAA certification means safe airplane FAA Good public perception of plane reflecting positively on FAA Pass required tests for certification Concerned over ―paperless‖ design and unproven technologies Federal law and regulations Boeing is competent and committed—will work with us Pilots Not difficult to fly Necessary data provided in timely, accessible manner Brand new airplane Don’t need new pilots—existing pilots can learn to fly 777 Flight Crew Sub-contractors Airport Operators 300 seats fuel efficient

What is a Problem Statement?

• A clear, unambiguous statement of the deficiency being

addressed

• May be one or multiple problems
• Should not be described in terms of a perceived solution
• Forms the basis for the Mission Statement

“If I had one hour to solve a problem, I would spent

50 minutes defining and studying the problem

and 10 minutes on the solution”

— Albert Einstein

What is a Mission Statement?

• The path forward statement—an action.
  • “Treat all waste on the site by the year 2012.”
• Flows from the problem statement
• Defines what the program expects to resolve

or accomplish

• First distributed description of the system
• Builds agreement and provides alignment on

the envisioned path forward.

How to Write a Good Mission Statement

• Use action verbs
• Expand on the problem statement and show a

clear tie back to the stated deficiency

• Limit the length to two or three sentences (no

more than a single paragraph)

System Boundary

• Identifies the “system of systems”

– What’s inside?

– What’s outside?

• Provides initial interface requirements

• Assists in identifying potential customers

• Helps ensure that the system will work

properly in its environment

Other

System

System of

Interest

Other

System

Other

System

Environment

Interfaces

Other

System

Concept of System Boundary