Merged Standards & Best Practices 30 Merged Standards and... · 2020. 4. 16. · © 2005-2020 Alain De Preter - All rights reserved - Tous droits réservés 5 Merged Standards & Best

© 2014 Alain De Preter - All Rights Reserved www.Labnaf.one

Merged Standards

& Best Practices

Strategy & Architecture Framework

http://www.labnaf.one/


5

Merged Standards & Best Practices



6

Key Visibility Issues

Merger & Acquisition

Application & Technology Rationalization

Migrating to the cloud

Data Governance (GDPR)

Current Business Context (SWOT)?



7

Key Visibility Issues

Merger & Acquisition

Application & Technology Rationalization Where are IT and other redundancies?

What is… not compliant with our standards, critical, not reliable enough, obsolete, expensive…?

Migrating to the cloud What can be migrated to the cloud? How easily? What are the

dependencies?

Data Governance (GDPR) Which data is sensitive? Where is it used (where it shouldn’t be)?

Where are our strengths, weaknesses, opportunities and threats?



8

Key Transformation Issues

Why and how shall we optimize our business model?

Which goals do we want to achieve?

What is our target capabilities roadmap?

Which projects shall implement this roadmap?

What is our target solution architecture?

How shall we govern architecture and implementation?



9

Key questions for driving changes

Where are we today?

How shall we get there?

This way

Where do we want to be in the future?



10

We need a Framework as a vehicle toEffectively Drive Transformations

This way

A Framework for Driving Transformations



Strategy & Architecture Framework

11

Business Context

Performers

People

Tools &Repositories

Process

Guidelines & Techniques

Methods

Content

Artefacts

Deliverables

TO-BE Capabilities

Competitive Advantage

AS-IS Capabilities

Time & Value Roadmap

use / produce communicate

perform Knowledge & control

Metadata

Building Blocks

A framework for driving an organization from as-is capabilities to target capabilities following some business vision in order to reach some competitive advantage



Strategy Definition

Enterprise Visualization

Project Architecture

Epic

Strategy Execution

Capabilities Roadmaps

Drive Changes to the Operating Platform



13

How shall we implement

this framework?

Performers

People

Tools &Repositories

Process


Methods

Content

Artefacts

Deliverables



Metadata

Building Blocks



Why don’t we use existing frameworks?

I mean Strategy & Architecture Standards?





16

Complementary but disconnected

No common process

No common metamodel

Inconsistent terminology


Too high-level to be actionable out of the box

Disconnected; Redundancies; Archimate: Missing semantics & levels of detail



So how could wemake the best of Standards?



Standards & Best Practices

By IntegratingBy Merging



19

Merging Standards & Best Practices

Links: ISO/IEC/IEEE 42010, IT4IT, TOGAF, Archimate, BPMN, PESTEL Analysis, Porter's Five Forces Analysis, Business Model Generation, Strategy Map & Balanced Scorecard, SAFe, Gartner EA Stage Planning, Systems Semantics


http://www.iso-architecture.org/42010/cm/

http://www.opengroup.org/it4it

https://strategyzer.com/books/business-model-generation

http://www.depreter.org/AutomationByNature/doc/030%20Systems%20Semantics.htm


By “merging” I mean

• Define one end to end process

• Identify common concepts and gaps

• Create one single language

• Implement the whole thing in one single tool

that is already used by 750 000 users worldwide



We didn’t know it was impossible,

Credit: Mark Twain

so we did it.




Transformation Process

L1

L2

Viewpoint Influence

Enterprise Description + Vision + Changes

L3

Language MetamodelSystems Semantics Conceptual Metamodel


Language items used in viewpoint

Semantics was added in order to create a transformation workflow


© 2014 Alain De Preter - All Rights Reserved www.Labnaf.one 23


Language items used in viewpoint

Language Metamodel

software




• Define one single end to end process







SWOT



Drive Changes to the Operating Platform Envisioning

Planning

Architecture

Legend

Project Architecture

StrategyDefinition

Portfolio of Demands

Internal Diagnoses

Competition& Regulation

Business & Tech. Trends

Proposed Architecture

Solutions

Target Business

Outcomes

TimeCapacity

Costs

Detailed Business Case

Solution Architecture

Blueprint

Implementation Roadmap

Deployed Solution in the updated

Deployed Architecture

SolutionArchitecture

Vision

External Diagnoses

Context (SWOT)

Solutions Weighing

Solution Recommendation

Implementation governance

Epic

Operational concerns

Threats

OpportunitiesStrengths

Weaknesses

Strategic Plan

Roadmaps

EpicsRelease Plan

Capabilities

User Stories

Features

Target Capabilities& Features

Approved Solution in the updated

transition and/or to be Architecture

as-is Architecture

Strategic Foundations

StrategyExecution

Strategic concerns

Architecture Solution Contents

