Learning Technology FrameWork.pdf

Learning 

Technology 

FrameWork 

Ptech FrameWork 5.4 for Windows

Ptech Inc. 

160 Federal Street 

Boston, MA 02110 

Tel: (617) 443-1170 

Fax: (617) 443-1136 

www.ptechinc.com 

© 1996–1999 Ptech Inc. 

All rights reserved. 

Printed in the USA. 

DFD02-540-0000 

This document describes version 5.4 of Ptech FrameWork for Windows. By receiving 

this document, you agree that: 

● The information in this document is confidential and cannot be copied or 

reproduced without the written consent of Ptech Inc. 

● This document and its contents cannot be used in the manufacture or 

reproduction of the product described, and the delivery of this document does not 

constitute any right or license to do so. 

The software described in this document is furnished under license and can be used or 

copied only in accordance with the terms of that license. Ptech Inc. is not liable for 

errors in this document or for any damages that may occur in connection with using 

this material. The information contained in this document is subject to change without 

notice. 

Restricted rights notice: Use, duplication, or disclosure by the US Government is 

subject to the restrictions set forth in subparagraph (c) (1) (ii) of the Rights in Technical 

Data and Computer Software clause at DFARS 252.227-7013. 

Ptech and the Ptech logo are trademarks of Ptech Inc. CORBA is a registered 

trademark and Interface Definition Language (IDL) and Object Request Broker are 

trademarks Object Management Group, Inc. Forté is a registered trademark of Forté 

Software, Inc. Java is a trademark of Sun Microsystems, Inc. Orbix is a registered 

trademark and OrbixWeb is a trademark of IONA Technologies PLC. Windows is a 

registered trademark of Microsoft Corporation. All other trademarks, trade names, and 

service marks appearing in this document are the property of their respective owners.

About This Book 

Lesson 1: Navigating FrameWork 

Contents 

Welcome! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 

How to use this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 

A note about the illustrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii 

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii 

Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x 

What you’ll learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 

Starting FrameWork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 

Opening a KnowledgeBase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 

Getting ready to explore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 

FrameWork tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 

Clearing the deck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 

Exploring existing folders and windows . . . . . . . . . . . . . . . . . . . .11 

Exiting FrameWork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 

Lesson 2: Creating Your First Use Case Diagram 

What you’ll learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 

Setting the stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 

Setting up your work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 

Opening a new KnowledgeBase for your work . . . . . . . . . . . . . .22 

Organizing your work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 

Creating a folder for your diagrams . . . . . . . . . . . . . . . . . . . .25 

Opening your first modeling window . . . . . . . . . . . . . . . . . . .26 

Contents 

iii

Contents 

iv 

Creating use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 

If you make a mistake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 

Creating composite use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 

Creating actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 

Creating communication relationships . . . . . . . . . . . . . . . . . . . . . . .37 

Creating bidirectional communications . . . . . . . . . . . . . . . . . . . .38 

Creating one-way communications . . . . . . . . . . . . . . . . . . . . . . .39 

Creating subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 

Saving your work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 

Using naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 

Lesson 3: Getting More Specific about Your Hiring System 


Breaking down a composite use case . . . . . . . . . . . . . . . . . . . . . . . .47 

Building an employee acquisition diagram . . . . . . . . . . . . . . . . . . . .50 

Adding actors and communications . . . . . . . . . . . . . . . . . . . . . . . . .53 

Checking spelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 

Lesson 4: Improving the Appearance of Your Diagrams 


Adding annotations to diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 

Formatting text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 

Aligning graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 

Bending connection graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 

Repositioning text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 

Resizing a graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 

Lesson 5: Creating a Java Class Diagram 


Creating the diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 

Creating classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 

Creating an association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 

Relating your first two classes . . . . . . . . . . . . . . . . . . . . . . . . . . .76 

Renaming the association ends . . . . . . . . . . . . . . . . . . . . . . . . .77 

Setting the multiplicity of an association end . . . . . . . . . . . . . . . .79 

Creating inheritance relationships . . . . . . . . . . . . . . . . . . . . . . . . . . .80 

Creating an incomplete partition . . . . . . . . . . . . . . . . . . . . . . . . .81 

Creating a generalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Adding more related classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 

Creating an ordering association . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 

Lesson 6: Adding More Detail to Your Java Classes 


Creating attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 

Creating operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 

Using forms to provide more information . . . . . . . . . . . . . . . . . . . . .98 

Viewing classes using compartment notation . . . . . . . . . . . . . . . . .102 

Lesson 7: Creating a Statechart Diagram 

What you’ll learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 

Creating the diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 

Creating an initial state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 

Creating states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 

Creating transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 

Creating final states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 

Lesson 8: Exploring What You’ve Done 

Lesson 9: Generating Code 

What’s Next? 


Navigating with forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 

Navigating from fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 

Using the form navigation toolbar . . . . . . . . . . . . . . . . . . . . . . .122 

Using queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 

Running reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 


Using the Java Class Information form . . . . . . . . . . . . . . . . . . . . . .134 

Generating code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 

Learning more about FrameWork . . . . . . . . . . . . . . . . . . . . . . . . . .137 

Additional FrameWork features . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 

Contents 

v

Welcome! 


Welcome to Learning Technology FrameWork. This book is a 

tutorial that introduces you to object-oriented application 

development (OOAD) modeling with Ptech Technology or 

Enterprise FrameWork. By doing the exercises in this book, you’ll 

become familiar with the modeling process and the FrameWork 

features that support it. 

To gain the most benefit from this book, you should be familiar with 

your Windows operating system. 

How to use this book 

You should start with Lesson 1 and proceed through the lessons in 

order. The modeling exercises build on each other. By doing the 

exercises in order, you’ll begin to develop a sense of the 

relationships between the models. You’ll learn how all the pieces 

come together to capture process requirements and implement 

them using the latest technology. 


vii

A note about the illustrations 

A note about the illustrations 


viii 

The FrameWork desktop and windows on your screen may differ 

slightly in appearance from the images in this book. The 

differences depend on the FrameWork product you’re using and on 

the environment in which you’re using it. For the purposes of this 

book, these differences are not significant. 

Related documentation 

Information on installing FrameWork for Windows is provided on 

an installation sheet distributed with the installation diskettes. 

Additional information about FrameWork and other Ptech products 

is available in: 

■ Learning Business FrameWork — This book contains a tutorial 

that introduces you to business process modeling with Business 

or Enterprise FrameWork. By doing the exercises in this book, 

you become familiar with the modeling process and the 

FrameWork features that support it. 

■ Using FrameWork — This book contains comprehensive 

information on using Ptech Business, Technology, and 

Enterprise FrameWork to capture your business processes and 

design the applications that support them. In this book, you’ll 

find both conceptual and procedural information on topics 

ranging from basic modeling techniques to sharing 

KnowledgeBase information. 

■ Modeling with Business FrameWork and Modeling with 

Technology FrameWork — These books describe the types of 

models directly supported by Ptech FrameWork. In these 

books, you’ll find information on the semantics and usage of 

each type of model, sample diagrams, and detailed information 

about the modeling tools and forms you use to create and modify 

model components.

Related documentation 

■ Generating C++ Code with FrameWork — This book explains 

how to generate C++ code from models you build using Ptech 

Technology or Enterprise FrameWork. This book also describes 

the C++-specific modeling tools and forms provided with 

FrameWork. 

■ Generating Java Code with FrameWork — This book explains 

how to generate Java code from models you build using Ptech 

Technology or Enterprise FrameWork. This book also describes 

the Java-specific modeling tools and forms provided with 


■ Generating CORBA IDL Code with FrameWork — This book 

explains how to generate Common Object Request Broker 

Architecture (CORBA) Interface Definition Language (IDL) 

code from models you build using Ptech Technology or 

Enterprise FrameWork. This book also describes the CORBAspecific 

modeling tools and forms provided with FrameWork. 

■ Customizing FrameWork — This book provides detailed 

information on using Enterprise FrameWork Professional to 

extend and customize the FrameWork modeling environment to 

meet the needs of your enterprise. Along with instructions for 

creating your own metamodels, diagram types, tool folders, 

queries, forms, and modeling contexts, this book includes an 

integrated set of examples that illustrate a customization 

scenario. 

■ Creating and Customizing ACG Templates — This book 

provides information that enables you to extend the reporting 

and code generation capabilities of the Ptech FrameWork 

products to meet the needs of your enterprise. The ability to 

create and customize Ptech Abstract Code Generator (ACG) 

templates is included only in Enterprise FrameWork 

Professional. 


ix

Customer support 

Customer support 


x 

Ptech offers its customers a variety of support services for 

FrameWork and its add-on products. In addition to the 

documentation and online help provided with the products, you can 

obtain information from the following sources: 

■ Formal training is available for all Ptech products. 

Experienced teachers can provide instruction tailored to your 

needs either at Ptech corporate headquarters or at your 

business site. For more information, please contact your Ptech 

sales representative at (800) 955-9345. 

■ The Ptech World Wide Web site provides access to up-to-date 

information on Ptech Inc. and the FrameWork family of products. 

You can browse the Ptech Web site at http://www.ptechinc.com. 

■ Technical support for Ptech products is available by telephone 

Monday through Friday between 9:00 a.m. and 6:00 p.m. 

Eastern time. To speak with a member of the Ptech Technical 

Support team, call (617) 443-1170 ext. 403. Alternatively, you 

can fax your questions to Ptech Technical Support at (617) 443- 

1136 or send email to support@ptechinc.com.

Navigating FrameWork 

What you’ll learn 

This lesson contains basic information you’ll use in the lessons that 

follow. In this lesson, you’ll: 

■ Learn how to start FrameWork 

■ Explore existing folders and diagrams 

■ Learn how to exit FrameWork 

Starting FrameWork 

FrameWork installation This book assumes that Ptech Technology FrameWork or 

Enterprise FrameWork is already installed on your PC. 

Note If Technology or Enterprise FrameWork has not yet been 

installed on your PC, see either the FrameWork installation 

instructions or your system administrator for assistance. 

1 

1 


1

Opening a KnowledgeBase 

What you do To start FrameWork: 


2 

Double-click on the FrameWork icon on your windows desktop. 


The FrameWork application 

window 

When FrameWork starts, the application opens like this:


The KnowledgeBase After you start FrameWork, you need to open the KnowledgeBase 

you want to use. A KnowledgeBase is a repository in which 

