CSE UML LAB MANUAL R18

WEEK 1:

Familiarization with rational rose

a. A Tour of Rational Rose

Environment

• Application Window: a title bar, tool bar, menu bar, and a work area
for displaying toolbox, browser, document window, diagram window,
and specification window
• Browser: a window with navigation tool for viewing diagrams and
many other model elements
• Documentation Window: for preparing text information to describe
model elements or relationships
• Diagram Windows
• Overview Window: can be showed through put the mouse pointer
over hand icon
• Other windows such as Log, Edit, can be access through View on menu
bar

Title Bar
Menu Bar
Tool Bar

Browser

Documentation Toolbox Diagram

Window Window

Computer Science & Engineering 1

CSE UML LAB MANUAL R18

Specification
Window

b) Creating a simple application

(Hello.java) Step 1: Run Rational Rose
Enterprise

Step 2: Create a Use Case Diagram

1. Click on Use Case View > Main

Computer Science & Engineering 2

CSE UML LAB MANUAL R18

2. From the menu bar select Tool > Create > Use Case
3. Select the Actor from the Toolbox and place it into the Use Case
Diagram
4. Right click on the Actor to see the pop-up menu, and then select Open
Specification menu
5. Select the Use Case from the Toolbox and place it into the User Case
Diagram
6. Right click on the User case to change the name to Hello UML

Actor HelloUML

Step 3: Create Hello Class Diagram (classes, attributes, and operations)

1. Click on Use Logical View > Main

2. Create a new class called “Hello”

- Tools > Create > Class
- Select the Class icon (rectangle box symbol) from the Toolbox
- Place a class to the workspace of the Class Diagram

Computer Science & Engineering 3

CSE UML LAB MANUAL R18

- Type in a desired class name: “Hello”

- Right click the new class diagram and select “Open Specification”
- View the class name in the name box: Hello - Select “class” in the
Type combo box

3. Add Attributes to the Hello class

- Right click the Hello class to select New Attributes from a dialog box
- Accept the default name, and hit enter
- Right click the Hello class again to select Open Specification - The
window called Class Specification for Hello is then displayed; change
the attribute name to message; select Type as: String; specify Initial
Value with a pair double quotes as: “Hello UML”; set Export Control
to: private

Computer Science & Engineering 4

CSE UML LAB MANUAL R18

4. Add Operations to the Hello class

- Right click the Hello class to get an dialog box
- Select New Operations, and give a new method name as getName,
then hit Enter key to enter another method name as Hello
- Doubleclick the getName method to display Operation Specification
menu for getName dialog box
- Add return type as: String; add some information on this operation
method to Document text box

5. Change Operation Specification for Hello method

- Right click on the class diagram Hello to select Operation
Specification for showing Class Specification for Hello
- Select Implementation radio button in the Export Control
- Verify the Hello class diagram is the same as shown below.

Hello
message : String = "Hello UML"
getName()
Hello()

Computer Science & Engineering 5

CSE UML LAB MANUAL R18

Step 4. Create the Test Class Diagram

1. Select Class icon from the Toolbox
2. Place a class into the workspace Class Diagram, and give the class
name: Test
3. Right click on the Test class, and select New Operations
4. Add two methods: main and Test

Test
main()
Test()

Step 5. Object Instantiation

1. Select the dash line icon (Dependency or instaintiates)
2. Draw the line starting from the Test to Hello to make an object
instantiation

Computer Science & Engineering 6

CSE UML LAB MANUAL R18

Computer Science & Engineering 7

CSE UML LAB MANUAL R18

WEEK 2, 3&4:
Case Study: Customer Supporting System
a) Identify and analyze events
b) Identify Use cases
c) Develop event table
An event in the Unified Modelling Language (UML) is a notable
occurrence at a particular point in time. Events can, but do not
necessarily, cause state transitions from one state to another in
state machines represented by state machine diagrams.
• Occurrences at a specific time and place
• Trigger all system processing

Requirement for defining events:

• Determine relevant events
• External events first
• Temporal events second
• Decompose system into manageable units

Event Table for Customer Supporting System:

Fig: Event Table for Customer Supporting System

Computer Science & Engineering 8
CSE UML LAB MANUAL R18

d) Identify & analyze domain classes

e) Represent use cases and a domain class diagram using Rational Rose

f) Develop CRUD matrix to represent relationships between cases and problem

domain classes

Computer Science & Engineering 9

CSE UML LAB MANUAL R18

Case Study: Point Of Sales

a) Identify and analyze events

b) Identify Use cases
c) Develop event table
d) Identify & analyze domain classes
e) Represent use cases and a domain class diagram using Rational Rose

f) Develop CRUD matrix to represent relationships between cases and problem

domain classes

Computer Science & Engineering 10

CSE UML LAB MANUAL R18

Case Study: Library Management System

