Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - adepreter

Pages: 1 [2] 3 4 ... 11
An enterprise, a country, a human, a team, the earth, the universe ... these are all systems.

So the first thing you need is the semantics of a system that can be fortuitous or intentional and that can belong to the digital, physical and mental sphere (any combination)

From systems semantics you can derive more specifically the semantics of an enterprise including the internal system that transforms the enterprise i.e. the transformation framework.
These more specific semantics are represented using a conceptual metamodel (here at 2 levels of details):

From the conceptual metamodel you can derive your language metamodel i.e. the metamodel expressed in the language used by the end user
The required language metamodel
- varies a lot depending on the existing enterprise culture and architecture maturity.
- needs to be readable easily by end users; so use the language that the end user uses)
- evolves very quickly over time, especially in the beginning; so it needs to be changeable very easily

This is summarized on this page

A very basic metamodel described using a metamodeling language is feasible.
But in the real world, describing a realistic Enterprise Architecture with that approach makes the metamodel unreadable and difficult to manage.
And if you add strategy and solution architecture then it is just not feasible for a member of the human kind at least.

By using the modeling language itself, you can scale and you make your end users happy.
You can change and deploy the metamodel in two clicks.

We could easily add the ability to specify the relationships using a type hierarchy of abstract types, but we haven't see the need yet.
It would make it easier for the administrator but not necessarily for the end user.

Here we have Strategy, Enterprise Architecture and Solution Architecture in a single language metamodel.
You can't do that with a meta-modeling language.
Nor can you do this with ArchiMate by the way (for several reasons).

This is how we successfully resolved these problems at very large scale:

We use target capabilities as in the Scaled Agile Framework (SAFe).
Since target capabilities are high-level requirements, we use stereotyped requirements.

So we can then create target capabilities roadmaps:

And to avoid the usual semantic mess around "business capabilty" vs "business function", we use the word "Enterprise Functions" to define our functional taxonomies and the word "capabilities" for the target capabilities that we plan to deliver. So there is no more discussion.

Whatever the terms are, we first focused on the definition of the transformation process and on the semantics needed (conceptual metamodel) throughout the process.
Then we derived a language metamodel which is our real user-friendly metamodel that is both readable and used for validation.
Then we defined the viewpoints needed throughout the process along with the dependencies between these viewpoints.

General Board / Re: How to create an ArchiMate model?
« on: March 12, 2020, 08:56:27 pm »
Another example.

Click on this link:

Then click on "Canonical Repository Structure"

Suggestions and Requests / Re: Allow Diagram Frames to be scaled
« on: March 11, 2020, 04:02:16 am »
+1  +++++

I really need this as well.

For now I have to create images instead .. and then update the image each time the referenced diagram changes too much.

Thank you skiwi for the request!!

Suggestions and Requests / Modernizing List/Model View
« on: March 11, 2020, 03:53:50 am »
In a List/Model View, users should be able to
- find selected element in the project browser without entering Edit mode
- add properties/tagged values e.g. like in Windows Explorer
- color cells based on "auto legend" and values (properties or tags)
- edit values
- sort

Automation Interface, Add-Ins and Tools / Re: Cover page not available
« on: March 11, 2020, 03:46:26 am »
I stumbled upon that bug as well.

Try using up and down keys instead.

Labnaf ( includes a customization workbench to ease language customization.

There are also commands to rename and delete tagged values as you wish, translate any language to any language....

Have a look at Labnaf (

In two clicks, all quick links are generated from the metamodel ... which is expressed using the modeling language itself.

General Board / Re: How to create an ArchiMate model?
« on: February 26, 2020, 02:41:07 am »
Have a look at Labnaf:

General Board / Missing word wrapping in Heat Maps => text unreadable
« on: February 26, 2020, 02:38:29 am »
Heat map rectangles display text on a single line which make many of these boxes unreadable

PCS General Board / Re: Capability Maps with maturity built in
« on: December 29, 2019, 10:02:47 pm »
Heat maps can be also automatically generated based on template diagrams.
You can put any auto legend on the template diagram to color as you wish based any tagged value or property.
Elements on the heat maps are real elements that you can navigate, trace and zoom in.
They are automatically grouped, colored and resized (based on the template) so that a maximum of elements can be visible.
Generation can be
- on demand using the UI for a specific item
- scheduled as you wish for the entire model

The generated heat map diagrams also automatically include links to all diagrams inside each element so that the HTML version of the model gets completely navigable. Each HTML version of any diagram includes a little envelope that you can click on to send an email with a link to the diagram.


It takes much more time to define what to do (in terms of semantics, language, transformation process and tools) then to do it.
If you know what to do then it would take one months to make something usable (at least to start with).
You might want to fix ArchiMate at the same time and come up with a language with real semantics.

I would not let security kill my business.
The key is to be able to manage complexity, have end to end traceability and be able to zoom in and out.

Therefore you need one repository with
- a prescribed structure of folders (packages)
- a prescribed structure of elements in these folders
- prescribed diagram types (viewpoints) in that structure of folders and elements

Here is some practical guidance for the structure of such a repository:

Look at the "Canonical Folder Structure" in the project browser.

You can download a full startup repository as part of the Labnaf trial software package available here:

Additional educational material regarding strategy, architecture and most relevant standards is available on


General Board / Re: Import of large model from an external source
« on: November 28, 2019, 08:10:55 am »
Once you completed your import you might want to translate your language element and connector types to other types in another language or in the same language.
You might also want to rename tagged values.
Or delete tagged values.
Or change the direction of connectors.
Or change connector types based on the types of the connector ends.
(by type I mean type and/or stereotype)

The Labnaf Addin ( comes with a free Language Translator that let you do all the language translations that you will need to/from any language.

Pages: 1 [2] 3 4 ... 11