online Tl.

doc, printed on 5/9/02, at 3:16 PM

AllFusion Model Manager

™

Getting Started
4.1
new MMprtTl.doc, printed on 5/7/02, at 2:20 PM

This documentation and related computer software program (hereinafter referred to as the
“Documentation”) is for the end user’s informational purposes only and is subject to change or
withdrawal by Computer Associates International, Inc. (“CA”) at any time.
This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole
or in part, without the prior written consent of CA. This documentation is proprietary information
of CA and protected by the copyright laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this
documentation for their own internal use, provided that all CA copyright notices and legends are
affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user
who are bound by the confidentiality provisions of the license for the software are permitted to
have access to such copies.
This right to print copies is limited to the period during which the license for the product remains
in full force and effect. Should the license terminate for any reason, it shall be the user’s
responsibility to return to CA the reproduced copies or to certify to CA that same have been
destroyed.
To the extent permitted by applicable law, CA provides this documentation “as is” without
warranty of any kind, including without limitation, any implied warranties of merchantability,
fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or
any third party for any loss or damage, direct or indirect, from the use of this documentation,
including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is
expressly advised of such loss or damage.
The use of any product referenced in this documentation and this documentation is governed by
the end user’s applicable license agreement.
The manufacturer of this documentation is Computer Associates International, Inc.
Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-
19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

 2002 Computer Associates International, Inc. (CA)

All trademarks, trade names, service marks, and logos referenced herein belong to their respective
companies.
01MM41TC.doc, printed on 5/8/02, at 12:30 PM

Contents
Chapter 1: Working Together Effectively!
Modeling in the Multi-User Environment! 1–1
Intended Audience 1–1
Efficient and Effective Modeling 1–1
Benefits 1–2
Key Features 1–2
What's New 1–3
CA Services: Enabling Solutions Through Experience 1–5
CA Education Services 1–6
Computer Associates: The Software That Manages eBusiness 1–6
For More Information 1–6

Chapter 2: Shared Processing of Models!

Understanding the Client/Server Relationship! 2–1
Before You Connect to the ModelMart 2–2
What's Next 2–2

Chapter 3: Set Up the ModelMart!

Installing ModelMart and Initializing the Database! 3–1
DBMS Requirements 3–1
Installing ModelMart 3–1
Initializing the ModelMart 3–2
What’s Next 3–7

Chapter 4: Secure Your Models!

Setting Up User Security! 4–1
Assigning Security Profiles 4–1
Using the Profile Manager 4–3
Using Lock Options to Restrict Model Access 4–4
What's Next 4–4

Chapter 5: Organize Your Models!

Setting Up Libraries! 5–1
Set Up a New Library 5–2
Viewing Libraries 5–3
What's Next 5–4

iii
01MM41TC.doc, printed on 5/8/02, at 12:30 PM

Chapter 6: Join the Workgroup!

Connecting to ModelMart! 6–1
What's Next 6–2

Chapter 7: Open, Close, Save Models!

Working with Models—the Basics! 7–1
Saving a Model to ModelMart for the First Time 7–1
Opening a Model 7–3
Closing a Model 7–4
Saving Models 7–5
What's Next 7–9

Chapter 8: Manage Changes to Models!

Using the Change Control Manager! 8–1
Review Changes 8–1
Changes Made by Concurrent Users 8–3
Filtering the Change List 8–6
What's Next 8–8

Chapter 9: Lock Your Models!

Working Simultaneously on the Same Models! 9–1
Lock Modes 9–1
Working with the Lock Modes 9–2
What's Next 9–3

Chapter 10: Track Changes with Versions!

Working with Versions! 10–1
Parent Versions 10–1
Versions 10–2
Locking 10–3
Saving 10–3
Marked Versions 10–6
Version Differences 10–7
What's Next 10–8

iv
01MM41TC.doc, printed on 5/8/02, at 12:30 PM

Chapter 11: Merge Data Models!

Understanding Model Merge! 11–1
Merge Results 11–1
Using the ModelMart Merge Manager 11–2
Merging a Model into the Current Model 11–7
Understanding How Differences Are Merged 11–9
What's Next 11–9

Chapter 12: Work With Data Model Submodels!

Submodeling Makes Working on Enterprise Models Easier! 12–1
Opening and Saving a Submodel 12–1
Creating a Submodel 12–3
What's Next 12–4

Chapter 13: Create Data Model Reports!

Using the Data Browser! 13–1
Generate a Report on a Data Model 13–1
Change Control Manager Reports 13–3
What's Next 13–4

Chapter 14: Manage Data Model Standards!

Using Consistent Naming and Datatype Standards! 14–1
Naming Standards 14–1
Datatype Standards 14–1
Working with the Standards Editors 14–1
Saving a Standards File to ModelMart 14–3
Attaching a Standards File to a Model 14–3
What's Next 14–3

Chapter 15: Sync Your Data Models and Process Models!

Verifying that Your Data Supports Your Business Processes! 15–1
Opening the ModelMart Synchronizer 15–1
Using the Synchronizer 15–2

Chapter 16: Ask Your Buddy!

Ask Your Buddy–Questions and Answers 16–1

v
 MD12.doc, printed on 5/2/02, at 4:19 PM

1
Chapter

Working Together Effectively!

Modeling in the Multi-User Environment!

W elcome to AllFusion™ Model Manager, hereafter referred to in this guide as

ModelMart®. ModelMart coordinates the development and management of
models created with AllFusion ERwin® Data Modeler and AllFusion
Process Modeler. Throughout this guide, these products are referred to by their former
names, ERwin® and BPwin®. Although ERwin is used in the examples given in this
guide, the concepts discussed are similarly applicable to BPwin, unless stated otherwise.

Intended Audience
This guide is intended for both users (modelers) and ModelMart administrators. The
guide provides an overview of ModelMart and explains how to use it in a workgroup
environment. However, the chapter “Set Up the ModelMart” is directed to ModelMart
administrators and can be skipped by other users. The chapter presents basic
instructions for installing ModelMart on the server and initializing the ModelMart
database.
ModelMart supports many security and administrative features related to its
multiuser capabilities and the client/server environment in which it operates. For this
reason, routine management of ModelMart is usually performed by a dedicated
administrator. Administrators will find detailed information regarding their tasks and
responsibilities in the AllFusion Model Manager Administrator Guide.

Efficient and Effective Modeling

Competing in today's eBusiness environment requires faster, better decisions based on
accurate data and a clear understanding of your company's operations. ModelMart's
sophisticated model management and workgroup capabilities provide a competitive
advantage by facilitating model management and development.
ModelMart provides a multiuser modeling environment that makes coordinated,
large-scale modeling possible. It enables collaboration among project managers, data
modeling team members, process modeling team members, and standards
administrators by providing workgroup modeling services—including conflict
resolution, versioning, security, and standards management.
Use ModelMart to coordinate the efforts of model teams to document existing
systems, create new eBusiness systems, and drive data standardization. ModelMart
facilitates model sharing and encourages teamwork, so modelers can work together
more efficiently to optimize model-based development. Your modelers will get more
work done in less time with better results.

1–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Modeling in the Multi-User Environment!

Easy to set up, ModelMart is platform and network independent, and sits on your
choice of popular relational databases. Models are stored in a central database called
the ModelMart that runs under Microsoft SQL Server, Sybase, Oracle, or Informix.
Administration overhead is relatively low and proportional to the number and activity
level of the users.

Benefits
ModelMart promotes individual productivity, development coordination, and
implementation of standards. ModelMart can meet your needs by:
• Providing secure, concurrent access to models by securing the models on
the server.
• Providing change control facilities that automatically track changes to
models and provide conflict resolution.
• Providing versioning capabilities that create a project audit trail and
rollback options.
• Allowing modelers to view, with ease, the impact of any changes they
make to a model.
• Providing reuse mechanisms to speed the development and deployment
of new eBusiness databases.
• Providing standards support for consistent database design across
projects.
• Enabling multiple ERwin data modelers and BPwin process modelers to
work together more efficiently.
• Encouraging teamwork and model sharing.
• Allowing you to manage even extremely large models.
• Acting as the hub for an organization's modeling activities and the
integration point for ERwin and BPwin.
• Providing the manager with the ability to define how people work
together by granting various levels of permissions.

Key Features
You will enjoy using the advanced features of ModelMart, which make working with
models easier. Here is a brief explanation of the key features:
Change Control Manager–Controls how changes are saved, helps you
resolve conflicting updates, and lets you see the impact of changes before you
save them.

1–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Modeling in the Multi-User Environment!

Versioning–Saves each set of changes as a new version that records who

made the changes, dates the changes, and allows you to compare versions and
decide which changes you'd like to keep.
Libraries–Organizes data models and process models into libraries to aid
standardization and control user access.
Locking–Locks out other users from saving changes until the lock on a
model is released.
Submodeling–Allows users to work on an ERwin subject area, making it
easier to work on large models.
Model Merge–Allows you to combine two ERwin models together.
Refresh–Allows you to update your model with any changes made by
another modeler after you checked out your model from the ModelMart.
Reporting–Allows you to generate reports of changes or conflicts.
Synchronization–Synchronization of BPwin models and ERwin models
verifies that business processes are optimally supported by their information
systems.
Security–Controls access to objects and what tasks users can perform.

What's New
If you are already familiar with the features from a prior version, you'll be interested in
what has changed. Here are some of the key enhancements in the new ModelMart 4.1
version:
Easy Conversion of Your ModelMart Database from an Earlier Version of
ModelMart–If you previously worked with ModelMart, probably the most
important task is preserving the database structure and the contents of your
ModelMart 3.0.2 database. That’s why we’ve provided a built-in conversion utility
with ModelMart 4.1, which the administrator uses to perform the conversion. The
ModelMart 4.1 Conversion Utility does all the work of transforming the old into
the new database and it converts the ERwin and BPwin models to the newest
version as well.
If you have a combined ModelMart 3.0.2 database (for ERwin and BPwin models),
the database and the models will automatically be converted to version 4.1 format
during the initialization process. You no longer need to run separate initializations
for ERwin and BPwin.
Buddy Tip—The ModelMart administrator will find details on the conversion feature in
the Administrator Guide.

1–3
MD12.doc, printed on 5/2/02, at 4:19 PM

Modeling in the Multi-User Environment!

Improved Security Management–Predefined ModelMart Users: In the past, adding