Demandsfrom Epics

DemandsBusiness

CasesPrinciples

Standards(rules)

Visible Enterprise Description

Satisfaction

Measures

Costs

Portfolios

Re-useable Portfolios Contents

Technologies

Applications

Processes

People

Information & Material

Enterprise Functions

Equipment











Natural Semantics and Ontology Across Spheres

28Automation by Nature © 2005-2007 Alain De Preter - All rights reserved - Tous droits réservés

Semantics of any System

that resides in any Sphere(s)

Physical

Reference



One Single Conceptual metamodel

Semantics of any SystemSystems Semantics

Excerpt











31

One Single Modeling Language & TerminologyA subset of the modeling language elements and connectors











ImportNew elements with properties

Properties of existing elements

Scheduled or On demand



Model

• Cloud Computing• Ecosystems• IoT• GDPR• AI• …



35

CalculateModel your value calculations

Dynamically + Periodically



36

Validate

Prevent creation of

invalid connectors

While Modeling

Send Error Emails to Relevant Recipients

Existing Invalid

Connectors

Labnaf PowerShell

The language metamodel is used both for documentation & automatic model validation

Dynamically + Periodically



37

Organize & Scalefollowing prescribedrepository structure

ArchitectureData

Changes

Scalable Shared

Modular

Traceable

Governed

TransitionAS-IS TO-BE

Integrated



38

Check Out your Real-time Dashboardsand Take Decisions

Anywhere, on any device



39

Generate diagrams

• Time Savings• Cost savings• Diagram completeness• Consistent diagram layout

Real navigable model elements(automatically resized following context)Scheduled or On demand



Generate Word, RTF and PDF documentsTemplates are provided

40




41

Element properties and/or tagged values with optional renaming and colored

groupings

Specific connections in specific direction to specific types of elements.Automatic connection consolidation into parent element relationships.

Reported collection of elements (e.g. applications) and relationships selected following any kind of rule

Generate Tabular Reports (Excel/CSV)

Filtering is automatically ON




42

Model your tabular report

Generate Tabular Report (cont.)

Model element properties and/or tagged values with

optional renaming and colored groupings

Model specific connections in specific direction to specific types of elements.Model automatic connection consolidationinto parent element relationships

Model leaf element connector to be reported and consolidated

Consolidation works also when each level in a hierarchy contains a different stereotype



Calculated Values

Generated Diagrams & Heat Maps

Backup as EAP

Mo Tu We

Errors Sent to Assigned

Individuals

Documents

Web Published Repository

Email Discussions

12

3

6

9

Schedule

Scheduled orOn Demand

Industrialize& Govern

Import

Excel & CSV Reports &

Relationships



44

Customize the modeling language & rulesusing the customization workbench


© 2014 Alain De Preter - All Rights Reserved www.Labnaf.one 45


Shared Repository

Language

software



“Unified” means

We play many different roles, but…

We speak the same language

We share the same information in the same repository

We follow the same process and we use the same tool

We collaborate effectively

software



BACKUP SLIDES

47



Standards are not actionable as a whole

Complementary but disconnected

No common process

No common metamodel

Inconsistent terminology


Cross-discipline collaboration is not easy!

Too high-level to be actionable out of the box

Disconnected; Redundancies; Archimate: Missing semantics & levels of detail



Strategy

Strategy & Architecture Framework – Laying the Bricks

How to Structure the Architecture Description of a

System like an Enterprise

Apply & Extend

The Semantics of Any System

Systems Semantics(Automation By Nature)

Build

The Process of Driving Enterprise Transformations

Drive Changes to the Operating

Platform

Build

Strategy

Porter’s FiveForces

Strategy MapBusiness Model Canvas

PEST(EL)

Integrate

Architecture & Planning

Key Sources of Inspiration

IT Value Chain

Strategy to Portfolio

Fully Implement

Extend Subset

Content

Foundations

ScopeRequirements to Deploy Request to Fulfill Detect to Correct

Enterprise Architecture Policies

Proposals DemandsServices



SWOT

Unified Standards and Best Practices



Labnaf Process vs IT4IT Functional Components

Enterprise

Architecture

Component

Enterprise

Architecture

Component

Policy

Component

(Enterprise)

Portfolio Demand

Component

Proposal

Component

Strategy

Component

Service

Portfolio

Component



Labnaf vs TOGAF components

52

Business Context

Performers

People

Tools &Repositories

Process


Methods

Content

Artefacts

Deliverables

TO-BE Capabilities

Competitive Advantage

AS-IS Capabilities

Time & Value Roadmap



Metadata

Building Blocks

TOGAF components (in color) are top-level framework organization constructs which are chapters in the TOGAF documentation.

Architecture Capability

Framework

Architecture Development

Methods

Architecture Content

Framework

Architecture Continuum and Tools

ADMGuidelines and

Techniques