FrameWork stores objects, their interrelationships, and the rules 

and constraints that govern their creation and manipulation. 

You’ll open a KnowledgeBase that contains some sample models. 

This KnowledgeBase is stored in a file named DemoExample.pkb. 

What you do To open the DemoExample KnowledgeBase: 

1 On the File menu, select Open KnowledgeBase. 


3



4 

2 In the Open KnowledgeBase dialog box, open the Kbs 

subdirectory of the FrameWork installation directory if it’s not 

open already. Then select the DemoExample.pkb file and press 

the Open button.

Project Organizer 


When the KnowledgeBase opens, FrameWork looks something like 

this: 

Document 

Project Workspace 

Output Window 

Note 

Depending on the version of FrameWork you’re using, you 

may not see the Welcome Window displayed in the Project 

Workspace. 


5

Getting ready to explore 

Getting ready to explore 


6 

The FrameWork desktop features a user interface that makes it 

easy to manage your modeling projects. The display area of the 

desktop contains separate, dockable windows that present different 

types of information: 

■ The main window in the display area is your Project 

Workspace. This is the space in which you do your actual 

modeling work. The Project Workspace is the only window you 

cannot move. 

■ The window on the left is your Project Organizer. This 

window contains folders and modeling windows in tree 

structures called folder views. You use the folder view on the 

User page of the Project Organizer to organize your modeling 

work. The Base page shows the folders and windows that are 

common to all KnowledgeBases. 

■ The window at the bottom left is the Document window. In 

this window, you can enter textual information about 

FrameWork objects. 

■ The window at the bottom right is the Output window. 

FrameWork uses this window to display processing messages. 

You’ll see other types of windows on the FrameWork desktop as you 

continue with the lessons in this book.

FrameWork tour 


To become familiar with some FrameWork basics, you’ll take a 

quick tour of an example contained in the Demo Example folder. 

To begin: 

1 On the File menu, select Close to close the Welcome Window (if 

it’s open). 

2 On the User page of the Project Organizer window, double-click 

on the Demo Example folder to open it. 

The Demo Example folder contains groups of diagrams 

representing structures and processes involved in the 

operations of a fictional company named SuccessTech. 


7



8 

3 In the Demo Example folder, double-click on Road Map. 

FrameWork opens the Road Map window. 

The Road Map window presents a conceptual organization of 

the diagrams in the Demo Example.

Clearing the deck 

Freeing up screen real 

estate 


As you can see, space is at a premium on your desktop. You 

probably can’t see as much as you’d like of the SuccessTech Road 

Map window. You’ll want to free up as much screen real estate as 

you can. This will maximize the area available to you for viewing 

diagrams in the Demo Example. 

Freeing up space simply means moving some toolbars and closing 

some of the windows that you don’t need at this particular moment. 

Think of it as simply tucking things away. They’re still there to 

help you when you need them. Meanwhile, the space you gain 

increases the area available in the Project Workspace. 

What you do To give yourself more space for exploring FrameWork: 

1 Open the View menu. Checkmarks next to the menu options 

indicate which FrameWork desktop elements are currently 

open. 

2 Click on the Output option to deselect it. 

FrameWork closes the Output window. 


9



10 

3 Using the same procedure, close the Document window. With 

these windows closed and with FrameWork maximized, you 

should have enough room to look at the models in the example. 

Moving toolbars You can also free up space on the FrameWork desktop by moving 

toolbars (including the menu bar). You can change the location of a 

toolbar within the toolbar area. Alternatively, you can dock the 

toolbar elsewhere on the desktop or leave it floating. Docking a 

toolbar means setting it in place in the toolbar area or along an 

edge of a window frame on the FrameWork desktop. A toolbar is 

floating when it isn’t docked. 

What you do To move a toolbar: 

1 Click and hold anywhere on the toolbar background. 

Alternatively, if the toolbar is floating, you can click and hold in 

the toolbar title bar. 

Docked 

Floating 

2 Drag the toolbar to a new location and release the mouse 

button. If the toolbar is in the toolbar area or next to a window 

frame, FrameWork docks it automatically. 

Tip 

To dock a floating toolbar in the toolbar area, double-click in 

its title bar.

Exploring existing folders and windows 


Now that you’ve cleared the decks and learned a little about 

manipulating the FrameWork desktop along the way, you’re ready 

to do a little exploring: 

1 In the Road Map window, double-click on the background of the 

Sales Use Case box located under USE CASE, STATECHART, 

& SEQUENCE DIAGRAMS. 

Tip 

If FrameWork opens an edit box for the Sales Use Case 

text, click outside the edit box to close it. Then try doubleclicking 

again on the background of the Sales Use Case box. 

FrameWork opens the Sales Use Case window. 


11



12 

This window contains a use case diagram, which shows the 

types of interactions that can occur between a system and users 

of the system. Within a use case diagram, interactions are 

represented nonsequentially, placing the focus on their 

structure rather than their behavior. This focus enables the 

diagram to present a clear view of the requirements of an 

existing or proposed system. 

You’ll build your own use case diagrams in Lesson 2, “Creating 

Your First Use Case Diagram,” and Lesson 3, “Getting More 

Specific about Your Hiring System.” 

2 Double-click on the Qualify Lead graphic. 

FrameWork opens the Qualify Lead Use Case window.


This is another use case diagram. It shows the details of the 

Qualify Lead composite use case. A composite use case is a 

use case that incorporates one or more other systems. 

3 Double-click on the Order Statechart graphic. 

FrameWork opens the Order Statechart window. 

This window contains a statechart diagram, which shows the 

changes an object undergoes during its life. An object changes 

from one state to another in response to internal or external 

events. The object in this statechart diagram is a sales order. 

You’ll create a statechart diagram in Lesson 7, “Creating a 

Statechart Diagram.” 


13



14 

4 In the Project Organizer window, double-click on the Business 

Objects folder to open it. 

5 In the Business Objects folder, double-click on Order Business 

Objects. 

FrameWork opens the Order Business Objects window.


This a class diagram that presents a static view of the objects 

involved in ordering products. A class diagram lets you describe 

information by defining types of objects, their properties and 

relationships to each other, and the operations that can be 

performed on them. 

You’ll build a special kind of class diagram in Lesson 5, 

“Creating a Java Class Diagram.” 


15



16 

6 In the Order Business Objects window, double-click on the 

Compute Total Weight graphic. 

FrameWork opens the Compute Total Weight window. 

This window contains an operation diagram, which describes 

the interface of an operation defined in a class model. An 

operation diagram shows what class of objects an operation 

applies to and what class of objects it returns. It can also show 

methods and arguments for the operation. 

7 In the standard toolbar, click on the Go Back tool. 

FrameWork makes the Order Business Objects window active 

again. This is the last window you opened before the Compute 

Total Weight window.


8 In the Order Business Objects window, double-click in the 

Order Distribution graphic. 

FrameWork opens the Order Distribution window. 

This is a distributed class diagram. It shows the objects that 

make up both sides of a client/server computing environment, 

including interface classes and their corresponding 

implementations. 


17



18 

9 In the standard toolbar, click on the History tool. 

FrameWork opens the navigation history list. The checkmark 

indicates which window is currently active. 

10 In the navigation history list, select Road Map. 

FrameWork makes the Road Map window active again. 

11 Continue exploring on your own. For example, you can view 

other diagrams by double-clicking on the boxes in the Road Map 

window or on graphics in those diagrams. 

Tip 

An enclosed plus sign ( ) at the bottom left corner of a 

graphic indicates that double-clicking will open another 

window. 

Alternatively, you can open additional windows from the Project 

Organizer. As you can see, there are many other folders in the 

folder view. Open some of them up. Look around. 

12 When you’re done exploring, select Close All on the Window 

menu.

Exiting FrameWork 

Exiting FrameWork 

Exiting FrameWork ends your current working session. 

FrameWork always gives you the opportunity to save your work 

and the organization of your desktop when exiting. However, 

because all you’ve been doing up to this point is exploring, there’s 

no need to save your work now. 

To exit FrameWork: 

1 On the File menu, select Exit. 

2 In the message box that FrameWork displays, press the No 

button. 


19

2 

Creating Your First Use 

Case Diagram 


In this lesson, you’ll create your first use case diagram. In the 

process, you’ll learn how to: 

■ Set up and organize your work 

■ Open a new modeling window 

■ Use a modeling tool folder 

■ Create a use case diagram 

■ Save your work 

Setting the stage 

■ Use naming conventions 

2 

Modeling a hiring system The diagrams you’ll build in this tutorial are based on a hiring 

system. That is, they are based on the objects and operations 

involved in recruiting, interviewing, testing, hiring, and training a 

steady flow of qualified employees. 


21

Setting up your work area 

UML compliance The diagrams you’ll create are fully compliant with the Object 

Management Group (OMG) Unified Modeling Language (UML) 1.1 

suggested standard. Technology and Enterprise FrameWork 

support all UML diagram types (including activity, collaboration, 

sequence, and instance interaction diagrams), although only a few 

are featured in this tutorial. 

Levels of modeling detail You’ll begin with a use case diagram that will represent the higherlevel 

usage scenarios for your hiring system and will serve to define 

the scope of the modeling project. This high-level diagram will 

describe the types of interactions that can occur between the hiring 

system and users of the system. In Lesson 3, “Getting More 

Specific about Your Hiring System,” you’ll model lower-level 

scenarios that provide more detail. 


22 

The basic components of a use case diagram are actors and use 

cases and the communications that occur between them. You’ll 

learn about these one at a time as you build your first use case 

diagram. 

Setting up your work area 

Before you begin modeling, you need to open a new KnowledgeBase 

in which you can save your work. A KnowledgeBase stores not only 

the models you build, but also the rules and constraints that govern 

their design. All the work you do in FrameWork is stored in a 

KnowledgeBase. 

You’ll also want to take care of some housekeeping details to create 

sufficient space in which to work. 

Opening a new KnowledgeBase for your work 

To open a new KnowledgeBase: 

1 Start FrameWork if you haven’t already done so.

2 On the File menu, select New. 

Opening a new KnowledgeBase for your work 

3 In the Name field in the New dialog box, type a name for the 

new KnowledgeBase. For example, type LearningTechnologyFW. 

Then press the OK button. 


23

Organizing your work 



24 

When the new KnowledgeBase opens, the FrameWork desktop 

looks like this: 

As you can see, the FrameWork desktop looks much the same as it 