a ModelMart user was a two-step process. In addition to adding ModelMart users
through the DBMS security tool, the ModelMart administrator needed to add the
same set of users in the ModelMart Security Manager. But in ModelMart 4.1, all
authorized database users automatically become potential ModelMart users. As a
result, a pre-defined set of ModelMart users appears in the ModelMart Security
Manager. However, before a user can login and access the ModelMart database,
the ModelMart administrator must assign a security profile through the
ModelMart Security Manager.
Guest Profile No Longer the Default: In ModelMart 4.1, the Guest security profile will
not be assigned by default as it was in previous versions of the product. Now, the
ModelMart administrator must assign each user to the appropriate security profile.
This methodology is more secure, because implied access is no longer a concern.
In addition, the Guest profile can now be used for its intended purpose, which is
to allow a guest to log in to ModelMart on a temporary basis. Other users will
have a security profile based on their assigned modeling role and in accordance
with the ModelMart license agreement.
Improved Version Management–In ModelMart 3.0.2, you could save a model
as a full version or as a snapshot. In ModelMart 4.1, version management is more
streamlined. Each time changes are saved to a parent model, a new parent is
created, and the prior parent becomes a version. Thus, each set of changes made
to a model is maintained by designating each save as a unique version. To protect
a version you can change it to a marked version to designate it as milestone in the
development process. Additionally, BPwin version management is now supported
in the same manner.
Introduction of the Source Model for Library Level Objects and
Recognition of the Design Layer Features of ERwin–In ModelMart 3.0.2, a
set of ERwin library-level objects were saved in every library and included
automatically in every data model in the library. These ERwin library level objects
included default trigger templates, domains, validation rules, valid values, bitmaps,
and physical storage objects. This automatic inclusion led to some unwanted
proliferation of these objects.
With the introduction of the source model and other design layer features in
ERwin 4.1, library-level objects are no longer necessary. However, library-level
objects served a great purpose in establishing and maintaining modeling standards
and maintaining consistency. In ModelMart 4.1, you can choose to save each set
of library-level objects in a separate source model. Then, you can use the models
that hold the library-level objects as a source model for other models in the same
library. By using the old library-level objects to create a new library standards
model, you can migrate the set of standard library objects from the old to the new
ModelMart database.

1–4
02MM4101.doc, printed on 5/6/02, at 12:29 PM

Modeling in the Multi-User Environment!

During the conversion process, the ModelMart administrator will be prompted to

save the library-level objects in a separate model or apply them to the newly
converted ERwin 4.1 models. If you choose to save them into a separate model,
the new model will be assigned a default name, which is based on the Library
Name and the target server for the models in the Library.
Introduction of ERwin's Complete Compare Technology to the Model
Merge Feature–ModelMart 4.1 has an enhanced feature that supports the
merging of two unrelated models. For example, you may want to merge
independent models to combine projects into one larger project, to migrate from a
stand-alone ERwin to the ModelMart, or to create an enterprise model.
Independent Model Merge now is built upon and expands ERwin’s Model-to-
Model Complete Compare technology.
New Multi-Mart Feature–ModelMart 4.1 allows you to save, change, and share
models across multiple ModelMart databases. ModelMart uses an internal object
identification system to recognize objects and track changes regardless of the
ModelMart database in which it was created or last saved. This functionality allows
you to save a ModelMart model to an ER1 file (ERwin) or a BP1 file (BPwin) and
then save the ER1 file or BP1 file as a ModelMart model in another ModelMart.
You can save changes to the ModelMart model in the other ModelMart. Then save
it as an ER1 file or a BP1 file, and then use the model merge feature to merge the
model into the same ModelMart model in the first ModelMart.
Support for Design Layers–AllFusion Modeling Suite encourages the practice of
using different model types for distinct purposes within the application
development lifecycle. For this reason, Design Layers, which were introduced in
ERwin 4.0, are now supported in ModelMart 4.1. As a modeling tool, ModelMart
identifies different model types and links related models within a design layer
hierarchy. This means that you can now use advanced modeling features such as
separate logical and physical data models, derive a new model, add a model source,
merge unrelated models, and apply transforms.

CA Services: Enabling Solutions Through Experience

When it comes to getting on the information fast track, CA Services can recommend
and install a full suite of portal and knowledge management solutions to keep your
business moving. And our associates offer the proprietary know-how on custom-
fitting your enterprise for solutions ranging from life cycle management, data
warehousing and next-level business intelligence. Our experts will leave you with the
technology and knowledge tools to fully collect, exploit and leverage your data
resources and applications.

1–5
MD12.doc, printed on 5/2/02, at 4:19 PM

Modeling in the Multi-User Environment!

CA Education Services
Computer Associates Global Education Services (CA Education) offerings include
instructor-led and computer-based training, product certification programs, third-party
education programs, distance learning and software simulation. These services help to
expand the knowledge base so companies can use CA’s products more efficiently,
contributing to their greater success. CA Education has been developed to assist
today’s technologists in everything from understanding product capabilities, to
implementation and quality performance. Because the vast community of education
seekers is varied, so too are CA’s methods of instruction. CA Education is committed
to provide a variety of alternatives to traditional instructor-led training, including
synchronous and asynchronous distance learning, as well as Unicenter simulation.
For training that needs to be extended to a wider audience — for a fraction of the
cost and logistical hassle of sending everybody away to a class — CA Education offers
excellent distance learning options.

Computer Associates: The Software That Manages eBusiness

The next generation of eBusiness promises unlimited opportunities by leveraging
existing business infrastructures and adopting new technologies. At the same time,
extremely complicated management presents challenges — from managing the
computing devices, to integrating and managing the applications, data, and business
processes within and across organizational boundaries — and look to CA for the
answers. CA has the solutions available to help eBusinesses address these important
issues. Through industry-leading eBusiness Process Management, eBusiness
Information Management, and eBusiness Infrastructure Management offerings, CA
delivers the only comprehensive, state-of-the-art solutions, serving all stakeholders in
this extended global economy.

For More Information

After walking through this Getting Started, you can refer to additional information
resources. To access the online help system, which offers conceptual and procedural
information, select Help on the ModelMart client toolbar. Alternatively, press the F1
key on your keyboard to view topics related to the ModelMart screen you are currently
viewing. Your ModelMart CD contains additional instructional documents.
Buddy Tip—If you need help with the product, consult esupport.ca.com on the Internet.

1–6
 MD12.doc, printed on 5/2/02, at 4:19 PM

2
Chapter

Shared Processing of Models!

Understanding the Client/Server Relationship!

M odelMart operates in a client/server environment—processing is shared

between the user's client workstation and the server where the models are
stored. Users access the stored models through one of the ModelMart
clients—ERwin or BPwin. Models are held in a database called the ModelMart, which
resides on a central server, using Microsoft SQL Server, Oracle, Sybase, or Informix as
the host database.
Once a model is saved to the ModelMart database, ModelMart controls who can
work on the model and how changes can be saved to the model, making it possible for
workgroups to work on large models without confusion. A typical ModelMart
environment is shown next.

CLIENT WORKSTATIONS SHARED SERVICES STORAGE

DBMS Server
Store/Retrieve
ModelMart Data ModelMart Control Tables,
Stored Procedures, and Queries
ERwin BPwin
ModelMart

…
Running: Informix, Microsoft SQL Server,
Model Navigator
Oracle, or Sybase

You can also use the AllFusion Model Navigator as a ModelMart client. This
product allows read-only access to ERwin data models and BPwin process models. So,
your workgroup can use it to share information with others without the risk that
unauthorized changes might be saved to the ModelMart.
Additionally, you can connect to ModelMart through the ERwin Naming
Standards Editor or the ERwin Datatype Standards Editor.

2–1
03MM4102.doc, printed on 5/7/02, at 4:26 PM

Understanding the Client/Server Relationship!

Before You Connect to the ModelMart

The following must be performed before you can connect to ModelMart through a
ModelMart client:
• The administrator of the relational database management system (DBMS)
must give users permission to access the DBMS, on which the
ModelMart will be set up.
• The ModelMart administrator must install the ModelMart files on the
server, and set up the ModelMart database. The administrator also
defines user security permissions and sets up the library structure in
which models are organized.
• At least one of the ModelMart client programs (that is, ERwin, BPwin, or
Model Navigator) must be installed on the client workstation. System
requirements for the client workstations are the same as those for the
ModelMart client software. You'll find the requirements in the
documentation provided with these products.
• The client connectivity software for your DBMS on the server must be
installed on the client workstation so that you can connect to the DBMS
on which ModelMart resides.

What's Next
Remember you do not install ModelMart on the client workstations. Users connect to
the ModelMart database on the server through the ModelMart client software
contained in ERwin, BPwin, or Model Navigator. The procedures that the ModelMart
administrator must perform before the modeler can begin using ModelMart are
outlined in the next chapter.
If you are not an administrator, skip the next three chapters and go to the chapter
“Join the Workgroup” where you will learn how to connect to ModelMart. Later, you
can return to the chapters “Secure Your Models” and “Organize Your Models” to gain
an understanding of how models are organized in libraries and secured in ModelMart.

2–2
 04MM4103.doc, printed on 8/5/2002, at 11:34 AM

3
Chapter

Set Up the ModelMart!

Installing ModelMart and Initializing the Database!

M odelMart supports many special security and administrative features

associated with a DBMS. For this reason, the routine management of the
ModelMart environment is usually assigned to a dedicated administrator.
The ModelMart administrator installs ModelMart and initializes the ModelMart
database on the DBMS server. The administrator also has the responsibility of setting
up the library structure in which models are organized, and assigning security profiles
to users. For details on how to set up libraries and user security, see the chapters
“Organize Your Models” and “Secure Your Models.” See the AllFusion Model
Manager Administrator Guide for details on installing and initializing ModelMart, as well
as the administrator’s role and responsibilities. If you are upgrading your ModelMart
software or license, see the Administrator Guide.

DBMS Requirements
The administrator should be the database owner (dbo) for Microsoft SQL Server or
Sybase, the schema owner for Oracle, or the database administrator (DBA) for
Informix, of the database that will contain ModelMart. Before the ModelMart
administrator can install ModelMart on the server, he or she must verify that the
DBMS environment is prepared for ModelMart installation, and that the server system
requirements meet at least the minimum specifications. For information regarding the
server system requirements and preparing the DBMS environment, see the
Administrator Guide. Additionally, the administrator of the DBMS, must set up user
permissions for the DBMS.

Installing ModelMart
The installation of the administrative files is the same for each DBMS supported by
ModelMart (Microsoft SQL Server, Sybase, Oracle, or Informix). The installation is
easy to do. Just insert the ModelMart CD and follow the dialogs.

3–1
04MM4103.doc, printed on 8/5/2002, at 11:34 AM

Installing ModelMart and Initializing the Database!

The InstallShield Wizard Complete dialog displays when the installation is

complete. At this point, you can choose whether you want to initialize the ModelMart
database now or at a later time.
Choose one of the following:
• To initialize ModelMart now–click Finish to complete the ModelMart
installation and connect to ModelMart.
• To initialize ModelMart later–clear the Launch ModelMart check box,
and click Finish to complete the installation and return to Windows.
If you choose to initialize the ModelMart database at a later time, you will not
need to use the CD to perform the initialization. You will simply click Start on you
computer desktop taskbar, and then choose Programs, Computer Associates,
AllFusion, Model Manager. This will open the ModelMart Manager where you will
begin the initialization process.

Initializing the ModelMart

After installation, you must initialize the ModelMart database before client users can
save and access models. The initialization creates the ModelMart tables and installs the
stored procedures and queries that manage client workgroup models in the
ModelMart. The initialization process prepares ModelMart for use with both ERwin
and BPwin. No additional steps are needed to make ModelMart compatible with
BPwin. The complete initialization steps are slightly different depending upon the
DBMS.

