Modelling languages
MODELLING LANGUAGES AND MODELLING GUIDES
#ArchiMate #UML #BPMN #mallinnuskäsikirja
3 min read
#ArchiMate #UML #BPMN #ArchitectureModelling


A single modelling language is often not sufficient for describing architecture; instead, a combination of different modelling languages is required. Most of the content can be created using the ArchiMate® modelling language, but UML and BPMN might also be needed. There are many benefits to using standardised modelling languages, such as ensuring that all created diagrams are consistent, they are easier to utilise, and more readable. Additionally, these standard languages are configured into most modelling tools, so you don't have to spend time developing your own modelling language.
However, it is not enough for an organisation to simply select specific modelling languages to use. It is also worth considering your needs for architecture and modelling. Standardised modelling languages are too wide, and few organisations require the entirety of their content. Therefore, you should agree on a subset of the modelling language and how the language(s) will be used. But first, let's take a closer look at the most common modelling languages.
ArchiMate®
ArchiMate® is a widely used architecture modelling language created and standardised by The Open Group. It includes elements for describing, among other things, the governance level, business, information, applications, technology, and project management. ArchiMate® supports the architecture methodology defined by the TOGAF® framework.
Below is an example of a layered ArchiMate® diagram, which is a very typical depiction used in both enterprise architecture and solution architecture (depending on the level of detail).


UML
UML (Unified Modelling Language) is a modelling language standardised by the Object Management Group, originally developed for system and software development. From an enterprise architecture perspective, its common use case is data models, which can be created as UML class diagrams. A data model made with UML notation can include more detail (e.g., attributes of concepts) than data models created using ArchiMate® notation, which is why it is often chosen to support ArchiMate®. Below is an example of a simple conceptual model.
Solution architecture can also be supported by other types of UML diagrams if needed, especially when ArchiMate® elements do not provide enough detailed description. For instance, state or sequence diagrams may be useful for depicting precise solutions.


BPMN
BPMN (Business Process Model and Notation) is a modelling language maintained by the Object Management Group, primarily used for process modelling. BPMN diagrams can support both enterprise and solution architecture, especially when there is a need to create detailed descriptions of processes or workflows. BPMN notation is typically used for swimlane diagrams, which can be used, for example, to support user instructions. Below is an example of a typical swimlane diagram.


BLOGIT
Johdanto siihen mitä mallintaminen oikeastaan on, ja mihin mallinnuskieliä tarvitaan.
Tiedolla johtaminen on tapetilla useimmissa organisaatioissa. Tavoitteita on asetettu, toimenpiteitä käynnistetty ja rekrytointi-ilmoituksia julkaistu. Näinkö se toimii? Nimitetään tiedolla johtamisen vastuuhenkilö ja hän hoitaa homman kotiin?
WEBINAARIT
Webinaarissa käydään läpi perusteet ArchiMatella mallintamisesta ja siitä, mitä kaikkea mallinnuskäsikirjaan kannattaisi sisällyttää. Kokonaisarkkitehtuurin sisältöjen rajaus ja yhteiset pelisäännöt tulee määritellä, jotta kokonaisarkkitehtuurin tekeminen ei muutu liian työlääksi.
ArchiMate mallinnuskieli ja mallinnustapa
KURSSI
ArchiMate® peruskuvaukset mallintajille
Haluatko oppia mallintamaan liiketoiminta-, tietojärjestelmä- ja teknologia-arkkitehtuurin kaavioita ArchiMate®-kuvauskielellä? Tällä kurssilla opit, harjoitusten ja esimerkkien kautta.