did when you opened the DemoExample KnowledgeBase in Lesson 

1. However, you’ll notice that the User folder view in the Project 

Organizer window now contains only the Workspace Items folder 

and the Recycle Bin subfolder. 

Your work is best organized by creating folders in which you store 

your diagrams and, possibly, other folders. As with anything else, a 

little planning and a little discipline will help you get and stay


organized. This discipline will serve you well when you’re fully 

engaged in more extensive modeling projects. 

To illustrate this and set the pattern for your modeling efforts, 

you’ll create a folder in which you’ll store all the diagrams you 

create in this tutorial. 

Creating a folder for your diagrams 

Organizing diagrams 

visually 

FrameWork displays folders in a tree view to make it easier for you 

to visually organize and maintain your diagrams. When you 

expand a folder in the tree, FrameWork lists the windows and 

folders it contains. When you create a new FrameWork window, 

FrameWork places it in the currently selected folder or in the same 

folder as the currently selected window in the Project Organizer. 

What you do To create a folder for the diagrams you’ll build in this tutorial: 

1 In the folder view in the Project Organizer, place your cursor on 

the Workspace Items folder and click right. 

2 On the popup menu, select New Folder. 

FrameWork creates a folder named New Folder and puts the 

folder name in edit mode, giving you the opportunity to rename 

it. 


25



26 

3 Type Learning FrameWork as the new name for the folder. Then 

press Enter to close the edit box. 

The Project Organizer should now look like this: 

You’re now ready to open your first modeling window. 

Opening your first modeling window 

Use case modeling window 

and tools 

Now you’ll open a modeling window to build a use case diagram. 

You’ll use the modeling tools in the Use Case Diagram Tools tool 

folder. 

What you do To open a modeling window for your use case diagram: 

1 On the File menu, select Close to close the Welcome Window (if 

it’s open). 

2 Make sure your Learning FrameWork folder is highlighted in 

the folder view.

3 On the File menu, select New. 


FrameWork displays the New dialog box. The list on the left 

shows the types of diagrams you can build. 

Tip 

You can get detailed information about any FrameWork 

dialog box by pressing the Help button in it. 

4 In the New dialog box: 

a In the list of diagram types, select UML Use Case. 

b In the Name field, type a name for the use case diagram. 

Call it Employee Hiring System. 

c Press the OK button. 


27



28 

FrameWork opens the modeling window and places it in your 

Learning FrameWork folder. 

Note 

If your Learning FrameWork folder was highlighted as 

described in step 1, the new diagram is properly placed within 

it. If the diagram isn’t there, find it in the folder view and drag 

it to the Learning FrameWork folder.


5 In the standard toolbar, click on the Show Tool Folders button. 

FrameWork opens the Use Case Diagram Tools tool folder. 

Your desktop should now look something like this: 


29



30 

6 To create more space in which to work: 

● Close the Output and Document windows (if they’re open), 

as described in Lesson 1, “Navigating FrameWork.” Also 

close any open toolbars except the standard and common 

toolbars. To close a toolbar: 

1 Click right on any open toolbar. 

2 In the popup menu, click on the toolbar to deselect it. 

● Drag the split bar between the Project Organizer and the 

Project Workspace to give yourself even more space in which 

to work. Do the same with the split bar between the Project 

Workspace and the Tool Folder window. 

A note about tool folders Each FrameWork diagram type is associated with one or more tool 

folders. When the Show Tool Folders button is pressed in, 

FrameWork automatically opens the tool folders associated with 

the diagram in the active window. You can also choose specific tool 

folders to open by selecting them in the folder view, by using the 

Open option on the File menu, or by using the Open Tool Folder 

button in the standard toolbar.

Creating use cases 

Creating use cases 

Note The common toolbar also contains modeling tools. You’ll 

learn about these tools in Lesson 5, “Creating a Java Class 

Diagram,” and Lesson 6, “Adding More Detail to Your Java 

Classes.” 

Your first use case Now that you’ve opened a use case modeling window and the Use 

Case Diagram Tools tool folder and cleared the deck, you’re ready 

to start your diagram. 

Use cases represent types of interactions that can occur between a 

system and its users. You’ll begin the Employee Hiring System use 

case diagram by placing a use case in the modeling window. You’ll 

call this use case Seek Resumes. 

What you do To create the Seek Resumes use case: 

1 In the Use Case Diagram Tools tool folder, click and hold on the 

Use Case tool. 

Tip 

When your cursor moves over a tool, the status bar gives a 

brief description of how to use it. 

2 Move your cursor to roughly the center of the Employee Hiring 

System modeling window and release the mouse button. 

FrameWork creates a new use case in the KnowledgeBase and 

places a graphic for it where you released the mouse button. 

FrameWork also opens an edit box for the use case name. 

3 Type Seek Resumes. Then click on the window background to 

close the edit box. 


31

If you make a mistake 


32 

Your Employee Hiring System diagram should look something 

like this: 

4 Using the procedure in steps 2 through 4, place a use case 

named Screen Resumes below the Seek Resumes use case. Don’t 

worry if your graphics aren’t exactly lined up. You’ll learn how 

to align graphics in Lesson 4, “Improving the Appearance of 

Your Diagrams.” 


Deleting objects If you inadvertently create an object that you don’t want, you can 

delete it. 

What you do To delete an object: 

1 Place your cursor on the object and click right to open its popup 

menu.


2 On the popup menu, select Terminate and then KnowledgeBase 

and Graphics. 

3 In the message box that FrameWork displays, press the Yes 

button. 

What happens When you select Terminate KnowledgeBase and Graphics for an 

object, two things happen: 

■ FrameWork deletes any graphics that represent the object in 

any modeling window. 

■ FrameWork deletes the object itself from the KnowledgeBase. 


33

Creating composite use cases 


34 

If you want to delete only the graphic representation of an object, 

but not the KnowledgeBase object itself, you can use the Graphics 

option on the Terminate submenu. Alternatively, you can use the 

Delete key on your keyboard or the Delete Graphics option on the 

Edit menu. 

Tip 

If you accidentally delete an object you want to keep, select 

Undo on the Edit menu to recreate it. Alternatively, if you’ve 

deleted only the graphic, you can recreate it by holding down the 

Control key while you use the tool with which you originally 

created the object. 

Creating composite use cases 

Use cases that contain 

other systems 

Composite use cases are use cases that incorporate one or more 

additional systems. In your Employee Hiring System use case 

diagram, you’ll include a composite use case representing a 

subsystem within the Employee Hiring system. In Lesson 3, 

“Getting More Specific about Your Hiring System,” you’ll create a 

second use case diagram to show the details of this composite use 

case. 

What you do To create a composite use case: 


Composite Use Case tool. 

2 Move your cursor below the Screen Resumes use case and release 

the mouse button to create the new composite use case graphic. 

3 Call your composite use case Hire Employees. Type this name 

and then click on the window background to close the edit box.

Creating actors 


You now have a composite use case to go with the two use cases. 

Users of a system Actors represent roles in which people, jobs, organizations, or 

other systems interact with one or more use cases. They represent 

the users of a system. 

What you do To create the actors: 

You’ll continue the creation of the Employee Hiring System 

diagram by adding four actors to the diagram. 


Actor tool. 

2 Move your cursor to the top left portion of the modeling window 

and release the mouse button to create the new actor graphic. 


35



36 

3 Call your actor HR Representative. Type this name and then 

click on the window background to close the edit box. 

You now have an actor to go with the use cases. 

You’ll create three more actors to expand your Employee Hiring 

System diagram. 

4 Using the procedure in steps 1 through 3, place an actor named 

Department Head in the bottom left portion of the window, an 

actor named Employee Recruitment Agency in the top right 

portion, and an actor named Candidate in the bottom right 

portion.

Creating communication relationships 

When finished, you should have a diagram that looks something 

like this: 

Creating communication relationships 

Communications establish relationships between actors and use 

cases. A communication can be: 

■ A bidirectional communication, in which messages flow both 

ways between the actor and the use case 

■ A communication from the actor to the use case 

■ A communication from the use case to the actor 

Now that you’ve created use cases and actors, you’ll want to show 

the communication relationships that exist between them. You’ll 

begin with bidirectional communications. 


37

Creating bidirectional communications 

Creating bidirectional communications 

What you do To create bidirectional communications: 


38 


Bidirectional Communication tool. 

2 Move your cursor to the HR Representative actor and release the 

mouse button. Then click on the Seek Resumes use case. 

3 Using the procedure in steps 1 and 2, create a bidirectional 

communication between the HR Representative actor and the 

Hire Employees use case. Then create two more bidirectional 

communications between the Hire Employees use case and the 

Department Head and Candidate actors. 

Your diagram should now look something like this:

Creating one-way communications 


The next step is to create communications that go in one direction. 

To do this: 


Communication from Actor tool. 

2 Move your cursor to the Employment Recruitment Agency actor 

and release the mouse button. Then click on the Seek Resumes 

use case. 

Your diagram should look like this: 


39



40 


Communication from Use Case tool. 

4 Move your cursor to the Screen Resumes use case and release the 

mouse button. Then click on the HR Representative actor. 

5 Repeat steps 3 and 4 to create a one-way communication from 

the Screen Resumes use case to the Department Head actor. 

Your Employee Hiring System use case diagram should now look 

something like this:

Creating subsystems 


Grouping use cases A subsystem represents an integrated group of processes and/or 

resources that, as a whole, serves some purpose within the 

enterprise. The use cases you’ve created belong to the Employee 

Hiring subsystem. You’ll show that now in your diagram. 

What you do To create a subsystem: 

1 If you don’t have enough room to add a graphic above the Seek 

Resumes graphic, do this: 

a On the Edit menu, select Select All. 

b Click and hold on any of the selected graphics. Then drag 

the graphics down to create more space at the top of the 

window. 

c Click on the window background to deselect the graphics. 


Subsystem tool. 

3 Move your cursor above the Seek Resumes use case and release 

the mouse button to create the new subsystem graphic. 

4 Name the subsystem Employee Hiring. 


41



42 

Your diagram should look something like this: 

Once you’ve created the Employee Hiring subsystem, the next 

step is to connect it to the use cases it contains. 


Subsystem Use Cases tool.


6 Move your cursor to a position above and to the left of the Seek 

Resumes use case and release the mouse button. Your cursor 

will change to indicate that you can draw a bounding box. 

7 While holding down the mouse button, drag a bounding box 

