See things clearly
I was posed an interesting question over the weekend.
The question was about OBASHI and Business and IT Alignment (BITA):
“I wonder why you did not include the I of Information in your layers / method. Would you please be so kind to explain that to me?”
I’d love to…
The alignment of information is seen by some as critical to BITA, and therefore the questioner would also seek to ask "Should the OBASHI methodology become the OB-I-ASHI methodology to show information between Business and Applications?"
When we created the OBASHI methodology we wanted it to be of benefit to everyone, regardless of their role in the organisation. Being tasked with B&IT alignment means that the structure and use of information passed between Applications and Business processes is where your analysis might take place.
However, if you are a network engineer tasked with reducing the latency in a bank’s trading system, the data (or information) passed between infrastructure devices will be where you want to focus your attention. For a programmer, the information and structures passed between software application interfaces will be critical to a successful implementation.
In fact, looking at the OBASHI methodology from all of these points of view you’d be hard pressed not to make a case for making it the O-I-B-I-A-I-S-I-H-I-I methodology. The analysis of information/data being passed between and within the layers is important to every domain expert … regardless of where their core competencies lie.
That’s why dataflow is so important, and why it is an integral part of the OBASHI methodology.
We use dataflow to show the interaction that takes place between, and within, the OBASHI layers. This forms a fundamental part of OBASHI, and is listed in The OBASHI Methodology as the first OBASHI Core Principle:
“The understanding of the flow of data is fundamental to an organization's financial well being”
Within the Laws of OBASHI, which govern the modelling and operations of the OBASHI methodology, Law No.9 states that "Any data type, or classification of data, can be attributed to a Digital Flow of data." This gives the ability to document exactly what information is passed between elements in as great a detail as the analysis dictates.
In the case of BITA we can start by mapping the current state of operations using B&IT diagrams, and then superimpose data flow to see the interactions for a more detailed analysis.
So should it become OB-I-ASHI? No. The flow of information, its structure and content is important at every layer, not just between Business and Application… why limit it to just Business and Applications?
O-I-B-I-A-I-S-I-H-I-I it is then, with information between every layer...well no, it's a bit of a mouthful.
Let’s stick to OBASHI...using dataflow helps keep things simple, yet powerful.
If you want to know more about OBASHI and how to use it, the manual is available here.
Add a Comment