1/36
Looks like no tags are added yet.
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.
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.
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.
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.
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. Two forms: Classify the newly introduced candidate element based on the concepts used in the model; 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.
Documentation
Document modeling actions. This action involves the administration and documentation of all or some modeling actions, such as refinement and abstraction.
Model
This is an explicit and intellectual conception of real-life aspects based on a clearly defined purpose.
Visualization
This pertains to the form in which a model is presented.
Fundamental Guidelines
A model has to provide answers to specific business, application, and/or technology-related questions; Make a clear distinction between a model and its visualization; Real-life aspects that are likely to change over time are often included in a model, so models must be dynamically designed; Be economical in models and views; Make concepts and structures recognizable; Apply real-life concepts in denoting elements in a model; Create consistent models; Keep abstraction levels consistent; Make models correct, accurate, and complete; Different concerns should be addressed in different parts of the model, or through related models; Select the design viewpoints that match the established objectives; Only include elements that directly contribute to the realization of the modeling objectives; Do not be afraid to abandon irrelevant elements that clutter a model; Make a model as self-explanatory as possible; Separate internal and external behaviors; Collect feedback from various stakeholders; Use enterprise architecture layer and group by phase.
Inwards
Towards the internal composition of the elements.
Upwards
Towards the elements that are supported by it.
Downwards
Towards its realization by other elements.
Sideways
Towards peer elements with which it cooperates.
Limiting the visual complexity of a model
Reduce the number of concepts in a model; Reduce the number of elements in the model; Reduce the number of relations depicted in the model.
Proximity
People have the tendency to relate objects that are near to each other. Therefore, related objects should be placed near to each other. The proximity rule also applies to colors, wherein objects with the same color can indicate relationships between objects.
Similarity
People have the tendency to perceive objects that are similar, belong together as a unit. Also, objects with similar size are often perceived as having the same or equal importance.
Continuity
People have the tendency to perceive a line as continuous establishing directions, based on their perspective. Therefore, lines forming a right angle should not be positioned next to each other in a model, to avoid confusion.
Closure
People have the tendency to perceive incomplete objects as complete and asymmetric objects as symmetric. Symmetry and regularity increase the readability of models and reduces perceived complexity.
Common Fate
People have the tendency to perceive different objects that move or function in a similar manner as a unit.
Use of Layouts
The layout aspects of a diagram include basic pattern, horizontal and vertical alignment, above/before positioning, symmetry, distance of objects, distribution and density objects and connectors. Guidelines: Properly utilize white space; Make a clear distinction between normal proceedings and exceptions; Apply symmetry to stress similarities; Model time dependencies from left to right; Avoid crossing lines.
Use of Symbols
The shapes of objects in a model usually match the intrinsic properties of the real-life objects. Guidelines: Use similar shapes for similar concepts; Use line width to stress important relations.
Use of Colors
Color is a strong visual signal. It is a visual attribute that is strongly influenced by "prior knowledge." It can also increase the appeal of a diagram, but can also lead to contrary effects, such as confusion and distraction. Guidelines: Use color for similarity; Use color to convey emotions; Limit the number of colors.
Use of Texts
Texts suggests proper interpretations, associations, and stimulates thinking. It also speeds up the creation of a proper mental state in modeling, while creating a good starting for the line of reasoning. Guidelines: Use domain-specific terminologies; Use appropriate naming conventions.