around the Seek Resumes, Screen Resumes, and Hire Employees 

use cases. Then release the mouse button. 

Your cursor will change to indicate that you can select an object. 

8 Click on the Employee Hiring subsystem. 

FrameWork draws the bounding box and connects it to the 

Employee Hiring subsystem. 

Tip 

If you cannot see the bounding box: 

a Move your cursor around slowly over the area where the 

bounding box should be until you see the box highlighted. 

b With the bounding box highlighted, click right to open its 

popup menu and select Graphic Properties. 

c In the Graphic Properties dialog box, change the value in 

the Pen Width field to 2. Then press the OK button. 


43

Saving your work 

Saving your work 


44 

You have now completed your Employee Hiring System use case 

diagram. It should look something like this: 

Tip 

To close the Use Case Diagram Tools tool folder, click again on 

the Show Tool Folders button in the standard toolbar. 

The KnowledgeBase file Now that you’ve completed your first diagram, you should save 

your work. When you save, FrameWork writes your 

KnowledgeBase to a file with the extension .pkb. The filename is 

the name you gave the KnowledgeBase when you created it in 

“Opening a new KnowledgeBase for your work” earlier in this 

lesson.

What you do To save your work: 

On the File menu, select Save KnowledgeBase. 

Tip 

Using naming conventions 

It’s good modeling discipline to save your work frequently. 

Using naming conventions 

Use case names Observing a few naming conventions will help keep your models 

consistent. Use cases are generally named with a verb phrase and 

a plural noun. For example, Hire Employees is a verb phrase. Use 

initial capital letters on the words. 

Actor names Actors are named with a singular noun phrase. For example, HR 

Representative is a singular noun phrase. Use initial capital letters 

on the words. 


45

3 

Getting More Specific 

about Your Hiring System 


In this lesson, you’ll get a little more specific about your use case 

diagram. You’ll learn how to: 

■ Show more detail about your composite use case by building a 

lower-level use case diagram 

■ Create a subdiagram 

■ Create graphic references to windows 

■ Check spelling in modeling windows 

Breaking down a composite use case 

From the general to the 

more specific 

3 

When modeling a business system or application, you often start 

with the more general components and then specify more detail. 

The use case diagram you built in Lesson 2, “Creating Your First 

Use Case Diagram,” describes the big picture of a system and is 

fairly simple and straightforward. The composite use case 

contained in the diagram, however, indicates the presence of a 

second system that serves as a component of the first. 


47


You can use additional diagrams to represent the components of a 

diagram in more detail. To illustrate this, you’ll break down the 

Hire Employees composite use case you created in Lesson 2 to 

provide more detail about it. 

What you do To break down the Hire Employees composite use case: 

1 Open the Employee Hiring System use case diagram if it’s not 

open already. 


48 

Tip 

If the Employee Hiring System diagram is open but not 

visible, simply click on its tab at the bottom of the Project 

Workspace to make it active. 

2 Make sure your Learning FrameWork folder is highlighted in 

the folder view. 

3 Place your cursor on the Hire Employees composite use case and 

click right to open its popup menu. 

4 On the popup menu, select New Subdiagram and then More. 

FrameWork displays the New dialog box.

5 In the New dialog box: 


a In the list of diagram types, select UML Use Case. 

b In the name field, type a name for the use case diagram in 

the Diagram Name field. Call it Employee Acquisition 

Subsystem. 

c Press the OK button. 

FrameWork opens a window for the new diagram and adds the 

window to your Learning FrameWork folder. 

Subdiagrams A diagram that shows the details of an object in another diagram is 

called a subdiagram. In this exercise, you opened a new modeling 

window to create a subdiagram of the Hire Employees use case. 

You’ll build this diagram in just a minute. Before you do that, 

however, make the Employee Hiring System window active again. 

Notice that FrameWork has marked the Hire Employees use case 

with an enclosed plus sign ( ). This symbol indicates that the use 

case has a subdiagram. 

Navigating to a subdiagram You can navigate from an object to its subdiagram by doubleclicking 

on the object or by selecting the diagram from the 

Subdiagrams submenu of the popup menu for the object. Doubleclick 

on the Hire Employees use case now to return to the Employee 

Acquisition Subsystem window. 


49

Building an employee acquisition diagram 


How to proceed Now that you’ve created the subdiagram window, consider how to 

proceed. You need to model just how a system that addresses the 

acquisition of employees might look. Some basic use cases in this 

diagram might be interviewing candidates, testing applicants, 

making job offers, and orienting new hires. Some of the actors 

might be the HR representative, the department head, the trainer, 

and the candidate. 

The principles you’ll use are the same as those you exercised when 

you created the higher-level Employee Hiring System diagram. 

That is, a subsystem contains use cases that represent the ways in 

which users, represented as actors, interact with the subsystem. 

What you do To build your second use case diagram: 

1 Open the Employee Acquisition Subsystem window if it’s not 

open already. 

2 If the Show Tool Folders button ( ) in the standard toolbar is 

not pressed in, click on it to open the Use Case Diagram Tools 

tool folder. 

3 Using the Use Case tool, create four use cases in the window 

and name them Interview Candidates, Test Candidates, Make Job 

Offer, and Orient New Hires. 


50



4 Using the Subsystem tool, create a subsystem named Employe 

Aquisition. Note that both words in this name are misspelled. 

You’ll learn how to find and correct these errors with the 

FrameWork spell checker later in this lesson. 


Subsystem Use Cases tool. 


51


6 Move your cursor to a position above and to the left of the 

Interview Candidates use case and release the mouse button. 

Your cursor will change to indicate that you can draw a 

bounding box. 

7 While holding down the mouse button, drag a bounding box 

around the four use cases. Then release the mouse button. 

8 Click on the Employe Aquisition subsystem. 

Your diagram should now look something like this: 


52

Adding actors and communications 


Copying and pasting actors Your Employee Acquisition Subsystem use case diagram will use 

three of the actors you created in your Employee Hiring System 

diagram: HR Representative, Department Head, and Candidate. You 

can copy these actors from one diagram to the other. 

What you do To copy actors from the Employee Hiring System diagram to the 

Employee Acquisition Subsystem diagram: 

1 Open the Employee Hiring System use case diagram if it’s not 

open already. 

2 Select the HR Representative actor. 

3 While holding down the Shift key, select the Department Head 

actor and then the Candidate actor. 

4 On the Edit menu, select Copy. 

5 Make the Employee Acquisition Subsystem window active. 

6 On the Edit menu, select Paste. 

FrameWork places copies of the three actor graphics in the 

Employee Acquisition Subsystem window. 

7 Click on the window background to deselect the actors. 

8 Click and hold on the Candidate actor. Then drag it up to the 

level of the HR Representative actor and release the mouse 

button. 


53


Your Employee Acquisition Subsystem diagram should now look 

something like this: 


54


Try it yourself Think about any other actors you need to represent in this 

Employee Acquisition Subsystem use case diagram. Also, think 

about how all the actors interact with the system consisting of the 

four use cases you’ve created already. Using what you’ve learned so 

far, try to model these actors and relationships yourself. 

The Employee Acquisition Subsystem diagram you develop could 

look something like this: 


55

Checking spelling 


Correcting your spelling 

errors 

FrameWork makes it easy for you to find and correct spelling errors 

in your modeling windows. To see how this works, you’ll now 

correct the spelling errors you made in the Employee Acquisition 

Subsystem diagram. 

What you do To find and correct these spelling errors: 

1 Open the Employee Acquisition Subsystem window if it’s not 

open already. 

2 On the Tools menu, select Spelling. 


56 

FrameWork begins to check the spelling of all the text that 

appears in the Employee Acquisition Subsystem window. When 

FrameWork encounters the first error, it displays the Check 

Spelling dialog box. The Not in Dictionary field shows the 

misspelled word. The field at the bottom of the dialog box 

shows the full text in which the error occurs.

3 In the Check Spelling dialog box: 


a In the Suggestions field, select Employee. FrameWork 

displays this word in the Change To field. 

b Press the Change button. 

FrameWork replaces Employe with Employee in the text at the 

bottom of the dialog box and shows you the next spelling error 

in the Not in Dictionary field. 

4 Press the Change button to replace Aquisition with Acquisition, 

which appears by default in the Change To field. 


57



58 

Because this is the last error it can find, FrameWork 

automatically closes the Check Spelling dialog box and applies 

your corrections to the text in the modeling window. Your 

finished Employee Acquisition Subsystem diagram should now 


Tip 

If you haven’t already done so, now would be a good time to 

save your work.

4 

Improving the Appearance 

of Your Diagrams 


Now that you’ve successfully built your first two diagrams, you’ll 

learn some techniques for improving their appearance. After 

completing this lesson, you’ll be able to use this information to 

enhance the appearance of your diagrams as you build them. 

In this lesson, you’ll find information on: 

■ Annotating diagrams 

■ Formatting text 

■ Aligning graphic objects 

■ Bending connection graphics 

■ Repositioning text 

■ Resizing graphic objects 

4 

You’ll practice the techniques in this lesson by making changes to 

the appearance of your Employee Hiring System diagram. This is 

the diagram you built in Lesson 2, “Creating Your First Use Case 

Diagram.” 


59

Adding annotations to diagrams 


Uses of annotations Annotations are freestanding text that you add to diagrams. You 

can use annotations to clarify concepts, provide instructions, add 

detail, or for any other purpose you choose. You’ll start this lesson 

by adding an annotation to your Employee Hiring System diagram. 

What you do To add an annotation to the Employee Hiring System diagram: 

1 Open the Employee Hiring System diagram if it’s not open 

already. 

2 In the common toolbar, select the Text tool. 

3 In the Employee Hiring System window, click on the window 

background near the HR Representative actor. 


60 

FrameWork places an anchor for the text in the window and 

opens an edit box. 

4 Type First to screen resumes. Then click on the window 

background to close the edit box. 

5 Drag the text to position it next to the actor.



Deleting freestanding text If you decide you don’t want the annotation in your diagram, you 

can delete it. FrameWork treats freestanding text as a graphic 

only, without a corresponding object in the KnowledgeBase. This 

means that to remove it, you need to delete only the graphic. To do 

this: 

1 Select the text you want to delete. 

2 On the Edit menu, select Delete Graphics. 

Tip 

FrameWork deletes the text. 

You can also use the Delete key to delete graphics. 


61

Formatting text 


Font changes FrameWork lets you format text by changing various aspects of the 

