Milky Way mapping is a visualization approach for illustrating an overall value stream of an organization.
Architectural Thinking Association (AT) ® is an interesting initiative in order to make the architecture easier for everybody (link). AT core model is relatively simple, it consists of few elements only as follows: Capability, Value Stream (Process), Business Object, Application and Technology Component. The AT core meta-model is illustrated in the diagram below (figure 1). These AT core elements can be visualized with any tool, such as drawing tools like MS Powerpoint or MS Visio. Formal architecture modelling can be used for complementary practice for AT approach. Formal modelling with an appropriate modelling tool (such as BIZZdesign, Orbus iServer, Mavim, Sparx […]
Here is an example of a Concept Canvas that can be used when analyzing an idea to a concept. This concept canvas (figure below) is based on Business Model Canvas, BMC (link), Lean Canvas (link) and Opportunity Canvas (link), but this layering and positioning of the boxes is analogical to architectural layers (e.g. as described here). This Concept Canvas above is created with Archi-tool (link). Note: This rearrangement of BMC boxes makes the canvas more practical to be filled, as the questions are to be asked in more logical order This layered layout matches to what is used in ArchiMate […]
What? Value Chain Based Lean Enterprise Aware Design, Development & Operations. Drivers For Change Continuous change in the operational environment with new digital enabler technologies are driving enterprises to cultural and organizational changes. The overall development has to be organized around creating and delivering added value to customers. Organizations have to be more efficient and capable of providing new digital services. Customer experience – during the customer journey through diverse services – is the most important driving force for enterprises and ecosystems in this digital era. New services have to be designed according to customer needs, organizational value streams have to […]
Value? Value is fundamental to everything that an organization does. The primary reason that an organization exists is to provide value to one or more stakeholders. It is the foundation of a firm’s business model, which describes the rationale for how a business creates, delivers, and captures value. [Value Streams, Open Group, 2017] Value Stream? A key principle of value streams is that value is always defined from the perspective of the stakeholder – the customer, end user, or recipient of the product, service, or deliverable produced by the work. [ArchiMate 3.1, Open Group, 2019] Value Stream Modelling can be used for defining […]
In this design science research, we (Eero Hosiaisluoma, Katja Penttinen, Juha Mustonen, Jukka Heikkilä) propose integrating Enterprise Architecture (EA) into an organization’s development work. We call this method Lean Enterprise Architecture Development (LEAD) – also known as Lean EA (LeanEA). See the research article from the Research Gate link. Or you can get the pdf from here, link. Note! The case story is an EA success story in the public sector, but the same approach applies to private sector too. This is a story, in which EA was re-designed and integrated into an organisation’s development work in an IT department. The […]
Business Architecture can be modelled with small set of diagrams and subset of ArchiMate elements. Here is introduced some typical diagram types, that can be used for business layer modelling, as well as linking business layer to application layer. Most of the diagram types introduced here are variations of the Layered View diagram type. Business Services View This is a simplification of layered view of business services. This view introduces how business services are produced and to which business actors they are provided. ArchiMate elements used in the diagram below are as follows: Business Actor, Business Service and Business Process. Business services […]
Introduction Application Architecture (or Solution Architecture, SA) can be modelled with the same set of ArchiMate diagram types as other levels of architecture (Enterprise- and Domain levels). Application architecture can be modelled with a small subset of ArchiMate elements as follows: Application Component, Application Service and Application Interface. Relationships between those elements can be modelled with ArchiMate relationships as follows: structural relationships (Composition, Assignment, Realization), dependency relationships (Serving, Access) and dynamic relationships (Triggering, Flow). Application Architecture Overview – the Context (Layered View) An overview of an application can be modelled with Layered View. Note! Layering is the categorization of the elements, […]
Introduction Holistic enterprise development can be supported by the Service-Driven Approach (SDA), which focuses on services (instead of projects) as primary units of value creation, design, development and operations. The SDA combines both customer oriented (“outside-in”) and organization internal behavior and structure oriented (“inside-out”) approaches. By focusing on services, enterprise development (or an IT function) can be organized as a “production line” that produces services. The SDA can be supported by practical and simple model-based method, which concentrates on service life-cycle. Service-Driven Thinking The service concept is crucial, according to idea where “everything is a service“: everything can be provided and consumed […]
ArchiMate can be used for holistic enterprise development purposes, as ArchiMate provides concepts that cover all the most relevant aspects of overall modelling. ArchiMate contains lots of elements, what makes it very powerful notation. However, only a subset of ArchiMate elements can be used for most of the cases – according to Pareto’s law (80/20 rule). The most relevant elements and relation types are illustrated in the meta-model diagrams below. An ArchiMate meta-model can be applied to fit for purpose, to be aligned to what is appropriate. Idea behind a metamodel is to introduce those elements that are relevant, with which most […]
ArchiMate can be used for process modelling at high level, especially if there is a need for linking process steps with specific application layer elements such as application services. Couple of examples how ArchiMate can be used for process modelling shown below. Business Process View This business process view provides a “high-level structure and composition of a business process (or several processes), the services that are offered, the assigned roles of actors, and the information used by the business process” [ArchiMate 2.1 specification]. This process diagram contains “Junction” -elements to model “fork” and “join” in the process flow. Business Process View With Roles […]
Here is the link to get ArchiMate example diagrams in pdf format: link Here is the original blog post of ArchiMate examples: link ArchiMate Examples See also ArchiMate Cookbook, link. Get a free ArchiMate modelling tool Archi: link.
Introduction ArchiMate is very powerful notation, it provides many elements (concepts) divided into layers and aspects (figure 1 below). There can be lots of diagram types to be used within each layer and aspect. However, most of the cases can be modelled with only a small set of diagram types, which can be created with a subset of ArchiMate elements. By identifying the most relevant diagram types and related elements, and providing simple examples of each diagram type, an organization can enable a simplified modelling approach. You know, “seeing is believing”, and visualization is the key to mutual understanding… The […]
Introduction It is necessary to depict the meaning and value for each development target. It is valuable to analyze first to WHOM and WHY the development target is important – before any further actions are to be taken. to analyse WHAT this means. The motivation view diagram makes visible the reason(s) of the development target: what is the customer and/or business value add of this development target we are going to develop. The Goal-Driven Approach (GDA) starts with defining the goals by utlizing the Goals View diagram type, which consists of ArchiMate Motivation -elements. These elements can be used for asking […]
See the reference implementation of the Lean Enterprise Architecture Framework (LEAF), which is created with Sparx EA -tool and published as HTML report. LEAF 2.2 link LEAF 2.0 link LEAF 1.0 link The LEAF can be used for linking enterprise architecture to solution architecture. High-level enterprise architecture diagrams can be modelled with ArchiMate, from which modellers (and other stakeholders) can drill-down to more detailed diagrams that can be modelled with BPMN or UML. The level-1 (the navigation landing page, the “front page”) of the LEAF is shown in the diagram below (figure 1). The level-2 (domain view) of the LEAF […]
Intro Lean EA approach supports the holistic development of an organization. Lean EA consists of value chain-based development operating model (LEAD) and integrated Enterprise Architecture (EA) practice – with the supporting framework (LEAF). The Lean EA combines management and operational development with the EA. First some basic facts: Lean EA is not focusing on EA. Lean EA is focusing on the overall business development work of an organization (incl. management, operational development and operational business). That’s the beef. A Lean way to produce services and products from idea to production. Lean EA is focusing on the outside-in view, the customer […]
1. Introduction In this digital age, Enterprise Architecture (EA) planning is more important than ever before. New computing models such as cloud, mobility, Internet of Things (IoT) and API economy have arisen, and the overall complexity of the organization’s landscape increases continuously. However, quite often conventional Enterprise Architecture Frameworks have been found too complex, too academic and cumbersome to understand. More practical and easier approach with simpler framework is needed. 1.1 The Lean Enterprise Architecture Development (LEAD) Method The Lean Enterprise Architecture Development (LEAD) method is a new style of EA approach. The LEAD consists of a) value chain-based operating model and […]
Here is a subset of ArchiMate (3.x) concepts in the form of meta-model. Another version with relationship explanations below. New ArchiMate 3 concepts such as Application Process and Technology Process are included in this meta-model, so that layers are aligned with each other. Now there is a process in each layer to model the behavior, which is related to an active structure element such as application or actor. A “Process” concept can be replaced with “Function” concept (e.g. Business Function, Application Function or Technology Function), which also models the behavior of an active element. For more detailed ArchiMate meta-models see […]
Introduction The TOGAF ADM can be used together with ArchiMate for business / digital transformation planning (see the figure below). TOGAF ADM development approach provides phases that are common to typical (digital) transformation plans, as TOGAF ADM fits to any kind of business transformation planning. The TOGAF ADM can be adapted and customized to any specific organizational need. TOGAF ADM and ArchiMate notation is perfect match, as the former provides the method and the latter provides the language for transformation development. The Method According to the TOGAF ADM, first a vision is to be defined for the transformation plan. Then business […]
Here is a proposal for mapping Service Design concepts to ArchiMate (v.3.x) concepts (figure below). These ArchiMate concepts can be used to modeling e.g. Customer Journey Maps or Service Blueprints. Get a free ArchiMate modelling tool Archi: link.
SAFe (Scaled Agile Framework) can be supported with an EA modeling tool for visualization purposes. SAFe encourages to utilize Lean & Agile practices in different development levels: Team-, Program- and Portfolio levels, and also in optional “Value Stream” level. SAFe development approach is based on project level agile practices and methods such as Scrum. According to SAFe, those team level practices can be applied to wider and more general levels too. ArchiMate though, grounds in Enterprise Architecture (EA), which can be categorized as a bridging practice between business and IT. SAFe concepts can be mapped to ArchiMate concepts, and ArchiMate can be used to support […]
Archi -tool provides ready-to-use canvas templates. E.g. Business Model Canvas (BMC) and Value Proposition Canvas for business model design, and Customer Journey Canvas for more detailed service design. These canvases utilize model elements that look like post-it chards. It is also possible to create custom canvases such as Kanban Board. All the canvases – as well as any other model artifacts (diagrams) – can be published in HTML or in document format from the Archi-tool. Business Model Canvas (BMC) Value Proposition Canvas Customer Journey Canvas Lean Canvas Kanban Canvas
A Business Model Canvas (BMC) can be modeled with ArchiMate as shown below. BMC canvases can be created with any of those EA modelling tools that support ArchiMate, such as Archi or Sparx EA. This version below is modelled by using ArchiMate Business and Motivation elements. ArchiMate Business Layer elements are covering the most of the BMC concepts, but the most important concept, the “Value”, is one of the Motivation -elements of ArchiMate. This is the basic form of the Business Model Canvas (BMC) by A. Osterwalder, but it can be variated according to what is appropriate. There are also versioned […]
A Service Blueprint can be modeled with ArchiMate. There can be different variations of the Service Blueprint, one of which is shown below. ..same diagram with another tool below.. This viewpoint is customer- and service-centric (“outside-in”), but it emphasizes also the “inside-out” part of the service. With the help of this approach, the service-driven development can identify the underlying behavioral and structural impacts of the service that is to be designed. As such, this viewpoint complements the customer-experience driven approach with process- and functional aspects. This variation (above) is using ArchiMate dynamic relationship “flow”. There can be several variations of this view. […]
A Customer Journey Map alike view can be modeled with ArchiMate. A customer journey can be modeled with the “Business Process” concept as shown in the diagram below. This customer-centric viewpoint is focusing on customer experience. This “service design” related approach is concentrating the “outside-in” development of the service that is to be designed. This highlights the services and products as essential aspects that produces value to customers – and indirectly to the organization itself. A customer journey path can be used to visualization of a customer value stream, which spans over several application services and applications. In addition, this view combines […]
Business Motivation Model (BMM) is a specification by the OMG, current version is 1.3 (2015). BMM can be used to model motivational aspects of the business. BMM concepts can be mapped to ArchiMate (3) concepts. BMM overview is shown in the figure below. BMM overview mapping to ArchiMate concepts is shown in the diagram below.
Motivation views can be used for modelling WHY a development target is important. What are the reasons and goals for a development target, what are the principles and requirements for development. Also, the value and meaning related to a development target can be modeled. Motivation Elements ArchiMate Motivation Layer consists of following elements shown in the figure below. Motivation View Pattern Main Motivation elements and their relations illustrated in the figure below. Capability element represents the development target here, but it can also be e.g. an Application Service or other core elements. Example Views Mission-Vision-Values View This view can be used […]
Strategy can be modeled with ArchiMate. There are elements from Motivation and Strategy elements in ArchiMate, which together can be used for visualizing how strategic goals can be modeled into more concrete strategy views. Strategy View Example Strategy to Capability View – Capability Based Planning (CBP) This view can be used for Capability-Based Planning (CBP) purposes, together with other ArchiMate concepts such as “Driver” and”Goal” as shown in the diagram below. This view can be used to support Strategy Planning (and -Execution) purposes. As such, these kind of views can be used in Strategy-to-Capability phase of the operating model (e.g. […]
From Models to Data Visualization ..and back. It is possible to transfer Enterprise Architecture (EA) models to database, from which the EA data can be enriched or used as a raw data for more advanced data visualization. Data visualization can be performed by diverse tools and techniques, as there are plenty of them available. Data visualization is makes it possible to make organization data available for all the stakeholders with modern, user-friendly and attractive way. EA data is a category of organization data, that is meaningful and valuable for decision makers, management, business representatives and all the roles that are […]
Enterprise Architecture Management (EAM) can be supported by a tool. A modelling tool should be supporting the ArchiMate language, which is the most comprehensive standard language for Enterprise Architecture modelling. There are several modeling tools available for Enterprise Architecture (EA) modeling with ArchiMate-notation. Some of the tools are certified by Open Group (see ArchiMate® Tool Certification Register). Some of the tools already support the new ArchiMate version 3.1 . BOC Group – ADOIT (also free community edition ADOIT:CE available) Archi – Archi (famous open source tool, start free, then donate) Modelio – Modeliosoft Sparx Systems – Enterprise Architect (+ Prolaborate portal) QPR – QPR […]
The new version of the Open Group modeling standard ArchiMate 3.0 (published by The Open Group, June 2016) is already supported in modeling tools such as Archi (Beta 4, December 2016) and Sparx EA (v.13). Also drawing tool MS Visio can be extended with ArchiMate 3 stencils (e.g. from here or here). ArchiMate 3 specification introduces some options by which some meta-information can be added into model elements. E.g. “an optional notation to denote the layer of an element. A letter ‘M’, ‘S’, ‘B’, ‘A’, ‘T’, ‘P’, or ‘I’ in the top-left corner of an element can be used to denote […]
Model Exchange When modeling an Enterprise’s (organization’s) behavior and structure, there is a need for unified modeling language. There is one comprehensive standard language by Open Group, ArchiMate (link), that can be used for overall modeling of an enterprise. In addition, there are several modeling tools that support ArchiMate language. Now and then there is a need for transferring the models between the tools. Now this is possible with a standard mechanism, which makes it possible to export and import ArchiMate models between the tools. ArchiMate Model Exchange File Format Open Group has published (2015) an XML-based ArchiMate Model Exchange File […]
Visualization And Collaboration According to research, most people understand complex problem domains by visualization. Things and their relations to each other can be understood with a picture – “one picture is worth a thousand words”. The more there are elements in “the big picture”, the more there are relations between them, and the more there is complexity. Visualization gives us possibility to interpret the details of the problem domain. Visualization supports development activities and communication between people from different organization levels – from C-level management to operational level. There is a need for a next generation visualization, collaboration and analysis […]
Several alternative approaches of modeling data switching between applications are shown in the examples (1 to 10) below. These alternative modelling approaches illustrate the situation as follows: “Application A” owns a “Data Object A-1”, which is requested by “Application B”. Data flows from “Application A” to “Application B”. “Application A” realizes a service “Application Service A-1” that is used by “Application B”. Accordingly, “Application Interface A-1” is the concrete structural implementation of the “Application Service A-1”. Practically, “Application B” requests the “Application A” and gets the “Data Object A-1” as a response – via the “Application Service A-1”, which behavior is exposed with […]
This table of terminology is to be updated continuously (now and then). Sorry bout the inconvenience… E.H.
Models are difficult to most of the business people. Others than architects find model diagrams too cumbersome. That’s why it is important to create such a diagrams that are easier to understand by the first sight. When modelling, it is important to follow best practices and principles. A modeler should be careful and always keep in mind that the diagrams are to be shown & publish to other audience. Modelling artifacts shall be easy to depict at first glance. So it is important to concentrate on aesthetic aspects when modelling. There are some valuable practices and very basic principles that […]
1 Abstract Strategy- and business driven operational development is in the heart of organization’s governance and management. Operational development supports organization’s mission, vision and strategy execution by developing business-driven capabilities to produce services and products to customers. Operational development is tightly linked with organization’s management and governance, as well as with strategy- and business development work (Azevedo et al. 2015a, Azevedo et al. 2015b, Aldea et al. 2013). Operational development links organization’s strategy- and business models to operations (Iacob et al 2012b, Ahlemann et al. 2012). This research covers all of these enterprise transformation related development activities from strategy development […]