170 likes | 183 Views
This article explores various architectural frameworks and tools used in systems engineering to capture, communicate, and support system architectures. The frameworks discussed include Zachman, SEMS, EPIC, IDEF0-9, DoDAF, and others. The article also covers the synthesis of architectures, modeling methodologies, and the importance of choosing the right architecture.
E N D
EMIS 8340 Systems Engineering Tool—applying tools to engineering systems Decomposition: Architecture & Trade Studies Mark E. Sampson
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 consulting • Business consultants each have their own extensions/tools [zifa.com]
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]
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,…
EMS Hydraulics Control Water Sys • 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 [SE Handbook 10] [DOE 2003]
Architecture: Synthesis… • You “just” have to choose an architecture that: • Satisfies the requirements • Implements the functions • Within budget, time, knowledge, resources,… • Built with available technology & availability risk • Is extensible to accommodate growth & new technologies • Allows you to go the next level of detail • Is robust enough to minimize back-tracking • …you may be starting from scratch or from existing art • …in a changing environment [SE Handbook 10]
Systems Synthesis FunctionalAnalysis Systems Analysis Problem Definition Decomposition VerificationValidation DevelopAlternatives DevelopAlternatives DevelopArchitectures ChooseAlternatives DevelopArchitectures ChooseAlternatives • Architecture: Synthesis • Develop alternativesuse the tools previously described—brainstorming, morphing, surveys, literature searches, Pugh, TRIZ,… • Develop architectures from those alternativesuse diagrams/models of appropriate types (at appropriate levels) • Choose & dive to the next levelapply criteria, decision trees, weighting, utility curves… • Repeat until components are • Realizable, verifiable,… [SE Handbook 10]
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) Partitioning [Armstrong 1993]
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]
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]
Modeling Methodology: Object Oriented Analysis • …identify what the system will have to deal with as objects • Similar to mission profiles, schematic block diagrams,… • UML/SysML • Presentation/demonstration • In our dental hygiene case, shows objects of our dental monitoring system [Armstrong 1993]
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]
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…)
Math/Behavior Modeling… • Math models (Excel, Matlab/Simulink, Mathematica, MathCad, Maple/Maplesim, Modelica,…) WolframAlpha Matlab/Simulink Modelica MapleSim
Performance Modeling… • Performance models—Queuing, Monte Carlo, etc. (Crystal Ball, SaS, SES Workbench,…) • DFSS (Design For Six Sigma) CrystalBall
Physical Modeling… • Physical Models—Materials, Aerodynamics, Kinematics, Thermal, Hydraulics, Electrical,…(ANSYS, NASTRAN, CAE ROSE, ADAMS, Easy5,… ) • Human factors (Jack, FactorySim,…) Thermodynamics Jack Stress Aerodynamics Hydraulics
‘ility’ Modeling… • Environmental—EMI/EMC, Acoustics,Weather,… • Reliability—Hazards, FMEA, Faults,... (MADE, ARM, @Risk,…) • Attribute modeling– Cost, Noise, MPG,…