Initializing ModelMart on Microsoft SQL Server or Sybase

Use the following steps to initialize ModelMart on Microsoft SQL Server or Sybase:
1. In Windows 98, Windows 2000, Windows ME, Windows XP, or Windows
NT Version 4.0, click Start on the taskbar, and then choose Programs,
Computer Associates, AllFusion, Model Manager, ModelMart.
2. In the ModelMart Connection Manager, enter the following:
• Type the login name and password for the dbo of the database
containing ModelMart
• Select your DBMS version and connection library from the Host DBMS
drop-down list.
• Type the server name in the Host DBMS Connection box.
• Type the name of the ModelMart master database in the Master Database
box. If you leave the Master Database box blank, you can choose the
ModelMart database from a list in the following dialog.

3–2
04MM4103.doc, printed on 8/5/2002, at 11:34 AM

Installing ModelMart and Initializing the Database!

3. Click Connect to connect to the ModelMart database and open the

ModelMart Manager dialog.
4. On the ModelMart Manager dialog verify the ModelMart master database
name in the Database drop-down list. A sample screen is shown next:

Verify the database

in which to store the
ModelMart.

5. Click Create to create the ModelMart tables and stored procedures in the
selected database. After the ModelMart is created, the ModelMart Security
Manager opens.

Important! The ModelMart and the ModelMart Control Tables must be

installed on the same database.

3–3
04MM4103.doc, printed on 8/5/2002, at 11:34 AM

Installing ModelMart and Initializing the Database!

6. In the ModelMart Security Manager dialog, drag your user name from the
User list to the Administrator profile in the Security Profile list.

Important! If you skip this step, you will not be able to access
ModelMart.

7. Optionally, use the controls in the Security Manager dialog to assign security
profiles for the database to other ModelMart users.
8. When you are done assigning profiles click OK. The Setup Complete message
displays.
9. Click OK to return to Windows.

3–4
04MM4103.doc, printed on 8/5/2002, at 11:34 AM

Installing ModelMart and Initializing the Database!

Initializing ModelMart on Oracle

Use the following steps to initialize ModelMart on Oracle:
1. In Windows 98, Windows 2000, Windows ME, Windows XP, or
Windows NT Version 4.0, click Start on the taskbar, and then choose
Programs, Computer Associates, AllFusion, Model Manager, ModelMart.
2. In the ModelMart Connection Manager, enter the following:
• Type the login name and password for the schema owner of the
database containing ModelMart
• Select the host Oracle DBMS version in the Host DBMS box
and type the connection string (for example, mm.world) in the
DBMS Connection box.
3. Click Connect to connect to the ModelMart database and open the
ModelMart Manager dialog.
4. On the ModelMart Manager dialog, select the Oracle MMUSER security
role from the ModelMart Role drop-down list.

Select MMUSER as the ModelMart

database role
Choose the Tablespace in which
to store the ModelMart tables.
Choose the Tablespace in which to
store the ModelMart table indexes.

Important! If you do not select the User role, users will not be able to
access ModelMart. This role is created in step 10 of the
procedure for creating the ModelMart database on Oracle. For
details, see the appendix “Creating the ModelMart Database” in
the Administrator Guide.

If you are initializing a ModelMart in an Oracle instance that also

contains a ModelMart 3.02 database, the conversion options display in
the ModelMart Manager dialog. Clear the convert from 3.0.2 to 4.1 check
box.

3–5
04MM4103.doc, printed on 8/5/2002, at 11:34 AM

Installing ModelMart and Initializing the Database!

5. From the Table Tablespace drop-down list, select the Oracle tablespace
in which you want to store the ModelMart tables. Optionally, select the
Oracle tablespace in which you want to store ModelMart indexes from
the Index Tablespace drop-down list. You can store the tables and
indexes in the same tablespace or in different tablespaces.
6. Click Create to automatically create the ModelMart objects. When the
ModelMart is created, the Security Manager dialog opens.
7. In the ModelMart Security manager dialog, drag your user name from the
User list to the Administrator profile in the Security Profile list. For a
sample Security Screen, see step 6 in Initializing the ModelMart on
Microsoft SQL Server or Sybase in this chapter.

Important! If you skip this step, you will not be able to access
ModelMart.

8. Optionally, use the controls in the Security Manager dialog to assign

security profiles for the database to other ModelMart users.
9. When you are done assigning profiles click OK. The Setup Complete
message displays.
10. Click OK to return to Windows.

Initializing ModelMart on Informix

Use the following steps to initialize ModelMart on Informix:
1. In Windows 98, Windows 2000, Windows ME, Windows XP, or
Windows NT Version 4.0, click Start on the taskbar, and then choose
Programs, Computer Associates, AllFusion, Model Manager, ModelMart.
2. In the ModelMart Connection Manager, complete the following dialog
information and click Connect.

• Select your DBMS version (for example, Informix Vers. 7/9.xx)

from the Host DBMS drop-down list.
• Type the name of the ODBC data source that lets you access the
Informix database in which you want to install ModelMart (for
example, informix911) in the DBMS Connection box.

NOTE: You must create the ModelMart in the database referenced by

the ODBC data source you specified when you logged on.

3–6
04MM4103.doc, printed on 8/5/2002, at 11:34 AM

Installing ModelMart and Initializing the Database!

3. Click Connect to connect to the ModelMart database and open the

ModelMart Manager dialog.

4. Click Create to automatically create the ModelMart objects. When the

ModelMart is created, the Security Manager dialog opens.
5. In the ModelMart Security manager dialog, drag your user name from the
User list to the Administrator profile in the Security Profile list. For a
sample Security Screen, see step 6 in Initializing the ModelMart on
Microsoft SQL Server or Sybase in this chapter.

Important! If you skip this step, you will not be able to access
ModelMart.

6. Optionally, use the controls in the Security Manager dialog to add and
remove other ModelMart users and assign security profiles for the
database.
7. When you are done assigning profiles click OK. The Setup Complete
message displays.
8. Click OK to return to Windows.

What’s Next
This chapter discussed the ModelMart administrator's job of setting up the
ModelMart. The administrator also needs to assign user security profiles and set up the
libraries in which models are stored. The next chapter explains how user security
profiles can help secure models.

3–7
 05MM4104.doc, printed on 5/7/02, at 11:17 AM

4
Chapter

Secure Your Models!

Setting Up User Security!

Y ou need to think about how you are going to secure your models—who will
have access to them and what can they do to them. Initially, only the
ModelMart administrator who installed the ModelMart database can assign
security profiles. However, the administrator can grant such authority to other users by
giving them an Administrator security profile. These tasks are performed in the
ModelMart Security Manager.
By assigning a user to a security profile, the ModelMart administrator can control
the actions that the user can perform. Models can also be protected by locking them
and by organizing them into libraries. For details on locking and libraries, see the
chapters “Lock Your Models” and “Organize Your Models.”

Assigning Security Profiles

The ModelMart administrator assigns each user to a security profile and makes the
assignment applicable to a specific database, library, model, or subject area. There are
five default profiles: Administrator, Architect, Modeler, Viewer, and Guest. Each
profile grants permissions at the object class levels: database, library, model, entity and
subject area. Permissions specify whether or not a user can create, delete, or perform
updates in each of these object classes.

4–1
05MM4104.doc, printed on 5/7/02, at 11:17 AM

Setting Up User Security!

If you have an Administrator profile, you can follow these steps to assign a user to
a profile applicable to a specific database, library, model or subject area:
1. Open the ModelMart Security Manager and select a database, library,
model, or subject area in the Object tree.
2. In the User pane, select the user that you want to assign to a security
profile.
3. Drag the icon for the user from the User list onto the security profile
icon in the Security Profile list.
4. Repeat Steps 2 through 4 for each ModelMart user.
In the following example, User02 is given the Modeler security profile for the Test
library:

Administrators can assign users to more than one profile. For example, a user can
have a different profile for different libraries. In Library 1, the Administrator can
assign a user to the Architect profile, which grants extensive read and write privileges.
In a Library 2, that same user can be assigned to the Viewer profile, which grants read-
only permission.

4–2
05MM4104.doc, printed on 5/7/02, at 11:17 AM

Setting Up User Security!

Using the Profile Manager

To view the permissions associated with a profile, click the Profile button in the
ModelMart Security Manager. The ModelMart Security Profile Manager will appear.
You can click on a security profile and an object class to view the associated
permissions in the Permission pane. This sample dialog shows the default permissions
applicable at the model object level for the Modeler security profile.

Only an administrator can change the permissions by selecting or deselecting them

in the Permission pane. An administrator can also modify the default security profiles
or create new security profiles. For example, a new security profile could be created to
restrict a user from creating entities in models. In the ModelMart Security Manager,
the administrator could then assign a user the new security profile for a specific model.
This restriction would apply even if the user had been assigned the Modeler profile at
the database level, which otherwise allows the user to create entities in models.

4–3
05MM4104.doc, printed on 5/7/02, at 5:01 PM

Setting Up User Security!

Buddy Tip—If you are an administrator and need to know how to add or modify a
security profile, see the Administrator Guide for details.

Using Lock Options to Restrict Model Access

When you open a model in the Open ModelMart Model dialog, you can change
the Lock Options so that you can avoid inadvertently updating a model. For example,
if you have update security permission for the model you want to open, you can
choose the Read-only Lock Option in the dialog. You can also choose to lock the
model, provided someone else has not already locked it. See the chapter “Lock Your
Models,” for more information on locking.

Buddy Tip—If you do not have permission to save changes to a ModelMart model, you
could still open the ModelMart model, make changes to the model, and then save it locally as
an ER1 (ERwin) or BP1 (BPwin) file. However, when you save changes back to
ModelMart, the model is updated with the changes for which you have permission, but all
prohibited changes are discarded.

What's Next
You've just learned how user security profiles protect models. You also need to know
about libraries, in which models are stored. After setting up the libraries, the
administrator may want to reassign security profiles, because security profiles can be
applicable to specific libraries or models. The next chapter will help you to set up your
libraries.

4–4
 MD12.doc, printed on 5/2/02, at 4:19 PM

5
Chapter

Organize Your Models!

Setting Up Libraries!

I n order to save a model in ModelMart, you must first create a library in which to
put the model. A library is a container object that is used to group models.
Initially, the ModelMart administrator or architect sets up the libraries. Later, other
users may be given security permission by the administrator to perform this task.
Libraries aid security and standardization as described next:
Limit access for security reasons–Libraries facilitate access control because
security profiles can limit access to specific libraries. In addition, security
profiles can allow a user to create, rename, or delete libraries.
Maintain clear boundaries between projects–Where isolation and clear
boundaries between projects must be maintained, a library provides that
boundary to protect the integrity of your project. Most organizations find that
establishing several libraries helps to distinguish one set of models from
another. For example, you may want to create two libraries one for Test and
the other for Production. Or, you may want to create a library for each
functional area such as Customer Service and Sales. Library-level security
permissions may be established to help protect the models in a library from
inadvertent changes or deletions.
Aid standardization–Templates with standards can be stored in each library.
Templates maintain ModelMart model settings such as background color,
foreign key color, shadow offset, display level, and predefined stored displays
that are automatically applied to each new model based on the template.
Templates provide the ideal way of maintaining a consistent look and feel
across models.
In addition, ERwin model objects can be maintained with one library
standards model that contains objects to be shared. The model that holds the
objects is used as a source model for other models in the same library. You
can use the Sync with Model Source wizard to synchronize the source model
with a model where you would like the change to take effect. To open the
Sync with Model Source wizard, choose Sync with Model Source on the
ERwin Tools menu.

