3. Architecture Dimensions

Question 1

Architecture Dimensions

Answer 1

1. Aspect
2. Aggregation
3. Abstraction
4. Realization

Question 2

Describes different specific ways to look at an architecture, providing a certain “cross-section” of an entire architecture description

Answer 2

Aspect dimension

Question 3

Describes the level of detail of an architecture description, ranging from very coarse (few elements) to very detailed (many elements)

Answer 3

Aggregation dimension

Question 4

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)

Answer 4

Abstraction dimension

Question 5

Describes the spectrum from very business-oriented descriptions (no attention for IT elements) to very IT-oriented descriptions (no attention for business details)

Answer 5

Realization dimension

Question 6

Truijens 5 modern aspects framework

Answer 6

1. Data aspect
2. Process aspect
3. Software aspect
4. Platform aspect
5. Organization aspect

Question 7

Kruchten 4+1 aspect framework

Answer 7

1. Logical view
2. Process view
3. Development view
4. Physical view
5. Scenarios

Question 8

Aggregation dimension: Explode components

Answer 8

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

Question 9

Abstract dimension: General vs. precise terms

Answer 9

1. Class type components
2. System type components
3. Vendor type components
4. Vendor version components

Question 10

Difference between aggregation and abstraction

Answer 10

Changing the number of elements (aggregation) or not (abstraction)

Question 11

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)

Answer 11

The dimension can be interpreted as ranging from very business-oriented to very technology-oriented

Question 12

We use the BOAT framework for the

Answer 12

Realization dimension

Question 13

BOAT framework

Answer 13

1. Business (B)
2. Organization (O)
3. Architecture (A)
4. Technology (T)

Question 14

BOAT: Business

Answer 14

Answers the question:

1. why a specific information system exists
2. what should be reached?

Is not interested in how things are done.

Question 15

BOAT: Organization

Answer 15

Describes how organizations are structured to achieve the business goals, using organization structures and business processes.

Automated systems are not part of this level.

Question 16

BOAT: Architecture

Answer 16

Describes how automated systems support the organization

Question 17

BOAT: Technology

Answer 17

Covers the concrete ingredients from information and communication technology (hardware, software, languages and protocols)

Question 18

How to structure a sequence of model transformations

Answer 18

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.

Question 19

Kruchten 4+1: Logical view

Answer 19

Specifies the object/module models

Question 20

Kruchten 4+1: Process view

Answer 20

The way objects/modules in the logical view dynamically collaborate in parallel

Question 21

Kruchten 4+1: Development view

Answer 21

The organization of the software in development environment

Question 22

Kruchten 4+1: Physical view

Answer 22

Mapping of software onto hardware

Question 23

Kruchten 4+1: Scenarios

Answer 23

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.