font it uses. You can format both freestanding text and text 

associated with graphic objects in your diagrams. In this exercise, 

you’ll format all the text in the Employee Hiring System diagram. 

What you do To format text in the Employee Hiring System diagram: 

1 Open the Employee Hiring System diagram if it’s not open 

already. 

2 On the Edit menu, select Select All. 


62 

FrameWork places selection handles on each graphic in the 

diagram. 

3 On the Format menu, select Text. 

FrameWork displays the Font dialog box.


4 In the Font dialog box, change one or more of the font, style, 

size, effects, and color options. The Sample field lets you 

preview the changes you make. 

5 Press the OK button to close the Font dialog box and apply the 

changes to the text in your diagram. 

If, for example, you selected Bold Italic as the font style, your 

diagram would now look something like this: 

Setting text defaults You can change the default settings for the text in all the diagrams 

you’ll create. Changing default settings has no effect on the 

diagrams you’ve already built. It affects only those you build later. 


63

Aligning graphic objects 

To change the default settings for text: 

1 Click on the background of the Employee Hiring System 

window to ensure that nothing is selected. 

2 On the Format menu, select Text. 

3 In the Font dialog box, make the changes you want. Then press 

the OK button. 


64 

FrameWork changes the default settings. The new settings will 

remain in effect until you change them again. 


Ways to align objects Your diagrams will be easier to read and understand if the graphic 

objects in them are aligned with each other. You can align objects 

by positioning them either with respect to each other or with 

respect to a grid. You’ll practice both ways, but first you’ll learn 

how to select multiple objects. 

Selecting multiple objects To select multiple objects: 

1 In the common toolbar, select the Select tool if it’s not selected 

already.

Aligning objects with 

respect to each other 

2 Do either of the following: 


● Click and hold on the window background near one of the 

objects you want to select. Then drag a bounding box 

around all the objects you want and release the mouse 

button. 

Note 

Depending on your operating environment, you may 

not see the bounding box while you’re dragging. 

FrameWork highlights the objects within the boundaries of 

the box, however, so you’ll be able to tell which objects you’re 

selecting. 

● Select one of the objects you want. Then hold down the Shift 

key and select each of the other objects. 

In the Employee Hiring System diagram, you’ll align the HR 

Representative actor with the Department Head actor. To do this: 

1 In the Employee Hiring System diagram, select the HR 

Representative actor and the Department Head actor. 

2 On the Format menu, select Icon Alignment and then Center. 

FrameWork aligns the center of the first graphic you selected 

with center of the second. 


65


Aligning objects with 

respect to a grid 

You can display a grid to help you arrange the graphic objects in a 

window. You can use the grid as a visual aid for positioning objects 

yourself, or you can have objects automatically align with the grid. 

To use the grid to align the Seek Resumes, Screen Resumes, and Hire 

Employees use cases: 

1 With the Employee Hiring System window active, select Show 

Grid on the View menu. 

FrameWork displays the grid. 


66

Aligning objects to the grid 

by default 

Bending connection graphics 

2 Select the Seek Resumes, Screen Resumes, and Hire Employees use 

cases. 

3 On the Format menu, select Align to Grid. 

FrameWork aligns the top and left sides of each selected object 

with the nearest grid lines. 

You can have each graphic object you create or move in a window 

align to the grid automatically. By default, this feature is enabled 

for each new diagram you create. To disable this feature for the 

active window (or to turn it back on): 

On the View menu, select Snap to Grid. 


Connections across other 

graphics 

As your diagrams become more complex, the graphics that 

represent connections between objects can sometimes cross over 

other objects and connections. This can make a diagram difficult to 

read. You can solve the problem partially by positioning connected 

objects near each other when possible. You can also address the 

problem by bending the connection graphics. 


67


What you do In this exercise, you’ll bend the connection graphics that represent 

the communications between the Screen Resumes use case and the 

HR Representative and Department Head actors. To do this: 

1 In the Employee Hiring System window, select the connection 

graphic for the communication between the HR Representative 

actor and the Screen Resumes use case. 

2 Click on the line portion of the selected connection. 


68 

FrameWork creates a joint in the line and marks it with a 

selection handle. A joint is a point at which you can bend a line.


3 Click and hold on the joint. Then drag to bend the connection 

graphic the way you want it and release the mouse button. 

4 Repeat steps 1 through 3 to put a second bend in the 

communication between the HR Representative actor and the 

Screen Resumes use case. 

5 Using the same procedure, bend the communication between 

the Department Head actor and the Screen Resumes use case in 

two places. 

When you’re finished, your diagram might look something like this: 


69

Repositioning text 

Repositioning text 

Text positions Another way to enhance the appearance of a diagram is to change 

the placement of the text for certain graphics. One option is to 

reposition the text so that it’s outside the graphic, as it is for the 

actor graphics in your Employee Hiring System diagram. You can 

place text above, below, or to either side of its associated graphic. 

Another option is to position text inside the graphic, as it is for the 

use case and subsystem graphics. 

Note 

By default, FrameWork wraps the text associated with a 

graphic to fit the width of the graphic, regardless of where the text 

is positioned. 

What you do To see how this works, you’ll reposition the text for the Employee 

Hiring subsystem. To do this: 

1 In your Employee Hiring System diagram, select the Employee 

Hiring subsystem. 

2 On the Format menu, select Text Position and then Top. 


70 

FrameWork moves the text above your Employee Hiring 

subsystem graphic.

Resizing a graphic 



Graphic too big? The new placement of the text for the Employee Hiring subsystem 

leaves the graphic appearing too large. You can improve the 

appearance of your diagram by resizing the graphic. 

What you do To make your Employee Hiring graphic smaller: 

1 Select the Employee Hiring graphic. 

2 Place your cursor on any one of the eight selection handles 

located at the corners and sides of the graphic. You’ll see the 

cursor change to a double-ended arrow. 


71


3 While holding down the mouse button, drag the handle until the 

graphic is the size you want. Then release the mouse button. 

4 Click on the window background to deselect the graphic. 

Tip You can also use this technique to change the dimensions of 

freestanding text. 


Don’t forget to save your work. 

Tip 

You can use the Graphic Properties option on the popup menu 

of a graphic object to change its color. You can also assign different 

graphics to your objects. For more information on this, see Using 



72

5 

Creating a Java Class 

Diagram 


In this lesson, you’ll build a Java class diagram. Along the way, 

you’ll learn about: 

■ The structure of Java class diagrams 

■ Associations and the inverse relationships between classes 

■ Association ends and their role names and multiplicity 

■ Inheritance relationships between classes, including incomplete 

partitions and generalizations 

■ Ordering associations, which create relationships between 

objects in the same class 

5 


73

Creating the diagram 


Java class diagrams A Java class diagram presents a static view of the objects on which 

a system acts and the operations that affect them. It contains 

objects that correspond to a range of Java constructs, including 

Java classes, interfaces, and exceptions. 


74 

The Java class diagram is a variation of the UML class diagram 

that has been specialized to facilitate Java code generation. 

FrameWork also provides diagram types for modeling other 

language-specific classes, such as C++ and CORBA IDL. 

In this lesson, you’ll build a simple Java class diagram that defines 

the information requirements of your hiring system. In the next 

lesson, “Adding More Detail to Your Java Classes,” you’ll enhance 

your diagram by adding attributes and operations to your Java 

classes. Then later in Lesson 9, “Generating Code,” you’ll use the 

classes you’ve defined to automatically generate Java code. 

Tip 

Don’t worry if you’re not familiar with Java. You can still do 

this lesson, and the techniques you learn will apply to your own 

development environment as well. 

What you do To create a Java class diagram: 

1 With your Learning FrameWork folder highlighted, select New 

on the File menu. 

2 In the New dialog box, select Java Class and name your new 

diagram Employee Hiring Classes. Then press the OK button. 


not pressed in, click on it to open the Java Class Diagram Tools 

tool folder.

Creating classes 

Creating classes 

Classes A class is a category of objects that share some common behavior 

or properties. A Java class is a class whose properties include 

some that are specific to the Java programming language. You’ll 

begin your Java class diagram by creating two Java classes. 

What you do To create Java classes in your Java class diagram: 

1 In the Java Class Diagram Tools tool folder, select the Java 

Class tool. 

2 Move your cursor to the center of the window and release the 

mouse button. 

3 Name the class Person. Then click on the window background 

to close the edit box. 

4 Create another Java class. Name it City. 

At this point, your diagram should look something like this: 


75

Creating an association 

Creating an association 

Associations An association represents a relationship between the objects in 

two classes. It consists of two association ends. These 

association ends define mappings in either direction between the 

two classes. They are inverses of each other. 

Source and target classes Each association end has a source and a target. The source is the 

class from which the association end is mapped. The target is the 

class to which it is mapped. 

Relating your first two classes 

People and cities In your hiring system, a relationship exists between people and the 

cities in which they live. You’ll show this relationship by creating 

an association between the Person and City classes. 

Using modeling tools in 

toolbars 


76 

You use the Association tool in the common toolbar to create 

associations. To use a modeling tool in a toolbar, you first select the 

tool by clicking on it and releasing the mouse button. Then you 

move your cursor into the modeling window and perform the tool 

actions. This is different from using tools in tool folders, which you 

start using by dragging from the tool into the modeling window. 

You can double-click on a modeling tool in a toolbar to keep it active 

for multiple uses. When you’re done with it, click on the Select tool 

( ) to deactivate it. 

What you do To create an association between the Person and City classes in your 

Java class diagram: 

1 In the common toolbar, select the Association tool.

2 Click and hold on the Person class. 

Renaming the association ends 

3 Drag from the Person class to the City class and release the 

mouse button. 

FrameWork draws the connection graphic for the association 

between the Person and City classes and labels each of the 

association ends that define the association. 

Tip When you use the Association tool to create an association 

between two classes, it doesn’t matter which class you start 

from. 


Tip 

If your classes are too close together, the labels for the 

association ends may appear to be reversed. To remedy this, you 

can either move the classes farther apart or move each label closer 

to the target class of its association end. 


Role names When you create an association, the name of each association end 

(called the role name) appears at the target class end of its 

connection graphic. By default, the role name is the same as the 

name of the target class except that it’s all lowercase. 


77



78 

As you can see, the role names of the association ends you created 

do little to describe the relationship that exists between people and 

cities. You’ll want to rename the associations ends to emphasize 

the fact that cities are where people live. 

What you do To rename the association ends: 