5–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Setting Up Libraries!

Set Up a New Library

To open the ModelMart Library Manager, click on the ModelMart toolbar. This
sample screen shows that two libraries–Test and Production–have been created in the
database named mdlmrt41.

To add a library:
1. Click on the database name in the tree control.
2. Then type the new library name in the Name box, and click Create.
3. If you need to rename a library, select the library by clicking on it. Then
type in the new name in the Name box and click Update.
4. If you want to, you can add a description for the library. Click the
Detailed button, and type in the Description box. Click Update to save
your changes.
If you click the Detailed button, the dialog changes to the details view. You will
see a Details box, which shows when the library was created and by whom. From the
details view, click Brief to return to the brief view.

5–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Setting Up Libraries!

This sample screen shows the details view, where a description has been added for
the Test library.

The Delete button should only be used if you are sure you want to delete a library
and all the models it contains.
Click Close when you are finished.

Viewing Libraries
Keep in mind that when you access ModelMart through ERwin, you will not be able to
see any BPwin models listed in the ModelMart Library Manager. If a BPwin library
exists, the library folder will be visible in the tree control, but it will appear to be
empty. The opposite is also true. If you access ModelMart through BPwin, you will not
be able to see any ERwin models in the Library Manager.
Buddy Tip—For more information, search the online help index for ModelMart Library.

5–3
MD12.doc, printed on 5/2/02, at 4:19 PM

Setting Up Libraries!

What's Next
Now you know how to set up libraries and why libraries aid security and
standardization. The next chapter explains how to connect to ModelMart.

5–4
 MD12.doc, printed on 5/2/02, at 4:19 PM

6
Chapter

Join the Workgroup!

Connecting to ModelMart!

A fter the ModelMart administrator has created a ModelMart database and

defined user permissions at the database level to allow you to access the
database, you can connect to the ModelMart. When you are ready to connect,
open one of the ModelMart clients. The ModelMart Connection Manager dialog
automatically appears, unless you previously checked the box for Suppress this Dialog
on Startup. If the dialog does not appear, go to the ModelMart menu and select
Connection.
On the ModelMart Connection Manager dialog, enter your login ID, which is the
ModelMart user ID given to you by your ModelMart administrator. Also, enter the
password given by your DBMS administrator.
Next, you must tell the ModelMart Connection Manager where to find the
ModelMart database. To do this:
1. Enter the Host DBMS, which is the database management system
(DBMS) version that is the host of your ModelMart.
2. For DBMS Connection, enter the name of the server that is used to
connect to ModelMart.
3. For Master Database, enter the database where the ModelMart Control
Tables are stored. If you already specified that the Host DBMS is Oracle,
the Master Database field is grayed out. If this is not the first connection
to ModelMart, you can refer to the History to see previous connections.

6–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Connecting to ModelMart!

After you have entered the appropriate information in the ModelMart Connection
Manager, you are ready to click Connect.

The History
list shows the
last few
connections to
a ModelMart.

To suppress the ModelMart Connection Manager dialog from displaying as soon

as you start ERwin, check the box for Suppress this Dialog on Startup. The next time
you want to connect, you will need to open the ModelMart menu and select
Connection in order for the ModelMart Connection Manager dialog to appear.
When you are ready to disconnect from ModelMart, open the ModelMart
Connection Manager and click Disconnect.

Buddy Tip—For more information, search the online help index for ModelMart:
connecting to.

6–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Connecting to ModelMart!

What's Next
Now that you know how to connect to ModelMart through a ModelMart client, you
should be ready to start working with models in ModelMart. In the next chapter, you'll
learn how to add models to the ModelMart, as well as how to open, close and save
them.

6–3
 08MM4107.doc, printed on 5/7/02, at 5:47 PM

7
Chapter

Open, Close, Save Models!

Working with Models—the Basics!

B
efore you can work on your ModelMart models, you must save them the to the
ModelMart database. To do this, open the model in the ModelMart client,
ERwin or BPwin; then save it to ModelMart. Once your models are saved in the
ModelMart, they become available to other members of the workgroup. ModelMart
provides workgroup modeling features–model status, lock options, review changes–
that help to control updates to models when you are opening, closing and saving
models.

Saving a Model to ModelMart for the First Time

When you save a model to ModelMart, you must first locate the library in which you
want to save the model. Then give the model a name. You can save BPwin models and
ERwin models to the same library. However, ERwin models can only be seen to exist in
the library when you are connected to ModelMart from ERwin. Similarly, BPwin
models can only be seen when you are connected to ModelMart from BPwin.
If the model was previously saved as an ERwin or BPwin model, by default it has
the same name as the previously saved model without the ER1 or BP1 file extension.
You can change the name.

7–1
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

Try the following exercise to see how to open an ERwin model and save it to
ModelMart in a library that you already created.

You can
rename
the default
model
name.

1. Open the sample EMOVIES.ER1 file, which is by default located in

C:\Program Files\CA\AllFusion ERwin Data Modeler\Samples
\Standard.

2. On the ModelMart toolbar, click to open the Save ModelMart

Model As dialog.
3. In the ModelMart Library list, select Test as the ModelMart library. At
this point, if you have permission to create libraries, you could create a
new library by clicking on the ModelMart Library button to open the
ModelMart Library Manager dialog.
4. In the ModelMart Model text box, after EMOVIES, type –MM to change
the default name of the model to EMOVIES-MM.
5. Click OK to save the model.
After the model is saved in ModelMart, the ERwin title bar changes to reflect the
ModelMart information.

7–2
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

Opening a Model
When you open a ModelMart model, ModelMart automatically creates a copy of the
model and sends it to your workstation. If you prefer, you can work off line by saving
the model to your workstation as an ER1 file (ERwin) or BP1 file (BPwin), and then
disconnecting from ModelMart.
When you work on a ModelMart data model, you can use all of the ModelMart
and ERwin tools and features to modify the model. When you work on a ModelMart
process model, you can use all of the ModelMart and BPwin tools and features to
modify the model.
To open a model:
1. Choose Open on the ModelMart menu to access the Open ModelMart
Model dialog.
2. Select the library that contains the model you want to open. All the models
in the library you selected will now appear in the ModelMart Model box.
3. Select the model you want to open, and click OK to open it. You may be
able to change the Lock Options before you open the model. To learn
more about these options, see the chapter “Lock Your Models.”

You can also open a subject area (submodel), rather than the entire model. The
submodel icon appears in front of each submodel. See the chapter “Work with
Data Model Submodels,” for more information.

7–3
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

Closing a Model
If you choose Close on the ModelMart menu, you will have the option to save the
model to ModelMart, save the model locally, or close without saving the model. The
Close dialog also shows the status of the file, such as if it was opened from the server,
its lock status, and whether there are unsaved changes.
A sample Close dialog is shown next.

If you had already saved all the changes you had made to the model while you had
the model open, the Save to ModelMart close option would be grayed out, and the text
in the Status box would state that your model was up-to-date. In that case, you could
choose to Save as ER1 file (or Save as BP1 file), or Close without saving.

7–4
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

Saving Models
ModelMart provides the following save options:
• Save–To simply save a model, click on the ModelMart toolbar or
choose Save from the ModelMart menu. This opens the Save Model to
ModelMart dialog:

Uncheck the Review All Changes Before Save box only if you do not want to
review any changes that you may have made to your model. Click OK to save
the model.
• Close–When you choose Close on the ModelMart menu, the Close dialog
gives you the options of saving the model to ModelMart, saving the model
locally as an ERwin or BPwin file, or closing without saving.
• Save As–If you want to rename a model, use the Save As option on the
ModelMart toolbar. You can also save a copy of the model to another library
using this option. You need to be careful when renaming models. For details,
see Renaming When Saving in the chapter “Track Changes with Versions.”

Buddy Tip—If the model you want to save has been locked, your changes will not be saved
to that model until it is unlocked. For details on locking, see the chapter “Lock Your
Models.”

7–5
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

Multi-Mart
The Multi-Mart feature allows you to save a ModelMart model locally, or to another
ModelMart, and then save it back to the ModelMart with all the functionality of the
ModelMart model intact.
When you save a ModelMart model as an ER1 file (ERwin) or BP1 file (BPwin),
you can later save it back to ModelMart. ModelMart automatically recognizes models
that were previously saved in it. When you open the model and save it in ModelMart,
the ModelMart Change Control Manager–Review Changes dialog opens and displays a
list of changes made to the model outside of ModelMart. The change list shows how
the model you are saving differs from the model on ModelMart, and you can use the
dialog to review these changes and accept or reject them, before saving to ModelMart.
This functionality also allows you to save a ModelMart model to an ER1 file or a
BP1 file and then save the ER1 file or BP1 file as a ModelMart model in another
ModelMart. You can save changes to the ModelMart model in the other ModelMart.
Then save it as an ER1 file or a BP1 file, and then use the model merge feature to
merge the model into the same ModelMart model in the first ModelMart.

Saving Changes
When you are finished working in a ModelMart model and want to save your changes,
if you choose the option Review All Changes Before Save, the ModelMart Change
Control Manager–Review Changes dialog opens and displays a list of changes. This
dialog shows the changes that you made to the model on your workstation. Also, if
you have been working on an unlocked model, the Review Change dialog may show
that changes were made to the ModelMart model by another modeler since you
opened the model from ModelMart or since you last saved the model to ModelMart.

Saving Your Changes

In the following exercise you will learn how to review your changes before saving
them.
1. With the EMOVIES-MM model open, click the drop-down arrow

on the ERwin toolbar and select the Physical model.

2. In the Model Explorer, expand the Tables list. Right-click on
CUSTOMER_1, and then select Rename from the context menu. When
the text box appears around the table name, change CUSTOMER_1 to
CUSTOMER INFO.
3. Change the name of CUSTOMER_2 to CUSTOMER_CREDIT.

4. On the ModelMart Toolbar, click the Save to ModelMart button .

7–6
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

5. When the Save to ModelMart dialog appears, be sure to check Review All
Changes Before Save and click OK. The ModelMart Change Control
Manager–Review Changes dialog will appear.

Reviewing Your Changes

The Change Control Manager–Review Changes dialog shows the changes that you
made to the model since the model was last saved. The direct changes listed in the next
screen show that you changed the entity name CUSTOMER_2 to
CUSTOMER_CREDIT, and CUSTOMER_1 to CUSTOMER_INFO.

