sysarchitecting7dec05.ppt

8/22/2019 SysArchitecting7dec05.ppt

1/38

Systems Engineering

1Version 1.0 October 18, 2005

Systems ArchitectingAn introduction


2/38

Systems Engineering


Agenda

Evolution of Systems

Relating Systems

Engineering & Architectures

Representing an Architecture

Using Architectures

Summary


3/38

Systems Engineering




4/38

Systems Engineering




5/38

Systems Engineering




6/38

Systems Engineering



Systems are becoming increasingly large and complex


7/38

Systems Engineering


No Easy Answer

Modern Systems:

Ill-Structured Involve New & Untested

Ideas

Complex


8/38

Systems Engineering


Overcoming these Problems

How will we:

Manage uncertainty Manage complexity

Manage technological

change

Maybe he doesnt want

to be in charge of the

next customer review


9/38

Systems Engineering


Systems Engineering: the Process

A process that transforms an operational need or

market opportunity into a system description to

support detail design.

Requirements Analysis

Functional Analysis

Synthesis

Systems Analysis /

Management


10/38

Systems Engineering


Systems Architecture: a Product

The design teams interpretation / implementationof customer requirements communicated thru:

System Usage Scenarios (i.e., Use Cases)

Functional Components & Interrelationships

Physical Subsystems & Interfaces

Etc


11/38

Systems Engineering


Systems Architecting: a Methodology

A Segment of the Systems Engineering Process

Which Facilitates the Identification of:

System Elements Relationships

Design Principles

That Collectively Satisfy Customer Requirementsand Meet User Needs.


12/38

Systems Engineering


Process

OutputsBest Value System Architecture

System Architecture Models and Specifications

Requirements AnalysisAnalyze Missions and Environments Identify Functional Requirements

Define/Refine Performance and Design Constraints

Identify Quality Attributes

Validate Requirements

Functional Analysis & AllocationDecompose to Next-Lower Level Functions Define/Refine Functional Interfaces (Internal/External)

Define/Refine/Integrate Functional Architecture

Allocate Performance & Other Requirements

SynthesisTransform Each Levels Architecture from Functional to Physical Define Alternative System Concepts & Configuration Items

Define/Refine Physical Interfaces (Internal/External)

Identify Candidate Architecture Styles

Select Best Value Design

System AnalysisModeling & Simulation Trade Studies

Effectiveness Analysis

System

Management

Risk Management Data Management

Configuration Management

Progress Measurement

IMP/IMS & TPMs

Technical Reviews

Process

Inputs Stakeholder Inputs

Operational

Requirements

MOEs

Environments

Constraints

Capability-Based

Acquisition

Quality Attributes

Interoperability

COTS/GOTS/BOTS

Re-Use and Legacy

Technology Base

Prior Phase Results

Applied Standards

Requirements Loop

Design Loop

Verification Loop

Iteration Loop(Derived Requirements for the

Next Level of Decomposition)

Goal/Mission

Analysis/Validation

Functional

Architecture

Analysis

Physical

Architecture Analysis

Architecting in the Systems Engineering Process


13/38

Systems Engineering


The Two Primary Methods of

Architecting Structured Analysis and Design Technique (SADT)

Graphical Representation of System Requirements

Boxes and Arrows

Logical Flows

Object-Oriented Analysis (OOA) and the UnifiedModeling Language (UML)

Structure Diagrams Behavior Diagrams

Interaction Diagrams


14/38

Systems Engineering


Goals of Systems Architecting

Take into account the whole picture

Life cycle phases, boundaries, external elements

Users, builders, benefactors, supporters, environments

Affordability, safety, availability, survivability, security, etc.

Communicate clearly the components and their

inter-relationships from user and engineering

perspectives for customer validation

for use in analysis and design by all engineering disciplines


15/38

Systems Engineering


Describing the Architecture

Physical Descriptions

Behavioral Descriptions

Operational Expectations

Many perspectives: physical, functional, operational, technical


16/38

Systems Engineering


Physical View to an Architecture

Front Elevation View

Plan View

Perspective View

Building Codes

Technical Standards View

Front Elevation View

Plan View

Perspective View

Building Codes

Technical Standards View


17/38

Systems Engineering


Functional View to an Architecture(Example Based on Unified Modeling Language)

Provide Access & Mobility

Provide Space

Provide Living Space

Provide Vehicle Storage

Provide Storage

Provide Object Storage

Provide Food & Drink

Provide Nurishment

Provide Waste Disposal

Provide Physical Security

Provide Protection

Provide Physical Protection

Provide Sleeping

Provide Personal Cleaning

Provide Seating

Provide Comfort

Provide Climate

Provide Video Entertainment

Provide Audio Entertainment

Provide Computing Entertainment

Provide Telephony

Provide Human Habitat

Provide Communications &

Entertainment


18/38

Systems Engineering


Mission plan completed inplanning system, encrypted,and ready for transfer

Display menu for selecting method oftransfer of mission plan to Air Vehicle

Radio mission plan toAir Vehicle

Transfer mission plan todata transfer cartridge

Choose appropriate missionplan transfer method

Carry data transfercartridge to Air Vehicle

