Architecture and Design Fundamentals

Transcription

1 by Gerrit Muller University College of South East Norway Abstract Defining and illustrating architectures. Architectures go beyond structure (parts, interfaces, fucntions, allocation). Architectures connect design to the context, by capturing customer value proposition, and the business proposition. Distribution This article or presentation is written as part of the Gaudí project. The Gaudí project philosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by an open creation process. This document is published as intermediate or nearly mature version to get feedback. Further distribution is allowed as long as the document remains complete and unchanged. status: planned

2 One Architecture Facilitates many Solutions flat detector C/V kv ma cardio single cardio vascular X-ray architecture kv ma many designs many variants vascular kv ma 2 Gerrit Muller ADFxRayVariants

3 Architecture Description Value Proposition Why does customer want to buy? Why do users like to use the? customer key drivers cost of ownership customer business analysis customer stakeholders and concerns work flow or ConOps et cetera Business Proposition How do we earn money? How do we run a healthy business? life cycle key drivers business model cash flow analysis life cycle stakeholders and concerns life cycle model supply chain System Specification What does customer get? What is the -of-interest that we deliver? functions qualities (e.g. quantified performance) interfaces constraints, standards, regulations Design How will we realize this specification? How do we ensure performance, safety, robustness, etc.? partitioning and interfaces dynamic behavior, e.g. functional model performance models and budgets concept and technology selection Engineering Getting all details right for all business functions. technical product documentation Why What How 3 Gerrit Muller ADFarchitecture

4 Functional Model for System Creation stakeholder needs business objectives architecting specification design procurement architecture guidelines top-level design rationale design partitioning interfaces functions allocation engineering documentation and parts data procedures production installation quality assurance lifecycle support 4 Gerrit Muller SPFCreation

5 Structure = Parts + Interfaces + Configuration ultimate goal: to facilitate: modular component catalogue fast creation of solutions well-defined interfaces concurrent engineering independent testable logistics and production variations and changes A1 A2 A3 A4 A1 A4 A2 A3 A4 B1 B2 B1 B2 5 Gerrit Muller ARCVpartitioning

6 Designing Desired Qualities and Behavior How do parts interact to create desired dynamic behavior? allocate functions How do desired qualities and performance emerge from the interaction? dimension and configure parts and functions A2 A3 A4 B2 6 Gerrit Muller ARCVdynamicsAndQualities

7 Design = Structure + Dynamics + Quantification characteristics prime interest of customer results in prime responsibility dynamics functionality interact parts prime interest of 7 Gerrit Muller SPFpartsDynamicsCharacteristics

8 Our Primary Interest developing of interest architect 8 Gerrit Muller SEMABcoreEntities

9 Context, Zoom-out and Zoom-in customer super developing of interest architect supplier 9 Gerrit Muller SEMABsuperSubEntities

10 Adding the Time Dimension past current future customer past super super future super developing past of interest of interest future of interest architect knowledge innovation supplier past future based on TRIZ 10 Gerrit Muller SEMABentitiesInTime

11 Architect,Architecture, Architecting past current future customer past super super future super developing architecting architect past of interest knowledge of interest architecture innovation future of interest past future supplier based on TRIZ 11 Gerrit Muller SEMABarchitecting