Professional Documents
Culture Documents
Home
for the lower level. Understanding the requirements and constraints necessitates communication
of knowledge and understanding from perspective to perspective. The Framework points the
vertical direction for that communication between perspectives
Let us have a look at these levels in some more details.
Contextual (Scope)
1.
(Why) Goal List primary high level organization goals. In most cases, these will be
defined elsewhere in the organisation, Such as Organisation Vision, Business goals etc.
2.
(How) Process List list of all known and proposed processes. At this level just the
identification of the processes is needed. No need to go into details of the process. Just
identify the process name and its purpose.
3.
(What) Material List list of all known organizational entities. A common and easy way
to list this is to identify thinks which can be classified as noun
4.
(Who) Organizational Unit & Role List list of all organization units, sub-units, and
identified roles.
5.
6.
(Why) Goal Relationship Model identifies hierarchy of goals that support primary goals
2.
(How) Process Model provides process descriptions, input processes, output processes
3.
(What) entity Relationship Model identifies and describes the organizational materials
and their relationships
4.
(Who) Organizational Unit & Role Relationship Model identifies enterprise roles and
units and the relationships between them
5.
(Where) Locations Model identifies enterprise locations and the relationships between
them
6.
(When) Event Model identifies and describes events and cycles related by time
1.
(Why) Rules Diagram identifies and describes rules that apply constraints to processes
and entities without regard to physical or technical implementation
2.
(How) process Diagram identifies and describes process transitions expressed as verbnoun phrases without regard to physical or technical implementation
3.
(What) Data Model Diagram identifies and describes entities and their relationships
without regard to physical or technical implementation
4.
(Who) Role Relationship Diagram identifies and describes roles and their relations to
other roles by types of deliverables without regard to physical or technical implementation
5.
6.
(When) Event Diagram identifies and describes events related to each other in
sequence, cycles occur within and between events, without regard to physical or technical
implementation
(Why) Rules Specification expressed in a formal language; consists of rule name and
structured logic to specify and test rule state
2.
3.
(What) Data Entity Specification expressed in a technology specific format; each entity
is defined by name, description, and attributes; shows relationships
4.
(Who) Role Specification expresses roles performing work and workflow components
at the work product detailed specification level
5.
6.
Eventually the cells with the detailed representation give Rules detail for (Why); Process detail
for (How); Data detail for (What); Role detail for (Who); Location detail for (Where); and Event
detail for (When).
Functioning (Actual System View)
This view is not used for enterprise architecture while the enterprise is described by rows one to six,
enterprise architecture uses only rows one to five