Module 5: Enterprise Architecture Modeling Processes (Prefinals)

Modeling as a Transformation Process

1. Knowledge Representation

2. Knowledge Goals

3. Knowledge State

4. Knowledge Transformation

5) Central Representations

Knowledge Representation (MTP)

This depicts an enterprise architecture model in a specific manner.

Important points in MTP

*** Architecture models are created in order to establish communication between the individuals reading the model and/or the individuals developing the model.

*** Models can also be used to describe the current and future situation of an organization, as well as the possible development requirements.

*** Enterprise architecture involves the identification of relationships between different domains while providing a high-level overview.

Different Modeling Activities

1. Establishing the purpose, scope, and focus

2. Selecting one or more viewpoints

3. Creating and structuring the model

4. Visualizing the model

5. Using the model

6. Maintaining the model

1 Establishing the purpose, scope, and focus

(Modeling Activities)

It is a goal-driven activity wherein architects determine all possible stakeholders and the different purposes of the model in relation to the stakeholders.

1 Establishing the purpose, scope, and focus

(Modeling Activities)

This is considered as a starting point in establishing a model.

2 Selecting one or more viewpoints

(Modeling Activities)

Models are created using different viewpoints that give a specific set of concepts and relations to be used during the modeling process.

3 Creating and structuring the model

(Modeling Activities)

This activity involves requirements gathering, such as appropriate information, to create, structure, and visualize an enterprise architecture model.

4 Visualizing the model

(Modeling Activities)

Stakeholders and their needs must be considered in visualizing a model.

Central Model

It is an example of a way to visualize a model.

5 Using the model

(Modeling Activities)

Evaluate whether the model and the visualization achieved the intended outcome.

Typical steps in using visual representation

(Using the Model)

1. Validation

2. Obtaining Commitment

3. Informing

Types of Modeling Actions

1. Introduction

2. Refinement

3. Abandoning

4. Abstraction

5. Translation

6. Documentation

Possible process-related translation

(Translation)

1. Creating or replacing an element so it matches the meaning of a concept from another language or context.

2. Linking an element to an element on another model or modeling language.

3. Linking an element to an intermediary language when a model needs to be translated to more than one language or context.

4. Specifying rules to empower standardized and coherent translation between a context and a language.

Reasons for documenting modeling actions

(Documentation)

1. To be able to backtrack the previous state of a model.

2. To revisit rejected alternatives.

3. To record modeling logical basis related to traceability, accountability, etc. of a modeling process.

4. To add conceptual meta-data, such as date, location, name of the person who performed the activity, and the specific model elements that were affected.

Knowledge Representation (MTP)

based on the agreed perception of the individuals involved in the process.

Knowledge Goals (MTP)

These are the goals under the modeling process of an enterprise architecture.

Knowledge State (MTP)

This involves the condition and commitment of stakeholders on enterprise architecture.

Knowledge Transformation (MTP)

This is the situation where knowledge passes through the modeling process while considering goals and guidelines.

Central Representations (MTP)

These are the primary and essential models that are used in the transformation of knowledge.

Architecture models, reading, developing

(Important points in MTP)

______ are created in order to establish communication between the individuals ____ the model and/or the individuals ____ the model.

Models

(Important points in MTP)

This can also be used to describe the current and future situation of an organization, as well as the possible development requirements.

Enterprise architecture

(Important points in MTP)

This involves the identification of relationships between different domains while providing a high-level overview.

2 Selecting one or more viewpoints

(Modeling Activities)

This serves as a guide in determining appropriate information to be included in the model.

3 Creating and structuring the model

(Modeling Activities)

· Additional information can be acquired using interviews or discussions with stakeholders. Structuring reduces the visual complexity of a model.

4 Visualizing the model

(Modeling Activities)

Different viewpoints, text, and tables are also used as a starting point in visualizing a model.

5 Using the model

(Modeling Activities)

This activity uses the model representation to communicate with the stakeholders.

Validation

(Using the Model)

This involves checking whether the key stakeholders agree that the viewpoints in the model are correct representations of the actual and intended situation.

Obtaining Commitment

(Using the Model)

After reaching an agreement during validation, the key stakeholders must commit that they fully understand the potential impacts of implementing the model.

Informing

(Using the Model)

This involves the dissemination of information to all the stakeholders.

6 Maintaining the model

(Modeling Activities)

Enterprise architecture model must be kept up to date for it not to lose its value for the stakeholders.

6 Maintaining the model

(Modeling Activities)

It is maintained to reflect changes in infrastructure, the business processes, or the enterprise products and/or services.

Introduction

(Modeling Actions)

Introduce a candidate element in a model.

Introduction

(Modeling Actions)

This is the act of placing a fresh term for a concept or relation within a model.

Introduction

(Modeling Actions)

The candidate element must be somehow relevant but not necessarily linked to the model.

Introduction

(Modeling Actions)

It may be refined or deleted later on.

Refinement

(Modeling Actions)

Refine an element in a model.

Refinement

(Modeling Actions)

Other than introducing new elements, refining can be done by adding specific details to existing elements.

Two (2) Forms of Refining an Element

(Refinement)

1. Classify the newly introduced candidate element based on the concepts used in the model.

2. Provide an additional description (such as adding internal details, writing a definition, and nesting models) to an element rather than adding a new element.

Abandoning

(Modeling Actions)

Abandon a model element.

Abandoning

(Modeling Actions)

This involves an explicit decision of eliminating or delete a concept or relation with proper documentation, to avoid the concept of "lingering around."

Abstraction

(Modeling Actions)

Abstract from a concept or relation.

Abstraction

(Modeling Actions)

The concept of abstraction is the opposite of refinement.

Abstraction

(Modeling Actions)

In this activity, an architect decides whether information, that is available in the model, is to be left out or not.

Translation

(Modeling Actions)

Translate an element.

Translation

(Modeling Actions)

This is the process of finding a suitable alternative for an element.

Translation

(Modeling Actions)

Documentation is required in order to keep track of the existing relationship between models or contexts.

Documentation

(Modeling Actions)

Document modeling actions.

Documentation

(Modeling Actions)

This action involves the administration and documentation of all or some modeling actions, such as refinement and abstraction.