1 Click once on the role name city. Then click again to open its 

edit box. 

Tip Even though you’re clicking twice in succession, this is not 

a double-click. Be sure to pause between clicks. Otherwise, 

FrameWork will interpret them as a double-click and display a 

message telling you there is no diagram anchored to the object 

(that is, the object has no subdiagrams). 

2 Rename the association end home city. Then click on the 

window background to close the edit box. 

3 Using the procedure in steps 1 and 2, change the role name of 

the person association end to residents. 

Your diagram should now look like this: 

Tip 

To fit the name of the home city association end on a single 

line, select it and use the selection handles to resize its anchor.

Setting the multiplicity of an association end 

Setting the multiplicity of an association end 

Multiplicity Along with the role name of an association end, FrameWork 

displays its multiplicity. The multiplicity of an association end 

specifies, for a given object in the source class, the minimum and 

maximum number of objects in the target class that the object can 

be connected to. 

When you create an association, the multiplicity of each association 

end is unbounded by default. That means that each object in the 

source class can be connected to any number of objects in the target 

class, including 0 (zero). 

Notation for multiplicity FrameWork shows the multiplicity of an association end after the 

role name. If the minimum and maximum are different, 

FrameWork shows both values, separated by two periods (for 

example, 1..7). If the minimum and maximum are the same, 

FrameWork shows the value only once (for example, 1). 

FrameWork uses an asterisk (*) to represent unbounded 

multiplicity. 

What you do In your Java class diagram, you’ll change the multiplicity of the 

home city association end to indicate that people can reside in at 

most one city. To do this: 

1 Place your cursor on the home city association end and click 

right to open its popup menu. 


79

Creating inheritance relationships 


80 

2 On the popup menu, select Multiplicity and then 0..1. 

Your diagram should now look like this: 

Creating inheritance relationships 

You can define inheritance relationships for classes in a Java 

class diagram. You create these relationships between 

superclasses and subclasses. A subclass inherits all the 

structural and behavioral features of its superclass.

Creating an incomplete partition 

FrameWork supports several types of inheritance relationships. 

You’ll learn about incomplete partitions and generalizations in this 

tutorial. For more information on inheritance relationships, see 

Modeling with Technology FrameWork. 

Creating an incomplete partition 

Incomplete partitions One kind of inheritance relationship is called an incomplete 

partition. An incomplete partition identifies two or more 

mutually exclusive subclasses of a superclass. Each object in the 

superclass may or may not also be in one of the subclasses. 

In your Java class diagram, you’ll create the Applicant and Employee 

Java classes. Then you’ll create an incomplete partition of the 

Person class containing the Applicant and Employee classes. This 

will show that both applicants and employees have the properties 

of people and that a person cannot be both an applicant and an 

employee at the same time. It also shows that there can be people 

who are neither applicants nor employees. 

What you do To create the two Java new classes and the incomplete partition: 

1 Using the Java Class tool, create a class and place it below and 

to the left of Person. Name the class Applicant. 

2 Create another Java class, placing it to the right of Applicant. 

Name the class Employee. 

3 In the common toolbar, select the Incomplete Partition tool. 

4 Click and hold on the window background outside of the 

Applicant class. Then drag a bounding box around Applicant and 

Employee and release the mouse button. 


81

Creating a generalization 


82 

5 Click on the Person class. 

FrameWork draws the incomplete partition and connects it to 

the Person class. 

Your Employee Hiring Classes diagram should look something like 

this: 


Single class inheritance In “Creating an incomplete partition” above, you used an 

incomplete partition to model an inheritance relationship between 

the Person class and two mutually exclusive subclasses, Applicant 

and Employee. Now you’ll model the inheritance relationship 

between your Applicant class and a single subclass. You’ll use the 

subclass to represent applicants that are qualified. 

To model a single subclass, you’ll use a generalization. A 

generalization is an inheritance relationship defined between a 

single superclass and a single subclass.

What you do To create a generalization: 


1 Using the Java Class tool, create a class and name it Qualified 

Candidate. Place the class below the Applicant class. 

2 In the common toolbar, select the Generalization tool. 

3 Drag from Qualified Candidate to Applicant and release the 

mouse button. 

FrameWork draws the generalization between the subclass 

Qualified Candidate and the superclass Applicant. 



83

Adding more related classes 


Expanding your diagram At this point, your Java class diagram requires some additional 

classes in order to present a more complete picture of the objects 

that make up your hiring system. You’ll create a new class named 

State and relate it to the City class. Then you’ll create two new 

classes named Position and Skill and relate them to the Employee 

class. These new classes will play a supporting role in your 

diagram by making the definitions of the City and Employee classes 

more complete. 

Try it yourself The table below describes the associations you’ll create. Using the 

techniques you practiced earlier in this lesson, add the three new 

classes and the associations described below to your Java class 

diagram. 


84 

Related classes Association ends Multiplicity 

State 

City 

Position 

Employee 

Skill 

Employee 

cities 

state 

assigned employees 

position 

employees 

skill set 

0..n 

0..1 

0..n 

1..1 

0..n 

0..n


With these added classes in place, your diagram should look 



85

Creating an ordering association 


Ordering associations An ordering association defines a relationship between objects in 

the same class. It consists of two different association ends that 

together impose an order on objects in the class. 


86 

In your Java class diagram, you’ll create an ordering association on 

the Employee class. You’ll name one association end manager and 

the other direct reports. Then you’ll change the multiplicity to show 

that a manager can have any number of direct reports, but a direct 

report can have no more than one manager. 

What you do To create an ordering association on the Employee class: 

1 Open the popup menu for the Employee class and select 

Duplicate.


FrameWork creates a copy of the graphic for the class and 

places it overlapping the original graphic. 

2 Drag the copy of the Employee class and place it so that there is 

some space between it and the original. 

Tip 

Move the Position class to create space for the ordering 

association you’re about to create. 

3 Using the Association tool, create an association between the 

Employee class and its copy. 

FrameWork names the association ends employee and 

employee1. 

4 On the popup menu for the copy of the Employee class, select 

Terminate and then Graphics. 

FrameWork deletes the copy and the graphic connection 

representing the association you just created. The Employee 

class and the association, however, are still defined in the 


Now you’ll use the Control key with the Association tool to 

recreate the connection graphic. 

5 Select the Association tool. 


87



88 

6 Position your cursor on the Employee class. 

7 While holding down the Control key, drag off and then back 

onto the class. 

8 Release the mouse button and Control key. 

FrameWork displays the Select Association End dialog box. 

Tip 

If you forget to hold down the Control key, FrameWork 

creates a new ordering association. Just terminate the new 

association as described under “If you make a mistake” in 

Lesson 2, “Creating Your First Use Case Diagram,” and try 

again. 

9 In the Select Association End dialog box, double-click on either 

of the association ends for the ordering association (that is, 

employee or employee1). 

FrameWork redraws the connection graphic for the ordering 

association. 

10 Rearrange the graphics in your Employee Hiring Classes 

diagram so that you can see the ordering association clearly. 

For example, move the Position class up in the window and then 

drag the lefthand joints of the ordering association to the right 

side of the Employee class. 

11 Rename one of the association ends manager and the other direct 

reports.


12 Change the multiplicity of the manager association end from 

unbound to 0..1. 

When you’re done, your Java class diagram should look something 

like this: 


89

6 

Adding More Detail to 

Your Java Classes 


In this lesson, you’ll add more detail to the classes in your Java 

class diagram. You’ll learn how to: 

■ Create attributes, which are named, structural components of a 

class 

■ Create operations that can change the state of objects in a class 

■ Use forms to provide more information about attributes 

■ View classes using compartment notation 

6 


91

Creating attributes 


Attributes Attributes are named, structural components of a class. Each 

attribute represents a property that provides more detail about the 

objects in the class. An attribute has a FrameWork type of integer 

or string, depending on which tool you use to create it. 


92 

You’ll now want to provide some details for the Person class in your 

Java class diagram. The Applicant and Employee subclasses will 

inherit these attributes. You’ll want to capture details like home 

phone number, social security number, address, and others. 

What you do To create attributes for the Person class: 

1 Open the Employee Hiring Classes diagram if it’s not open 

already. 

2 In the common toolbar, select the String Attribute tool. 

3 Click and hold on the Person class. Then drag from Person and 

release the mouse button to place the graphic. 

4 Name the attribute home area code. Then click on the window 

background to close the edit box.



Try it yourself You can continue adding attributes for the Person class. Use the 

String Attribute tool for text strings and the Integer Attribute tool 

( ) for numbers. 


93


Adding an attribute to a 

subclass 


94 

When you finish, your Employee Hiring Classes diagram could look 


The Applicant and Employee subclasses inherit all the attributes you 

just added for the Person class. Subclasses can have attributes of 

their own as well. Attributes defined on a subclass do not apply to 

the superclass. That’s because inheritance goes in only one 

direction.

To show that subclasses can have their own attributes: 


Add two attributes to the Employee class — one named employee 

id, the other salary. 



95

Creating operations 


Operations An operation is an action that changes something about an object. 

When you define an operation, you specify the class of objects it can 

affect. This class is called the owner class for the operation. 


96 

In your Java class diagram, you’ll create two operations, one that 

applies to objects in the Applicant class and another that applies to 

objects in the Employee class. 

What you do To create the operations: 

1 In the Java Class Diagram Tools tool folder, click and hold on 

the Operation tool. 

2 Move your cursor onto the Applicant class and release the mouse 

button. Then click where you want to place the operation 

graphic. 

3 Name the operation Screen Applicant. 

4 Using the procedure in steps 1 through 3, create an operation 

for the Employee class named Orient New Hire.


When you’re done, your Employee Hiring Classes diagram should 



97

Using forms to provide more information 


Information on forms A form is a formatted display of information in a window. Each 

form in FrameWork is designed to show information about a 

particular type of object (for example, use cases or classes). The 

rectangular areas in which FrameWork displays information on a 

form are called fields. 

Using the Java Attribute 

Information form 


98 

Forms give you a view of objects that’s different from the views in 

your modeling windows. When you’re interested in one particular 

object, viewing it on a form is an easy way to find out what you 

want to know. You can use forms to both view and modify 

information. You’ll use one now to change the data type of the 

salary attribute you created earlier in this lesson. 

To change the data type of the salary attribute: 

1 In the popup menu for the salary attribute, select View in Form 

and then Java Attribute Information.


FrameWork opens the Java Attribute Information form. Notice 

