Part 2 - EA Modelling: ArchiMate, Views and Viewpoints, Analysis of EA Models Flashcards Preview

EAM > Part 2 - EA Modelling: ArchiMate, Views and Viewpoints, Analysis of EA Models > Flashcards

Flashcards in Part 2 - EA Modelling: ArchiMate, Views and Viewpoints, Analysis of EA Models Deck (29)
Loading flashcards...
1

What are the drivers of the need for an integrated architecture language?

Or why ARIS, BPMN, UML don't fit:

  • Poor definition of relationship between domains (views).
  • Poor alignment of layers.
  • Situation in paxis = no standard... 
    • leading to misunderstanding and usage of "own" languages.

2

What does the service concept and concept of layering mean and how is ArchiMate generally designed?

3

Which are the main layers and their respective purposes of ArchiMate?

  • Business layer
  • Application layer
  • Technology layer
  • Implementation & Migration layer

4

What are the ArchiMate modeling dimensions?

  • External (services, interfaces) - Internal
  • Collective (interaction, collaboration) - Individual
  • Structural (active, passive) - Behavioral

5

What is the difference between structural and behavioral elements?

Structural elements can be active or passive and can represent business actors or data objects.

Behavioral elements (like processes, functions) represent the behavior performed by actors (active structural elements).

6

What are the main concepts on the different layers and what is their respective purpose?

Business layer: 

  • offers products and services to external customers, which are realized in the organization by business processes.

 

Application layer:

  • supports the business layer with application services which are realized by (software) applications functions and components.

 

Technology layer:

  • offers infrastructural services (e.g. processing, storage and communication services) needed to run applications, realized by computer and communication devices and system software.

7

How are the three layers of ArchiMate interconnected?

They are interconected through services.

8

What are the posibilites of modeling:

interconnection

cooperation

collaboration

between elements on each layer?

9

How can the (main) elements of ArchiMate be related to one another?

Relations can be done through (see picture):

  • Association
  • Access
  • Used by
  • Realisation
  • Flow
  • Triggering
  • Specialization
  • Assignment
  • Aggregation
  • Composition
  • Grouping

10

Which elements and relations regard behavioural aspects and which regard structural aspects?

11

What are the two extensions to ArchiMate?

  1. Motivation Extension
  2. Implementation and Migration Extension

12

How does the meta-model of ArchiMate (in its entirety) looks like?

It depicts all the possible interactions between the elements of the Business, Application and Technology layers (see picture).

13

Regarding ArchiMate, what are views and viewpoints?

A view is governed by its viewpoint: the viewpoint establishes the conventions for construction, interpreting and analyzing the view to address concerns framed by that viewpoint.

A viewpoint is a specification of the conventions for constructing and using views.

14

For which purposes are viewpoints defined on an architecture?

A viewpoint is a specification of the conventions for constructing and using views.

15

How can viewpoints generally be classified?

How do the classification dimensions look like?

Viewpoints can be classified by:

  1. Purpose:
    • ​​Designing
    • Deciding = decision making
    • Informing
  2. Content:
    • ​​Details = one layer
    • Coherence = multi layers or multi aspects
    • Overview = multi layers and multi aspects

16

How do general guidelines for the creation of viewpoins look like?

A general guideline follows:

  1. Scoping
  2. Creation of views
  3. Validation
  4. Obtaining commitmen (if applicable)
  5. Informing

17

What application scenarios exist for model analysis?

18

What 8 analysis types does Niemann introduce?

  1. Dependency Analysis
  2. Coverage Analysis
  3. Interface Analysis
  4. Heterogeneity Analysis
  5. Complexity Analysis
  6. Compliancy Analysis
  7. Cost Analysis
  8. Benefit Analysis

19

From the 8 analysis types introduced by Niemann:

What is the aim of each type?

What are typical questions?

  1. Dependency Analysis
    • What elements will be affected when "X" is replaced?
  2. Coverage Analysis
    • Find redundancy or gaps in IT support (landscape map) 
  3. Interface Analysis
    • Interconnection of systems? Interfaces on standards?
  4. Heterogeneity Analysis
    • How many different technologies for the same problem exist?
  5. Complexity Analysis
    • How many ERP systems are deployed in total?
  6. Compliancy Analysis
    • Compliance with Government regulations?
    • -------- Functional / Non-functional --------
  7. Cost Analysis
    • Cost for using "X"?
  8. Benefit Analysis
    • Contribution of app "X" to the enterprise goals?

20

What are the (5) dimensions of analysis?

The 5 dimensions of analysis are:

  1. Body of analysis
  2. Time Reference
  3. Analysis Techniques
  4. Analysis Concerns
  5. Self Reference

21

How does a Gap analysis work?

What are the possible results of comparing two artifacts?

  • Included
  • Potential match
  • Eliminated: intentionally, unintentionally
  • Gap: to be deployed

22

Draw a general gap analysis matrix and explain its structure:

23

How do ArchiMate models have to be structured in order to perform a quantitative analysis?

(e.g. how does the general model structure looks like?)

  • Norm to Sec
  1. Assumption: Services realized by exact one internal behaviour (e.g. function)
  2. Assupmtion: Internal behaviour elements (e.g. functions) can be assigned to max of one resource (e.g. application component)

24

Which quantitative input has to be provided in order to perform a quantitative analysis?

A quantitative analysis needs 3 inputs:

  • Arrival frequency
  • Service Time S
  • Capacity R of resources

25

Which are the steps in a quantitative analysis?

Which measures are calculated in these steps?

  1. Workload (top-down approach)
  2. TUR (bottom-up approach)
    • Processing time T
    • Utilization U
    • Response time R

(see image with formulas)

26

Regarding the quantitative analysis:

How do normalized models have to look like?

27

Regarding the quantitative analysis:

How does workload propagate from top layers to bottom layers (top-down calculation)?

How is the workload calculated?

  • Workload (top-down approach)


28

Regarding the quantitative analysis:

Which time-related performance measures are propagated in the bottom-up calculation?

How are these measures calculated?

  • TUR (bottom-up approach)
    • Processing time T
    • Utilization U
    • Response time R

29

What is the general aim of the quantitative analysis?

  • Find overloads or bottlenecks
  • Check if response time at top level (customer contact) is sufficient to satisfy customer needs.