a) Identify and analyze events
b) Identify Use cases
c) Develop event table
d) Identify & analyze domain classes
e) Represent use cases and a domain class diagram using Rational Rose

f) Develop CRUD matrix to represent relationships between cases and problem

domain classes

Computer Science & Engineering 11

CSE UML LAB MANUAL R18

Computer Science & Engineering 12

CSE UML LAB MANUAL R18

Week 5 & 6

Case Study: Customer Supporting System

a) Develop Use case diagrams

Computer Science & Engineering 13

CSE UML LAB MANUAL R18

b) Develop elaborate Use case descriptions & scenarios

Computer Science & Engineering 14

CSE UML LAB MANUAL R18

c) Develop prototypes (without functionality)

d) Develop system sequence diagrams

Computer Science & Engineering 15

CSE UML LAB MANUAL R18

Case Study: Point Of Sales

a) Develop Use case diagrams

b) Develop elaborate Use case descriptions & scenarios

Computer Science & Engineering 16

CSE UML LAB MANUAL R18

c) Develop prototypes (without functionality)

d) Develop system sequence diagrams

Computer Science & Engineering 17

CSE UML LAB MANUAL R18

Case study: library management System

a) Develop Use case diagrams

Computer Science & Engineering 18

CSE UML LAB MANUAL R18

b) Develop elaborate Use case descriptions & scenarios

c) Develop prototypes (without functionality)

Computer Science & Engineering 19

CSE UML LAB MANUAL R18

d)Develop system sequence diagrams

Sequence diagram for issuing book:

Sequence diagram for returning book:

Computer Science & Engineering 20

CSE UML LAB MANUAL R18

Week 7, 8, 9 &10:

Case Study: Customer Supporting System

a) Develop high-level sequence diagrams for each use case

b) Identify MVC classes / objects for each use case

c) Develop Detailed Sequence Diagrams / Communication diagrams for each

use case showing interactions among all the three-layer objects

Computer Science & Engineering 21

CSE UML LAB MANUAL R18

d) Develop detailed design class model (use GRASP patterns for responsibility
assignment)

e) Develop three-layer package diagrams for each case study

Computer Science & Engineering 22

CSE UML LAB MANUAL R18

Case Study: Point Of Sales

a) Develop high-level sequence diagrams for each use case

b) Identify MVC classes / objects for each use case

Point of Sale Terminal:

View Model Controller
ICashier Sale Saleslineitem

ICustomer Store Product Specification

IManager Payment Item
IProductCatalog Post

Computer Science & Engineering 23

CSE UML LAB MANUAL R18

c) Develop Detailed Sequence Diagrams / Communication diagrams for each

use case showing interactions among all the three-layer objects

d) Develop detailed design class model (use GRASP patterns for responsibility
assignment)

Computer Science & Engineering 24

CSE UML LAB MANUAL R18

e) Develop three-layer package diagrams

Case Study: Library Management System

a) Develop high-level sequence diagrams for each use case

b) Identify MVC classes / objects for each use case

View Model Controller

Librarian Member Record Book Journal
Transaction Magazines
Bill Text Books

Computer Science & Engineering 25

CSE UML LAB MANUAL R18

C) Develop Detailed Sequence Diagrams / Communication diagrams for each

use case showing interactions among all the three-layer objects

d) Develop detailed design class model (use GRASP patterns for responsibility
assignment)

Computer Science & Engineering 26

CSE UML LAB MANUAL R18

Develop three-layer package diagrams

Computer Science & Engineering 27

CSE UML LAB MANUAL R18

Week 11 & 12:

Case Study: Customer Supporting System

a) Develop Use case Packages

Case Study: Point Of Sales

a) Develop Use case Packages

Computer Science & Engineering 28

CSE UML LAB MANUAL R18

b) Develop component diagrams

Case Study: Library Management System

a) Develop Use case Packages

b) Develop component diagrams

Computer Science & Engineering 29

CSE UML LAB MANUAL R18

Week 13
Case Study: Customer Supporting System

a) Develop sample diagrams for other UML diagrams - state chart diagrams,
activity diagrams and deployment diagrams

State chart diagrams

Activity diagrams

Computer Science & Engineering 30

CSE UML LAB MANUAL R18

Deployment diagrams

Case Study: Point Of Sales

a) Develop sample diagrams for other UML diagrams - state chart diagrams,
activity diagrams and deployment diagrams

State chart diagrams

Computer Science & Engineering 31

CSE UML LAB MANUAL R18

Activity diagrams

Deployment diagrams

Computer Science & Engineering 32

CSE UML LAB MANUAL R18

Case Study: Library Management System

a) Develop sample diagrams for other UML diagrams - state chart diagrams,
activity diagrams and deployment diagrams

State chart diagrams

Computer Science & Engineering 33

CSE UML LAB MANUAL R18

Activity diagrams

Deployment diagrams

Computer Science & Engineering 34