7–7
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

By default, the dialog does not show detail-level or graphical changes. These are
the indirect changes that ModelMart automatically implements as a result of the direct
changes you made. However, if you click the Show Graphical Changes tool , the
Review Changes dialog will show additional information as follows:

The Graphical Changes tool displays or hides graphical changes. These are
changes to the visual appearance of the model, such as repositioning an entity, a
relationship line, or changing an entity name as we did in this exercise.

Accepting and Rejecting Changes

You can accept or reject any direct changes that appear in the Review Changes dialog.
1. If you decide to reject a change, select the direct change and click the
Toggle button . An will appear in front of the change where the
arrow had been, and the text will turn red to indicate that this change
will not be saved.

7–8
08MM4107.doc, printed on 5/7/02, at 5:47 PM

Working with Models—the Basics!

The next screen shows that the change of the entity name from
CUSTOMER_2 to CUSTOMER_CREDIT has been turned off.
Reject a
Specific
Change

2. To accept all of the changes that appear in the Review Changes dialog,
except any changes that you have turned off, and save the model back

to ModelMart, click the green arrow on the ModelMart toolbar.

3. If you want to exit from the Change Manager dialog without saving
any changes, click . You will return to the model in which you
were working, and all the changes that you had made to the model will
still appear on the screen, even though you did not saved them.
Buddy Tip—To learn more about the ModelMart Change Control Manager, see the
chapter “Manage Changes to Models.”

What's Next
The basics of saving, opening, and closing models were discussed in this chapter. Now,
you are ready to learn more about the Change Control Manager, which helps you to
see what changes were made and to control what changes will be saved.

7–9
 09MM4108.doc, printed on 5/8/02, at 11:17 AM

8
Chapter

Manage Changes to Models!

Using the Change Control Manager!

T
he Change Control Manager is useful to workgroup modelers who work with
shared models, and to individual modelers who work with their own models.
This feature enables a user to review their own changes before saving them,
view changes previously saved, and compare changes saved to two different versions.
It also enables a user to refresh the unlocked model they have open with any changes
made by another concurrent modeler.
Changes are viewed in the change list, which can be filtered by type of change and
searched so that you can easily find any specific changes you want to review. You can
use the change list to turn off your own changes before you save them and resolve
conflicting changes made by other modelers.
There are several variations of the Change Control Manager–Review Changes,
Conflict Resolution, Refresh Client, and Version Differences. The variation of the
dialog depends upon the operation you performed to invoke it. The dialogs are very
similar, but not all of the capabilities of the Change Control Manager are available in
each.

Review Changes

You can review changes in an open model at any time by clicking the Review
Changes icon on the ModelMart toolbar. This opens the Change Control Manager–
Review Changes dialog where you can review all the changes made since opening the
model. Every time you save a ModelMart model, you have the option of using the
Change Control Manager–Review Changes dialog to selectively accept or reject
individual model changes.
For an example of how to save your own changes, see Saving Your Changes in the
chapter “Open, Close, Save Models.”

8–1
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

A sample Review Changes screen is shown next:

Special symbols combined with a transaction statement identify the types of

changes that appear in the change list. Here are some of these symbols and statements,
which are located in front of the change they identify:
Delete
Add or Create
Set, Update, Clear, or Define
Buddy Tip—For more information about the change list icons, search the online help index
for Change Control Manager: icons.

8–2
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

Changes Made by Concurrent Users

When you compare your changes with changes made by other modelers in the
workgroup environment, the change Control Manager allows you resolve conflicts by
accepting and rejecting model changes made by you and other modelers. This feature
is available when you save a ModelMart model and choose to review model changes. It
is also available when you have a ModelMart model open and you choose the Refresh
option, which compares your open model with the current state of the model to see if
any other modelers have saved changes since you opened the model.

Conflict Resolution
In a workgroup modeling environment, you and other users may be working on the
same ModelMart model (ERwin or BPwin) at the same time. For example, if you
opened a model from ModelMart and you do not lock it, another modeler could save
changes to the model. When you save your changes with the option Review All
Changes Before Save, their changes will appear in the Change Control Manager–
Conflict Resolution dialog along with the changes you made. However, the changes
made by the other modeler will appear in a separate list. Your changes are shown on
the left side and changes saved to the ModelMart model by the other modeler are
shown on the right side. If you right-click on a change statement in the right side of a
two-panel dialog, you can access more information about the change (who made the
change and when).
For example, if you did the exercise in the section Saving Your Changes in the
chapter “Open, Close, Save Models,” you would have made the following changes to
the EMOVIES-MM model:
• Changed the table name of CUSTOMER_1 to CUSTOMER_INFO
• Changed the table name of CUSTOMER_2 to CUSTOMER_CREDIT
Suppose that after you opened your model from ModelMart, and before you
chose to save it, another modeler saved the following changes to the ModelMart
model:
• Changed the table name of CUSTOMER_2 to CUSTOMER_CR
• Changed the table name of EMPLOYEE to EMPLOYEE_NUMBER

8–3
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

When you save the model to ModelMart with the Review All Changes Before Save
option, the following Change Control Manager will appear:

Changes already saved to the

Changes you made ModelMart model after you
to the model on your opened the model from
workstation. ModelMart.

Your conflicting changes appear on the left. The conflicting changes already saved
to the model in the ModelMart database appear on the right. By default, the Conflict
Resolution change list shows that all your conflicting changes have been cancelled and
all of the your nonconflicting changes have been accepted. However, in this sample
dialog, the change lists are filtered to show only conflicting changes. (For information
about filtering, see Filtering the Change List later in this chapter.) Changes that appear
in red text with an in front of them will not be saved; changes that appear in black
with an in front of them will be saved.

8–4
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

To use this dialog to resolve conflicting changes:

1. Compare the changes in the left and right change lists and decide which
changes you want to accept or reject.
2. You can choose to accept your conflicting changes and override the
corresponding change in the right side. To do this, double-click the in
front of your change. The text of your change will now appear in black
and the corresponding rejected change will now appear in red. You can
toggle back and forth using to turn selected changes on and off.
You can use SHIFT+click or CNTRL+click to simultaneously cancel or
accept multiple changes.
3. When you have made your choices in the Conflict Resolution dialog,

click .
4. The Review Change dialog with a single change list showing the
approved changes will open. You can review the change list before you
save to ModelMart and reject any change in this list.

5. When you have finished your review, click to save your changes.
Buddy Tip—If your changes conflict with changes made by other users, in addition to
selectively saving or canceling each change in the list, you can filter the list to highlight items,
and create a customized report to help resolve conflicts in collaboration with other modelers.
For details about filtering, see Filtering the Change List later in this chapter. For details
about reports, see the chapter “Create Data Model Reports.”

Refresh
While you are working on an unlocked copy of a ModelMart model, other users can
save changes to that model. You can use the refresh feature to see the changes made
by other users and update your model with any changes that do not conflict with
changes made by you.
After you choose Refresh on the ModelMart menu, if no changes were made by
other users, a message appears indicating that your copy of the model is current:

8–5
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

If other modelers have made changes, the Change Control Manager–Refresh

Client dialog is displayed. This dialog shows your changes and any changes saved to
the model by other modelers since you opened the model or since you last saved it.
You can accept or reject conflicting changes made by you or by other workgroup
modelers.
Here is a sample Refresh Client dialog:

Filtering the Change List

You can filter the change list to control the type of changes that are displayed in the
list. Keep in mind that the following levels of changes can be viewed in the change list,
depending upon how you set the filters:
Top-level changes–These are the direct changes that you or another user makes
to a ModelMart model. An example would be creating a relationship between
two entities.
Detail-level changes– These are the indirect changes that ModelMart
automatically applies when you make a change to a ModelMart model. For
example, when you create a relationship between two entities, ModelMart
automatically adds a foreign key attribute in the child entity.

8–6
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

Select any of the following tools on the ModelMart Change control manager
toolbar while you review the conflicts:

• To display conflicting changes only, click .

• To display or hide detail-level changes (such as a foreign key attribute),

click .
• To display or hide graphical changes (such as the new position of an
entity), click .

• To search for changes in the change list, click .

• To display detailed information about a specific change, select the change
in the change list and click .
You can also filter the list by setting the filter options. From the View menu,
choose Filters. The Change Manager Filter Selection dialog will appear. You can turn
the filters on and off by checking or unchecking the filter options.
For example, if you want to filter out details, graphical properties, and read-only
properties as selected in the sample Change Manager Filter Selection shown next, the
change list will include conflicting and unconflicting graphic objects only.

You must click OK to apply the filters to the current Change Control Manager
screen. These filters will continue in effect each time the Change Control Manager
opens, unless you change the filters in the filter selection dialog or select the filters
using the toolbar icons.

8–7
09MM4108.doc, printed on 5/8/02, at 11:17 AM

Using the Change Control Manager!

Buddy Tip—For more information, search the online help index for ModelMart Change
Control Manager.

What's Next
You learned how the Change Control Manager can help you to control changes to
models. You can also protect your models by using the lock options. How to do this is
explained in the next chapter.

8–8
 10MM4109.doc, printed on 5/8/02, at 3:12 PM

9
Chapter

Lock Your Models!

Working Simultaneously on the Same Models!

L ock options help to secure models and manage how changes are saved to
ModelMart. You can change the lock option when you open a model. However,
the options available to you depend upon your security profile and whether or
not another user has already locked the model. You can also change the lock option
after you have opened a model and are working in the model, and when you close it.

Lock Modes
ModelMart provides the following lock options:
Locked–If you have permission to update and save a model, you can lock the
model exclusively for your own use and prevent other users from saving
changes to the model in the ModelMart database during your modeling
session. In effect, other modelers are locked out from saving changes until
you unlock the model. Because you hold an exclusive lock, you can save the
ModelMart model without having to check for conflicting changes made by
other users. In addition when you close a ModelMart model, you can select
the Keep ModelMart Diagram Lock option on the Close dialog to keep a
model locked for your own use even after you have disconnected from
ModelMart. For example, if you save an ER1 file to work offline, you can
keep the ModelMart model locked so that no other user can make changes to
it while you are working offline.
Unlocked (default)–If you have permission to update and save a model, you
can open a model in Unlocked (shared) mode. Because other users can save
changes to the ModelMart while you are working on an unlocked model, you
may have to resolve conflicts with their changes when you save your work to
ModelMart.
Read-only–This lock mode is automatically assigned to you, if your security
profile does not grant you permission to update and save the selected model.
When you open a ModelMart model in read-only mode, you can view the
model and save it locally as an ERwin or BPwin file, but you cannot save the
model back to the ModelMart database.
Before you open a model, ModelMart checks your assigned permissions and
determines whether or not another user has locked the model you want to open. This
information is used to determine which locking options are available in your modeling
session.

9–1
10MM4109.doc, printed on 5/8/02, at 3:12 PM

Working Simultaneously on the Same Models!

Buddy Tip—Whether or not you can update and save a model is defined in your security
profile. Contact your ModelMart administrator if you need to update a model that
automatically opens as read-only.

