ZACHMAN FRAMEWORK

PLUGIN
17.0.4
user guide

No Magic, Inc.
2013
All material contained herein is considered proprietary information owned by No Magic, Inc. and is not to be
shared, copied, or reproduced by any means. All information copyright 2012-2013 by No Magic, Inc. All Rights
Reserved.
CONTENTS

1 GETTING STARTED 4
Installing Zachman Framework Plugin 4
Creating Zachman Framework Project 5
Using Zachman Framework Sample 6

2 WORKING WITH ZACHMAN FRAMEWORK 8

Executive Perspective 9
Inventory Identification 9
Process Identification 10
Distribution Identification 11
Responsibility Identification 11
Timing Identification 12
Motivation Identification 12
Business Management Perspective 12
Inventory Definition 12
Process Definition 13
Distribution Definition 14
Responsibility Definition 15
Timing Definition 15
Motivation Definition 15
Business Management Perspective 16
Inventory Representation 16
Process Representation 17
Distribution Representation 18
Responsibility Representation 19
Timing Representation 19
Motivation Representation 20
Engineer Perspective 21
Inventory Specification 21
Process Specification 21
Distribution Specification 22
Responsibility Specification 23
Timing Specification 24
Motivation Specification 25
Technical Perspective 26
Inventory Configuration 26
Process Configuration 27
Distribution Configuration 27
Responsibility Configuration 27
Timing Configuration 27
Motivation Configuration 28
Enterprise Perspective 28

3 Copyright © 2009-2013 No Magic, Inc.

 1 G ETTIN G S TA RTE D

The Zachman Framework is a formal and highly structured way of viewing and defining an enterprise from
different perspectives. It is represented as a classification schema for artifacts that is used for enterprise
architecture modeling.

In order to meet this vision, No Magic has developed and introduces for MagicDraw users a new free Zachman
Framework plugin which provides:
• Zachman Framework schema with a clickable interface.
• Zachman Framework project template
• Zachman Framework perspective
• Sample project

Chapter contains the following sections:

• Installing Zachman Framework Plugin
• Creating Zachman Framework Project
• Using Zachman Framework Sample

Installing Zachman Framework Plugin

There are several ways to install the Zachman Framework plugin. Choose one of the following:
• Download and install the plugin directly via the Resource/Plugin Manager dialog in the
MagicDraw.
• Download the Zachman_Framework_Plugin_<version number>.zip file and then install the
plugin via the Resource/Plugin Manager dialog.
• Install the plugin manually, in case the direct downloading and installing via the Resource/
Plugin Manager dialog is not available.

To download and install the Zachman Framework plugin via the Resource/Plugin Manager dialog

1. From the MagicDraw main menu, select Help > Resource/Plugin Manager. The Resource/
Plugin Manager dialog opens and prompts you to check for the latest product updates and
resources. Click Check for Updates > Check.
NOTE Specify HTTP Proxy Settings for the connection to start MagicDraw
updates and resources. HTTP Proxy Settings can be provided by your
network administrator.

2. Select the check box near the Zachman Framework Plugin and click Download/Install.
3. Restart MagicDraw after the installation is completed.

To install the Zachman Framework plugin from the downloaded .zip file via the Resource/Plugin Manager
dialog

1. From the MagicDraw main menu, select Help > Resource/Plugin Manager.
2. Click the Import button to specify the Zachman_Framework_Plugin_<version number>.zip file
location. The plugin will be extracted and installed automatically.

4 Copyright © 2011-2013 No Magic, Inc.

1 GETTING STARTED
Creating Zachman Framework Project

3. Restart MagicDraw.

To install the Zachman Framework plugin manually

NOTE Quit MagicDraw before installing the plugin.

1. Download the Zachman_Framework_Plugin_<version number>.zip file.

2. Extract the downloaded file to the same directory wherein MagicDraw is installed.

IMPORTANT! If your operating system is other than Windows, use the command
line interface to go to the MagicDraw folder and extract the
Zachman_Framework_Plugin_<version number>.zip file there.