that the Source Class field shows the class for which the 

attribute is defined. Notice also that the attribute has a default 

type of string. 

2 Click in the Type field. 


99



100 

3 In the form shortcut toolbar at the top of the form, press the 

Remove button. 

FrameWork draws a line through the value in the Type field to 

indicate that it will be removed. 

4 In the form shortcut toolbar, press the Apply button. 

FrameWork removes string as the data type assigned to the 

salary attribute.


5 Click again in the Type field. Then click on the arrow on the 

right to open a list of Java data types. 

6 In the list of data types, select float. 

7 In the form shortcut toolbar, press the Apply button. 

8 On the File menu, select Close to close the form. 


101

Viewing classes using compartment notation 

Viewing classes using compartment 

notation 

Ways to show classes FrameWork provides two alternative notations for classes. Box 

notation, which you’ve been using to build your Java class 

diagram, displays a class as a box with the class name. The other 

notation, called compartment notation, shows a class as a set of 

three compartments and complies with the OMG UML 1.1 

suggested standard. 

Compartment notation When you view a class in compartment notation: 


102 

■ The top compartment shows the class name, which can be 

edited in place, just as it can in box notation. 

■ The middle compartment lists the attributes defined for the 

class. Each attribute name is preceded by a graphic indicating 

the attribute visibility and followed by the attribute data type. 

■ The bottom compartment lists the operations defined for the 

class. Each operation name is preceded by a graphic indicating 

the operation visibility and followed by the operation return 

type. 

Note 

Visibility is the property of an object that specifies the level 

of access other objects have to it. 

So far, you’ve viewed classes only in box notation. Now you’ll view 

them in compartment notation.


What you do To view the classes in your Employee Hiring Classes diagram in 

compartment notation: 

1 With your Employee Hiring Classes window active, select Select 

All on the Edit menu. 

Tip 

To change the notation for individual classes, select only 

those classes. 

2 On the View menu, select Use Compartment Notation. 


103



104 

FrameWork switches the selected classes to compartment notation. 

After resizing and moving objects to accommodate the larger class 

graphics, your diagram should look something like this:


Hiding compartments When a class uses compartment notation, you can hide or redisplay 

one or both of the attribute and operation compartments. To hide 

the attribute compartment for the Employee class: 

1 Select the Employee class. 

2 On the View menu, select Show Compartments. 

FrameWork displays the Show Compartments dialog box. 


105


Switching back to box 

notation 


106 

3 In the Show Compartments dialog box, click on Attributes to 

deselect it. Then press the OK button. 

FrameWork hides the attribute compartment for the Employee 

class. 

After you’ve viewed your classes using compartment notation, you 

can switch back to box notation at any time. To do this: 

1 On the Edit menu, select Select All. 

2 On the View menu, click on Use Compartment Notation to 

deselect it.

7 

Creating a Statechart 

Diagram 


In this lesson, you’ll build a basic statechart diagram. Along the 

way, you’ll learn about: 

■ The structure of a statechart diagram 


■ Initial states that represent starting points for objects 

■ States that describe the conditions of objects over time 

■ Transitions that show the relationships between states 

■ Final states that represent ending points for objects 

7 

Statechart diagrams A statechart diagram shows the changes an object can undergo 

during its lifetime. Objects change in response to actions 

performed by other objects or by themselves. 


107



108 

In this lesson, you’ll build a statechart diagram for objects in the 

Applicant class you created in Lesson 5, “Creating a Java Class 

Diagram.” Your statechart diagram will show the sequence of 

states a job applicant goes through within your hiring system. 

Specifically, it will show the changes of state during a screening 

process that concludes with an applicant being rejected or hired or 

not accepting an offer that is made. 

You’ll create your statechart diagram as a subdiagram of the 

Applicant class. That way, you’ll be able to open the diagram by 

double-clicking on Applicant in your Employee Hiring Classes 

diagram. 

What you do To build your statechart diagram: 


already. 

2 With your Learning FrameWork folder highlighted, click right 

on the Applicant class to open its popup menu. Then select New 

Subdiagram and More.

Creating an initial state 

3 In the New Diagram dialog box, select UML Statechart. Then 

press the OK button. 

4 In the Open New Diagram dialog box, name the statechart 

diagram Applicant. Then press the OK button. 

FrameWork opens a modeling window for the new diagram. 


not pressed in, click on it to open the Statechart Diagram Tools 

tool folder. 

Creating an initial state 

Initial states An initial state indicates a starting point for a statechart diagram 

(for example, the point at which the object is created). The object is 

never actually in an initial state. Rather, the initial state provides 

an anchor for the transition to the first state in a series of state 

transitions. 

What you do You’ll begin your Applicant statechart diagram by placing an initial 

state in the window. To do this: 

1 In the Statechart Diagram Tools tool folder, click and hold on 

the Initial State tool. 

2 Move your cursor to the center left portion of the Applicant 

modeling window and release the mouse button. 

3 Name the initial state Resume Submitted. Then click on the 

window background to close the edit box. 


109

Creating states 



110 

Your Applicant diagram should look something like this: 

States A state represents a condition that describes an object for some 

finite amount of time. 

What you do To create states in your Applicant diagram: 


the State tool.


2 Move your cursor above and to the right of the initial state 

graphic in the Applicant modeling window and release the 

mouse button. 

3 Name the state Initially Qualified. Then click on the window 



4 Using the procedure in steps 1 through 3, add three more states 

named Rejected, Not Interested, and Hired below the Initially 

Qualified state. Then add four states named Tested, Fully 

Qualified, Interviewed, and Offered in the right side of the 

window 


111



112 

When you’re done, your Applicant diagram should look something 

like this:

Creating transitions 


Transitions Transitions show the ways in which objects can change from one 

state to another. In your Applicant diagram, you want to show how 

the initial state provides an anchor for the transitions to the first 

states in the series, Initially Qualified and Rejected. Then you want 

to show the sequence of transitions to each subsequent state. 

What you do To add transitions to your statechart diagram: 


the Transition tool. 

2 Move your cursor to the initial state in the Applicant modeling 

window and release the mouse button. Then click on the 

Initially Qualified state. 

FrameWork draws the transition graphic and opens an edit box 

for the name of the event that triggers the transition. 

3 Name the event resume accepted. Then click on the window 


4 Using the procedure in steps 1 through 3, create a second 

transition from the initial state to the Rejected state. Name the 

triggering event for this transition resume rejected. 


113



114 

With these transitions in place, your diagram should look 


Try it yourself Now try creating transitions on your own. Using the names of the 

states to guide you, try creating transitions that make sense in the 

context of your hiring system. For example, you would test only 

initially qualified applicants, which in turn can result in some 

applicants being rejected and others being considered fully 

qualified. Additionally, only applicants who have received a job 

offer can say that they’re not interested. 

Tip 

Don’t worry if you can’t think of a name for the event that 

triggers a transition. Just click on the window background to close 

the edit box.

Creating final states 


When you’re done, your diagram should look something like this: 

Final states A final state indicates an ending point for a statechart diagram 

(for example, the point at which the applicant is rejected). As with 

an initial state, the object is never actually in a final state. Rather, 

the final state provides an end point for the transition from the last 

state in a series of state transitions. 

You’ll complete the Applicant diagram by creating two final states: 

one indicating that the applicant has been hired and another 

indicating that the applicant has not. 


115


What you do To create the two final states in the Applicant diagram: 


116 


the Final State tool. 

2 Move your cursor below the initial state between the Rejected 

and Not Interested states and release the mouse button. 

3 Click on the window background to close the edit box without 

typing a name for the final state. Final states typically don’t 

have names. 

4 Using the procedure in steps 1 through 3, create another final 

state below the one you’ve already created and to the left of the 

Hired state. 

5 Create transitions from both the Rejected and Not Interested 

states to the first final state you created. 

Tip 

Transitions to final states typically don’t have triggering 

events. 

6 Create a transition from the Hired state to the second final state 

you created.


Your finished Applicant diagram should look something like this: 


117

8 

Exploring What You’ve 

Done 


In this lesson, you’ll take a different view of the work you’ve done in 

the preceding lessons. Along the way, you’ll learn about: 

■ Using forms to navigate through the KnowledgeBase 

■ Using queries to retrieve information from the KnowledgeBase 

■ Running reports on your models 

Navigating with forms 

8 

In Lesson 6, “Adding More Detail to Your Java Classes,” you saw 

how you can use forms to view and modify information about the 

objects you create. And you saw that a form for one object can show 

other related objects as well. For example, you saw that the Java 

Attribute Information form shows the class for which an attribute 

is defined. 


119

Navigating from fields 



120 

You can view information about any object already showing on a 

form by opening another form. You can do this directly from the 

form that’s already open. You don’t need to go back to the modeling 

window. By opening one form from another, you can navigate the 

information paths established in the KnowledgeBase by the 

connections you’ve created among the objects in your models. 

You can navigate from form to form either directly from the fields 

on the forms or by using the form navigation toolbar. In this lesson, 

you’ll try both techniques. 

Your navigation path To practice navigating directly from the fields on forms, you’ll start 

by looking at information about the Person class. You created this 

class in Lesson 5, “Creating a Java Class Diagram.” From there, 

you’ll look at information about a subclass of this class and an 

operation defined on that subclass. 

When you navigate directly from fields, FrameWork opens each 

form in a new window. These windows remain open until you close 

them, so you can easily return to any them by clicking on its 

workbook tab in the Project Workspace or selecting it on the 

Window menu. 

What you do To look at information about Person: 

1 Open your Employee Hiring Classes diagram if it’s not open 

already. 

2 In the popup menu for the Person class, select View in Form and 

then Java Class Information. 

FrameWork opens the Java Class Information form for Person. 

This form tells you about the associations, attributes, and 

operations defined for the class. It also lists the direct 

superclasses and subclasses of the class. You’ll look at 

information about the Employee class now.


3 In the Direct Subclasses field on the Java Class form, click right 

on Employee to open its popup menu. Then select View in Form 

and Java Class Information. 

FrameWork opens the Java Class Information form for the 

Employee class. You should now have two open windows that 

use this form — one for the Person class and one for the 

Employee class. 

4 Continue navigating by opening the Java Operation 

Information form for the Orient New Hire operation. 


121

Using the form navigation toolbar 


Your navigation path Now you’ll practice navigating with the form navigation toolbar. 

You’ll start by looking at information about the subsystem you 

