Enterprise Architecture Modeling Processes

Knowledge Representation 

This depicts an enterprise architecture model in a specific manner based on the agreed perception of the individuals involved in the process.

Knowledge Goals 

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

Knowledge State 

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

Knowledge Transformation

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

Central Representations 

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

Modeling as a Transformation Process Important points 

Modeling as a Transformation Process Important points 

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

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

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

• Establishing the purpose, scope, and focus

• Selecting one or more viewpoints

• Creating and structuring the model

• Visualizing the model

• Using the model

• Maintaining the model

What are the 6 Different Modeling Activities?

hints: ETPSF, SOOMV, CASTM, VTM, UTM, and MTM

Establishing the purpose, scope, and focus 

It is a goal-driven activity wherein architects determine all possible stakeholders and the different purposes of the model in relation to the stakeholders. This is considered as a starting point in establishing a model.

Selecting one or more viewpoints

Models are created using different viewpoints that give a specific set of concepts and relations to be used during the modeling process. This serves as a guide in determining appropriate information to be included in the model.

Creating and structuring the model 

This activity involves requirements gathering, such as appropriate information, to create, structure, and visualize an enterprise architecture model. Additional information can be acquired using interviews or discussions with stakeholders. Structuring reduces the visual complexity of a model.

Visualizing the model 

Stakeholders and their needs must be considered in visualizing a model. Different viewpoints, text, and tables are also used as a starting point in visualizing a model. Central Model is an example of a way to visualize a model.

Using the model 

This activity uses the model representation to communicate with the stakeholders and evaluate whether the model and the visualization achieved the intended outcome.

Maintaining the model 

Enterprise architecture model must be kept up to date for it not to lose its value for the stakeholders. It is maintained to reflect changes in infrastructure, the business processes, or the enterprise products and/or services.

o Validation

o Obtaining Commitment

o Informing

(USING THE MODEL)

What are the typical steps in using visual representation?

Validation

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 

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

Informing

This involves the dissemination of information to all the stakeholders.

• Introduction

• Refinement

• Abandoning

• Abstraction

• Translation

• Documentation

What are the 6 Types of Modeling Actions?

Introduction 

Introduce a candidate element in a model. This is the act of placing a fresh term for a concept or relation within a model. The candidate element must be somehow relevant but not necessarily linked to the model. It may be refined or deleted later on.

Refinement 

Refine an element in a model. Other than introducing new elements, refining can be done by adding specific details to existing elements. 

READ ONLY TEXT

READ ONLY TEXT

(REFINEMENT)

The following are the two (2) forms of refining an element:

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

o 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 

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

Abstraction

Abstract from a concept or relation. The concept of abstraction is the opposite of refinement. In this activity, an architect decides whether information, that is available in the model, is to be left out or not.

Translation

Translate an element. This is the process of finding a suitable alternative for an element. Documentation is required in order to keep track of the existing relationship between models or contexts.

READ ONLY TEXT

READ ONLY TEXT

(TRANSLATION)

The following are some of the possible process-related translation:

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

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

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

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

Documentation

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

READ ONLY TEXT

READ ONLY TEXT

(DOCUMENTATION)

The following are some of the reasons for documenting modeling actions:

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

o To revisit rejected alternatives.

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

o 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