3. Start MagicDraw. The Zachman Framework plugin is now applied to MagicDraw.

Creating Zachman Framework Project

When creating a new project, you will get a message asking if you want to switch to the Zachman Framework
perspective. If you select to accept the change, your current perspective will be changed to the Zachman
Framework perspective containing the UML diagram, analysis diagram, and other diagram toolbars.
NOTE You can decline the perspective change and continue working in your
current perspective.

To create a Zachman Framework project

1. Do one of the following:

• Under Manage Project on the left of the Welcome screen, click Create New
Project.
• From the MagicDraw main menu, select File > New Project.
• Press CTRL+N.
• On the main toolbar, click the New Project <figure> icon.
2. In the Enterprise Modeling domain (you may need to expand it) on the left, click the Zachman
Framework Project icon.
3. Specify project name and select location.
4. Click OK.

5 Copyright © 2011-2013 No Magic, Inc..

1 GETTING STARTED
Using Zachman Framework Sample

Figure 1 -- Creating new Zachman Framework project

Using Zachman Framework Sample

The Zachman Framework sample project gives an example on how to use the Zachman Framework for the
Zachman Framework-based enterprise modeling.

The Zachman Framework sample project is located in <MagicDraw installation directory>\samples\Zachman

Framework.

To open the Zachman Framework sample project

Do one of the following:

• From the MagicDraw main menu, select File > Open Project and, in the opened dialog,
browse through files to open the Zachman Framework sample project.
• Under Manage Project on the left of the Welcome screen, click Open Project and, in the
opened dialog, browse through files to open the Zachman Framework sample project.
• On the Welcome screen, click Samples and then, under Zachman Framework, click
Zachman Framework sample.

6 Copyright © 2011-2013 No Magic, Inc..

1 GETTING STARTED
Using Zachman Framework Sample

In the opened sample project, a Zachman Framework diagram with name “Zachman Framework
Implementation” is displayed. This diagram displays all Zachman framework steps. Double-click each step
shape to open its sample diagram.

7 Copyright © 2011-2013 No Magic, Inc..

 2 WORKING WITH
Z ACHM AN FRA ME W ORK
The purpose of this document is to introduce the Zachman Framework implementation in MagicDraw.

The Zachman Framework represents the interaction between aspects and perspectives. Six rows represent six
perspectives and six columns represent six different aspects. In the following figure, you can see the Zachman
Framework two-dimensional schema as it is represented in the Zachman Framework plugin for MagicDraw.

Figure 2 -- Zachman Framework Implementation

In the following table, you can see how the Zachman Framework perspectives and aspects are represented in
MagicDraw and what models will be created in each level.

8 Copyright © 2011-2013 No Magic, Inc.

2 WORKING WITH ZACHMAN FRAMEWORK
Executive Perspective

Perspectives Aspects
Zachman Implementation in Model name in Zachman Implementation
Framework MagicDraw MagicDraw Framework in MagicDraw
Planner Executive Perspective Scope Contexts (Scope Things What
(Business Context Identification Lists)
Planners)
Owner Business Management Business Concepts Processes How
Perspective (Business (Business Definition
Context Owners) Models)
Designer Business Management System Logic (System Connectivity Where
Perspective (Business Representation Models)
Logic Developers)
Builder Engineer Perspective Technology Physics People Who
(Business Physics Builders) (Technology Specification
Models)
Subcontractor Technical Perspective Tool Components (Tool Timing When
(Business Component Configuration Models)
Implementers)
Functioning Enterprise Perspective Operations Instances Motivation Why
Enterprise (Business Component (Implementations)
Implementers) The Enterprise

Related web resources

The Zachman Framework and the OMG's Model Driven Architecture. Retrieved April 20, 2012,
from [Link]
WP_Mapping_MDA_to_Zachman_Framework1.pdf
NOTE In further description of perspectives, we will recommend what
diagrams can be used for modeling each step. You are free to choose
any other diagrams to define your models.

