week 6 - systems engineering and analysis

1

Week 6 - Systems Engineering and Analysis

Buede ch 8 & Wasson ch 40 – Physical Architecture

Believe it or not – we’ll even apply this topic to the “Newton free” world of software!

Image of “Second Life” from http://secondlifetalk.com/.

http://secondlifetalk.com/

2

Functional vs. Physical

Functional• What the system must

do.

Physical• How the system will do

it.

Buede starts here – for Wasson, see slide 47!

3

Physical Architecture

• Provides system resources for every function in the Functional Architecture

Resource types :– Hardware– Software– Facilities– People– Procedures

4

Physical Architecture-2

• Must be a Physical Architecture for each system associated with the system life cycle.

• Two types of Physical Architectures :

– Generic and Instantiated.

5


For software:• We are used to having a design

experience that feels free of physical limitations!

Don’t like the way the world actually looks? Add/change/delete your own features!

Image from http://www.indiamike.com/india/chai-and-chat-f73/nasa-world-wind-software-t12187/

http://www.indiamike.com/india/chai-and-chat-f73/nasa-world-wind-software-t12187/



6


For software:• “Physical” means “real” – like:

– What families of components would we choose?

– What “bottom up” characteristics would fit?• Without going all the way to naming those pieces

• But this is systems engineering, and we also can learn from design work that does have some physical reality…

7

Generic Physical

Architecture for Elevator

Elevator CallAnnouncem ent

Com ponent

DestinationControl

Com ponent

DoorControl

Com ponent

Em ergencyCom ponent

PhoneCom ponent

Car ControlCom ponent

PassengerInte rface

C om ponent

CabCom ponent

Interior DoorCom ponent

Ventilation& Lighting

Com ponent

Car Com ponent Shaft StructuralCom ponent

Exit Com ponent& Controls

Floor StopCom ponent

LevelingCom ponent

Shaft Sw itchCom ponent

Norm alD rive /BrakeC om ponent

E m ergencyBrak ing

C om ponent

D rive /BrakeC om ponent

E leva torC ar/S ha ft

C om ponent

Hardw areC om ponent

S oftw areC om ponent

C ontro lC om ponent

M a intenance& S e lf-T es tC om ponent

Eleva tor System

Figure 8.2

USED AT: CONTEXT:

NODE: TITLE: NUMBER:

AUTHOR:PROJECT:

NOTES: 1 2 3 4 5 6 7 8 9 10

DATE:REV:

WORKING

DRAFT

RECOMMENDEDPUBLICATION

READER DATE

P.

A-0

3

xElevator Case StudyDennis Buede

George MasonUniv.

09/29/1999

PROVIDE ELEVATOR SERVICESA0

ACCEPTPASSENGERREQUESTS &

PROVIDEFEEDBACK

A1

CONTROLELEVATOR

CARSA2

MOVEPASSENGERS

BETWEENFLOORS

A3

ENABLEEFFECTIVE

MAINTENANCE& SERVICING

A4

DigitizedPassengerRequests

Assignmentsfor ElevatorCars

ElevatorPosition &Direction

Sensed Malfunctions,Diagnosis &Test Responses

TemporaryModificatin to

ElevatorConfiguration

ElectricPower

ElectricPower

Up Service Request,Floor Request,

Request to Extend Entry support

Relayed Info about Emergency,Electric Power,Sensed Building Heat

Comm. about Emergency,Passenger Weight Characteristics,Sensed Passenger Heat Loss/Gain

Maint. Action,Diagnosis Signals,

Repairs,Test Signals

Diagnosis Response,Test Response

MalfunctionSignal

Feedback: Service Request Recieved,

Floor Request Received, Car On Way,

Door Opening, Door Closing,

Floor Where Stopped, About Emergency;

Fire Alarm;Entry/Exit Opp'y Ending Signal;

Capacity Exceeded Signal

EmergencyComm'n

Elevator Entry/Exit Opportunity,

Information about Emergency,Elevator Heat

Loss/Gain