Put data transfer

cartridge in Air Vehicle

Air Vehicle powered up,checked out and ready formission plan

Radio receivemission plan

Receive data

transfer cartridge

Requestdecryption key

Display confirmation of missionplan & pilot acceptance

Air Vehicle ready fortaxi and operationaluse

See Mission Plan &Pilot AuthenticationUse Case

:PSS Air Vehicle:PSS Pilot:Planning System

Piloted Strike System& SoS Aggregationswith System of SystemClasses in green

Air Operations Com mander Missio n Area Commander

OperationCommander

Combat AirOperations Group

11 0..n0..n

Operation Group

11

1..n1..n

Mission Commander

Small Diameter BombP SS Air V ehic le JDAM

Flight Package

1..n1..n

11

PSS Pilot

Piloted Strike System

0..n0..n11 0..n0..n

1..n1..n

11

Perform Final Pre-Flight Tests

Taxi Solo to Point

Enter Solo Flight Holding Pattern

Take Off Solo Air Vehicle

Enter Solo Landing Approach

Taxi Solo to Taxi Hold-Point

Taxi Solo to Take Off Hold-Point

PSS Pilot

Air Traffic Controller

Land/ Taxi Solo Air Vehicle

Operation Commander

Receive Solo Mission Start

Clearance

Taxi/ Take Off Solo Air Vehicle

: PSS Pilot : PSS Air Vehicle

: AirborneTanker

: RefuelingSpecialist

Initiate Fuel FlowThrough Fuel Boom

Display Fuel Level,Report Fuel Level

Visually MonitorTanking Operation,Monitor Fuel Level

5: Radio Relay FuelingAnomaly Report(VerbalAnomaly Report : Dat a)

4: Report Fueling AnomalyStatus(Anomaly Scene :

View, Anomaly Fuel LevelData : Data)

1: Flow Fuel to AirVehicle(Initiate Fuel Flow :

Command)

3: Monitor Fueling SituationDisplay(Fuel Level : Data,

Fueling Operation Scene : View)

6: Audio Message FuelingAnomaly Report(VerbalAnomaly Report : Data ) 7: Monitor for Fueling

Anomaly Reports(Verb alAnomaly Report : Data )

Display FuelingProgress,Display InterlockLocked Status

Seq's 3, 7, and 8 areconcurrent2: Update Fueling Progress

Display(Fuel Level : Data)

8: Automatically Monitor forFuel Level andEmergencies( )

Class DiagramsUse Case Diagrams

Activity & State DiagramsSequence Diagrams

Product Diagrams of the Systems Architecture


19/38

Systems Engineering


DoDAF DoD Architecture FrameworkCustomer Defined Views of the Model

S t E i i


20/38

Systems Engineering


Operational View (OV)What needs to be done & Who does it

High Level Operational Concept Graphic (OV-1)

Operational Node Connectivity Diagram (OV-2)

Operational Exchange Matrix (OV-3)

Organizational Relationships Chart (OV-4)

S t E i i


21/38

Systems Engineering


System View (SV)Relates Systems and Characteristics to Operational Needs

System Interface Description (SV-1)

System Functionality Description (SV-4) UML Version

System Systems Matrix (SV-3)

System Functionality Description (SV-4)

S t E i i


22/38

Systems Engineering


Technical View (TV)Prescribes Standards and Conventions

System Products Associated With Standards (TV 1)Template for Time Records (TV-1)

Technical Standards Profile Template (TV-1)

S t E i i


23/38

Systems Engineering


AV 1 Overview & Summary Information

AV 2 Integrated Dictionary

OV 1 High Level Operational Concept

OV 2 Op. Node Connectivity Description

OV 3 Op. Informational Exchange Matrix

OV 4 Org. Relationships Chart

OV 5 Activity Model

OV 6a Operational Rules

OV 6b Operational State Transition

OV 6c Op. Event Trace Description

OV 7 Logical Data Mode

SV 1 Systems Interface Description

SV 2 Systems Communication Description

SV 3 Systems Matrix

SV 4 System Functionality Description

SV 5 Op. Activity to Systems Function Traceability Matrix

SV 6 System Data Exchange Matrix

SV 7 System Performance Parameters

SV 8 System Evolution Description

SV 9 System Technology Forecast

SV 10a System Rules Model

SV 10b System State Transition Description

SV 11 Physical Data Model

TV 1 Technical Architecture Profile

TV 2 Standards Technology Forecast

25 Views Integrated Together

S stems Engineering


24/38

Systems Engineering


DoDAF Summary

DoDAF isa way of describing a

system.

DoDAF representsa number of

different views of the

architecture.

DoDAF isa required output to our

customers.

DoDAF is NOTa methodology orprocess.

DoDAF is NOTa UML based set

of views.

Systems Engineering


25/38

Systems Engineering


Benefits of Architecting

Identifies All System Elements Earlier vs. Later

Matches Function to Requirements

Capture & Communicate Key concepts

Results in ONE design

Manages Increasing Complexity

Allows Modular Design

Systems Engineering


26/38

Systems Engineering


Users of the Architecture

Systems Arch i tect :Translate Client Needs into BuilderRequirements

