3. Architecture Dimensions Flashcards
Architecture Dimensions
- Aspect
- Aggregation
- Abstraction
- Realization
Describes different specific ways to look at an architecture, providing a certain “cross-section” of an entire architecture description
Aspect dimension
Describes the level of detail of an architecture description, ranging from very coarse (few elements) to very detailed (many elements)
Aggregation dimension
Describes how abstract or concrete an architecture is, ranging from very abstract (few concrete choices have been made) to very concrete (all concrete choices have been made)
Abstraction dimension
Describes the spectrum from very business-oriented descriptions (no attention for IT elements) to very IT-oriented descriptions (no attention for business details)
Realization dimension
Truijens 5 modern aspects framework
- Data aspect
- Process aspect
- Software aspect
- Platform aspect
- Organization aspect
Kruchten 4+1 aspect framework
- Logical view
- Process view
- Development view
- Physical view
- Scenarios
Aggregation dimension: Explode components
A component at the upper level corresponds to a number of components at the lower level, the functionality of which is usually a partitioning of the functionality at the higher level: all functionality is covered and there is no overlap
Abstract dimension: General vs. precise terms
- Class type components
- System type components
- Vendor type components
- Vendor version components
Difference between aggregation and abstraction
Changing the number of elements (aggregation) or not (abstraction)
The realization dimension defines a number of levels ranging from architecture goals (what we want to accomplish) to means (how we want to accomplish it)
The dimension can be interpreted as ranging from very business-oriented to very technology-oriented
We use the BOAT framework for the
Realization dimension
BOAT framework
- Business (B)
- Organization (O)
- Architecture (A)
- Technology (T)
BOAT: Business
Answers the question:
- why a specific information system exists
- what should be reached?
Is not interested in how things are done.
BOAT: Organization
Describes how organizations are structured to achieve the business goals, using organization structures and business processes.
Automated systems are not part of this level.
BOAT: Architecture
Describes how automated systems support the organization
BOAT: Technology
Covers the concrete ingredients from information and communication technology (hardware, software, languages and protocols)
How to structure a sequence of model transformations
Using architecture frameworks and/or architecture design methods, that provide the “cooking recipes” by specifying the sequences of design process steps and intermediate results between these steps.
Kruchten 4+1: Logical view
Specifies the object/module models
Kruchten 4+1: Process view
The way objects/modules in the logical view dynamically collaborate in parallel
Kruchten 4+1: Development view
The organization of the software in development environment
Kruchten 4+1: Physical view
Mapping of software onto hardware
Kruchten 4+1: Scenarios
Describe use cases that illustrate the four basic views. The scenarios make things concrete and provide a basis for discussions between the various groups of stake holders.