Fire Alarm SignalSignal for Partial Maint. Mode,Signal for Full Op'g Mode


Up Service Request,Floor Request





Fire Alarm

Entry/Exit Opp'y Ending Signal;


OperatingMode

Diagnosis Signals,Maint. Action,Repairs,Test Signals

8

Elevator First Level Functional Model

USED AT: CONTEXT:


AUTHOR:PROJECT:

NOTES: 1 2 3 4 5 6 7 8 9 10

DATE:REV:

WORKING

DRAFT


READER DATE

P.

A-0

3


George MasonUniv.

09/29/1999



PROVIDEFEEDBACK

A1

CONTROLELEVATOR

CARSA2

MOVEPASSENGERS

BETWEENFLOORS

A3

ENABLEEFFECTIVE


A4







ElectricPower

ElectricPower








MalfunctionSignal







EmergencyComm'n



Loss/Gain








Fire Alarm



OperatingMode


9

Functional Allocation: 1-1 and ‘Onto’

Figure 8.4

Functions

f2

f3

f4

f1

f5

Components

c2

c3

c4

c1

c5

Function for the allocation of functions to components

Functions

f2

f3

f4

f1

f5

Components

c2

c3

c4

c1

c5

One-to-one and ontofunction for the allocation

of functions to components

Functions

f2

f4

f5

f1

f8

Components

c2

c3

c4

c1

c5

Onto, but not one-to-onefunction for the allocation


f3

f7f6

Functions

f2

f3

f4

f1

f5

Components

c2

c3

c4

c1

c5

Relation for the allocation of functions to components

10

Functional Allocation Goal

• Allocate Functions Components.

• There is great advantage to having Functional and Physical Architectures match (one-to-one and onto).

11

Functional Allocation Goal

• There is great advantage to having Functional and Physical Architectures match (one-to-one and onto).

– When does this happen ??

– When does this not happen ??

Product or system architecture decisions ??

13

Two Levels of Physical Architecture

• Generic physical architecture: description of the partitioned elements of the physical architecture without any specification of the performance characteristics of the physical resources that comprise each element

• Instantiated physical architecture: generic physical architecture to which complete definitions of the performance characteristics of the resources have been added

14

The Process

• Generic Physical Architecture provides ‘common designators’ for physical resources. (No real physical items).

• Morphology Box to create and list instantiated architectures – options for choice.

• Create many alternate instantiations to choose from.

15

Morphological Box for Hammer

Handle Size

Handle Material Striking Element Weight of Hammer

Head

Nail Removal Element

8 inches Fiberglass with rubber grip

1-inch diameter flat steel

12 oz. Steel claw at nearly a straight angle

22 inches

Graphite with rubber grip

1-inch diameter grooved steel

16 oz. Steel claw at a 60 degree angle with handle

Steel with rubber grip

1.25-inch diameter flat steel

20 oz.

Steel I -beam encased in plastic with rubber grip

1.25-inch diameter grooved steel

24 oz.

Wood

Table 8.3

(Top row – generic components, 320 possible combinations)

16

Morphological Box for Auto Navigation Support System

Direction Localization Processor User I/O Other System Support Interfaces

Map & None None Regular None Database Cell Phone

Map, Database, Direction Vehicle’s Special HornRouting Algorithm Sensor Processor Cell Phone

Staffed Electro 32-bit 4” LCD Lights Control Center Gyros Processor

Automated GPS Portable 6” LCD Car Door Control Center Transponder PC (486+) Locks

Full GPS 6” LCD & Emergency Support Touch Screen Signal

Button & Air Bag Key Panel

Joy Stick

Control Knob

Voice Output

Oldsmobile Guidestar

Acura Navigation System

BMW Navigation System

Cadillac’s OnStar

Lincoln’s RESCU

RETKI

Figure 8.5

We can use morphological boxes with software, too

17

Image from http://hcil2.cs.umd.edu/trs/2004-17/2004-17.html

http://hcil2.cs.umd.edu/trs/2004-17/2004-17.html

