SYSTEMS ARCHITECTURE DESIGN Introduction into Architecture Frameworks Engineering

SYSTEMS ARCHITECTURE DESIGN Introduction into Architecture Frameworks Engineering Design & Architecture: Differentiation Quality Assurance of Architectures

Content Overview • Introduce into some state-of-the-art architecture frameworks • Discuss differences between “engineering design“ and “architecture design” • Present means of quality assurance for elaborated architectures

Architecture Frameworks - Introduction • Architecture makes complex systems understandable • Term „Architecture“ (ANSI/IEEE 1471 -2000) • The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution • Architectures relate to domains • Term „Architecture Framework“ • An architecture framework establishes a common practice for creating, interpreting, analyzing and using architecture descriptions within a particular domain of application or stakeholder community. (ISO/IEC/IEEE 2007)

Architecture Frameworks by Intention • Enterprise Management (rather no tech. focus) • Zachman, TOGAF, SABSA, . . . • Government and Agency • NIST, TEAF, . . . • Military • Do. DAF, Mo. DAF, NAF, . . . • Manufacturing Specific • CIMOSA, PERA, GIM-GRAI, . . . • Technically Specific (rather no mgmt. focus) • POSIX OSE, HIF, RM-ODP, . . • Interoperability • EIF, C 41 F, . . .

Architecture Frameworks brief view on a few Label Specification Scope „metrics“ Zachman The Zachman Architecture Framework Enterprise Management 500 Pages 6 fundamental areas 6 major views TOGAF The Open Group Architecture Framework Development / Maintenance of an Enterprise Management Architecture Framework 787 pages 7 fundamental areas 1 major views Do. DAF Do. D Architecture Framework Military Ancestor: C 41 SR 386 pages 2 fundamental areas 8 major views Mo. DAF Mo. D Architecture Framework Military Ancestor: Do. DAF, Zachman 256 Pages 3 fundamental areas 7 major views NAF NATO Architecture Framework Military (includes enterprise management aspects) 882 pages 7 major views 9 fundamental areas

Engineering Design & Architecture • A differentation

Engineering Design & Architecture A differentation • Engineering is to design and build something using scientific principles • Architecture is to design something but a design outcome is not neccessarily architecture • Architectural Engineering includes not only the architectural design but provides with a holistic (end to end) view onto all aspects of the end product to deliver a turnkey solution. (Bach et al, Hofmeister et al) • Links • http: //ssse. ch/node/195 • http: //sebokwiki. org/wiki/Guide_to_the_Systems_Engineering_Body_of _Knowledge_%28 SEBo. K%29 • http: //www. incose. org/About. SE/What. Is. SE • https: //en. wikipedia. org/wiki/List_of_systems_engineers

Means of Architecture Quality Assurance

Architecture Quality Assurance Analysis I Metamodel View (generic) Specific Viewpoint embodied in its components All items on the BOM their relationships to each other and the environment required to build the system planned principles governing its design and evolution any required item has been denoted From Question to Model: What are the components? How are they related / interconnected? What are the governing principles

Architecture Quality Assurance Analysis II Metamodel View (generic) Specific Viewpoint embodied in its components All items of the same kind their relationships to each other and the environment different kinds assemble to the systems principles governing its design and evolution Any kind of item is available Architecture to answer specific Questions: How shall aspect „A“ of my original system look like?

Architecture Quality Assurance Analysis III Metamodel View (generic) Specific Viewpoint embodied in its components All components from different teams their relationships to each other and the environment different teams contribute into one complete system principles governing its design and evolution Any team has contributed Architecture to answer Questions: How will my original system react on that specific event?

Architecture Quality Assurance Analysis IV Metamodel View (generic) Specific Viewpoint embodied in its components All BOM items to build the system their relationships to each other and the environment assemble in that certain order principles governing its design and evolution Any step to build is denoted Good architectures support different levels of design & realization work - Strategic architecture QA Does the system align with specific aspects? - Semantic architecture QA Analyze a specific aspect of the system re fulfilment of rules! - Syntactical Architecture QA Is the system architecture design valid and viable?

Architecture Quality Assurance Sample • Syntactial QS sample • Can the system be build without breaking with the given central principles and is it vialble to build it? • Answer (fiction): Yes • Semantical QS sample (add on requirement) • Late add on requirement: Will the system can operate in central africa? • Answer (fiction): Yes • Strategic QS sample: • Group of creators splits, one wnat‘s to take his patents with him. • Answer: No. As the system is designed it seems to be rather difficult to remove the inflicted components.

Architecture Quality Assurance Synthesis • Different architecture views focus on specific aspects of the system and answer specifc questions • A system has a many architecture viewpoints • Each architecture viewpoint answers specific questions • An architecture view reduces complexity by providing a simplification of the reality • QA: Define the context relevant viewpoints • Derive the relevant metamodel information (checkpoints) • Check against that points of interest • Denote deviation (something to learn) • Denote near perfect fulfillment (something to know or something to learn)

Architecture Quality Assurance Closure • Architecture as a method is a powerful to master complex systems design and operation. • The enable for quantitative and qualitative QA • The many different complex architecture frameworks provice valuable support for notations, sample views and descriptions. They are horrible for the young architects • We all use architectures daily with being explicitly aware • Layered application • Syntactic QA: valid and viable? • Semantic QA: are the aspects desired under control? • Strategic QA: Optimization of the system as a whole

References • Zachman - The Zachman Architecture Framework • http: //www. zachman. com/about-the-zachman-framework • TOGAF - The Open Group Architecture Framework • https: //www. opengroup. org/ogsys/jsp/publications/Publication. Details. jsp? catalogno=g 116 • Do. DAF- Do. D Architecture Framework • http: //cio-nii. defense. gov/sites/dodaf 20/ • Mo. DAF- Mo. D Architecture Framework • http: //www. mod. uk/Defence. Internet/About. Defence/What. We. Do/Information. Management/MODAF / • NAF - NATO Architecture Framework • http: //www. nhqc 3 s. nato. int/ARCHITECTURE/_docs/NAF_v 3/ANNEX 1. pdf