Executive Perspective
This perspective is a planning level. Business context planners describes what, how, where, who, when, and
how should be done. During this phase, six scope identification lists should be prepared, each for the six
different aspects.

Scope contexts describe a scope of models, architectures, and descriptions for the organization. This
perspective also describes what planners should consider when thinking about the organization and how it
interacts with the world.

Inventory Identification
In this inventory identification phase, you can describe a list of things that affect the enterprise, its direction, and
purpose.

In the following figure, you can see the example list of things, how it is represented in MagicDraw using the
class diagram.

9 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Executive Perspective

Figure 3 -- Inventory identification. List of things

Process Identification
In this step, you can create a list of business functions or activities. Business processes can be described using
an activity diagram.

Figure 4 -- Process identification. List of processes

10 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Executive Perspective

Distribution Identification
In this step, you can create a list of locations where the business operates. Locations can be listed in a
component diagram or in a separate document.

Figure 5 -- Distribution identification. List of locations

Responsibility Identification
In this step, you can define a hierarchical model of the organizational units and their mission. The
organization’s hierarchy can be described using a class diagram.

Figure 6 -- Responsibility identification. Organization structure

11 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Timing Identification
In this step, you can describe the business cycle and when events significant to the business occur. Events can
be described using an activity diagram.

Figure 7 -- Timing identification. List of business events

Motivation Identification
In this step, you can identify the general goals and strategies of the enterprise. Business goals can be defined
using a class diagram.

Figure 8 -- Motivation identification. List of business goals

Business Management Perspective

In this perspective, you can create the business concept model. Business concepts describe models,
architectures, and descriptions that are used by owners of the business process. A focus of this perspective is
on the usage of products.

Inventory Definition
In this step, you can define a model of things important to the business. Various relationships can be described
using a class diagram.

12 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Figure 9 -- Inventory definition. Conceptual class model

Process Definition
In this step, you can define the business function activities and processes independently of the system
implementation. The inputs and outputs describe the business resources. A business process model can be
described using an activity diagram.

13 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Figure 10 -- Process definition. Magic library process

Distribution Definition
In this step, you can describe how various locations interact with each other. Network communications,
protocols (for example, data, post, shipping, and so on) can also be described in this step. Business logistics
can be described using a component diagram.

Figure 11 -- Distribution definition. Logistics network

14 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Responsibility Definition
In this step, you can extend the organizational model with provided products. Requirements for security are
also described in this step. A workflow model can be described using a class diagram.

Figure 12 -- Responsibility definition. Librarian workflow

Timing Definition
In this step, you can describe the occurrence of business functions. Business functions can be described using
an activity diagram.

Figure 13 -- Timing definition. Business master schedule

Motivation Definition
In this step, you can translate previously defined business goals and strategies into the specific rules and
constraints that apply to enterprise operations. A business plan can be described using an activity diagram.

15 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Figure 14 -- Motivation definition. Business plan

Business Management Perspective

In this perspective, you can create the system logic model. System logic describes models, architectures, and
descriptions that are used by designers, engineers, and architects who are searching for a compromise
between what is desirable and what is technically possible.

Inventory Representation
In this step, you can describe a technologically simple logical data model. Attributes can be defined for
recording information important for the business. A logical data model can be described using a class
diagrams.

16 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Figure 15 -- Inventory representation. High level domain analysis

Process Representation
In this step, you can describe a logical system process architecture by creating a use case model of the
system. Each use case can be described using an activity diagram.

17 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Figure 16 -- Process representation. Register return

Distribution Representation
In this step, you can describe the architecture of data distribution. It is a simple description defining what
information is created and where is that information used. Distributed systems architecture can be described
using a component diagram.

18 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

Figure 17 -- Distribution representation. Reservation structure

Responsibility Representation
In this step, you can define people, their roles and responsibilities, and how they interact with technologies to
create deliverables. A human interface can be described using a class diagram.

Figure 18 -- Responsibility representation. Roles