18

Pairwise Infeasible Combinations within a Morphological Box

8 inches

22 inches

Angled

Straight

Fiberglass

Steel

Graphite

Steel I-beam

Wood

1 inchflat

1 inchgrooved

1.25 inchgrooved

1.25 inchflat

Handle Material

Handle Length

Nail Removal Feature

Striking Feature

24 Oz.

12 Oz.

16 Oz.

20 Oz.

Weight of Hammer Head

HammerExample

Figure 8.6

19

Elevator CallAnnouncem ent

Com ponent

DestinationControl

Com ponent

DoorControl

Com ponent

Em ergencyCom ponent

PhoneCom ponent

Car ControlCom ponent

PassengerInte rface

C om ponent

CabCom ponent

Interior DoorCom ponent

Ventilation& Lighting

Com ponent

Car Com ponent Shaft StructuralCom ponent

Exit Com ponent& Controls

Floor StopCom ponent

LevelingCom ponent

Shaft Sw itchCom ponent

Norm alD rive /BrakeC om ponent

E m ergencyBrak ing

C om ponent

D rive /BrakeC om ponent

E leva torC ar/S ha ft

C om ponent

Hardw areC om ponent

S oftw areC om ponent

C ontro lC om ponent

M a intenance& S e lf-T es tC om ponent

Eleva tor System

Compare lower levels to functional

decompositionIs it 1-to-1 ??

Matches first levelFunctional decomposition

USED AT: CONTEXT:


AUTHOR:PROJECT:

NOTES: 1 2 3 4 5 6 7 8 9 10

DATE:REV:

WORKING

DRAFT


READER DATE

P.

A-0

3


George MasonUniv.

09/29/1999



PROVIDEFEEDBACK

A1

CONTROLELEVATOR

CARSA2

MOVEPASSENGERS

BETWEENFLOORS

A3

ENABLEEFFECTIVE


A4







ElectricPower

ElectricPower








MalfunctionSignal







EmergencyComm'n



Loss/Gain








Fire Alarm



OperatingMode


20

Block Diagrams of Physical Architecture

(Most common graphical representation)

CentralController

CrewCommandSensors

AircraftDevice

Sensors

ActuatorController

ActuatorController

Actuator

Actuator

AircraftDevices

(e.g.,flaps,

ailerons)

CrewCommand

Devices(e.g.,

throttle,pedals)

. . .

Aircraft Control Component

Figure 8.7

Block diagram for software

21

Image from http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=hdwr&db=bks&fname=/SGI_EndUser/RASC_UG/ch04.html .

http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=hdwr&db=bks&fname=/SGI_EndUser/RASC_UG/ch04.html

22

Issues in Physical Architecture Development

• Functional performance, availability (cost, safety, fault tolerance), and other system-wide traits.

• Commercial and ‘product line’ factors.

• Operational architecture finishes this process.

• Looking ahead – physical architecture elements are added as mechanisms on the Functional Architecture to produce the Operational Architecture.

Vehicle Theft Deterrence

• It’s fairly easy to understand conceptually how an effective system could work…

23

See https://www.youtube.com/watch?v=Ee3L9BQQ4Gs

https://www.youtube.com/watch?v=Ee3L9BQQ4Gs

24

Example- Vehicle Theft

A0

Provide Vehicle Security

A3

Provide Robber Activity

A1

Provide User Services

A2

Provide Vehicle Services

Disable vehicle signal

Request arm/disarm

Request audible alarm

Security Alarm

Power

Status of vehicle sensors

Request Panic Alarm

Confirm arm/disarm, panic, test

System armed indication

Provide criminal activity

Provide criminal activity

NODE: NO.:A1 TITLE: Vehicle Anti-Theft System

MaintenanceRequired

signal

User needs

Audible Alarm

Owner / User VehicleTheif

M. Clarizia

NODE: NO.:TITLE: Operating Scenario for Vehicle Theft Deterrent System

Thief VehicleDeterrent System

Vehicle User

Input Commands

Feedback Commands Accepted