System Designers:Design Guidance

Program Managers:Program Performance Measurement and

Guidance

Customers:Validation of Requirements and Design

Other Stakeholders:Various Views of the System*

Manufacturers - Trainers

Testers - Users

Purchasers - Logistics Personnel Handlers - Maintainers

* Adapted from: Agile Systems Engineering Architecting: Methods, Processes, and Practices

Stevens Institute of Technology, March 15, 2004

Systems Engineering


27/38

Systems Engineering


Architecture Used In

Analysis of Alternatives (AoA)

Business and Technical Planning

Communications among Organizations

Internal to Internal

Internal to External Input to Subsequent System Design and Development

Criteria for Certifying Conformance of Implementations

Development, Maintenance, and Reuse Repositories

Review, analysis, and evaluation of the system across the lifecycle

Basis for incremental/spiral development

Systems Engineering


28/38

Systems Engineering


Characteristics of a Systems Architect

Analytical

Attention to Detail

Visionary

Generalist

Common Sense

Know-How Drive

Critical Attitude

Multi-tasking

Teamwork

Communicator/Documenter Flexible

Process Insight

Political Insight/Negotiation

Systems Engineering


29/38

Systems Engineering


The Risks of Architecting

EarlyIdentification of

Problems

Perception of ProgramDelay

Inconsistent Application

of Methodologies

Limited Numbers of

Skilled Creators/

Reviewers

Systems Engineering


30/38

Systems Engineering


Risks ofNotArchitecting

Late Identification of

Problems

Lack of Unified

Design

Issues of Complexity

Management

Systems Engineering


31/38

Systems Engineering


Example Architecture Issues

Audi 2006 A8, A8 L, and A8 L W12 Passenger VehiclesOn certain passenger vehicles, a wiring harness condition exists that may

deactivate the passenger side frontal air bag even under circumstances when it

should remain activated.

Starbucks Coffee Company Recall of Ceramic TeapotsThe teapots are labeled safe for microwave use, but the handles can become

hot in the microwave oven. This poses a possible burn hazard to consumers.

Microsoft Xbox 360 Class Action LawsuitThere may be a design flaw which causes the console's power supply and CPUto overheat, causing the whole system to seize up. Complaints of similar

freezing problems began to surface almost as soon as the Xbox 360 went on

sale November 22.

Systems Engineering


32/38

Systems Engineering


Summary

Increasingly complex systems drive a need for better,

clearer design descriptions

Architectures convey the system designers

interpretation of the requirements

Architectures may be presented by a variety of views

which collectively describe the system

As part of the systems engineering process, systemsarchitecting defines and manages development of a

system

Systems Engineering


33/38

Systems Engineering


Systems Engineering


34/38

Systems Engineering


References

Boeing Systems Architecture Development Guidebook

The Art of Systems Architecting, Eberhardt Rechtin, Mark W.

Maier

DoD Architecture Framework (DoDAF)

Systems Engineering


35/38

Systems Engineering


Recommended Use of DoDAF Products

Systems Engineering


36/38

Systems Engineering


DoDAF View Extraction

Systems Engineering


37/38

y g g


Evolving Architectures: Impact of Spiral

Development

Continuous User Assessment & Col laborat ion; Sustainment & CONOPSContinuous User Assessment & Col laborat ion; Sustainment & CONOPSRefinementRefinement

CollaborativeSpirals

OCA = Ops Capability Assessment Spiral Definition / Requirements

System Technology Demo

Fieldable Prototype Demo

OCA

Integrated

Acquisition

Team

UsersUsers AcquirersAcquirers

TestersTesters

ResearchersResearchers

LogisticiansLogisticiansOCA

Production

Spiral 2

Spiral 3

OCA

OCA

Spiral 1 Development

FY02 FY03 FY04 FY05 FY06 FY07 FY08 FY09 FY10 FY11 FY12

TraditionalFY13

Development

Production

FY01FY99-00Concept Demo

Continuous User Assessment & Col laborat ion; Sustainment & CONOPSContinuous User Assessment & Col laborat ion; Sustainment & CONOPSRefinementRefinement

CollaborativeSpirals

OCA = Ops Capability Assessment Spiral Definition / Requirements

System Technology Demo

Fieldable Prototype Demo

OCA

Integrated

Acquisition

Team

UsersUsers AcquirersAcquirers

TestersTesters

ResearchersResearchers

LogisticiansLogisticiansOCA

Production

Spiral 2

Spiral 3

OCA

OCA

Spiral 1 Development

FY02 FY03 FY04 FY05 FY06 FY07 FY08 FY09 FY10 FY11 FY12

TraditionalFY13

Development

Production

FY01FY99-00Concept Demo

Systems Engineering


38/38

y g g

Model-Based Architecture

Why Model-BasedArchitectures?

Help to Explain How Things Work

Broaden Our Perspective

Provide a Common Conceptual Frame of

Reference

Express Rules More Simply

Clarify Relationships, Identify Key Elements, andConsciously Eliminate Confusion Factors

From: Forsbert, Kevin; Visualizing Project Management, Pg. 14

sysarchitecting7dec05.ppt

Documents