Developing a Strategic Model
Preparing for Strategic Modeling
Identifying Business Activities
from a Data Map
Deriving Project Plans for Rapid
EA Delivery
Project Maps Are Do-It-Yourself
Construction Kits
A strategy model constitutes a strategic plan,
or model, designed to improve a process.
A strategic model applies to column 1
(what)/row 2 (owner) of the Zachman
Framework, where it is referred to as a
semantic model or enterprise model.
Followingcolumns of row 1 and 2 are used
for development of strategic model:
Column 1 (what) uses the managers and
business experts from column 4 to help
identify the data and information needed to
support the enterprise based on its
transformation plans for the future.
Column 4 (who) identifies managers in the
enterprise responsible for implementing the
business plans. It identifies the staff who will
help them (as business experts) to transform
the enterprise for that future.
Column 6 (why) focuses on the business plans
for the future, to understand the directions for
that future.
Business planning Questionnaire used in
preparing for strategy analysis.
Questionnaire used as a catalyst for strategy
analysis in a business planning Workshop.
A template of the Questionnaire is disscussed
in that chapter.
Facilitated modeling draws on expert
business knowledge. Two days is a
significant amount of time for managers and
business experts to allocate. The session
should focus on developing a picture of the
business based on strategic plans and
questionnaire responses.
A table repeated from chapter 3 Box 3.1:
Policies, Objectives, or Strategies
Project ownership: Each project must have
a project owner, responsible for allocating
and managing the project budget.
Project Management: Each project must
have a project manager, responsible for
completing the project by the scheduled
date, within budget.
Project authorization: Projects are only
authorized that can achieve project
objectives by the scheduled completion
date, within budget.
The potential existence of business activities
and processes can be identified from the
intersecting entities in a data map. These
entities can be used to identify relevant
activity, process, or system names for the
How column and the Planner row [C2R1].
This identification of activities, processes, or
systems defines the list of processes for the
How column and the Planner row [C1R1] for
prioritization by management.
Business Activity 1: Project Budget Management
Business Activity 2: Related Budget Knowledge Base
Business Activity 3: Related Project Knowledge Base
Business Activity 4: Project Objective Management
Business Activity 5: Project Skill Management
Business Activity 6: Project Activity Management
Business Activity 7: Person Skill Management
Business Activity 8: Project Resource Management
Business Activity 9: Project Team Member Management
Business Activity 10: Project Team Member Skill
Management
Business Activity 11: Project Team Member Task Skill
Management
Business Activity 12: Task Activity Management
Business Activity 13: Project Task Management
Business Activity 14: Task Skill Management
What is Project Budget Management ?
It is the alignment of IT(Information
Technology) and EA(Enterprise Architecture)
for ensuring business.
Characteristics of Entity Dependency
Analysis:
Activities are indicated by intersecting
entities. Activity names are formed on the
basis of suffix management with intersecting
entity. Project plans derived from data maps.
Each intersecting entity is a separate
implementable project called cluster.
Phase number derived on the basis of Entity
Dependency Analysis.
Entities with bold numbers are common,
independent entity that is re-usable.
Not bold are prerequisite entity that can be
shared.
Rule 1: Association Degree (or Cardinality)
Rule : An association degree of One is
stronger than an association degree of Many:
One (—-) is stronger than Many (——<)
We start by identifying end-point entities.
These are so called because they have only
many associations touching them, with no
one association.
We will first use the entity dependency rules
to identify ownership.
This will enable us to derive the project
phase sequence for this part of the data map
as a project plan.
A Project Map is a generic overview of the
structure of a project.
"Do it yourself" ("DIY") is the method of building,
modifying, or repairing things without the direct
aid of experts or professionals.
Using the project maps and derived clusters,
priority subproject clusters can be identified
and resources allocated for rapid delivery
using the technologies.
Clusters that are of a lower priority can be
implemented later only when they are
needed.
