September 2, 2015
A recent, provocative, post on linkedin, posed some issues about the Archimate standard.
One of my first doubts, using introducing Archimate in our Architecture Capability, was: “why was it created as a separate graphical language and not as an UML profile?”. This doubt is still in my mind, in my previous post about this topic, I have inserted some links about this argument. The “UML profile” solution appears as natural, because a lot of classifiers from UML are available – with the same semantic and graphical notation – also in Archimate.
What are the consequences of a “separate” graphical model?
(+) dedicated modeling tools
(-) multiple skills/tools/repositories
(-) requirements for model integration
On the other side, I think that we should remember that Archimate and UML have different “meanings”:
- Archimate is for architecture,
- UML is for engineering.
Also if you look at building design, you will find an “Architectural” project, showing you the shape, internal space allocation, external appearance, of the building, and several specialized views (structural project, electrical plant, elevators, etc.); perhaps the potential buyer of the house is not interested in how many cables or switches are necessary to operate the elevator – and could not understand this view – but is interested in the size and number of windows of the living room.
Despite this, I believe that “Archimate as UML profile” could bear the same expressiveness, the same semantic content, and a seamless integration of architectural and technical layers.
Personally, I am evaluating the introduction of Archimate, and starting to represent (maybe with better results) our architecture with this language. But, in the mean time, and waiting for the similar OMG work, I am starting do develop an UML profile with the same content of Archimate. At this point, we are working on the Business Layer. The modeling tool that we use, by Sparx Systems, allows for an easy integration on different models using UML, BPMN or Archimate, so it does not force the user to a specific adoption profile. But, in the meantime, the UML-profile approach is allowing us to obtain stakeholder-oriented documentation with a better quality, and an easier transition from the previous graphical representation standards.
At the same time, the introduction of Archimate shows its usefulness in a more formalized and rigorous architectural design practice, relaying on a number of elements that fits well with the various organizational patterns that exists in our Company.
The results – at this point – are promising, I will share them later, and introduce some of them in the second edition on my book about BPMN.
Bottom line: I believe that we need archimate, as a component of our architecture capability. Maybe, representing it as an UML profile could help its adoption.
July 29, 2015
Representing organizational structures, roles, responsibilities, and linking this model with the process model, could be a mess, especially if your Architecture model should integrate perspectives modeled according to different standards.
I expose here some ideas that we are putting in practice across our Enterprise Architecture projects, in my current Company.
The topic of model mapping is hot: you can find a lot of interesting toughts in the blogs of Gerben Weirda. At the same time, the OMG is working on a UML profile for Archimate.
I will start with Archimate, and the basic elements from the Business Layer: Actor and Role.
The following picture, shows a suggested extension:
The Role is specialized, leading to four different stereotypes:
- Organizational role: a role that is specific of an organizational unit, eg. Director (role) of IT (unit).
- Functional role: a role that is specific of a function or authority assigned to a person, eg. Sales Representative.
- Process role: a role that has a meaning in the context of one or more processes, eg. “Purchasing requester”, “credit approver”
- Partner role: a role of an external partner in a collaboration, eg. Customer, Bank, Tax agency.
At the same time, the Actor element is specialized:
- Organization unit: an element of the organization which may be aggregated at an higher level, or may aggregate lower level units. The dependency may follow several patterns: hierarchical, matrix.
- Human Business Actor: a single, identified person.
- External partner: a person or organization external from our business.
The diagram shows the main relationships among elements. The “Process role” may be assigned to a human actor, another functional or organizational role. Anyhow, it is meaningful only n he context of execution of a single instance of one or more processes,
Why do we need those extensions? Well, mainly for ease of communication with some stakeholders. It is common wisdom that complexity in the metamodel leads to obscure resulting models (for the eyes of non-professional stakeholders). But in this case, I think that a little bit of specialization is useful:
- specialization of user roles helps the overall classification of them, and provide some guidance also for junior analysts and people outside the Architecture practice.
- Specialization of business actors helps avoiding the potential ambiguity deriving from the fact that a branch, an office, a bank, or a receptionist are all modeled with the same element.
In the following posts, I will describe how we have translated this profile in UML, and how we have linked the Business Layer with the relevant elements of BPMN models.
June 1, 2015
Every business deals with a finite number of entities, concepts, things, as you may prefer to name them.
Every modeling standard and project framework deals with this, approaching this description from several different viewpoints.
The existence of different descriptions, at different abstraction levels, for the same thing, and the logical links between these different modeling contexts, is one key output of an Enterprise Architecture capability.
Let’s look at the following picture, showing a common concept, “Vendor”, at different architecture layers.
The picture shows modeling elements from two widely adopted standards: BPMN and Archimate.
Context / Behaviour
A Vendor is usually a stakeholder, and an external party, for our business, As such, it may be represented with a Partner Role element, according to BPMN. This is mainly a reference role, a bookmark, also if we may wish to attach some documentation or classification elements. This element will have a place in BPMN process modeling, as a Participant in a collaboration.
Archimate modeling language includes two elements that can be used as a collaboration participant: Business Role and Business Actor. The Actor is an element modeling something which may or may not have a defined identity (in BPMN Partner Role doesn’t have an identity, while Partner Entity does), but have an independent capability to perform actively some tasks. A Role, on the contrary, is more a formal description of the duties, responsibilities, capabilities, interfaces used and provided, related to a business organizational unit or single person.
So, if we want to emphasize “what the partner does”, we can model it with a Role, but if we have more interest on “what kind of partner is”, we will prefer an Actor. Usually, and Enterprise Architect is interested in the “internal” architecture of his business and, in my opinion, will find the Actor element better suited for this task.
This is a typical element of Archimate, representing a wide range of possible items. I usually see the Business Object (a passive element in the Business Architecture Layer) as an element of the business dictionary. In every Company, when you start an interview with people with different roles, you will recognize a number of common “words”. They represent the products, the market, the external parties, the production facilities. They are the better candidates to be represented with a Business Object (behind this analysis, we may like to perform a more detailed ontological analysis on the concepts and relationships, but this is another chapter). At the Business Layer, a Business Object is not an “information item”, but is a collection of information, rules, connection with processes and internal organizational units, that will remain unchanged if we replace the information system with another one, without changing the business architectural layer.
In BPMN there isn’t a corresponding element, but we often use the Data Object to show which activities interacts with some parts of a Business Object. In general, I prefer to limit the “technical data structure pollution” in BPMN diagrams, this means trying to be as abstract as possible with respect to the actual data structure. The BPMN standard encourages this, providing a number of Item Aware Elements, that may reference any kind of physical, logical or informational element.
So, for instance, a process where one of the deliverable is the Vendor Master data, or a new Vendor Dossier, will see the “Vendor” Data Object.
Application and Database
Coherently with the approach followed for Data Objects, I usually use Data Stores to model “logical” database representations, detached from the actual database storing their data. Following the example in this article, we will have a “Purchasing” Data Store, including everything that is connected to the purchasing cycle: items, prices, vendors, orders, deliveries, etc. Someone may observe that a “Vendor” is also relevant in the “Accounting” Data Store, as part of the Accounts Payable, but I don’t agree. We deal with a Vendor because it is a provider of services and goods, not because we have an account opened with his name in our books.
Archimate, on the opposite, makes a clear distinction between the Application/Data layer – where the Data Object will have a strong “structure/database table” meaning, and the Device elements, which is used to represent the actual “hardware” hosting the Database.
By using a limited number of partially-overlapping modeling standards (in our choice: TOGAF, Archimate, BPMN and UML), we can obtain a powerful and detailed representation of our Business Architecture according to different perspectives and viewpoints. Business Concepts modeling is a key part of the Enterprise Architecture capability, allowing us to catch what is maybe the core knowledge base of our business. Extending upwards (Business interactions and processes) and downwards this modeling layers will give us the ability to track the impact of any change in our business scenario on all the levels of the Architecture.
April 28, 2015
Archimate uses the “Business Object” element to model a passive entity representing a concept or a business entity manipulated by behavioral business elements.
- using the “Meaning” element in Archimate;
- using an aggregation.
April 17, 2015
When you decide, or are involved, in an evolution project regarding your Organization division, perhaps your Company is willing to transform it in an Enterprise Architecture Capability, in other words a set of resources dedicated to design and support change management using comprehensive frameworks, like TOGAF.
It’s a good moment to think carefully about your objectives, and you can use TOGAF itself as a supporting framework for this project (TOGAF manual describes this task in the “preliminary” phase).
The core of this activity will be synthesized by:
- you “as-is” practice, that is your baseline Architecture Capability;
- the desired target Architecture Capability.
The differences between those two situations will be described using a list of gaps, that will be the starting point for your project definition.
Using Archimate – the modeling language that integrates very well TOGAF in many parts – we can describe these elements.
The figure is only an overview, but the gaps highlighted will guide you through a series of questions that will define your evolution:
- people and skills involved,
- organizational position of the Architecture team,
- usage of internal/external resources,
- scope (horizontal and vertical) of the analysis,
- interaction with IT, HR, Board, etc.,
- tools, standards,
- project management practice,
and so on.
This will be also a good opportunity to start practicing, in your “real” business, your new organizational structure. At the same time, during this project, you will produce – as a deliverable – an initial Enterprise Architecture, covering the basics layer of Business, Data, Application and Technology. This initial Architecture, stored in your Architecture Repository, will be used and refined in your following architectural projects.
April 7, 2015
The structural element representing the organizational unit in Archimate is the Business Actor. As the standard says, a Business Actor may be “a human, a department, or a business unit”.
- the sales organization is a business unit, with a manager; we suppose that the manager will be a single person.
- There are more Area Manager; the composition relation shows that the Sales Manager is their direct boss. Again, this “Actor” will perhaps be a single person, but there will be more people in this role, each of them assigned to a different geographical area.
- Within each “Area”, there are separate managers for each “Product”. All the Product Managers of an Area will report to the Are Manager. The geographical dimension appear to be the prevalent one.
- Perhaps there is also an orthogonal Product dimension; we can imagine that there is a global Product Manager, it’s not represented here, but is clearly possible.
- There is a single back office unit, working for the whole sales organization.