OBASHI® Methodology - Glossary

Above :  A Y-Axis Spatial classification.
Application layer :  The Application layer contains elements representing software applications. These are positioned beneath the business processes that utilize them and above appropriate System layer elements. Application elements can be positioned beneath other Application elements to create a hierarchy of applications.
Application Portfolio :  A database or structured document used to manage applications throughout their lifecycle. The Application Portfolio contains the key attributes of all applications. The Application Portfolio is sometimes implemented as part of the Service Portfolio, or as part of the Configuration Management System.
Asset :  Any resource or capability. Assets of a Service Provider include anything that could contribute to the delivery of a service.
Asset Register :  A register of all elements used within the model, detailing their name, type, a brief description and unique identifier.
Audit :  Formal inspection and verification to check whether a standard or set of guidelines is being followed, that records are accurate, or that efficiency and effectiveness targets are being met. An audit may be carried out by internal or external groups.
Below :  A Y-Axis Spatial classification.
Best Practice :  Proven Activities or Processes that have been successfully used by multiple organizations. ITIL is an example of Best Practice.
Bi-Directional :  Provides the ability for data to flow in both directions.
Big Picture :  One or more B&IT diagrams.
Blueprint :  A model of the business or organization, its working practices and processes, the information it requires and the technology that will be needed to deliver the capability described in the vision statement.
Bottom :  A Y-Axis Spatial classification.
Bottom-Up :  Bottom-Up refers to a way in which elements can be portrayed hierarchically within their own layer, e.g. for the Application layer, the whole application is shown at the bottom, and associated modules are positioned above.
Business & IT diagram :  A framework to document and model how people, process and technology interact to make a business work. A Business and IT diagram consists of six layers, separated by horizontal lines. The layers, arranged from the top of the diagram to the bottom, are called: Ownership, Business Process, Application, System, Hardware and Infrastructure.
Business as Usual :  The way the business normally achieves its objectives.
Business-Critical documents :  Documents containing information that is critical to the continued well-being of the business. The information has to be accurate and secure, and controlled and managed appropriately.
Business operations :  The day-to-day execution, monitoring and management of business
Business process :  A process that is owned and carried out by the business. A business process contributes to the delivery of a product or service to a business customer.
Business Process layer :  The Business Process layer contains elements representing the business process or functions that are being used by the 'Owner(s)'. These elements are positioned under their appropriate 'Owner'. Business Process elements can be positioned beneath other Business Process elements to create a hierarchy of business processes.
Co-Dependent :  An element can be co-dependent, such that, element A is dependent on element B, AND element B is dependent on element A.
Component :  A general term that is used to mean one part of something more complex.

