Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

OBASHI® Methodology study guide mind map by Mind Map: OBASHI® Methodology study guide mind map
5.0 stars - 49 reviews range from 0 to 5

OBASHI® Methodology study guide mind map

OBASHI® is a Registered Trade Mark in the United Kingdom and other countries. Trademarks are properties of the holders, who are not affiliated with mind map author.

OBASHI® consists of: 5 Laws of Digital Dynamics, 9 Laws of OBASHI, 5 Core Principles, 2 Diagram types, 6 Layers types, 6 Element types, 3 types of contextual information, 10 Relationships Rules, 6 Relationships Types, 10 Impact Rules, 10 Spatial classifications, 1 Color Standard, 5 Generic Project phases (influenced by PRINCE2).

Download: OBASHI® Project Lifecycle based® ion PRINCE2 approach

OBASHI® - a methodology from UK (containing both framework, method and software) for mapping and visualizing business to IT relationships using 6 simple layers and 6 simple elements positioned within those layers. Based on it's simplicity business stakeholders (and decision makers) can clearly see impact of changed into IT infrastructure showing security, risk and compliance issues.

The OBASHI® methodology was originally developed in 2001 by Fergus Cloughley and Paul Wallis.

Laws of Digital Dynamics™ (5)

Digital Dynamics™ is the study of the transmission and flow of data between people, process and technology.

Laws of Digital Dynamics™ are way of thinking behind OBASHI® Methodology.

1. For flow to exist, the flow of data must have taken place.

2. Digital flow has two or more nodes.

3. Digital flow can consist of one or more digital flows.

4. An interruption in the transmission or flow of data causes an effect.

5. A measured value pertaining to a digital flow must be aggregated from the values of each node comprising that digital flow.

OBASHI® Core Principles (5)

OBASHI® is based around a core principle: that IT exists for one reason, namely, to manage the flow of data between business assets.

OBASHI® has 5 principles called - OBASHI® Core Principles.

The OBASHI® 5 Core Principles have their origins in work undertaken in the UK oil and gas industry during the late 1990s.

1. The understanding of the flow of data is fundamental to an organization’s financial well-being.

2. Business resources (including people) and IT assets are either providers or consumers of data, or are the conduit through which data flows.

3. Information Technology exists for one reason, namely, to enable the flow of data between business assets.

4. Business risk cannot be fully assessed qualitatively or quantitatively unless the cause and effects of interruptions to a flow of data, or changes to any data contained in that flow, have been evaluated.

5. A data security model cannot be fully assessed unless the cause and effects of interruptions to a flow of data, or changes to any data, have been evaluated.

OBASHI® Laws (9)

1. An element can represent any business resource or asset, physical or non-physical.

2. An element can only reside in its own OBASHI® layer and cannot be resized beyond the dimensions of that layer.

3. An element can be related to any other element.

4. Any data type, or classification of data, can be attributed to an element.

5. Elements can be related using one or more of the 6 Relationship Types.

6. The 6 Relationship Types are Connection, Dependency, Spatial, Set, Layer and Sequential.

7. The relationship types adhere to the OBASHI® Relationship Rules.

8. The OBASHI® methodology complies with the Laws of Digital Dynamics.

9. Any data type, or classification of data, can be attributed to a Digital Flow of data.

OBASHI® Elements (6)

Elements characteristics

OBASHI® has 6 types of elements.

Elements should be given a name when positioned on a B&IT or DAV diagrams.

Ownership elements

Business Process elements

Application elements

System elements

Hardware elements

Infrastructure elements

OBASHI® Layers (6) (a.k.a. OBASHI® framework)

The OBASHI® models the enterprise / an organisation in 6 horizontal layers on both diagram types: B&IT and DAV.

The layers provide a framework (aka. the OBASHI® framework) for organising individual elements that represent individual Business or IT assets and resources.

The OBASHI framework is used to create Business & IT Diagram (B&IT).

Typical hierarchies within a layer

Ownership Layer

Business Layer

Application Layer

System Layer

Hardware Layer

Infrastructure Layer

OBASHI® Diagrams (2)

Diagrams characteristics

OBASHI® has 2 types of diagrams

OBASHI® Relationship Rules (10)

1. An element placed beneath or above another element has an implicit relationship with that element.

2. All elements within the same layer have an implicit relationship to each other.

3. Connected elements have an explicit relationship to each other, with rules governing connectivity.

4. A dependency is a uni-directional relationship i.e. element X may be dependent on element Y, but element Y might not be dependent on element X.

5. An element may have one or more instances within a layer.

6. An element can exist on more than one OBASHI® B&IT diagram.

7. A dataflow comprises two or more connected or dependent elements.

8. A dataflow can contain one or more dataflows, enabling a hierarchy of dataflows.

9. A dataflow may span multiple B&IT diagrams.

10. Element relationships prersists across an OBASHI® model.

OBASHI® Relationship Types (6)

OBASHI® has 6 Relationship Types.

Relationships characteristics

Connection

Dependency

Layer

Set

Sequential

Spatial

OBASHI® Project Lifecycle with Phases (5) (based on PRINCE2® process model)

OBASHI® project lifecycle was derived from PRINCE2® project lifecycle.

OBASHI® project phases can be interative or sequential based on requirements

OBASHI® project lifecycle does not defines any roles since role will be derived from your chosen project management practice.

OBASHI® project lifecycle has 5 phases

Yet originally OBASHI® project lifecycle is based on PRINCE2® model, it is very generic and can be replaced with any other project management practice (e.g. PRINCE2®, PMBOK® Guide, DSDM®, AgilePM® etc.).

OBASHI® project lifecycle as most of the project lifecycles can be incorporated within programme mamagement practice (e.g. MSP®, AgilePgM™ etc.).

OBASHI® Color Standard (1)

OBASHI® Color Standard for elements and connections on all diagrams.

OBASHI® visual standards ensure consistency across all of the B&IT diagrams covering.

It is often the case that non-standard colors are used to highlight particular parts of a B&IT diagram to aid the communication of a particular message.

Where different colors or visual guidelines are used in the creation of B&IT diagrams, a legend should be attached as an explanation.

Ownership

Business Process

Application

System

Hardware

Infrastructure

OBASHI® Official publications

The OBASHI® Methodology

OBASHI® Official resources

OBASHI® sample exams, available online

OBASHI® White Papers

OBASHI® website

OBASHI® shop

OBASHI® forum "Think"

OBASHI® LinkedIn group

OBASHI® Twitter

What is OBASHI®?

A methodology for creating a visual map of a business relationships with IT assets, which shows:

Simple, easy to adopt methodology.

Applies to all types, sizes and sectors of organisations.

Formal and structured way of communicating the logical and physical relationships and dependencies between IT assets and resources.

OBASHI® is both methodology and technology.

OBASHI® 'family' has 4 components:

Why OBASHI® is important? / OBASHI® benefits.

Watch: OBASHI® introduction video (by Fergus Cloughley)

Interactive OBASHI® Glossary

Interactive OBASHI® Glossary

This freeware, non-commercial mind map (aligned with the newest version of OBASHI®) was carefully hand crafted with passion and love for learning and constant improvement as well for promotion the OBASHI® methodology and as a learning tool for candidates wanting to gain OBASHI® qualification. (please share, like and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)

Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Please don't hesitate to contact me for :-) Mirosław Dąbrowski, Poland/Warsaw.

OBASHI® Impact Rules (10)

OBASHI® Spatial classifications (10)