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.
Therefore Digital Dynamics™ is the study of Digital Flow.
If data has not been passed from one element to another, then there is no flow of data.
If there is only one node, there is nowhere for data to flow to or from. Therefore, there must be a minimum of two nodes.
When studying the flow of data between people, processes and technology, it is possible to combine digital flows to create the bigger picture., Many of the smaller digital flows may need to interact with other digital flows. This creates s combined flow.
If a break in the transmission of data between the nodes will not effect the digital flow, then a digital flow does not exist., There must be some form of dependency or connection.
Financial values (or other context) are placed against every measured flow to monitor costs and maximize profits.
OBASHI’s Core Principles outline the principles on which the OBASHI® methodology is based.
1770s:, mechanization, factories, and canals, flow of water
1830s:, steam engines, coal, and iron railways, flow of steam
1870s:, steel and heavy engineering, telegraphy, refrigeration, flow of electricity
1910s:, oil, mass production, and the automobile, flow of oil, petrol
now:, IT, flow of data / information
How does the infrastructure support the flow of data / information around an organisation?
Who uses / depends on that data / information throughout the execution of a business process?
How valuable is the data / information?
What would be the total business impact if that data / information flow were interrupted?
Data / information is passed between individuals, departments, processes.
The IT infrastructure enables the flow of data.
Data in, data out.
Simplify a process.
Streamline a process.
Enable a process to happen.
Not the beginning or end of a process.
Where are we at risk of failure in terms of business at risk?
How great would the impact be on business objectives?
How does the infrastructure support the Confidentiality, Integrity and Availability (CIA) of our information?
see Relationship Types for more information ...
see Relationship Rules for more information ...
see Laws of Digital Dynamics® for more information ...
Each element represents an asset (logical or physical) or a resource.
Illustrated as a rectangle or square.
Elements size depends on relationships.
Elements positioning depends on relationships.
Same elements are used on B&IT and DAV diagrams.
Each element has it’s standard color., see OBASHI® Colour Standards for more information ...
No one element type can be connected to every other type.
No element can connect outside of its adjacent layer.
Elements of the same type can be connected together – create hierarchical structures.
It is good practice to develop a naming convention for all types of elements before an OBASHI® project begins.
What is it?, Business Process owner(s), e.g. Project Manager, Business Analyst, Sales, Marketing department, London, Warsaw ...
3 Categories of Owner, Personnel, Location, Organizational Unit
Can be mapped directly to:, in UML language ..., UML Actor (with custom stereotype), in Archimate language ..., Archimate Business Actor, Archimate Business Role
What is it?, Processes or functions used by the owner(s), e.g. Order processing, Payment approval ...
Can be mapped directly to:, in UML language ..., entire UML Activity diagram, entire UML Sequence diagram, entire UML Interaction Occurrence diagram, entire UML Communication diagram, in BPMN language ..., entire BPMN diagram, in Archimate language ..., Archimate Business process, Archimate Business collaboration
What is it?, Application, or a collection / suite of applications, e.g. Oracla DB, IBM DB2, Liferay Portal, JBoss Portal, MS Sharepoint, MS Office 2013, MS Outlook, Adobe Reader, WinRAR ...
Can be mapped directly to:, in UML language ..., UML Component (with custom stereotype), UML Node with Execution Environment stereotype, in Archimate language ..., Archimate Application Component, Application Collaboration Component
What is it?, Operating systems (classic / bare metal or virtualized), e.g. IBM AIX, IBM z/OS, IBM PowerVM, Oracle Solaris, RedHat Linux, VMware ESXi, Windows Server, Windows 8 ...
Can be mapped directly to:, in UML language ..., UML Component (with custom stereotype), UML Node with Execution Environment stereotype, in Archimate language ..., Archimate System Software
What is it?, Computer hardware, e.g. Sun Blade 6000, SunFire X2200, IBM x3560, Dell Workstation ...
Can be mapped directly to:, in UML language ..., UML Node with Execution Environment stereotype, UML Node (with custom stereotype), in Archimate language ..., Archimate Node, Archimate Device
What is it?, Computer network hardware and logical network configurations, e.g. Switches, Routers, Multiplexers, Bridges, Hubs, VPN, DMZ ...
Can be mapped directly to:, in UML language ..., UML Node (with custom stereotype), UML Component (with custom stereotype), in Archimate language ..., Archimate Node, Archimate Device
Elements can only reside in their own OBASHI layer., Once an element has been created and positioned in a particular layer it becomes implicitly associated with that layer.
The Ownership Layer contains elements representing the person(s) or group(s) that ‘owns’, or is responsible for, business processes portrayed in the Business Layer., Ownership elements can be positioned beneath other ownership elements to create a hierarchy of owners.
Example elements could be:, Accountancy, Planning Manager, Logistics, New York, Purchasing Officer, Environmental Health, ...
The Business Layer contains elements representing the business processes or functions that are being used by the ‘Owner(s)’., These elements are positioned under their appropriate ‘Owner’.
Example elements could be:, Monthly Balance, Sales Transactions, Tank Stock Management, Production Data, Capture Budgeting, ..
The Application Layer contains elements representing software applications., These are positioned beneath the business processes that utilise them.
Example elements could be:, Excel, Oracle, Sage, SAP, PeopleSoft, ...
The System Layer contains elements representing the operating systems on which the applications run., These elements are positioned beneath the appropriate applications.
Example elements could be:, Windows XP, Windows 8.1, Unix, Solaris, Linux, ...
The Hardware Layer contains elements representing the computer hardware on which the operating systems run., These elements are positioned beneath the appropriate operating systems.
Example elements could be:, Workstations, Servers, Laptops, Tablet PCs, Mainframes, ...
The Infrastructure Layer contains elements representing the network infrastructure into which the hardware is connected., Infrastructure elements can be positioned beneath other infrastructure elements to create a hierarchy that supports the business.
Example elements could be:, Switches, Routers, Multiplexers, Bridges, Hubs, ...
Each diagram uses the same 6 types of elements.
Often DAV diagrams have exactly the same layers and elements only to show contextual information not displayed on B&IT diagrams.
Business & IT Diagram (B&IT), What is it?, A B&IT diagram is a diagrammatic representation of the logical and physical relationships (connectivity) between an organisation’s IT assets and resources and the business operations which they support., 6 layered model, showing how the people, processes and technology of a business interact, Layers logically divided on 2 groups:, How business works (top 2 layers), IT assets supporting business (bottom 4 layers), Layers are used to create B&IT diagrams., Easy for understanding for non technical people.
Dataflow Analysis View (DAV), What is it?, OBASHI® Dataflow Analysis View (DAV) is a graphical and statistical document that illustrates a subset of elements, in a pre-defined sequence, from one or more B&IT diagrams.”, 6 layered model, illustrates how IT systems support the flow of data / information within and between business processes., Model, analyse, value and report on all the data flows that underpin your business, across multiple B&IT diagrams., Facilitates same layers from B&IT diagrams., Provides clear visualization of data / information Suppliers and Providers., In comparison to B&IT diagrams, DAVs adds so called: Additional contextual information:, 3 types, Financial, Statistical, Reference data, Contextual information can be placed:, Within each element., On each connection., Contextual information is optional., Same OBASHI® Layers are used to create DAV diagrams as in B&IT., Same as B&IT diagram, easy for understanding for non technical people., DAVs allows you to extract full value from the data appended to your elements in your B&IT diagrams. (requires software - Control Centre)., DAVs enables cost / value statistics to be generated to understand the contribution IT assets make to the business. (requires software for automation)., Analysis of the DAV can highlight vulnerabilities, mis-alignment and areas for consolidation.
Relationship Persistence, Relationships on one B&IT hold true across all B&IT diagrams whether shown or not.
Impact Rules, Impact rules determine how impact would cascade through the OBASHI®model.
Dependencies v Connections
BLACK LINE - standard color.
Explicitly connected to show a bi-directional coupling.
Signify ONLY data paths., Does NOT necessarily signify that data is exchanged bi-directionally between the elements.
Straight lines, horizontal and / or vertical or right angled connections.
No limit on number of connections., Multiple connections between two elements.
An element can be connected to any number of other elements - in accordance with the OBASHI® relationship rules., Can be used for showing eg. resilent networks., Can be used for identifying SPOFs - Single Point of Failure.
Not restricted by layer., Line may follow any path.
RED ARROW - standard color.
Explicitly connected uni-directionally to show how one element is dependent on another.
An element can have one or more dependencies / dependent(s).
No limit on number of dependencies.
An implicit relationship which exists between all elements within a particular layer.
Two or more elements within the same layer have an implicit relationship (see Relationship Rule 2), know as a Layer relationship
A set is a grouping of elements according to a specified relationship., Just logical grouping (without regard for their position on one or more B&IT diagrams, thus creating sets of related elements), as simple as that.
Two or more elements within the same set have an explicit relationship, known as a set relationship.
Explicit logical groups of elements, that exist without regard to their position on a B&IT diagram.
Any element can be assigned to a Set., No restriction on the number of Sets to which an element can be assigned.
There are no formal rules governing Sets, Any element can be placed within sets., Any element can exists in multiple sets.
An explicit relationship denoted by a list of elements in which adjoining elements in the list have a connection relationship or dependency relationship - i.e. a string of connected elements.
Sequential relationships are used within OBASHI® to model data flows.
A list of elements, the order of which forms a sequence.
Sequences therefore consist of chains of connected or dependent elements or sequences.
An implicit relationship which is formed between elements which are placed above or below each other.
Geographical positioning relative one to another.
if an element is placed directly above or below another element there is an implied relationship between them.
There are many classifications of Spatial relationships which are derived from how an element is positioned in relation to another on a B&IT diagram.
Spatial Rules, There are many classifications of Spatial relationships which are derived from how an element is positioned in relation to another on a B&IT diagram.
1. Scope, Objectives, Establish the project., Create a set of management products to enable the project to be set up and approved., The Project Brief defines key outcome and the Project Approach defines the methods of working., Steps, not defined, Associated documentation:, Daily Log, Lessons Log, (Outline) Business Case, Detailed Business Case, Project Brief, Project Plan, Strategies, Communication Management Strategy, Risk Management Strategy, Registers, Ownership Register, Business Process Register, Application Portfolio Register, System Register, Asset Register, Infrastructure Register, License Management Register, Configuration Item Register, B&IT Register, Establishment Document
2. Capture, Objectives, Gather and analyse information used to create OBASHI® model., Source and validate the information that represents the people, process and technology in each of the OBASHI® layers., Steps, Step 1 - Identify Information Sources., Step 2 - Evaluate Scope Against the Information Sources., Step 3 - Plan Workshops., Step 4 - Prepare Questionnaires., Step 5 - Manage Communications., Step 6 - Ensure Security Clearance., Step 7 - Perform Interviews., Step 8 - Hold Workshops., Step 9 - Extract Information., Step 10 - Link to Data Sources.
3. Design, Objectives, Analyze and model the information gathered during the Capture phase., Steps, Step 1 - Create a B&IT diagram., Step 2 - Add Elements (by manual drawing or using a software tool / application)., Step 3 - Review Element Positioning., Step 4 - Connect Elements., Step 5 - Relate Dependent Elements., Step 6 - Add Holds and Notes for Information that is Outstanding., Step 7 - Create Dataflow Analysis Views (DAVs).
4. Refine, Objectives, Prepare the OBASHI® model, and all the B&IT diagrams and DAVs associated with the project, for approval and sign-off., Steps, Step 1 - Review B&ITs., Step 2 - Review DAVs., Step 3 - Update B&ITs., Step 4 - Review Registers (with authorized personnel only)., Step 5 - Approve Sign-off on Revision No. 1 and Issue for Comment.
5. Handover, Objectives, Ensure the deliverables created during the project are passed into the operational business environment., Close out the OBASHI® project and transfer the OBASHI® knowledge and documentation over to operational environment., Master documents should slot into the existing critical document processes to be controlled and managed in a similar way to other business critical documents., Steps, Step 1 - Prepare Planned Closure.
see DSDM® AgilePF (v6, 2014) mind map
see AgilePM® mind map
see PMBOK®5 mind map
see AgilePgM™ mind map
see MSP® mind map
Visual effects can be placed on the elements such as beveling, patterning or gradients to give an enhanced appearance, but they should not vary too far from the standard color unless a legend is included indicating what the non-standard appearance signifies.
If any color other than black is used to represent connections a legend must be supplied on the diagram to show the meaning of the colored connections.
If any color other than red is used to represent dependencies a legend must be supplied on the diagram to show the meaning of the colored dependencies.
R: 213 G: 183 B: 225
R: 232 G: 214 B: 227
R: 255 G:176 B: 183
R: 196 G: 216 B: 229
Hardware, #eeea9d, R: 238 G: 200 B: 46
Hardware - Server, #ffc82e, R: 255 G: 216 B: 229
R: 171 G: 222 B: 190
The most important, key position on OBASHI® preparing for Foundation exam.
Practitioner, ... under development, currently not available
OBASHI® Explained, http://www.apmg-international.com/nmsruntime/saveasdialog.aspx?lID=3369&sID=7765
“big picture” of how the business works.
How a business is supported by IT assets.
The assets that make it work.
The interdependencies between the assets.
How data / information flows around the business.
How critical IT is for business.
How failure of IT asset can bring down service delivery.
A ‘Common Language’ for technical and non-technical people.
OBASHI® is a generic methodology, yet not "one size fits all".
methodology ..., way of thinking and working
technology ..., software
"OBASHI® - Methodology, standard, notation and technology in one."
Framework, see OBASHI® Layers (a.k.a. OBASHI® framework) for more information ...
Diagrams, see OBASHI® Diagrams for more information ...
Technology (Control Centre / software)
OBASHI® slogan: “with clarity and vision, you can develop and improve.”
Clarity, Clarity - Freedom from ambiguity., The OBASHI® Methodology creates easy-to-read diagrams which help remove ambiguity from business decision-making., OBASHI® does not requires any specialist skills (either technical or analytical) to interpret a B&IT and DAV diagrams., OBASHI® can be used for providing common understanding among professionals from all areas of the business., OBASHI® can be used for providing communication tools for brainstorms and workshop sessions.
Vision, Vision - The Power of anticipation., The OBASHI® Methodology allows you to anticipate issues and challenges which can prevent a business achieving its goals., OBASHI® can be used for identifying gaps in the current operating environment that could impact on the achievement of future strategic goals., OBASHI® can be used to visualize AS-IS, transitional and TO-BE relationship between business and IT, before and after a project / programme., OBASHI® can be used for defining the programme of activities required to transform the organization to its future state.
Develop, Develop - The Enhance the capabilities., The OBASHI® Methodology can enhance business capability through successful programme and project implementation., The clarity and common understanding provided by B&IT and DAV diagrams support change programmes by facilitating:, More detailed understanding of IT projects., Easier planning., Improved project communication., Cost saving through better system analysis., Easier identification of redundant assets., Clearer communication with third parties., Clearer communication of Key Risk Indicators (KRI) for management., ...
Improve, Improve - To become a better business., The OBASHI® Methodology can enhance business performance through better operational management., OBASHI® B&IT diagrams can be used for providing a mechanism to support the effective communication and audit processes., OBASHI® diagrams with contextual information, can provide static view on assets e.g., Mission critical assets (risk), Too costly, but not critical (TCO / TCI), Redundant / Duplicated (TCO / TCI), Overloaded (low performance), Too dependent (risk), …