IT1913

Enterprise Architecture Modeling Processes are also used as a starting point in visualizing a model. Central Model is
Modeling as a Transformation Process an example of a way to visualize a model.
• Knowledge Representation – This depicts an enterprise architecture • Using the model – This activity uses the model representation to
model in a specific manner based on the agreed perception of the communicate with the stakeholders and evaluate whether the model and
individuals involved in the process. the visualization achieved the intended outcome. The following are the
• Knowledge Goals – These are the goals under the modeling process of typical steps in using visual representation:
an enterprise architecture. o Validation – This involves checking whether the key stakeholders
• Knowledge State – This involves the condition and commitment of agree that the viewpoints in the model are correct representations
stakeholders on enterprise architecture. of the actual and intended situation.
• Knowledge Transformation – This is the situation where knowledge o Obtaining Commitment – After reaching an agreement during
passes through the modeling process while considering goals and validation, the key stakeholders must commit that they fully
guidelines. understand the potential impacts of implementing the model.
• Central Representations – These are the primary and essential models o Informing – This involves the dissemination of information to all
that are used in the transformation of knowledge. the stakeholders.
• Maintaining the model – Enterprise architecture model must be kept up
Important points (Lankhorst, et al., 2017). to date for it not to lose its value for the stakeholders. It is maintained to
o Architecture models are created in order to establish communication reflect changes in infrastructure, the business processes, or the enterprise
between the individuals reading the model and/or the individuals products and/or services.
developing the model.
o Models can also be used to describe the current and future situation of an Types of Modeling Actions
organization, as well as the possible development requirements. • Introduction – Introduce a candidate element in a model. This is the act
o Enterprise architecture involves the identification of relationships between of placing a fresh term for a concept or relation within a model. The
different domains while providing a high-level overview. candidate element must be somehow relevant but not necessarily linked
to the model. It may be refined or deleted later on.
Different Modeling Activities • Refinement – Refine an element in a model. Other than introducing new
• Establishing the purpose, scope, and focus – It is a goal-driven activity elements, refining can be done by adding specific details to existing
wherein architects determine all possible stakeholders and the different elements. The following are the two (2) forms of refining an element:
purposes of the model in relation to the stakeholders. This is considered o Classify the newly introduced candidate element based on the
as a starting point in establishing a model. concepts used in the model.
• Selecting one or more viewpoints – Models are created using different o Provide an additional description (such as adding internal details,
viewpoints that give a specific set of concepts and relations to be used writing a definition, and nesting models) to an element rather than
during the modeling process. This serves as a guide in determining adding a new element.
appropriate information to be included in the model. • Abandoning – Abandon a model element. This involves an explicit
• Creating and structuring the model – This activity involves requirements decision of eliminating or delete a concept or relation with proper
gathering, such as appropriate information, to create, structure, and documentation, to avoid the concept of "lingering around."
visualize an enterprise architecture model. Additional information can be • Abstraction – Abstract from a concept or relation. The concept of
acquired using interviews or discussions with stakeholders. Structuring abstraction is the opposite of refinement. In this activity, an architect
reduces the visual complexity of a model. decides whether information, that is available in the model, is to be left out
• Visualizing the model – Stakeholders and their needs must be or not.
considered in visualizing a model. Different viewpoints, text, and tables
05 Handout 1 *Property of STI
 [email protected] Page 1 of 2
 IT1913

• 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. The
following are some of the possible process-related translation (Lankhorst,
et al., 2017):
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 – Document modeling actions. This action involves the
administration and documentation of all or some modeling actions, such
as refinement and abstraction. 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.

References:
Lankhorst, M., BiZZdesign, Enschede, & The Netherlands. (2017). Enterprise Architecture at
Work Modeling, Communication, and Analysis (4th ed.). Berlin, Germany: Springer Nature

05 Handout 1 *Property of STI

 [email protected] Page 2 of 2