Timing Representation
In this step, you can create a system events model, define the entity state changes, and specify when to
complete the data transformation processes.

19 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Business Management Perspective

A processing structure can be described using a state diagram. An activity, communication, or sequence
diagrams can be used as well.

Figure 19 -- Timing representation. Library item states

Motivation Representation
In this step, you can define business system rules. Business rules can be described using a class diagram.

Figure 20 -- Motivation representation. Business rules

20 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Engineer Perspective

Engineer Perspective
In this perspective, you can create the technology physics model. Technology physics describes models,
architectures, and descriptions that are used to design and create an actual project. The main focus here is on
constraints and what will actually be constructed.

Inventory Specification
In this step, you can convert your business entities model into the physical data model containing classes with
attributes.

A physical data model can be described using a class diagram. All keys, indexes, check constraints, database
storage information, and so on, can be defined as well.

Figure 21 -- Inventory specification. Data

Process Specification
In this step, you can concretize your previously defined system model with class methods. Physical system
processes can be described using the activity, sequence, or communication diagrams.

21 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Engineer Perspective

Figure 22 -- Process specification. Loan library item

Distribution Specification
In this step, you can define the physical model of computer facilities, including details of the hardware and
software used at the business locations.

The implementation architecture can be described using a deployment diagram.

22 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Engineer Perspective

Figure 23 -- Distribution [Link] architecture

Responsibility Specification
In this step, you can define persons and their competencies, screens, navigation paths, and security rules.

The presentation architecture can be described using a user interface diagram. You can also provide a
hyperlink to the external documentation.

23 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Engineer Perspective

Figure 24 -- Responsibility specification. People

Timing Specification
In this step, you can define triggers, messages, and responses described as system events.

The control structure can be described using a sequence diagram.

24 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Engineer Perspective

Figure 25 -- Timing specification. Loan library item

Motivation Specification
The business rule design can be described using an activity diagram.

25 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Technical Perspective

Figure 26 -- Motivation specification. Business rule design

Technical Perspective
In this perspective, you can create the tool concept model. Tool components describe particular elements or
element parts that are included in the final product (for example, software components, documentation, and so
on).

Inventory Configuration
In this step, you can represent data in detail. An artifact of this phase is a description of physical data base
implementation.

Figure 27 -- Inventory configuration artifact

26 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Technical Perspective

Process Configuration
In this step, you can represent the program in detail. You can define what artifacts will be created for previously
designed programs.

Figure 28 -- Process configuration artifact

Distribution Configuration
In this step, you can represent the network in detail. You can define requirements as the specification of
particular computers, protocols, communications facilities, and so on.

The artifact of this phase is a hyperlink to external documents describing the network architecture.

Figure 29 -- Distribution configuration artifact

NOTE There is no document attached in the Zachman Framework sample.

Responsibility Configuration
In this step, you can represent the security in detail. You can define individual program access permissions for
users and assign actions they are authorized to perform.

The security architecture can be implemented as an external document with descriptions of users, programs,
permissions, security mechanisms, and so on. Hyperlinks to the code stored in a configuration management
application can be created as well.

Figure 30 -- Responsibility configuration artifact

NOTE There is no document attached in the Zachman Framework sample.

Timing Configuration
In this step, you can define how all descriptions are implemented by specific programs.

Figure 31 -- Timing configuration artifact

27 Copyright © 2011-2013 No Magic, Inc..

2 WORKING WITH ZACHMAN FRAMEWORK
Enterprise Perspective

Motivation Configuration
In this step, you can define how physical model drivers become real programs. Rule specifications can be
implemented as applications and database tables.

Figure 32 -- Motivation configuration artifact

Enterprise Perspective
The perspective of the Operations instances have no detailed description as it is the physical representation of
your model defined in the previous perspectives. This perspective shows the goal of your model. You do not
have to define any model in this perspective. Every step of this perspective represents a particular resource
(real person, building, program, and so on).

28 Copyright © 2011-2013 No Magic, Inc..