1 decomposition: architecture & trade studies mark e. sampson emis 8340 systems engineering...
TRANSCRIPT
1
Decomposition: Architecture &Trade Studies
Mark E. Sampson
EMIS 8340
Systems Engineering Tool—applying tools to engineering systems
2
Architectural Frameworks…
• …a means of representing, capturing, communicating system architectures from a variety of perspectives…
• 100’s of frameworks out there…• Aimed at different problem domains
Business/IS systems…Zachman, SEMS, EPIC…
Tools help capture & support these frameworks… CaseWise, Synthesis…Usually can’t buy them without consultingBusiness consultants each have their own extensions/tools
[zifa.com]
3
Architectural Frameworks…continued
• IDEF0-9…based on SADT
• IDEF0—functional modeling• IDEF1—information modeling…• IDEF1x—activity modeling• IDEF2—system dynamics• IDEF3—process & states• IDEF4—object modeling• …• IDEF9—user interface• …• IDEF14—network modeling
Tools help capture & support these frameworks… KBSI, Popkin SA, ProSim,…
[idef.com]
4
Architectural Frameworks…continued
• DoDAF…next generation C4ISR
• Operational views• OV1-operational concepts• …• OV5-activities• …• OV9-logical Data
• System views • SV1-interfaces• …• SV12-events
Tools help capture & support these frameworks…Popkin SA, Statemate, P-Tech…
Most used is Powerpoint, Excel,…
B-1
NBCFacillity
B2
F17 A1
U2
CRECRC
AFFORAOC
AWACS
JSTARS
DSPComm
Wx GPS
Missile
IADS
DGS CRC to CRE
AWACS to U2
Comm to AOC
AFFOR to JSTARS
AWACS to JSTARS
AOC to CRC
U2 to B-1
U2 to F17AAWACS to B-1
JSTARS to B2
AWACS to AOC
AWACS to F-16 IN
AWACS to AOC IN
5
Architectural Frameworks…continued
• Translates functions into physical architecture by grouping functions into logical/physical elements
• Elements include: hardware,software, material, data, facilities,people, services, and/or processes
• Alternatives are evaluated againstthe requirements to identifybest approach
• Continue to developarchitecture until youcan verify that requirementshave been met
…produces WBS, spec’s, & CI’s
Hydraulics
Water Sys
EMS
Control
[SE Handbook 10] [DOE 2003]
6
Architecture: Synthesis…
• You “just” have to choose an architecture that:
1. Satisfies the requirements2. Implements the functions3. Within budget, time, knowledge, resources,…4. Built with available technology & availability risk5. Is extensible to accommodate growth & new
technologies6. Allows you to go the next level of detail7. Is robust enough to minimize back-tracking
…you may be starting from scratch or from existing art…in a changing environment
[SE Handbook 10]
7
Architecture: Synthesis
1. Develop alternativesuse the tools previously described—brainstorming, morphing, surveys, literature searches, Pugh, TRIZ,…
2. Develop architectures from those alternativesuse diagrams/models of appropriate types (at appropriate levels)
3. Choose & dive to the next levelapply criteria, decision trees, weighting, utility curves…
Repeat until components are Realizable, verifiable,…
[SE Handbook 10]
Problem Definition
FunctionalAnalysis
Systems Synthesis
Systems Analysis
DecompositionVerificationValidation
ChooseAlternatives
DevelopArchitectures
DevelopAlternativesDevelop
Alternatives
DevelopArchitectures
ChooseAlternatives
8
Modeling Methodology: Schematic Block Diagrams
…capture & communicate potential product architecture, what makes it up, & their interactions
• Shows internal & external interfaces without pushing a particular design• Encourages looking “outside the box”
In our dental hygiene case, shows the preliminary product partitioning)
[Armstrong 1993]
Partitioning
9
Modeling Methodology: Behavior Diagrams
…combine data flow and functional flow
• More thorough analysis of actions & what is being acted on in the same diagram. • Support function to system allocations
…tools like CORE, Cradle-SEE, …use thesetypes of diagrams
[Armstrong 1993]
10
Modeling Methodology: State Diagrams
…analysis of system states or modes
• Identify lock conflicts—on, standby,…• Identify transition problems during design
Presentation/Demo by IBM
In our dental hygiene case, shows the system needs to be made ready before it can be used [Armstrong 1993]
11
Modeling Methodology: Object Oriented Analysis
…identify what the system will have to deal with as objects
• Similar to mission profiles, schematic block diagrams,…
•UML/SysMLPresentation/demonstration
In our dental hygiene case, shows objects of our dental monitoring system
[Armstrong 1993]
12
Methodology: Data Flow
…like functional flow, except emphasis on how information flows among system elements.
Helps identify data input/outputconflicts• Data dictionaries
In our dental hygiene case, shows a decomposition of monitoring brushing after meals
[Armstrong 1993]
13
Modeling Methodology: others…
• Entity-Relationship Diagrams• Math models (Excel, Matlab,…)• Statistical Models—(SAS, MiniTab,…)• Performance models—Queuing, Monte Carlo, etc.
(Crystal Ball, SES Workbench,…)• Environmental Models—• Physical Models—Hydraulics, Electrical,…(Easy5,
CAERose, Matlab/Simulink…)
Product ModelProduct Model(equation, (equation, simulation,simulation,
workbook, data,workbook, data,hardware, etc.)hardware, etc.)
C
E
A
B
D “Non-compliant”
“Non-compliant”
Y
ULLL T
PNCPNC
“Compliant”
Product ModelProduct Model(equation, (equation, simulation,simulation,
workbook, data,workbook, data,hardware, etc.)hardware, etc.)
C
E
A
B
D “Non-compliant”
“Non-compliant”
Y
ULLL T
PNCPNC
“Compliant”
Product Requirement I
Customer Need
Module A Requirement Module B Requirement Module C Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Component 1Requirement
Component 2Requirement
Component 3Requirement
Process 1Requirement
Process 2Requirement
CustomerEnvironment
ProductDevelopment Team
Environment
Product Requirement I
Customer Need
Module A Requirement Module B Requirement Module C Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Component 1Requirement
Component 2Requirement
Component 3Requirement
Process 1Requirement
Process 2Requirement
CustomerEnvironment
ProductDevelopment Team
Environment
LARGEWATER TANK
T1
75 PSI
H
H
H
Orifice
CentrifugalPump
Orifice
WATER TANKT2
50 PSIGWATER TANK
T3
100 PSIG HTank Level
Sensor(TLF) 0100%
Pressure Transducer (PSF)
Suction Tank
Recycle Valve (W-5)(3 Sec Open, 3 Sec Shut)
Diverter Valve (W-3)
Flow Valve (W-1)(4 Sec from Suction to Discharge)
Discharge Tank
Pressure Transducer (PSB)
Backup Valve (W-4)(2 Sec Open 2 Sec Shut)
Pressure Transducer (PSL)
Diverter Valve (W-2)
H
Tank LevelSensor(TLF) 0100%
P-1 3” Suction Header P-2 4” Discharge Header
5” Suction/Discharge P-3
5” Suction/Discharge P-4
P-5 4” SuctionTank Header
P-6 4” DischargeTank Header
P-8 4” Pump Suction fromDischarge Tank
P-7 4” Pump Suction fromSuction Tank
P-9 4” Pump Discharge ToSuction Tank
P-10 4” Pump DischargeTo Discharge Tank
Pump SuctionShutoff (W-6)
Pump DischargeShutoff (W-7)
Pump FlowCheck (W-8)P-11 4” Pump
Suction P-12 4”Pump
Discharge
P-13 3” Recycle Header
PipingClass 1
PipingClass 4
PipingClass 5
PipingClass 2
PipingClass 3
PipingClass 6
NOTE: Logical Product Structure (Excel File)depicts representative data for components ofPiping Class 1 and Piping Class 5.
14
Math/Behavior Modeling…• Math models (Excel, Matlab/Simulink, Mathematica,
MathCad, Maple/Maplesim, Modelica,…)
Modelica
WolframAlphaMatlab/Simulink
MapleSim
15
Performance Modeling…
• Performance models—Queuing, Monte Carlo, etc. (Crystal Ball, SaS, SES Workbench,…)
• DFSS (Design For Six Sigma)
Product ModelProduct Model(equation, (equation, simulation,simulation,
workbook, data,workbook, data,hardware, etc.)hardware, etc.)
C
E
A
B
D “Non-compliant”
“Non-compliant”
Y
ULLL T
PNCPNC
“Compliant”
Product ModelProduct Model(equation, (equation, simulation,simulation,
workbook, data,workbook, data,hardware, etc.)hardware, etc.)
C
E
A
B
D “Non-compliant”
“Non-compliant”
Y
ULLL T
PNCPNC
“Compliant”
Product Requirement I
Customer Need
Module A Requirement Module B Requirement Module C Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Component 1Requirement
Component 2Requirement
Component 3Requirement
Process 1Requirement
Process 2Requirement
CustomerEnvironment
ProductDevelopment Team
Environment
Product Requirement I
Customer Need
Module A Requirement Module B Requirement Module C Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Assembly 1Requirement
Assembly 2Requirement
Component 1Requirement
Component 2Requirement
Component 3Requirement
Process 1Requirement
Process 2Requirement
CustomerEnvironment
ProductDevelopment Team
Environment
CrystalBall
16
Physical Modeling…• Physical Models—Materials, Aerodynamics,
Kinematics, Thermal, Hydraulics, Electrical,…(ANSYS, NASTRAN, CAE ROSE, ADAMS, Easy5,… )
• Human factors (Jack, FactorySim,…)
Aerodynamics
Stress
Jack
Thermodynamics
Hydraulics
17
‘ility’ Modeling…• Environmental—EMI/EMC, Acoustics,
Weather,…• Reliability—Hazards, FMEA, Faults,...
(MADE, ARM, @Risk,…)• Attribute modeling– Cost, Noise, MPG,…