In this post we explain what modeling is and how switching to a modeling standard drives a fundamental shift in understanding of how the output of architect’s work can add value.
In many organizations, architecture output is delivered via design documents where the content is primarily text complemented with pictorial illustrations, often Visio diagrams. The content is usually written in the context of the project. The organization may provide the architect with architecture templates to “document the architecture”. As the template controls the content and the flow, the objective is to fill the templates like ‘forms’ and omit any blanks.
The design documents are typically stored in a document repository often called ‘design repository’ where the documents are grouped by projects. In order to find any information, one must find the right documents and weed through the text and pictures. Understanding the project context in which the document was written is also important. When the content is not understood, subject matter experts or document authors come to the rescue.
A design repository is, essentially, a shelf for electronic documents, and the process that fills the shelf is a document flow.
The described style of production of architecture artifacts is widely used across the industry and is also recognized as highly inefficient and the process is conceptually no different than paper-based document flow.
The advances in the architecture tools and modeling languages paved the way for the modeling approach, which also changes the way information is captured, stored and then utilized. This also improves the ability to quickly access any necessary information from across the entire corporate ecosystem, which directly affects project costs and timelines.
The content of the model can be produced in the two complementary ways: modeling and automated data uploads. In this article, we focus on modeling.
Modeling is usually defined as a continuous and systematic process of discovery, analysis, drawing and then optimizing the model to produce the desired output. The modeling approach requires a standard visual modeling language and a modeling tool.
A visual modeling language is defined by a consistent set of rules, or grammar and it uses graphics to express information as structures composed of elements and their relationships. When a standard modeling language is used, it is more effective for trained users to either produce or consume a model than any unstructured text and random-style illustrations. For example, an electrical engineer can understand electrical schematics without reading any complementary text documents or watching presentations that would explain what the drawing means. That is because the model tells the story.
The following example compares visual model created with the use of ArchiMate 3.0 modeling language and its textual equivalent:
Textual Narrative:
‘Jane is using web interface provided by OkLink application to self-register to Dr. Kane’s dental office’.
Visual equivalent:
The architecture diagram, which we refer to as view is shown in Figure 4. It has been created with a standard modeling language ArchiMate. The view reads like a text, and it is intended to replace text within design content. However, it provides more useful information than was captured in the text:
The elements of the view are stored in the database. The elements and their relationships are called ‘model’. Many views can be produced out of a model.
The model provides a structure which we would extend when we need to elaborate more e.g. add the location, processes in the office, etc.
As the language is formal, some rules need to be followed. For example, we must be very specific e.g. we capture the names, their people’s roles, the services provided, etc.
As the models are stored as data, the data can be used for searches, drilling downs, and reporting either manually or with the use of the tools. When a model has enough data, multiple views can be created to show various focal points or perspectives (called viewpoints) dedicated to targeted audiences: business, project management, developers and engineers and other interested parties.
In our example, we use the business and application concepts, but it can be more. ArchiMate is used with TOGAF ADM (Architecture Development Method). Mapping between these two is shown in the figure below:
The modeling process flow starts from the vision and it goes top-down through the layers. The process of modeling resembles the process of software development. When we say that a software program compiles, we mean that it follows all the rules that make it runnable. Similarly, a model “compiles” when all its elements are defined and linked such that the whole structure is ready to be used for searching, reporting, drilling up and down through the links, and other activities.
Therefore, a living model (data), not the documents, become the primary source of reliable and up to date information collected from every corner of the organization. The documents can be produced on demand in a desired format including custom templates, while the process of producing the documents can be fully automated.
Therefore, transition to the modeling approach represents a fundamental shift in understanding of what Architects should deliver to the organization and how the output of Architecture work can add value.
To be successful in adopting the modeling approach, the organization need to tune up its processes, adopt the standards and apply certain rules. None of this is meant to increase risks or raise costs. Quite the opposite, this is a great opportunity to increase the quality and speed, reduce the risks and turn costs into innovation funds.
Learn More
Comments