Problem – How do you transform a business Strategy to an IT implementation artefact?,
Let’s quickly look at some of the challenges?
- Is there a connection between business strategy and the software programs?
- What are the key abstractions for modelling business ideas?
- What are the types of artefacts to capture the system models?
- How to map business activities with the software component definition?
- How easy is to transform the business models to system models?
- What are the various elements to model Technology models?
- How helpful is Zachman Framework in initiating such transformation?
In order to realize the existing gap and the transformation efforts, we need to understand the various types of models, categories, connections and dependencies among these models which form the basis of any enterprise definition. Let’s look at the steps of transformation and the existing connections.
Step 1 – Understand and define strategy & objectives. It’s critical to describe the business objective and its connection with other strategic elements such as what are the key stakeholders, key organizations’ units, important business events, schedule, information overview, etc.
If we observe the Fig 2, there are several traceable connections.
a)Business objective Connections as mentioned in Fig 2.
| Source | Target | Notes | |
| Business objective | Business Services | Market share to increase by 3% |
b)Business Service Connections as mentioned in Fig 2.
| Source | Target | Notes |
| Business Services | Business objective | Yearly subscription to replace monthly |
| Business Service | Business HQ | Client locations |
| Business Services | Business Processes related to service definition | Understand the business processes, activities, tasks |
| Business Services | Important Dates | Date, month |
| Business Services | Organization structure | Key actors, roles |
Step 2: Transformation of Strategy services and objectives to the Business models.
This transformation consists of two-phase. In the phase one,you need to describe the various business primitive models and then in the phase 2, one needs to do the mapping and transformation from strategy elements to the business elements.
Phase I – Mapping across business primitive models
Business Process Connections as mentioned in Fig 3
| Source | Target | Notes |
| Business Processes related to service definition | Business Events | Important dates, schedule |
| Business Processes related to service definition | Business Information | Key Information, Assets, Entity |
| Business Processes related to service definition | Business locations | Branch Locations, Facility Locations |
Business location Connections as in Fig 3
| Source | Target | Notes |
| Business locations | Network & Distribution | Nodes, Servers, Storage, devices, |
| Client locations | Business locations |
Phase II – Mapping across strategy to business models
If need arise, one can extend this transformation with set of extended elements for both strategy as well business models.
Step 3: Transformation of Business models to System models
Figure: 4
Data Model – logical Connections
| Source | Target | Notes |
| SW model for Business Logic | Data Model logical | Data store,Data Flow,Elements & Relationship |
| Data Model - logical | Technical Data Model | Table , View, Procedure |
| Business Information | Data Model logical | Data Distribution Business Entity Assumptions Assets Equipment AssetsDocument Assets |
Network & Distribution Connections
| Source | Target | Notes |
| Business locations | Network & Distribution | |
| SW model for Business Logic | Network & Distribution | |
| Network & Distribution | Network & distributionTechnical models | Device, Node,Storage |
For the details on the transformation from system models to technology models and how does it fits to the zachman framework, wait for the second part of this posting.
Hopefully, sometime later this week.
Related articles
- How do you transform a Business Strategy to an IT implementation artefact?, part II (sunilduttjha.wordpress.com)


May 16, 2011






Hi Sunil
Thanks for a very well detailed analysis of a very common stumper question.
I would start by working backwards – what happens when the implementation is complete – what will it look like.
Then comes the harder task of drawing up the current picture.
This in theory can provide the starting point of drawing up a roadmap.
To keep this short, I have left out the level 2 of analysis:
1) What is the current IT Growth Model within the organization?
2) What is the change needed in the model?