| Modelling Information Views |
|
|
|
|
Information Views are used to capture the particular views of an Information Concept that exist within the business. This tutorial describes how Information Views are captured in Essential Architecture Manager.
An Information View describes in more detail a particular view that a part of the organisation has of an Information Concept, e.g. Marketing's view of Customer. An Information Concept can have many different Views - enabling you to identify the different perspectives on an Information Concept that exist in your architecture and to understand the requirements for the diverse views of the concept.
The purpose of the Logical Information Layer is not to capture detailed entity relationship diagrams but rather to understand the types of Information elements that exist in the Enterprise Architecture and the dependencies between them.
In each Information View you can capture the specific attributes that the view has, e.g. to model the difference between two views. However, you do not have to capture the attributes for each Information View if this level of detail is not important for your architecture initiatives. You can always add them later. Examples include:
Information Views have fully-qualified names that are managed automatically by Essential Architecture Manager. These fully-qualified names are constructed from the Information Concept that this is a view of and the specific view name. You only have to supply the specific view name. Creating an Information View
You need to give the View a name - in the 'View Name' field - that succinctly describes the particular view of the Concept, e.g. Marketing View. Essential Architecture Manager will then create the fully-qualified name, Customer::Marketing View for you in the 'name' field.
To do this click on the Add Instance button Once you have completed these, complete as much detail in the form as you can at this time.
Remember to use the Add Instance button
|