For example, a computer system may be a component of an IT service, and an Application may be a component of an HR Department.
Connection :  A connection shows a logical or physical connection between elements.
Connection relationship :  The bi-directional relationship formed by a Connection.
Connectivity :  The logical and physical relationships between an organization's people, IT assets and resources and the business processes and services which they support.
Consumer :  Within OBASHI the last'element in a dataflow is known as the Consumer.
Dataflow :  The flow(s) of data between elements within the context of the OBASHI framework.
Dataflow Analysis View :  A graphical and statistical representation, a diagram, of all the business and resources that support an individual dataflow, enables individual dataflows to be analyzed and studied.
Deliverable :  An item that the project has to create as part of its requirements, it may be part of the final outcome, or of an intermediate outcome on which one or more subsequent deliverables are dependent.
Dependency relationship :  A relationship that shows that one element is dependent on another element in order for it to function normally and that there will be an impact on operations should failure occur. Elements can be dependent on one or more elements. Dependency relationships are uni-directional and can have more than one dependent element.
Design :  An activity or process that identifies requirements and then defines a solution that is able to meet these requirements.
Design phase :  Part of the OBASHI Project Lifecycle, information gathered is modeled in B&IT and DAV diagrams.
Digital Dynamics, The laws of :  The study of the transmission and flow of data between people, process and technology.
Digital Flow :  The dependant relationships between the flow of data, the people associated with the data, and the information technology that supports the data.
Element :  In OBASHI, an element represents an asset or resource in an organization. An element is illustrated on a B&IT diagram or a DAV as a simple rectangle.
Handover phase :  Part of the OBASHI Project Lifecycle, this phase ensures that the deliverables created during the project are passed into the operational business environment.
Hardware layer :  The Hardware layer contains elements representing the computer hardware on which the operating systems run. These elements are positioned beneath the appropriate operating systems and above the appropriate network infrastructure assets. Hardware elements can be positioned beneath other Hardware elements to create a hierarchy of hardware.
Hierarchy of elements :  Elements placed above or below each other in the same layer.
Hold Cloud :  On a B&IT diagram, a hold cloud represents missing information or the need to investigate or check that part of a diagram further.
Hybrid diagram :  A modeling technique whereby logical and physical elements are shown on the same diagram.
Impact Analysis :  The resultant set of elements produced after impact rules have been applied to an element or group of elements.
Impact rules :  The rules that determine how impact would cascade through the OBASHI model and define how each type of element cascades impact onto other element types.
Infrastructure layer :  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. Infrastructure elements can be positioned beneath other infrastructure elements to create a hierarchy of Infrastructure.
IT Service Management :  The implementation and management of quality IT services that meet the needs of the business. IT Service Management is performed by IT service providers through an appropriate mix of people, process and information technology.
Laws Of OBASHI, The :  The laws that govern the modeling and operation of the OBASHI methodology.
Layer :  One of six areas on a B&IT diagram that together provide the framework for organizing elements.
Layer relationship :  The implicit relationship created between two or more elements when they are placed in the same OBASHI layer.
Left :  An X-Axis Spatial classification.
Logical Element :  An element that represent a nonphysical entity in an OBASHI model.
Logical Modeling :  The ability to show how elements are used by an organization without regard to their physical location or connectivity.
Master Documents :  The approved and controlled set of B&IT diagrams.
Modeling :  The technique used to create OBASHI Business and IT (B&ITs) and Dataflow Analysis View (DAVs) diagrams. In addition, it is a technique that is used in OBASHI to predict the future behavior of assets, people, process and technology.
Node :  A representation of a person, process or technology that provides or consumes data.
OBASHI :  SEE OBASHI Methodology, The
OBASHI Color Standards :  The standard colors used to color elements within each layer.
OBASHI Core Principles :  The principles on which the OBASHI methodology is based.
OBASHI diagram :  A Business and IT diagram or a Dataflow Analysis View diagram.
OBASHI Framework, The :  A framework for organizing individual elements that represent business or IT assets and resources into the six OBASHI layers.
OBASHI Methodology, The :  A way of thinking that will help you get a clear picture of how your business works.
OBASHI model :  The OBASHI model comprises all of the diagrams, registers and forms relating to project.
OBASHI Project Lifecycle :  A set of project phases that are used to execute a project using the OBASHI methodology.
OBASHI rules :  Define how elements can be positioned in a B&IT diagram and which Relationships are permissible between different types of elements.
Outwith :  An X-Axis Spatial classification and also a Y Axis Spatial classification.
Ownership 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 Process layer. Ownership elements can be positioned beneath other ownership elements to create a hierarchy of owners.
PMBOK® :  A project management standard maintained and published by the Project Management Institute. PMBOK stands for Project Management Body of Knowledge.
Predecessor :  The element that is positioned immediately before an element in a sequence.
PRINCE2® :  The standard UK government methodology for project management. The acronym stands for PRojects IN a Controlled Environment.
Programme :  A temporary flexible organization structure created to coordinate, direct and oversee the implementation of a set of related projects and activities in order to deliver outcomes and benefits related to the organization's strategic objectives.
Project :  A temporary organization, with people and other assets required to achieve an objective or other outcome. Each project has a lifecycle that typically includes, planning, execution, closure etc. Projects are usually managed using a formal methodology such a PRINCE2.
Project Executive :  A member of management who is a key stakeholder and decision maker.
Red Triangle :  Denotes the reference between a Hold Cloud and the textual description in the notes column of a B&IT diagram.
Refine phase :  Part of the OBASHI Project Lifecycle, this phase drills down further into the B&IT diagrams created in the Design phase, adding more detail where required.
Relationship Persistence :  The fact that once a relationship has been defined for an element that relationship persists, regardless of where else the element is reused.
Relationship rules :  The rules which govern the implicit and explicit relationships between elements.
Relationship types :  There are six types of relationship that can exist between elements: Connection, Dependency, Layer, Set, Sequential and Spatial. Each type of relationship works in a particular way, giving implicit and explicit meaning to the model.
Repository :  A store of information.
Right :  An X-Axis Spatial classification.
Scope :  The boundary, or extent, to which a project applies.
Scope phase :  Part of the OBASHI Project Lifecycle. defines what is to be achieved by activities to which OBASHI is being applied.
Senior Responsible Owner (SRO) :  The single Individual! with overall responsibility for ensuring that a project or programme meets its objectives and delivers the projected benefits.
Sequence :  A list of elements, and the order of the elements in the list forms the sequence. Sequences can also contain other sequences,
Sequential relationship :  Sequential relationships are used within OBASHI to model dataflows. The sequence of connected or dependant elements forms the path through which data flows, originating at the first element, the Provider, in the sequence, passing through each element in the list in turn, before terminating at the last element in the sequence, the Consumer.
Set relationship :  A grouping of elements according to a specified relationship, Sets have no geographic limitations within a single B&IT diagram and are not bound by any layer.
Spatial classification :  The two-part classification of how an element is positioned in relation to another element on a B&IT diagram.
Spatial relationship :  An implied relationship which only exists through the geographical positioning of elements relative to one another on a B&IT diagram.
Spatial rules :  Govern the method by which Spatial relationships are implied. Elements which adhere to the rules are said to have a Spatial relationship with each other.
Stakeholder :  People who have an interest in an organization, project, IT Service etc. Stakeholders may be interested in the activities, targets, resources, or deliverables. Stakeholders may include customers, partners, employees, shareholders, owners, etc.
Stakeholder Map :  A matrix showing stakeholders and their particular interests in the programme.
Standard :  A mandatory requirement.
System layer :  The System layer contains elements representing the operating systems on which the applications run. These elements are positioned beneath the appropriate applications and above the appropriate hardware. System elements can be positioned beneath other System elements to create hierarchy of systems.
Title block :  Holds various details specific to a B&IT diagram. The title block is located in the bottom right hand corner of a B&IT diagram and, at minimum, it should contain the B&IT name, its unique identification number (document number) and the document revision number.
Top :  A Y-Axis Spatial.
Top-Down :  Top down refers to a way in which Elements can be portrayed hierarchically within their own layer, e.g. for the Application layer the whole application at the top with associated modules positioned below.
Transformation :  A distinct change to the way an organization conducts all, or part of, its business.
Uni-Directional :  Provides the ability for data to flow in one direction only.
Visual Standards :  The correct method of depicting how the components of OBASHI diagrams are shown.
Within :  An X-Axis Spatial classification and also a Y-Axis Spatial classification.