Input Opportunity

Feedback Monitor Status

Suspicious and Theft Activity Theft Signals

Feedback Alarm StatusTheft Deterrent Commands

Input Opportunity

Feedback Commands Accepted

Feedback Monitor Status

Request Theft Signals

Power

Theft Deterrent Signals

Input Commands

25

Vehicle Theft Example

NODE: NO.:A0 TITLE: Vehicle Anti-theft System - 1st Level Decomposition

A1

Provide User Interface

A2

Accept Inputs/Provide Outputs

A3

Provide data processing

A4

Provide Diagnostic Capability

Request Arm/Disarm Request panic test

Power

CriminalActivity

Vehicle status

Input request

Output response

Maintenance required

Maintenance required signal

Arm/Disarm & Alarm confirmation

User interfacerequests

Audible alarm

Disable vehicle

M. Clarizia

26

Major Concepts for Physical Architecture

• Centralized vs. Decentralized

• Modular vs. Integral

• Standardization, Serviceability

• ‘COTS’ components

27

Mostly Software Example :FBI Fingerprint Identification System

• IAFIS: Integrated Automated Fingerprint Identification System– ITN/FBI: Identification Tasking and

Networking segment – focus of this case study

– III/FBI: Interstate Identification Index segment

– AFIS/FBI: Automated Fingerprint Identification System segment

28

ITN/FBI: Identification Tasking and Networking

• RFP identified subelements• TPS: Ten-print Processing Subelement was key

– Processed paper cards with 10 fingerprints– Organized as work stations within a workgroup

(distributed system)– Processed ~ 30,000 per day– Scanned, converted to binary data, and analyzed– Images had to be compressed by at least 10 to 1– Average time to perform a fingerprint image

comparison was 60 seconds– Time allowed for display of human-machine interface

was 1 second from time of request

29

Critical Design Issues for TPS

• Implementation of wavelet scalar quantization (WSQ) algorithm (hardware vs. software)

• Workstation capabilities• Server capabilities• Workflow management capabilities• Communications interface

30

Alternate Design Allocation Options Studied

Basic Workgroup ServerRISC/6000 Model 570

256MB RAM2GB DASD

SPECint92 48.4SPECfp92 97.0

Basic WorkstationRISC/6000 Model 22W

32MB RAM400MB DASD


Ethernet LAN 10 Mbps

LocalWorkgroupWorkflow

Enhanced Workgroup ServerRISC/6000 Model 970B512MB RAM5GB DASDSPECint92 58.8SPECfp92 108.9

Enhanced WorkstationRISC/6000 Model 340

64MB RAM2GB DASD


EnterpriseWide

Workflow

Software?

Hardware

AllocateAlgorithm

Server?

Workstation


32MB RAM400MB DASD


Ethernet LAN - 100 Mbps

Basic Workgroup ServerRISC/6000 Model 570256MB RAM2GB DASDSPECint92 48.4SPECfp92 97.0


32MB RAM400MB DASD


Ethernet LAN - 100 Mbps

Enterprise WideWorkflow



Enhanced WorkstationRISC/6000 Model 340

64MB RAM2GB DASD



Server?

Workstation

Workstation Only

Server w/ Any Workstation

Server w/ Local Workstation

Software Allocation

Enhanced Workgroup ServerRISC/6000 Model 970B

512MB RAM5GB DASD


Basic WorkstationRISC/6000 Model 22W32MB RAM400MB DASDSPECint92 20.4SPECfp92 29.1



Hardware Allocation

Custom LSI Chip On Co-processor Card


FDDI Ring

Enhanced Workgroup ServerRISC/6000 Model 970B

512MB RAM5GB DASD



32MB RAM400MB DASD




Server Only

Workstation Only

Server Only


Figure 8.8

31

Morphological Box of Instantiated Design Option

Workstation Server Software LSI Chip

Workflow Management

Communications

Basic Workstation RISC/6000 Model 22W

32MB RAM 400MB DASD

SPECint92 20.4 SPECfp92 29.1

