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 […]
Yearly Archives: 2018
12 posts
Value Chain Based Lean Enterprise Aware Design, Development & Operations. Drivers For Change Continuous change in 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 customer. 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 be adapted 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 organisation’s development work. We call this method Lean EA Development (LEAD) – also known as 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 CIO requested to completely […]
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 small set of diagram types, which can be created with subset of ArchiMate elements. By identifying the most relevant diagram types and related elements, and providing simple examples of each diagram types, an organization can enable a simplified modelling approach. You know, “seeing is believing”, and visualization is the key to mutual understanding… The most useful diagram […]
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 […]