SCHOOL OF COMPUTING

SESSION 2020/2021
SEMESTER 2

SCSP-3744
ENTERPRISE SYSTEM DESIGN & MODELLING

ASSIGNMENT 2: ZACHMAN FRAMEWORK

LECTURER:

DR NAGHMEH NIKNEJAD

NINA KHAIRINA MOHD KHAIRIL A18CS0175

ANIS HUMAIRA BINTI MOHAMMAD HAIZAM A18CS0034

NUR SYAZWANI BINTI ASYMAL A18CS0203

Details of Zachman Framework

The Zachman Framework is a template for organizing architectural artifacts referred to

words, design documents, specifications, and models. The template takes into account both the
artifact targets such as business owners and the particular issue that is being addressed such as
data and functionality. Basically it is a fundamental structure for Enterprise Architecture which
provides a way of viewing the enterprise and its information system from multiple different
points of views and how these components of enterprise are related.

Traditionally, we used the common system development life cycle process in order to
plan the strategy to develop the system. However, John Zachman published and introduced a
different approach where he took account of multiple player’s point of view, providing
organizations with an effective way of assessing the completeness of software development
process models. This includes the needs of business owners in the organization.

Many large companies struggle on adapting to the situation in today's diverse market
environments. Part of the problem stems from a lack of internal knowledge of the organization's
complicated structure and components in various fields, where legacy company information is
hidden in the minds of specific employees or business units without it being stated clearly.

The Zachman structure is a classification system for an organization's architecture. It's a

strategic business tool for modelling an organization's existing roles, elements, and processes, as
well as managing business change. Zachman's framework is based on his awareness of how

transition is handled in complicated items like aeroplanes and houses.

Components in Zachman Framework
The building architect prepares different architectures for each of these players. Every
player demands complete information, however what constitutes completeness is different for
each of the players. The analogy of this framework can be seen when building a house. The
house owner is interested in a complete description of the functionality and aesthetics of the
building. The builder is interested in a complete description of the materials and the construction
process. Essentially, the owner does not care about the placement of studs in the walls or what
nails are used. The builder does not bother when the bedroom windows are aligned with the
morning sun.

Zachman’s framework consists of six functional focuses, each considered from

the perspective of a major player. Based on the diagram, the owners and builder refers to the
role of the player in developing the project. There are points of view from planner, owner,
designers, builder, subcontract and enterprise. The second dimension is the descriptive focus of
the artifact. This refers to the what, how, where, who, when and why. Both dimensions are
independent from each other. However, it is important to understand the differences of the
owner’s what to the builder’s what.
 According to this framework, each player has different meanings about certain words in
the development. For example, based on the business‘s perspective, ‘data’ means business
entities. This includes information about the entities such as customers and products or
information about relationships between those entities. Usually from the developer side, data
refers to the row and columns organized into tables which are linked together by joins and
relationships projection. Differ from the database designer, data refers to the normal form of
relational tables.

These perspectives do not have any better or more details than another. The important
feature is to ensure that their perspectives on data are critical to an understanding of the systems
architecture. According to Zachman’s framework, his first suggestion is that every architectural
artifact should live in one and only cell. This means that there should be no doubt or uncertainty
about where a particular artifact lives. Secondly, Zachman’s framework suggests that a whole
architecture can be considered complete only when each cell is complete. Thirdly, the framework
suggested the cell in the column should be related to one another. This means that even though
the ‘data’ bring different meaning to each player, there should be a similar understanding to what
the system should be developed.
 Zachman Framework in our Project

WHAT HOW WHERE WHO WHEN WHY

Scope Create a useful Process of UTMSmart UTMDigital One whole To ease the
(contextual) Information system Application as system Semester process of
from the Dining includes developer ordering
Module browsing system in
stores and UTM cafes
Planner
menu, placing including
order and view ordering
payment process
details

Business Model Plan a whole Identify Implementat - Staff and Updated Fulfilling
(conceptual) complete Functional and ion of Students as every business
system’s design Non-functional system users semester needs while
like, creating an requirement explained - UTM as solving
ERD system. based on through Use business organization
owner
business Case owner current issues.
process model. Diagram

System Model Producing a Study system Implementat Human One whole Constructing
(logical) good logical architecture in ion of Interface Semester system
ERD with user planning and system Architecture is development
designer Interface and designing architecture important for prototype.
user experience. phase eg: describe user
Flowchart through experience
Flowchart especially
Students and
Staffs

Tech. Model Designing Pick one UTM Data Admin One whole Producing a
(physical) physical ERD, development Center Semester system with
database style and apply good user
architecture and SDLC experience
system throughout the and matching
builder
interface. system user
development requirements.
process.

Detailed The complete The list of UTMSmart UTM student Application Helps
Representation system for restaurants, Application and staff is available students to
(out-of-context) Dining Module menus, contact 24 hours per order food
in UTMSmart information to day using
Application order food UTMSmart
subcontractor
Application
 In conclusion, we think that Zachman Framework is a good implementation for the
system since it brings a lot of advantages and benefits toward this project. The strength of
Zachman Framework includes, enhancing interaction between professionals within the
information systems sector and acknowledges the pros and cons of not developing a single
architectural representation. Comparing and contrasting a broad range of methods and/or
methodologies while developing better methods (including methodologies and tools) on
producing the architectural representations, along with potentially reconsidering the traditional
"application development process" as we know it today.

The understanding of no single unified architecture that satisfies everyone's needs is

probably the only reason for Zachman Framework's success. By realizing that different people
have different, but complementary perspectives, a richer collection of architectures can be
created, which generally define the information system's architecture.

Using these six simple questions, the structure allows complicated subjects to be
transformed into hierarchical categories in the column headers or called as 5WH questions.
Depending on the perspective or audience, the answers to these questions will vary which is
represented in the rows.

As shown in table above, each view is described from a specific perspective and has a
representation which is a model or working system.

We think that this insight has greatly clarified many of the challenges that we will face on
our path, and it has also addressed many of the questions that will be raised later on, so the
Zachman framework will serve as an effective guide until the project is completed.