(b, c, e, f) (g, h)

Basic Server RISC/6000 Model

570 256MB RAM 2GB DASD

SPECint92 48.4 SPECfp92 97.0 (a, c, e) (g, h)

No WSQ Algorithm

(e, f) (g, h)

None

(a, b, c, d)

Local Workgroup Workflow

(a, b, d, e, f)

(g)

Ethernet LAN (10BaseT) - 10 Mbps

(a, e)

Enhanced Workstation RISC/6000 Model 340

64MB RAM 2GB DASD


(a, d)

Enhanced Server RISC/6000 Model

970B 512MB RAM 5GB DASD


(b, d, f)

WSQ Algorithm

(a, b, c, d)

WSQ on LSI Chip

(d, e) (g, h)

Enterprise Wide Workflow

(c) (h)

Ethernet LAN (100BaseT) – 100

Mbps

(b, d, f) (g)

FDDI WAN - 100 Mbps (c) (h)

2 new alternatives (g & h) identified

Table 8.5

32

Use of Redundancy to Achieve Fault Tolerance

• Hardware: adds extra hardware to enable detection of and recovery from errors

• Software: N-version– N different software developers for same routine– Comparison of results via voting– Seldom used due to expense of software development

• Information: adding extra bits of information to enable error detection

• Time: replaces hardware or software redundancy when there is slack processing time - recalculation

33

Hardware Redundancy -A crucial choice for software

• Passive: extra hardware operating concurrently using voting– Errors are masked or hidden (system unaware)– Approaches

• N-modular redundancy (NMR)– Triplicated: TMR – masks 1 error– 5MR – masks 2 errors

• Triplicated NMR

• Active: detects errors, confines damage, recovers from errors, & isolates/reports fault– Duplication with comparison: extra hardware with comparison,

not voting– Hot standby: extra hardware, only one reporting, monitor of

outputs to detect error– Cold standby: extra hardware inactive until error detected– Pair-and-a-spare: Duplication with comparison & hot standby– Hybrid: combinations of the above

34

TMR & Triplicated TMRComponent 1

Component 2

Component 3

Voter

Input 1

Input 2

Input 3

Output

Component 1

Component 2

Component 3

Voter

Input 1

Input 2

Input 3

Output 2

Triple Modular Redundancy (TMR)

Triplicated TMR

Voter Output 3

Voter Output 1

Voter is single point of failure

Figure 8.9

Issues with Voting

35

Software Implementation of Triplicated TMR

Two-port Memory

Two-port Memory

Two-port Memory

Input 1

Input 2

Input 3

Sampler

Sampler

Sampler

Two-port Memory

Two-port Memory

Two-port Memory

Processor

Processor

Processor

Figure 8.10

36

Active Hardware Redundancy: Duplication with Comparison

Component 1

Comparator

Component 2

Input

Output

Agree/Disagree

Figure 8.11

37

Hot Standby Sparing, N-1 Replicas

Component 1

Component 2

Input Output

ErrorDetection

ErrorDetection

Component N

ErrorDetection

~~

. . .

. . .

N to 1Switch

Figure 8.12

38

Pair-and-a-spare

Component 1

Component 2

Input

Output

ErrorDetection

ErrorDetection

Component N

ErrorDetection

~~

. . .

. . .

N to 2Switch

Compare

Agree/Disagree

Figure 8.13

39

Practicality of Redundancy

•How practical is redundancy ?

– In your car.

– In an airplane.

40

Redundancy Warning

• Redundant components and systems must truly be independent systems.

• Often a ‘single point of failure’ takes out all ‘redundant’ systems.– Space Shuttle Challenger (o-rings)– Genesis space vehicle (g-switches)– UA 232 Sioux City (hydraulic systems) (P.242)

41

Discussion Q1

• The physical architecture for the hammer :

– what does the functional architecture look like

42

Discussion Q2

• For the drink machine functional architecture, does Hatley Pirbhai or ‘Energy, Materials, Signal Flows’ ‘work better’ with respect to giving a functional architecture that produces a ‘more realistic’ physical architecture.

