Introduction
The terms enterprise taxonomy or classification, enterprise architecture frameworks, and enterprise reference architecture frameworks are often used interchangeably – this is the beginning of the enterprise puzzle. The enterprise Rubik cube has now become the prime game for all of the enterprise. However, "The rules of logic are to mathematics, those of structure are to architecture". This week’s discussion will delineate between each of these terms. This issues aims to solve the enterprise architectural twist with the help of a classification framework.
What is Enterprise: Decide ‘A’ Versus ‘The’
The enterprise can be imagined as a set of interacting business processes functioning as a whole, which is distinguishable from its surroundings by recognisable boundaries. The function of an enterprise depends upon the nature and collaboration of the business processes. It [usually] changes if any of the process is added, removed, or modified.
The nature of any enterprise can be understood by looking at how CIMOSA sees an enterprise. This is illustrated in Figure 1.
Fig. 1: An Enterprise as a Matrix (Reference [CIMOSA])
An enterprise, therefore, consist of a few domain process boundaries collaborating with the value chains enabled through business process integration. Figure 1 shows the matrix nature of an enterprise. This diagram is a modified version of CIMOSA-based decomposition of the Domain Model into granular Functional Entities. This simplified diagram clearly explains the decomposition of an enterprise into a matrix. Each Functional Operation represents functionalities (sub-activities) and each Functional Entity represents Technology (aggregation of resources). Each Functional Operation may be executed by one or more Functional Entity, which means that two different Functional Entities may share some common concern. So an enterprise can be imagined as a matrix of macro-level Activities and micro-level Functional Entities.
Therefore, an enterprise could be depicted in UML , as illustrated in Figure 2.
Fig. 2: UML Depiction of an Enterprise – (The Figure Shows Enterprise Participants and Their Interrelationships Modeled in UML)
The story starts with the creation of the Enterprise Architecture. Enterprise architecture is a view representation of the entire system from the stakeholders’ perspective and a realisation of the associated set of concerns. Enterprise views are the input criteria for any enterprise architect to design the right enterprise architecture. Enterprise viewpoint covers concerns of the enterprise stakeholders, which eventually realises into specific views. This view versus viewpoints relationship can be compared tothe object-oriented class concepts where viewpoints are abstract class types and views are concrete class type. Figure 3 depicts the relationship between views and viewpoints.
Fig. 3: Views Versus Viewpoints Relationship
The creation of an Enterprise Architecture is therefore the implementation of the associated views of that system boundary, involving following sequential steps:
- Identification of enterprise entity
- Identification of the associated stakeholders (an effective way is to use the onion model as discussed in the previous issue)
- Identify the concerns
- Identify the viewpoints
- Derive the views based on the identified viewpoints
- Implement the views
Creating an Enterprise Architecture therefore involves careful consideration of the views and viewpoints.
Enterprise Classification or Translation Framework
An enterprise classification framework organises the explicit knowledge and intelligence of the enterprise business entity in an efficient way on the basis of stakeholders’ views and viewpoints to help build the enterprise architecture. On the other hand, the Enterprise Architecture Framework builds the enterprise considering classification information. The Enterprise Classification Framework is an analytical tool that facilitates clear descriptive representations of any complex adaptive enterprise system. Figure 4 explains how the Enterprise Classification fits into the Enterprise Architecture Framework Puzzle stack.
Figure 4: Enterprise Architectural Puzzle Stack
Enterprise classification provides the following benefits to Enterprise Architecture:
- Accumulates all disjoint or noncohessive information intelligence about the enteprise business entity
- Elaborates the fuzzy enterprise boundary
- Helps to form an ordered enterprise system
- Enables an integrated operative systems that bridges the gap between the business and technology
- Acts as an analytical information intelligence system that provides enterprises a common integration baseline
Figure 5 depicts the top-down approach of the architecture development process:
Figure 5: Top-down Approach of Architecture Derivation Techniques
Enterprise Classification Framework generates a set of information that helps us to build up the actual enterprise architecture very easily and quickly.
Enterprise Architectural Concepts and Enterprise Classification Framework Contribution
In the issue, Enterprise Architecture Concepts, I detailed the Enterprise Architectural concepts as introduced by GERAM. Table 1 is a summary of those areas where the Enterprise Classification Framework provides a substantial contribution.
Figure 6 depicts the contribution of enterprise classification framework within the Enterprise Architecture Framework context:
Figure 6: Classification Framework as a Helping Hand
The Enterprise Classification Framework and Enterprise Architecture Framework are therefore not a substitution of the other; they are complimentary to each other.
Conclusions
Enterprise Classification Framework is an excellent way to classify or translate the Enterprise Business Entity information into Enterprise Architecture Requirements. This week we have introduced the concept of Enterprise classification Framework that helps us to quickly build a solid EA foundation. Next week, we are introducing the way of creation of a MDA based enterprise classification framework called E=MC2 where Matrix Enterprise is powered by models and driven by cross cutting concerns. The discussion will also highlight the position of Zachman framework as an Enterprise Classification Framework.
References
[GERAM] GERAM: Generalised Enterprise Reference Architecture and Methodology. Version 1.6.3 ( http://www.cit.gu.edu.au/~bernus/taskforce/geram ) also in P.Bernus, L.Nemes and G. Schmidt (Eds) Handbook on Enterprise Architecture, Berlin : Springer (2003) pp 22-64.
Handbook on Enterprise Architecture, by Bernus, P., Nemes, L. and G. Schmidt (eds.) , Springer, (2003), ISBN is 3540003436
[CIMOSA] http://www.pera.net/Methodologies/Cimosa/CIMOSA.html
Extending and Formalising the framework for information systems architecture by J.A.Zachman and J.F.Sowa Published in IBM Systems Journal, 31(3): p 590-616, 1992
|