Working with the Lock Modes

When you open a ModelMart model, you use the Open ModelMart Model dialog,
which is accessed by choosing Open on the ModelMart menu. On this dialog, the
Lock Option box shows whether the model will open as unlocked, locked, or read-
only. Models open in unlocked mode by default. If another modeler already has the
model open, that user may have already locked it. A model could also be locked if a
user closed it and selected the option to keep it locked on the Close dialog. If a model
is unlocked any user can lock it, if they have permission to update and save the model.
The read-only mode depends on the security profile assigned to the user who opened
this dialog.
The lock options are dimmed if you do not have permission for an action or if
another user has locked the selected model. For example, if you do not have
permission to update a model, ModelMart dims both the Locked and Unlocked
options and automatically selects Read-Only.
A sample Open ModelMart Model dialog is shown next:

9–2
10MM4109.doc, printed on 5/8/02, at 3:12 PM

Working Simultaneously on the Same Models!

You can change the lock mode in an open model, by checking or unchecking
Lock on the ModelMart menu, provided you have permission to update and save the

model. You can also toggle the lock mode by clicking the Lock button on the
ModelMart toolbar. However if another modeler already holds the lock, you can't
unlock it. Users who don't hold the lock are able to open and work on a locked model,
but they are not able to save their changes to ModelMart. You could save the model
with the changes to ERwin or BPwin. Then save it back to ModelMart after you know
it has been unlocked.
If you choose to keep the lock on the model, no one else can save his or her
changes until you unlock it. If you choose to work on a model without locking it, you
and other users can save changes on a first-come-first-serve basis. As a result, you may
have to resolve conflicts with their changes in the ModelMart Change Control
Manager dialog when you save the model back to the ModelMart database. ModelMart
tracks the changes made to a model since you opened it, so you can safely merge in
your changes without overwriting changes made by other users. For details about
conflict resolution, see Changes Made by Concurrent Users in the chapter "Manage
Changes to Models."

Buddy Tip—If a data model submodel is locked, it locks the entire model.

What's Next
In this chapter, you learned that the lock options can help protect your models from
unauthorized changes. Next, you'll see that each time you save changes, a new version
of a model is created. Thus, the versioning feature creates an audit trail that will help
you to keep track of changes that were saved.

9–3
 11MM4110.doc, printed on 5/2/02, at 4:23 PM

10
Chapter

Track Changes with Versions!

Working with Versions!

A record of each set of changes made to a model is maintained by designating

each save as a different version of the model. The parent model is the most
recent state of the model. Each time changes are saved to a parent model, a
new parent is created, and the prior parent becomes a version. Each version represents
the state of a model at the time of a particular save. The versioning feature allows you
to see who made what changes to each version and when, and allows you to revert
back to earlier states.

Parent Versions
When you open a model from the Open ModelMart Model dialog, you are opening the
parent model. If you click on the model to select it, you will be able to see who created
the model and who made the last changes, along with the dates. This information will
appear in the lower area of the dialog below the name of the model you selected. A
sample Open ModelMart Model dialog is shown next:

Details
about the
selected
model.

10–1
11MM4110.doc, printed on 5/2/02, at 4:23 PM

Working with Versions!

Versions
To see if prior versions of the parent model exist, open the ModelMart Version
Manager. If there are any prior versions, they will appear in the expanded view of the
directory tree under the parent model with the most recent prior version appearing
directly under the parent model and the earliest version appearing at the end of the list.
The earliest version is v.1, which is the state of the model when it was first added to
the ModelMart. Each time changes are saved, a new version is created with a
sequential version number. Here is a sample ModelMart Version Manager dialog:

Version numbers

Parent
model

Model
versions

Earliest
version
of the
model

10–2
11MM4110.doc, printed on 5/8/02, at 3:50 PM

Working with Versions!

Locking
When you open a parent model on the Open ModelMart Model dialog, you can select
the Lock Option. When you open a version, you do not have the option to select the
lock mode on the ModelMart Version Manager. However, once the parent or version
is open, you can turn the lock mode on or off by checking or unchecking the Lock

option on the ModelMart menu. You can also use on the ModelMart toolbar to
toggle the lock mode on or off.

Saving
When you save a ModelMart model, ModelMart saves your changes as the parent
model. At the same time, what had been the parent model before you saved your
changes becomes the most recent prior version. Each version is assigned a unique
name, with a sequential version number, the user ID of the modeler who saved the
changes to that version, and the date that the save was made.
Every save creates a new parent and the old parent becomes the latest prior
version. If you save changes to a parent model, the save creates a new parent (from the
parent plus the changes you made), and the old parent becomes the latest version that
is identified by a unique version number. This is also true when you save a prior
version. However, when you open, change and save any prior version, that prior
version remains unchanged, and it retains the same unique name and version number.
Thus each version is preserved and serves as a record of each set of changes made in a
particular save.
If you want to revert to an earlier version, you can promote a version to parent
status by opening it and saving it. It will then become the current parent. You can also
save the version using the Save As option on the ModelMart menu to save it with a
new name. For details, see Renaming When Saving in this chapter.

10–3
11MM4110.doc, printed on 5/2/02, at 4:23 PM

Working with Versions!

Example of Saving a Version

Look at the sample screen below, and assume that you opened, changed and saved
EMOVIES-MM: v.1.

The result of your action would be threefold:

ΠEMOVIES-MM: v.1 would remain unchanged.
 Your save (which consists of EMOVIES-MM: v.1 and the changes you made
to it) would become the new parent model E-MOVIES-MM.
Ž The old parent would become the latest version. Because there are already
three versions, the old parent would be renamed
EMOVIES-MM: v.4.

10–4
11MM4110.doc, printed on 5/2/02, at 4:23 PM

Working with Versions!

When the save is complete, the screen would show the new version v.4, which was
the prior parent. The prior parent would be replaced with the latest save:

Renaming When Saving

You can open, change, and save a parent or version with a new name using the Save
As option on the ModelMart menu. In this case, the new model is not recorded as a
version of the model from which it was created.
If you use the Save As option to save a version and change the version name to
the parent model's name, the result is a new parent with no prior versions. All the
version information is lost.

10–5
11MM4110.doc, printed on 5/2/02, at 4:23 PM

Working with Versions!

Marked Versions
You can designate a version as a marked version to distinguish it as a milestone in the
development process. Although versions can be deleted using the Purge button on the
ModeMart Version Manager, marked versions cannot be purged.
To mark a version:
1. Select the version.
2. Click the Mark version button to open the Save ModelMart Version
dialog.
3. In the Save ModelMart Version dialog, provide a description to
distinguish this version from other versions. If you want to, you can also
use this dialog to change the name of the version.
4. Click OK when you are finished.
The icon in the ModelMart Version Manager directory tree identifies marked
versions. The marked version does not replace the version from which it was created.
In the following sample screen, you can see that version v.2 still exists in the directory
tree below the new marked version. The default name of the marked version shows
that it was created from version v.2. You can change the name.

Marked
Version

created from

Version v.2

10–6
11MM4110.doc, printed on 5/2/02, at 4:23 PM

Working with Versions!

Version Differences
In addition, you can compare the contents of any version with another version of the
same model or with the parent model.
In order to compare the differences between versions:
1. Select Versions in the ModelMart menu. The ModelMart Version Manager
will open.
2. Select the two versions that you want to compare by clicking on one
version or parent, and while holding down the keyboard Ctrl key, click on
the second version.
Versions v.1 and v.2 are selected in this sample screen:

3. To compare the versions you selected, click Diff. The ModelMart

Change Control Manager–Version Differences dialog will open with
a single change list.

10–7
11MM4110.doc, printed on 5/2/02, at 4:23 PM

Working with Versions!

The change list in this Version Differences screen shows the differences
between version v.1 and version v.2, and that two changes were saved in
version v.2:

Buddy Tip—For details on working with the Change Control Manager, see the chapter
"Manage Changes to Models."

What's Next
You learned how helpful the versioning feature is because it records all changes made
to your models. Next, you'll see how easy it is to merge models together.

10–8
 MD12.doc, printed on 5/2/02, at 4:19 PM

11
Chapter

Merge Data Models!

Understanding Model Merge!

T he model merge feature allows you to merge independent data models together.
A ModelMart data model can be merged with another ModelMart data model
or with an ERwin (ER1) model. An ERwin model can be merged with a
ModelMart data model or with another ERwin model.
You might want to use model merge if:
• You have been working independently from other data modelers in your
workgroup, and now want to merge your models together.
• You have a set of models that you want to combine into an enterprise-
wide model.
• You decide to bring together two projects that you previously had
thought were separate projects.

Merge Results
When you merge two independent data models, you choose whether to create a new
model or update a current model:
New model–Merge two independent models into a single new model. The
original models remain unchanged.
Update current model–Merge changes from another model into the current
model. The other model remains unchanged.

11–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

Using the ModelMart Merge Manager

The following steps describe how to use the ModelMart Merge Manager to create a
new model or update a current model:
1. While connected to ModelMart, open an ERwin model (ER1) or a ModelMart
model. This is the current model.
2. Click on the toolbar to open the ModelMart Merge Manager. A sample
dialog follows:

3. In the Merge With pane, select the other model type–ModelMart or ER1–that
you want to merge with the open model. Use the Browse button to locate the
other model. After you choose the model, its path appears in the Merge With
field.
4. In the Merge Results pane, choose Update Current or Create New Model to
update the current model or create a new model.

11–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

5. In the Merge Method pane, choose one of the following options:

Select Filters and Resolve Differences–If you choose this option, the
Update Model wizard will allow you compare the current model and the other
model to import specific physical or logical model objects.

NOTE: The Select Filters and Resolve Differences option is similar to

the Complete Compare feature in ERwin. For details, see the
online help index for Complete Compare, or press F1 in any
merge dialog.

Automatic–This option automatically merges the current model and other

model together. You can accept or reject matching entities.
6. In the Compare Level pane, choose Logical Level or Physical Level. This
determines whether logical or physical filters will be used in the merge wizard.
7. Click Next. What happens now depends upon which merge method you
selected:
If you selected Merge Method Automatic, the current model will immediately
merge with the other model. If there are matching entities in both models,
you will be able to select the matching objects you want to merge in the
Merge Options–Matching Objects dialog.

11–3
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

If you selected the Merge Method Select Filters and Resolve Differences, the
Update Model wizard begins. At this point, the Update Model–Items to
Compare dialog opens listing the logical or physical model object types to be
used in comparing the current model with the other model. You can change
the compare options in the default Options Set by unchecking any items that
you do not want to compare with the other model.
The Compare Level option–logical or physical–that you choose on the
Update Model ModelMart Merge Manager determines the compare options in
the Update Model–Items to Compare dialog. A sample dialog follows
showing the logical default option set.

11–4
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

8. Click Next. The Update Model–Object Filter Options dialog appears. It

displays a list of the model object types that you can filter out of the
compare with the current model. Simply uncheck the check box next to
the object type.

11–5
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