43

Discussion Q3

• For the ATM machine, develop an external systems diagram and a first level function decomposition for the Acme ATM Company – a manufacturer and seller of ATM machines.

• Consider the possible uses of the functional model and physical implementations of the system.

45

Discussion Q4

• Given the first level decomposition for the ATM machine:

1. Sketch the generic physical architecture2. Sketch a morphological box and some

possible instantiated physical implementations

46

USED AT: CONTEXT:


AUTHOR:PROJECT:

NOTES: 1 2 3 4 5 6 7 8 9 10

DATE:REV:

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READER DATE

P.

Activity Selection,Account Type,Deposit Type,Deposit of Funds,Trans Amount,Source Account,Dest Account,Source of Payment,Payment on Account,Request to Cancel,Choice to End

Cust Status Inf..,Fmax

General ID,Unique ID

EmployeeID Code

AudibleAlarm,

OperationTerminatedBreak-in

Attempt

SafetyRegulations

Americans withDisabilities Act

Choice, ATM Reset,No Input Device,

Request for ID #2,Request for ID #3,

Customer Alert, Apology,Request for Paymt Source

Request for Unique ID,Request for Activity,

Request for Account Type,Request for Deposit Type,Physical Means for Insert,

Receipt, Request for Amount,Request Denied, Cust Cash,

Request for Source Account,Request for Dest Account

Transaction,Request for Fmax,

Request for Status Inf..,Input Not Working,Request for Funds,

Request for Receipts,Break-in Attempted

Request to Open,ATM Cash, Blank Receipts,Initialization,Diagnostic Test,ATM Fixes,Request to Close

Access Opportunity,ATM Opened,

Cust Deposits,Cust Payments,

Test Results,Fixes Applied

ATM Closed

Main Menu

Provide Access to

ATM

A1

Accept Customer

Requests and Provide

Feedback

A2Determine

ATM Responses

A3

Communicate with Bank Computer

A4

Enable Re-Supply and Maintenance

A5

Respond to Hostile

SituationsA6

Request forUnique ID

BankingPolicies

No Input Device,Request for ID #2,Request for ID #3,Customer Alert

Choice, ATM Reset,Apology, Requestfor Paymt Source

Request for Activity,Request for Account Type,Request for Deposit Type,Physical Means for Insert,Receipt, Request for Amount,Request Denied, Cust Cash,Request for Source Account,Request for Dest Account

CustomerValid

EmployeeValid

ID Validation

ID Received

Activity Selected,A/C Type Entered,Deposit Type EnteredDeposit Received,Amount Entered,Source A/C Entered, Dest A/C Entered,Ftrns>Fmax

Need for Fmax,Trans Complete,Receipts<25

Need to Open,Paymts Inserted,Deposits Inserted,Diagnostics,Fixes to ATMNeed to Close

Creq>Cleft

Balance Inf.,Paymt Source Entered,Payment Received,Ptrns>Fmax, Cancel Received,Choice Received

AccountFMax

Account Balance

Cust Activity,Cust A/C Type,Deposit Entered,Cust Amount,Trans Source,Trans Dest,Paymt Source,Payment Entered,Cancel Entered,Choice Entered

Attempted Break-in

Clim

CalculationsforWithdrawal

Input notAvailable

3

xAutomatic Teller MachineSYST 520 Student

George Mason University

08/07/00

Provide ATM ServicesA0

Wasson’s Ch 40• Let’s look at Wasson’s recommended

methodology:

47

Wasson’s “Domain solution challenges” (Sec 40.6)

1. Solution space validation2. Technical design integrity3. Multi-domain solution agreement4. Risk identification and mitigation5. Environment, safety and health6. System solution stability7. System support8. Interfaces9. System optimization10.Phases and modes of operation

48

49

Step 2 – Allocate capabilities

Extra Slides

• See the last slide!

50

51

Example - F-22 Physical Architecture

F-22 Weapon System

