TECHNIQUES AND TOOLS
The activities of an (enterprise) architect can be supported by the use of techniques and tools.
Architecture Techniques
Most of the architecture techniques are very descriptive in nature. They assist in the description or modeling of a particular situation. There are very few methods that can be used to define and document design principles. Most of the techniques are directed the descriptive architecture concept and focus primarily on modeling.
Many of the techniques come from IT. This means that the techniques are quite useful for (IT) system development but are much less useful for the design of an enterprise architecture. Despite this IDEF and UML are used by architects.
The modeling languages like ArchiMate, on the other hand, do concentrate on the enterprise as a comprehensive entity consisting of business; organization; information and technology. ArchiMate was developed to handle the enterprise architecture modeling and description.
IDEF
IDEF stands for Integrated Definition Methods. IDEF is actually a collection of 16 different techniques, all suited for a specific target.
Well known IDEF techniques are:
IDEF0 for process modeling of activities; actions and decisions
IDEF1 for data modeling
IDEF3 to describe systems by using functions and logical operators.
IDEF is used regularly for process modeling. However, as indicated earlier, only the descriptive aspects of the architecture are addressed and that only for a limited domain within enterprise architecture.
UML
The Unified Modeling Language was defined by the Object Management Group (OMG) as a standard development language for object oriented systems. UML is used primarily in the analysis and design phases of the development cycles. UML is routinely used for architecture descriptions. UML consists of the following components:
· Use case diagrams: describes what a system does from the standpoint of an external observer.
· Class diagrams: overview of a system by showing its classes and the relationship between them.
· Sequence diagrams: interaction diagram that details how operations are carried out.
· Collaboration diagrams: similar to sequence diagrams, but focus on object roles rather than times.
· Package diagrams: diagrams where a number of logically related UML elements have been combined into packages.
· Statechart diagrams: shows the possible states of the object and the transitions that cause a state change.
· Activity diagrams: in effect an elegant flowchart. Activity diagrams and Statechart diagrams are related.
· Component diagrams: components are code modules. Component diagrams are physical analogs of class diagrams.
· Deployment diagrams: show the physical configuration of software and hardware.
Extensions have been developed in addition to the abovementioned models. For instance: Use case diagrams for business modeling. The OMG is actively expanding UML to UEML (Unified Enterprise Modeling Language). These developments indicate that UML is transitioning from pure IT modeling to more enterprise modeling. Whether it will become an appropriate technique for architecture has yet to be seen. After all the focus is still on the descriptive aspect of architecture.
ArchiMate
Until recently there was very little practical support for architects modeling the enterprise. ArchiMate is changing that.
A number of years ago, a consortium of IT delivery and implementation stakeholders from industry and academia, initiated the development of the “ArchiMate” Project. The motivation for the initiative was the observation that business changes often failed due to the lack of an integrated and comprehensive approach. Domains affected by the changes are characterized by their isolationist approach, each with their own language; methods and resources.
The objective of the ArchiMate Project is to offer an integrated architectural approach that describes and visualizes the various enterprise domains and their relationships. Key is the development of an “architecture language” and visualization techniques in support of the architecture development process. The prospective language is primarily focused on inter-domain relationships and high level intra-domain relationships.
Comparison of modeling languages
A comparison of modeling languages and their application can be found in Chris Magee’s thesis: “Successful modelling of the enterprise”.
Architecture Tools
There are a number of different architecture tools available that have different backgrounds. A number of the better known ones are:
Enterprise Architecture Tools:
Architect (BiZZdesign), based on ArchiMate. Architect is ArchiMate certified.
IDS Scheer ARIS
Metis Enterprise (Troux). Metis is ArchiMate certified.
System Architect (Telelogic)
Process Modeling Tools:
IDS Scheer ARIS
BiZZDesigner (BiZZdesign)
Repositories:
Adaptive
Rochade (Allen Systems Group)
In general the tools offer the possibilities for modeling and development principles; visualization and publication; analysis; storage and administration.