created in Lesson 2, “Creating Your First Use Case Diagram.” 

From there, you’ll look at information about a use case within this 

subsystem and another use case incorporated in that one. 


122 

When you use the toolbar to navigate through forms, FrameWork 

opens each form you request in the same window. As a result, only 

one form is open at a time. However, FrameWork keeps a list of the 

forms you open in the window, so you can return to them just as 

easily as if they were still open. 

What you do To look at information about the Employee Hiring subsystem: 

1 Open your Employee Hiring System diagram if it’s not open 

already. 

2 On the popup menu for the Employee Hiring subsystem, select 

View in Form and then Basic Subsystem Information. 

3 On the View menu, select Form Navigation Toolbar. 

FrameWork displays the form navigation toolbar at the top of 

the Basic Subsystem Information form. The object field in the 

toolbar shows the subsystem for which you opened the form.


4 In the Use Cases field on the form, click on the Hire Employees 

use case. 

Notice that the object field in the form navigation toolbar now 

shows the use case you just selected. 

5 In the form navigation toolbar, click on the arrow in the form 

field (to the left of the object field) to open a list of the forms on 

which you can display the selected use case. Then scroll down 

and select Composite Use Case Object. 


123

Using queries 


124 

6 In the form navigation toolbar, click on the Open tool. 

FrameWork opens the Composite Use Case Object form for the 

Hire Employees use case in the same window you’ve been 

working in. 

7 Use the form navigation toolbar to open the Use Case 

Information form for the Interview Candidates capability. 

Try it yourself Take a few minutes to explore the objects you’ve created in your use 

case, statechart, and Java class diagrams. FrameWork comes with 

forms for viewing all types of objects. Try to use both of the 

navigation techniques you’ve just learned. Experiment with the Go 

Back ( ), History ( ), and Go Forward ( ) buttons in the form 

navigation toolbar. 

Using queries 

Tip 

You can also explore the objects in the DemoExample 

KnowledgeBase, which you used in Lesson 1, “Navigating 

FrameWork.” Many of these objects have more detail than the 

objects you’ve created in this tutorial. 

Queries A query is a request to FrameWork to retrieve information from 

the KnowledgeBase. To make the request, you invoke the query for 

a specific object. This is called evaluating the query on the object. 

Like forms, each query is defined to work on a particular type of 

object. 

How queries work A query works by using associations to navigate through the 

KnowledgeBase and by using set operations to manipulate objects 

along the way. The result of a query is a set of objects. Because of 

the operations they perform, queries are often able to retrieve 

information that is not directly available for an object.

Using queries 

What you do In this lesson, you’ll evaluate queries on the Qualified Candidate 

class in the Employee Hiring Classes diagram. To do this: 


already. 

2 Select the Qualified Candidate class. 

3 On the Queries menu, select Evaluate. 

FrameWork opens the Evaluate Query dialog box. The 

Evaluate field lists the queries you can evaluate on the Qualified 

Candidate class. 

4 In the Evaluate field, scroll down to find the CLASS superclasses 

query. Then double-click on it. 


125

Using queries 


126 

The CLASS superclasses query retrieves all the classes from 

which a class inherits properties. FrameWork shows you the 

result of this query for the Qualified Candidate class in the 

Result field. 

5 Now scroll back up to find the CLASS all functions query and 

double-click on it. This query retrieves all the associations and 

attributes that the Qualified Candidate class either inherits or 

has defined for it. Again, FrameWork shows you the result in 

the Result field.

Running reports 

6 Press the Close button to close the Evaluate Query dialog box. 

Try it yourself Now that you’ve learned how to evaluate queries, take a few 

minutes to evaluate queries on other objects in the diagrams you’ve 

built. When you’re finished, close all open Evaluate Query dialog 

boxes. 


Tip 

You can experiment more by evaluating queries on objects in 

the DemoExample KnowledgeBase. 

HTML-based reports A report is a formatted presentation of information retrieved from 

the KnowledgeBase. FrameWork reports use HTML to define their 

format. To view or print these reports, you can use any application 

that lets you open HTML documents. 


127



128 

In this exercise, you’ll run a report on the classes in the Employee 

Hiring Classes diagram you built in Lessons 6 and 7. The name of 

the report is Java. 

What you do To run the Java report: 

1 Use the Output option on the View menu to open the Output 

window on the FrameWork desktop if it’s not open already. 


already. 

3 Click on the background in the diagram window to ensure that 

no objects are selected. 

4 On the Tools menu, select Reports. 

FrameWork opens the Reports dialog box. 

5 In the Reports dialog box, select Java. Then press the Generate 

button.


While creating the report, FrameWork shows you its progress 

on the Generated Output page of the Output window. 

Viewing the report FrameWork writes the Java report to a directory named 

Java_EmployeeHiringClasses. This directory is a subdirectory of 

the PtechACG directory in the current root directory. If the current 

root directory is on your C: drive, the directory path for the report 

files is C:\PtechACG\Java_EmployeeHiringClasses. 

The name of the main report file is index.html. Use an HTML 

browser to open this file. The opening page of the report should 



129



130 

To view the information on a class (for example, the Employee 

class), click on the class name in the left frame of the report. The 

Employee information should look something like this: 

continued



131


Generating Code 

In this lesson, you’ll generate Java code from the Java class 

diagram you built in Lessons 5 and 6. Along the way, you’ll learn 

about: 

■ Using forms to provide language-specific information about 

objects in your models 

■ Generating Java class definitions 

Although this lesson shows the generation of Java code, both 

Technology and Enterprise FrameWork also include support for 

generating C++ and CORBA IDL class definitions. Additionally, 

Ptech offers code generation products for other development 

environments (including Orbix, OrbixWeb, and Forté). These 

products are all fully integrated with FrameWork. 

Tip Don’t worry if you’re not familiar with Java. You can still do 

this lesson, and the techniques you learn will apply to your own 

development environment as well. 

9 

9 


133

Using the Java Class Information form 

Using the Java Class Information form 

The Java Class form While building your diagrams, you can provide language-specific 

information about the objects in them. You provide this 

information by using forms. In this lesson, you’ll use the Java 

Class Information form to provide some additional information 

about the Person class in your Java class diagram. 

What you do To provide Java-specific information about the Person class: 


134 


already. 

2 Open the Java Class Information form for the Person class. 

3 Click in the Visibility field. Framework displays an arrow on 

the right side of the field. 

4 Click on the arrow to open the list of visibility options and select 

private. 

5 Select the Leaf option. 

6 In the form shortcut toolbar, press the Apply button ( ). 

7 Close the form.

Generating code 


What you do To generate Java code for the classes in your Employee Hiring 

Classes diagram: 

1 Open the Output window if it’s not open already. 


already. 

3 Click on the background of the Employee Hiring Classes 

window to ensure that nothing is selected. 

4 On the Tools menu, select Code Generation. 

5 In the Code Generators dialog box, select Java. Then press the 

Generate button. 


135


Where to find the 

generated code 


136 

While generating code, FrameWork reports its processing 

status on the Generated Output page of the Output window. 

FrameWork stores the generated Java files in subdirectories of a 

directory named Java. The Java directory itself is a subdirectory of 

the PtechACG directory in the current root directory. If the current 

root directory is on your C: drive, the directory path for the code 

generation files is C:\PtechACG\Java. You can use any text editor 

to view these files.


Learning more about FrameWork 

You’ve now completed the lessons in this book. You’ve learned 

many basic modeling concepts and become familiar with the tools 

you use to build models in FrameWork. You’re ready to start 

modeling your own business systems and applications. You’re also 

ready to learn about the more advanced features of FrameWork. 

Some of these features are summarized under “Additional 

FrameWork features” below. 

Note 

Some of the features described may require different Ptech 

product licenses. 

As you build your models, your sources of information will be Using 

FrameWork, Modeling with Technology FrameWork, and the 

FrameWork online help. To help you be successful with 

FrameWork, Ptech offers both training classes and consulting 

services. For more information about these offerings, please 

contact your Ptech sales representative. 

10 11 


137

Additional FrameWork features 


Using external graphics FrameWork supports the use of third-party and user-created 

graphics. You can import graphics stored as Windows metafiles 

(.wmf or .emf files) and then use them as icons for the objects in 

your diagrams. This capability gives you great flexibility in 

building diagrams that are specific to your problem domain, 

visually appealing, and easy to understand. 

Linking to other 

applications 


138 

To support or supplement your models, you can create links 

between KnowledgeBase objects and documents you create using 

other applications. Once you create such a link, you can open the 

document in its own application from within FrameWork. You can 

use this feature, for example, to link a class or operation in 

FrameWork with a Microsoft Word or video file that further 

documents it. 

Verifying models FrameWork includes a testing capability that allows you to verify 

that your models correctly represent your application processes. 

With this capability, you create samples of the objects in your 

classes and run them through the processes you’ve modeled, 

checking for expected and unexpected outcomes. Testing your 

models can help ensure the success of your application designs. 

Creating your own forms FrameWork forms are an integral part of the tools you use to build 

and verify your models. FrameWork comes with a set of forms that 

allows you to view information about all types of objects. With 

Enterprise FrameWork Professional, you can create new forms, so 

you can add, modify, and view information in the way that best 

meets your needs.


Creating your own queries FrameWork KnowledgeBase queries are powerful tools that can 

help you examine the relationships among the objects in the 

KnowledgeBase and retrieve useful information that would 

otherwise be difficult to obtain. In addition to using the queries 

included with FrameWork, you can use Enterprise FrameWork 

Professional to create your own queries. By creating queries to 

retrieve information specific to your application objects, you 

increase the value of the models and objects stored in the 


Defining new model types 

and tools 

Sharing KnowledgeBase 

information 

With Enterprise FrameWork Professional, you can extend and 

customize the FrameWork modeling environment in a variety of 

ways. For example, you can modify the rules and constraints that 

govern how you build models to support additional application 

development concepts and modeling techniques. You can even 

define new types of models with components that meet the specific 

needs of your enterprise. With simple drag-and-drop actions, you 

can create new tools and use them to add new objects and 

relationships to the KnowledgeBase. 

FrameWork includes an import/export facility that allows you to 

share information with other users. With this facility, you can 

export diagrams, query definitions, metamodel extensions, and 

other objects you create from one KnowledgeBase and import them 

into another. You can use this facility to reduce duplication of 

effort and to support the cooperative development of your business 

applications. 


139

Learning Technology FrameWork.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?