Vehicle Training Support

AvionicsSystems

Utilities &Subsystems

CockpitSystems

VehicleManagement

System

ElectronicWarfare

Navigation,Identification

Processing

Controls&

Displays

StoresManagement

InertialReference

SystemRadar

Figure 8.1

52

Work Breakdown Structure - WBS

• MIL-STD-881B : WBS for defense material items.

• WBS is often similar to Physical Architecture – work organized along lines of resources for development or procurement.

• Examples – Aircraft system (10 elements, 17 resource categories)

• (See Blanchard and Fabrycky Section 18.2.)

53

WBS Elements and Related Life Cycle Phases

WBS Elements Life Cycle Phase

Air vehicle Operational

Systems engineering/Program management Development

System test and evaluation Development

Training Training

Data Manufacturing and refinement

Peculiar support equipment Operational

Common support equipment Operational

Operational/site activation Deployment

Industrial facilities Manufacturing

Initial spares and repair parts Operational

Table 8.1

54

Resource Categories for Generic Air Vehicle

Airframe Survivability

Propulsion Reconnaissance

Air vehicle application software Automatic flight control

Air vehicle system software Central integrated checkout

Communications/Identification Antisubmarine warfare

Navigation/Guidance Armament

Central computer Weapons delivery

Fire control Auxiliary equipment

Data display and controls

Table 8.2

55

Development Process for the Physical Architecture

USED AT: CONTEXT:


AUTHOR:PROJECT:

NOTES: 1 2 3 4 5 6 7 8 9 10

DATE:REV:

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READER DATE

P.

Originating & System Requirements,

Objectives Hierarchy, Boundary & Qualification

System Requirements

System-level Operational Concept

Candidate Physical

Architectures

System-level Physical

Architecture

System-level Functional

Architecture

Candidate Generic Physical

Architectures

Brainstorm and Select a Generic

Physical Architecture

A1131

Generate a Morphological Box

for Alternate Instantiated Physical

Architecture

A1132

Select Alternate

Instantiated Physical

Architecture

A1133

GenericPhysicalArchitecture

MorphologicalBox

PhysicalArchitectureChanges

8

x

Engineering Design of a SystemDennis Buede

GMU Systems Engineering

Program

05/24/99

Design System Physical ArchitectureA113

Figure 8.3

56

Functional Allocation: 1-1 and ontoFunctions

f2

f3

f4

f1

f5

Components

c2

c3

c4

c1

c5

Relation for the allocation of functions to components

Functions

f2

f3

f4

f1

f5

Components

c2

c3

c4

c1

c5

Function for the allocation of functions to components

Functions

f2

f3

f4

f1

f5

Components

c2

c3

c4

c1

c5

One-to-one and ontofunction for the allocation


Figure 8.4

57

Option Creation TechniquesBrainwriting and Brainstorming Categories Examples

Brainwriting I - an individual works alone to create a list of ideas. Analogy, attribute listing, people involved

Brainwriting II - a group of individuals separated in space generates ideas separately and the ideas are collected but not shared

Collective notebook

Brainwriting III - a group of individuals separated in space generates ideas separately, the ideas are shared, and additional ideas are generated

Delphi method

Brainwriting IV - a group of individuals working in the same room generates ideas separately and the ideas are collected but not shared and no discussion takes place

Nominal group technique

Brainwriting V - a group of individuals working in the same room generates ideas separately; all of the ideas are shared but none are discussed; additional ideas are generated

Brainwriting pool

Brainstorming I - a group of individuals generates ideas via verbal discussion, no defined procedure is used

Unstructured group discussion

Brainstorming II - a group of individuals generates ideas via verbal discussion within the bounds of predefined procedures

Classical brainstorming

Brainwriting/Brainstorming I - a group of individuals generates ideas via predefined written and verbal procedures

Brainwriting game

Table 8.4

week 6 - systems engineering and analysis

Documents

physical resources

physical reality

physical architecturebelieve

free of physical limitations

real physical items

physical means real

system architecture

level functional model