9. Click Next. The Other Model Filter Options dialog appears. You can
base the filters on a specific subject area. Check the box to select this
option, and then click the button to the right to specify the subject area.

10. Click Next to proceed to the Resolve Differences dialog. This is where
you can pick and choose specific model objects from the other model to
import into the current model. An example of this dialog is shown in the
following section.

11–6
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

Merging a Model into the Current Model

The following example shows you how to merge another model to update the current
model and resolve model differences. This example assumes that you opened the
ERwin sample model EMOVIES and saved it to ModelMart with the name
EMOVIES-MM. In the following steps, you will open a submodel, change it and save
it with a new name. Then merge the new model (with the changed submodel) into the
original EMOVIES-MM.
1. Connect to ModelMart.
2. In the Open ModelMart Model dialog, open the EMOVIES-MM
submodel MOVIE.
3. In the physical model, change the table names MOVIE to FILM and
MOVIE_COPY to FILM_COPY.
4. Use ModelMart Save As to save the changes to a new model named
EMOVIES-MMFILMS.
5. Close EMOVIES-MMFILMS.
6. Open EMOVIES-MM. This is the current model.
7. Open the ModelMart Merge Manager by choosing Merge on the
ModelMart menu.
8. In the Merge With pane, select ModelMart and use the browse button to
find EMOVIES-MMFILMS. This is the other model.
9. In the Merge Results pane, select Update Current.
10. In the Merge Methods pane, choose Select Filters and Resolve
Differences.
11. In the Compare Level pane, select Logical Level.
12. Click Next. The Merge Wizard will start.
13. Click Next. The Items to Compare dialog opens. Because you chose the
Compare Level of Logical on the Model ModelMart Merge Manager, you
will see that Default Option Set–Logical appears in the Option Set field.
For purposes of this example, do not make any changes to the defaults
and click Next in this dialog and in each of the following filter dialogs
(the Update Model–Object Filter Options and the Update Model–Other
Model Filter Options dialogs)

11–7
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

The following Update Model–Resolve Differences dialog appears:

Current Model Other Model

The right side of this dialog shows the model objects in the other model that
will be copied into the current model on the left side. Note that this dialog
shows only the differences between the two models, because the option to
Show Only Differences is checked in the lower left area of the dialog.

11–8
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

The Resolve Differences dialog indicates whether the differences in the other
model will be created or modified in the resulting model. Remember that in
this example, you changed the physical names but not the logical names for
MOVIE and MOVIE_COPY. In this dialog, you can see that the physical
table names FILM and FILM_COPY in the other model differ from the
corresponding table names in the current model. The in the differences
list indicates that the differences in the other model will be imported into the
current model. You can choose to ignore these changes by using the toolbar
buttons in the dialog.

Buddy Tip—For more information about the Update Model–Resolve Differences dialog,
see the online help index for Update model: resolving differences. For more information about
merging models, see the online help index for ModelMart model: merging.

13. Click Next. A message box will tell you that the import items you selected will
be applied to model: EMOVIES-MM.

NOTE: If you choose to create a new model, rather than update a model,
a message will inform you of the new model name that is
automatically chosen for you. You can change the name when
you save the new model using Save As.

14. Click Next. The updated model will appear. Look at the table names in the
physical view to see that FILM and FILM_COPY were imported into the
new model and replaced the prior tables named MOVIE and
MOVIE_COPY.

Understanding How Differences Are Merged

If you choose Merge Method Select Filters and Resolve Differences in the ModelMart
Merge Manager, you have the option to select the model object types to be compared,
and to decide the changes to be imported into the resulting model.
By default, differences in the other model that conflict with the current model will
be imported in to the current model, regardless of whether you chose to update the
current model or create a new model. However, you can use the Resolve Differences
dialog to accept or ignore conflicting changes before you complete the merge.

11–9
MD12.doc, printed on 5/2/02, at 4:19 PM

Understanding Model Merge!

When two models are merged, it is first determined if any of the objects in the
other model duplicate an object in the current model. If two objects are the same, they
become a single object in the merged model. The new object includes all the
characteristics from both of the objects. If two objects are different, the two separate
objects are included in the merged model.
The merge rules allow similar objects in different models to be merged even
though they may contain some minor non-identical properties. For example, two
entities can be merged even if different fonts are used for the Entity Name in the
current model and the other model. When this happens, you can resolve the
differences in the Resolve Differences dialog.

What's Next
This chapter showed how to merge data models together. In the next chapter, working
with subject areas is discussed.

11–10
 13MM4112.doc, printed on 5/8/02, at 4:30 PM

12
Chapter

Work With Data Model Submodels!

Submodeling Makes Working on Enterprise Models Easier!

W hen you save an ERwin data model that contains subject areas to the
ModelMart, each subject area automatically becomes a ModelMart
submodel. You can work with a ModelMart submodel independently of the
main model. When you save the submodel, the main model is automatically updated
with your changes.
Using the ModelMart Subject Area Manager you can create, update, and delete
ModelMart submodels, much as you can in the ERwin Subject Area Editor. You can
also use the ERwin Subject Area Editor to create, update, and delete submodels in an
open ModelMart model.

Opening and Saving a Submodel

You can open a ModelMart submodel in the Open ModelMart Model dialog. First
select the library in which the model is stored. Then, select the subject area you want
to open and click OK. The icon appears in front of each submodel.

12–1
13MM4112.doc, printed on 5/8/02, at 4:30 PM

Submodeling Makes Working on Enterprise Models Easier!

You can make changes to a ModelMart submodel in the following ways:

• By changing the membership of entities in the submodel using the
ModelMart Subject Area Manager.
• By changing the membership of entities in the submodel using the ERwin
Subject Area Editor.
• Using ERwin standard features to add, delete, or update submodel
components.
Saving changes to a ModelMart submodel is the same as saving any ModelMart
model. Choose Save to ModelMart on the ModelMart menu. On the Save Diagram to
ModelMart dialog, check the Review All Changes Before Save box, if you want to
review your changes before saving them. The main ModelMart model is automatically
updated with your changes.
Buddy Tip—User security permissions can be applied at the subject area (submodel) level.
If there are conflicting security levels, the most restrictive security level prevails. .

12–2
13MM4112.doc, printed on 5/8/02, at 4:30 PM

Submodeling Makes Working on Enterprise Models Easier!

Creating a Submodel
You can create new submodels in ModelMart by using the ModelMart Subject Area
Manager. When you choose ModelMart Subject Area Manager on the ModelMart
menu, the dialog opens where you can access all models and submodels in the
ModelMart. To create a submodel, simply select the model in the
ModelMart/Library/Diagram/Subject Area tree control, type a name in the Subject
Area Name field, and click the Create SA button.

After you create the submodel, you can specify the entities that you want to
include in the submodel. In the tree control, click on the submodel you just created.
The Entities in Diagram box shows all the available entities in the main model.
Drag the entities that you want to include in the submodel from the Entities in
Diagram box to the Entities in Subject Area box. Check the Include Parents and
Children box, if you want to move parent and child entities when you move an entity.
Entities can be moved back and forth between the boxes. Click OK, when you are
finished.
When you save the model to ModelMart, the Review Changes dialog displays
where you can review your changes to the model before committing them to being
saved.

12–3
13MM4112.doc, printed on 5/8/02, at 4:30 PM

Submodeling Makes Working on Enterprise Models Easier!

If you want to rename a submodel, simply select the submodel in the tree control
and type the new name in the Subject Area Name field, and click the Rename SA
button. This change is treated like any other change; therefore, you must save the
change.

What's Next
Working with data model submodels was discussed in this chapter. How to generate
reports on data models is explained in the next chapter.

12–4
 MD12.doc, printed on 5/2/02, at 4:19 PM

13
Chapter

Create Data Model Reports!

Using the Data Browser!

W ith the Data Browser, you can create and print reports about the current
state of a ModelMart data model, as well as the changes that have been
made to a model.
You can also use the Data Browser to generate reports about libraries or security.
In order to access these options in the Data Browser, you need to open the Data
Browser from either the Library Manager or the Security Manager by clicking the
Report button.

Generate a Report on a Data Model

To generate a report about a ModelMart data model, open the Data Browser by
clicking on the ERwin toolbar or on the ModelMart Change Control
Manager. If you open the Data Browser from the Change Control Manager you will
also have the option to report on changes, which is discussed later in the section
Change Control Manager Reports.
To generate a report about a model, follow these steps:
1. In the All Reports box of the Data Browser, open the report folder for
the model you wish to report on.

2. Choose which of the reports types you would like to generate. For this
exercise, choose Entities. When you click on a report type to select it, a
description of the report type appears in the lower left box.

3. Click on the toolbar to generate the report.

13–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Using the Data Browser!

As shown in the following screen, a report of the Entities in EMOVIES-MM

has been generated and the result set appears in the right side box. All the entities in
this model are listed with the table titles and a description of each entity.

After a report is generated, the new report is listed in the All Reports box of the
Data Browser under the report type you selected.

NOTE: A result set for a ModelMart report exists only during your
current ModelMart session. If you want to keep a result set for a
new ModelMart session, you must create a folder and save the
result set in the folder. For details, see online help.

13–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Using the Data Browser!

Change Control Manager Reports

To report on changes made to a model, you must access the Data Browser through the
ModelMart Change Control Manager. The type of change information you can report
on in the Data Browser depends on what type of operation you executed to bring up
the Change Control Manager. For example, you can report changes made to an open
ModelMart model, or compare an open version with its parent. If you compare the
differences between two versions of a model by opening the ModelMart Version
Manager, selecting two models, and clicking Diff, you will be able to create a report
that compares the two versions. During the process of merging two models together,
you could also report on the differences between the models that are being merged.

Generate a Change Control Manager Report–Version Differences

Here is an example that shows you how to generate a report after you chose to
compare the differences between versions. Suppose you followed the exercise in the
section Save Your Changes in the chapter “Open, Close, Save Models.” You changed
and saved the entity name CUSTOMER_2 to CUSTOMER_CREDIT, and
CUSTOMER_1 to CUSTOMER_INFO. Now, open the ModelMart Version Manager
dialog, and select both the new version you created and the parent model. Click Diff
and the Change Control Manager—Version Differences dialog will appear.
From the Change Control Manager, follow these steps:

1. Click on the Change Control Manager toolbar to bring up the Data

Browser.
2. Expand the Script Reports folder in the All Reports box:

3. Choose one of the predefined reports in the Script tree. Each predefined
report is an SQL query that returns the requested results set from the
ModelMart. Your options are:
Script with Details–Will report on all details including graphical changes.
Script–Will not show details or graphical changes.
Compare EMOVIES-MM: v. 1 by user01 on Jan. 30, 2002 with EMOVIES-
MM–In this exercise the option compares version v.1 and the parent
model. This option varies depending upon the type of operation you
executed to bring up the Change Control Manager.

4. Execute the report by clicking on the toolbar.

5. The result set will appear in the right side of the screen.

13–3
MD12.doc, printed on 5/2/02, at 4:19 PM

Using the Data Browser!

