(c) 2003 James Leo, Vision IT Management pty ltd. All rights reserved
Despite recent negative headline news reported in the media with regards to the inability of IT to deliver tangible business values, the OECD recognises that the use of information and communication technology represents a key platform for organisation in gaining competitive strength, increase in productivity, and ensuring their future prosperity. This is because according to OECD productivity data study in 2003, the United States, Canada, the Netherlands and Australia received the largest boost from investment in ICT.
Today there is a greater reliance on the use of IT to realise many urgently required business strategy and innovations in management, business process, product, and service. The impact of IT solution has potential to transform the way organisations conduct their business and thus exert significant impact on business, process, organisation structure and people than merely as a technology service. The 'technology/productivity paradox' news rightly highlighted the fact that throwing large sum of money into IT expenditure and rushing after new technology do not magically translate into higher productivity. This is because unlike utility such as power and water, the adoption of technology in using IT solution to reap business benefits does not represent a simple process of 'turning on or off' the needed utility service. In fact, it requires organisation to carefully plan and architect an appropriate business solution and IT capability that can deliver effective and efficient systems and process.
Vision-IT believes the 'architecture of business solutions' should represent a 'living blueprint' that strategically show how components of technology, process, people and organisation interact with each other in order to deliver the actual business solution capability needed. Unlike the traditional architecture blueprint of a building or engineering drawings, we argue that the architecture of a business solutions and its enterprise architecture model need to become a 'living blueprint'. This is because components within the architecture solutions should properly represent the real-life situation of a business and its IT environment as well as its evolution toward the targeted visionary goals. Today the technology and know-how is available to make this on-going 'living blueprint' of business architecture a reality.
Currently there are numerous frameworks, models, process, patterns and tools available to create business model and architecture representations. These include the use of Zachman Information System Architecture (ISA) framework, The Open Group Architecture Framework, Federal Enterprise Architecture Framework, DoD Architecture Framework (C4ISR), and to a lesser extent architecture concepts and practices contained in methodology such as Rational Unified Process (RUP), Process MeNtOR and the Information Engineering Methodology.
Among all these the Zachman's work is widely recognised as a key enterprise architecture approach. The ISA framework approach has been derived from similar classification structures which are found within the older 'Architecture/Construction' and 'Engineering/Manufacturing' disciplines. The following table presents the view on the architectural representation produced over the process of building a complex engineering project, along with analogies in the building, airplane and information systems.
| Generic | Buildings | Airplanes | Information Systems |
| Ballpark | Bubble charts | Concepts | Scope / objectives |
| Owner's representation | Architect's drawings | Work breakdown structure | Model of business / business description |
| Designer's representation | Architect's plans | Engineering design / Bill-of-Materials | Model of information system |
| Builder's representation | Contractor's plans | Manufacturing engineering design /Bill-of-Materials | Technology model |
| Out-of-context representation | Shop plans | Assembly/fabrication drawings | Detailed description |
| Machine language representation | ---- | Numerical code programs  | Machine language / object code |
| Product/Artefact | Building | Airplane | Information system |
source: 'A Framework for Information System Architecture' (Zachman 1987)
The ISA framework represents a logical structure for classifying descriptive representation of an 'enterprise model' and its associated planning, designing and implementation artefacts. It attempts to provide a view on the enterprise model along the perspective of its various stakeholders from the 'planner', 'owner', 'designer', 'builder' to 'artefacts'.
The following diagram depicts Vision-IT "who, What, When, Where, Why and How" approach to business architecture framework using UML (Unified Modelling Language) representations.
| People
Who |
Data
What |
Time
When |
Location
Where |
Motivation
Why |
Function
How |
|
| Scope
Planner |
List of Stakeholders | Enterprise data required to support Business Processes | List of major business events | List of locations in which the business operates | List of Business Goals and Strategy | Business functional requirements |
| Enterprise Model
Owner |
Organisation Chart | Enterprise Data Model, technique and process | The timing of business events, business cycles and schedule for specific business process | Non-Functional Requirement Specification | Business Plan | Business
Process Definition
Business Process Map Transaction Definition |
| System Model
Designer |
Actor
interaction with system
User Interface needs |
Logical Data Model | Control structure, sequence and timing information | Architecture Solution | Business Rules | System Model |
| Technology Model
Builder |
Actor
(person)
User Interface Design |
Data definition implementation | Control Structure and Timing technology technique and process | Nodes
Communication protocol and link
Network transport |
Rules design conditions or constraints | Component Model |
| Component
Artefacts |
Screen
Prototype
Navigation Diagram Sequence Diagram Actor Diagram Organisation structure |
Component
Specification on attributes
Data Definition |
Business
Event
Timing for Events Semaphore Message Queue Job Control Language Workflow |
Deployment
Diagram
Architecture diagrams Network Communication |
Business
strategy
Business Process Business Rules, conditions and triggers Domain Dictionary |
Component
Specification on behaviour
Program, scripts |
In conclusion, the business architecture resulting from the application of the "six honest serving-men"1 approach can provide organisation with a blueprint to devise effective and efficient system and process.
Please
for an obligation free
discussion to find out how we can assist you to develop the appropriate business
architecture.