This screen displays the results of this exercise. The results set for the query shows
that the entities CUSTOMER_2 and CUSTOMER_1 were updated in the parent
model.

After you run a report and generate a results set, you can customize the content
and appearance of the results set. In addition, you can create and save your own
custom report views. Search features allow you to find information in the results set.
You can also print your report.

Buddy Tip—For more information, search the online help index for ModelMart reports.

What's Next

In this chapter, you learned how to use the Data Browser to create and print reports
about the current state of a ModelMart data model, as well as the changes that have
been made to a model. In the next chapter, you'll see how you can control naming and
datatype standards in ModelMart data models.

13–4
 MD12.doc, printed on 5/2/02, at 4:19 PM

14
Chapter

Manage Data Model Standards!

Using Consistent Naming and Datatype Standards!

W
hen multiple individuals or groups are responsible for designing a set of data
models, the enforcement of standards is critical. The ERwin Naming
Standards Editor and the Datatype Standards Editor can help you avoid
problems of inconsistency by facilitating the management of naming conventions and
datatype standards. These features are fully integrated with ModelMart. You can use
them to create or edit your standards files, and save them to ERwin or to ModelMart
libraries.

Naming Standards
Use the Naming Standards Editor to define parts of logical and physical names and
build a glossary of words, abbreviations and alternate abbreviations. This information
is saved in a naming standards file (*.nsm). This file must be attached to each model to
which you want the standards to apply using the Model Naming Options dialog.

Datatype Standards
Use the Datatype Standards Editor to define logical datatypes and map datatypes
between systems. This information is saved in a datatype standards file (*.dsm). Using
the Model Datatype Options dialog, you must attach a datatype standards file to each
model to which you want the standards to apply. If you do not attach a standards file,
default datatype mapping is used.

Working with the Standards Editors

The editors can be opened from within ERwin. To open the Naming Standards Editor,
choose Tools on the ERwin toolbar. Then choose Names, Edit Naming Standards. To
open the Datatype Standards Editor, choose Datatypes from the Tools menu, and
choose Edit Datatype Standards.

14–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Using Consistent Naming and Datatype Standards!

Both editors can also be accessed without opening ERwin, by selecting them on
the Computer Associates AllFusion ERwin Data Modeler programs list. Click Start on
your computer desktop taskbar, and then choose Programs, Computer Associates,
AllFusion, ERwin Data Modeler, ERwin Naming Standards Editor, or ERwin Datatype
Standards Editor:

When you open the Naming Standards Editor or the Datatype Standards Editor
from the programs list, the ModelMart Connection Manager automatically opens,
unless you previously checked the Suppress this Dialog on Startup box on the dialog.
To connect to ModelMart, follow the instructions provided in the chapter “Join the
Workgroup.”
You do not have to be connected to ModelMart to work in the editors. You can
close the ModelMart Connection Manager, and use the editors to create and update
naming and datatype standards files and save them locally. However, you must be
connected to ModelMart in order to save the standards files to ModelMart or to attach
a standards file to a ModelMart model.

14–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Using Consistent Naming and Datatype Standards!

Saving a Standards File to ModelMart

To save a standards file to ModelMart, select Save As on the ModelMart menu to
open the Save ModelMart Model As dialog. Select the library in which you want to
save the file and type in the name of the file in upper left field. Click OK to finish.
Save your naming standards files with an .nsm extension; save your datatype standards
files with a .dsm extension.

Attaching a Standards File to a Model

In order to attach a standards file to a model, you must have the ER1 file or
ModelMart model open.
To attach a naming standards file, open the Tools menu on the ERwin toolbar,
and choose Names. Then select the Model Naming Options dialog. This dialog gives
you the option to attach a naming standards file from ERwin, or attach a file from
ModelMart.
To attach a datatype standards file to a model, select Datatypes from the ERwin
Tools menu, and then select Model Datatype Options. This dialog allows you to attach
a datatype standards file from ERwin, or from ModelMart.
Buddy Tip—For details on creating, using and attaching standards file to models, search
the online help index for Naming Standards, and Datatype mapping.

What's Next
In this chapter, you learned how you can control naming and datatype standards in
ModelMart data models. The next chapter explains the how to synchronize an ERwin
data model in ModelMart and a BPwin business process model in ModelMart.

14–3
 16MM4115.doc, printed on 5/8/02, at 4:43 PM

15
Chapter

Sync Your Data Models and Process Models!

Verifying that Your Data Supports Your Business Processes!

T
he ModelMart Synchronizer is an independent application that you can use to
synchronize an ERwin data model in ModelMart with a BPwin business process
model in ModelMart or vice versa.
The synchronizer enables you to reuse the shared aspects of data and process
modeling, allowing a controlled movement of entity and attribute descriptions between
ERwin and BPwin, in either direction. In business applications, this synchronization
allows you to verify that your business processes are supported by their information
systems.

Opening the ModelMart Synchronizer

You can open the ModelMart Synchronizer by selecting it from the Computer
Associates AllFusion ERwin Data Modeler programs list. Click Start on your computer
desktop taskbar, and then choose Programs, Computer Associates, AllFusion, ERwin
Data Modeler, ModelMart Synchronizer:

If you select the synchronizer from the programs list, the ModelMart Connection
Manager will automatically open. To connect, follow the instruction in the chapter
“Join the Workgroup.”
If you are already connected to ModelMart, you can open the dialog by selecting

BP/ER Synchronizer on the ModelMart menu, or by clicking on the ModelMart

toolbar.

15–1
16MM4115.doc, printed on 5/8/02, at 4:43 PM

Verifying that Your Data Supports Your Business Processes!

Using the Synchronizer

To synchronize a data model and a process model:
1. In the ModelMart Synchronizer dialog, you must choose one of the
following options in the Operation box:
a) Choose Update ERwin Model from BPwin Model to associate
activities, entities, and attributes in a BPwin model with subject
areas, entities, and attributes in a corresponding ERwin model.
b) Choose Update BPwin Model from ERwin Model to associate
entities, and attributes in an ERwin model with entities and
attributes in a corresponding BPwin model.
The sample ModelMart Synchronizer dialog shown next indicates that
the chosen operation will update the target ERwin model with the entity
and attribute descriptions in a the specified BPwin model:

2. In the Model/Diagram to Synchronize box, use the Browse buttons to

select the models you want to synchronize. The fields show the
library\model names that you have chosen.
The sample screen shows that EMOVIES-MM in the ERwin models
library will be updated with the Test model in the BPwin Models library.
3. Click the Sync Now button to run the Synchronizer and update the target
model.

15–2
16MM4115.doc, printed on 5/8/02, at 4:43 PM

Verifying that Your Data Supports Your Business Processes!

NOTE: If you run the Synchronizer with the target model open, you will
need to refresh the model in order to complete the
synchronization. For details, see Refresh in the chapter “Manage
Changes to Models.”

Buddy Tip—For details, search the online help index for ModelMart Synchronizer.

15–3
 MD12.doc, printed on 5/2/02, at 4:19 PM

16
Chapter

Ask Your Buddy!

Ask Your Buddy–Questions and Answers
Where is ModelMart located?
ModelMart resides on a central server, using Sybase, Microsoft SQL Server, Informix,
or Oracle as the host database. ModelMart takes advantage of the host database's
storage mechanisms and stored procedure facilities to provide openness, centralized
services and scalability. Client access leverages the databases' native interfaces to
provide secure, high performance access to ModelMart.

What target databases does ERwin support when coupled with ModelMart?
ERwin supports more than twenty leading SQL and desktop databases, regardless of
whether it is used with ModelMart or not. For example, a ModelMart hosted on an
Oracle database could manage data models for any number of databases, ranging from
Access to DB2.

Is ModelMart simply a multi-user version of ERwin?

Not at all. ModelMart is a separate intelligent server providing model management and
workgroup capabilities to ERwin and BPwin. It promotes collaborative model
development and publishing without sacrificing security or control. ModelMart also
provides extended modeling capabilities in ERwin, including impact analysis,
versioning and model merge.

Is ModelMart a general-purpose repository?

No. ModelMart is designed to provide optimized storage and services for ERwin and
BPwin models.

How does ModelMart promote reuse?

Reusable model objects, such as domains, validation rules, common entities, may be
saved in ModelMart template models. These template models can then be used to
create new models. Templates can also be used to update existing models using the
synchronize feature. In addition, Naming Standards models and Datatype Standards
models may be saved in ModelMart and referenced by any number of data models and
common entities.

16–1
MD12.doc, printed on 5/2/02, at 4:19 PM

Ask Your Buddy–Questions and Answers

How does the conversion process affect model data?

When the ModelMart administrator converts a ModelMart 3.0.2 database to a
ModelMart 4.1 database, ERwin and BPwin models in ModelMart 3.0.2 are converted
to version 4.1 ModelMart models. The converted models are the same as if you
opened the model in the upgraded client and saved the model to ModelMart 4.1.

How are versions in converted databases handled in ModelMart 4.1?

Versioning in ModelMart 4.1 is different than it was in ModelMart 3.0.2. ModelMart
3.0.2 versioning included a parent model and delta versions, which recorded each set
of saved changes. You could also create full versions, which were complete versions of
the model at a specific point in time. ModelMart 4.1 versioning includes a parent
model and versions. A new version is created with each save. Each version is a
complete model at the time of a particular save.
When the ModelMart administrator converts a ModelMart 3.0.2 database to a
ModelMart 4.1 database, each parent model becomes a parent model, each delta
version becomes a version of the parent, and each full version becomes another parent
model that does not have any versions associated with it.

Does the conversion of a ModelMart 3.0.2 database to a ModelMart 4.1

database change the prior library structure?
No. The complete ModelMart 3.0.2 library structure is preserved in ModelMart 4.1.

How are library-level objects handled in ModelMart 4.1?

Library level objects are a thing of the past. In ModelMart 3.0.2, library-level objects
were shared among all models in a library. With the introduction of the source model
in ERwin 4.1, this is no longer necessary. During conversion of your ModelMart 3.0.2
database to a ModelMart 4.1 database, ERwin library-level objects are grouped together
and stored in a separate source model named after the library. The objects can be
maintained in one source model that contains all objects to be shared. If an object is
changed, you can then synchronize this source model with any other model where you
would also like the change to take effect.

How do I add a user to ModelMart?

The ModelMart administrator can simply apply permissions to a current database user.
This will automatically add the user to ModelMart. This simplifies the previous process
of first adding a user, then adding the permissions.

16–2
MD12.doc, printed on 5/2/02, at 4:19 PM

Ask Your Buddy–Questions and Answers

Can I restrict changes to part of a model?

The ModelMart security system is based on customizable security profiles, for
complete control over model updates. Changes by individual modelers can be
restricted at the ModelMart, library, model, and subject area level. For example, a
modeler could be permitted to change the order entry subject area, while being
restricted from updating other parts of the database design.

What additional steps are required to make ModelMart compatible with

BPwin?
None. The installation and initialization process prepares ModelMart for use with both
ERwin and BPwin. No additional steps are needed to make ModelMart compatible with
BPwin.

16–3