14
Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Rational Rose Overview Diagrams, Directory Structure, Working with Rose

  • View
    216

  • Download
    1

Embed Size (px)

Citation preview

Page 1: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Rational Rose Overview

Diagrams, Directory Structure, Working with Rose

Page 2: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Diagrams in Rational Rose

• Global Use Case Model Diagram

• Use Case Diagram

• Business Domain Class Model Diagram

• Robustness Class Diagram

• Design Class Diagrams

• Use Case Realization Diagram

• Use Case Realization Sequence Diagram

Page 3: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Business Use Case

Model Diagram

Page 4: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Use Case Diagram

Page 5: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Business Domain Class Model Diagram

Page 6: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Robustness Class Diagram

Page 7: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Design Class Diagram

Page 8: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Use Case Realization Diagram

Page 9: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Use Case

Realization -

Sequence Diagram

Page 10: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Rose Directory Hierarchy for RUP • Model

– Use Case View• Business Use Case Model

– Global Use Case Model• Use Case Model

– Actors» Individual actors

– Use Cases» <individual use case folders>» <individual use case diagrams>» Architecturally significant use cases» <like network, portal, security, etc.>

– Logical View• Analysis View

– Key Abstractions– Business Domain Model

» Domain class diagram» Entity stereotype classes

• Design Model– <application layers – example web, logic, data, batch>

» Layer implementation class diagram» Controller stereotype classes» Interface stereotype classes» Boundary stereotype classes

– Use Case Realizations» <individual use case folders>» Use case realization diagrams» Robustness diagrams» Sequence diagrams

Use casesGlobal use case modelActors

Entity (static) classesdomain model

Use case realization diagrams Robustness diagramsSequence diagrams

Design classes,diagrams for boundary,controller, and interface

Page 11: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Business Use Case Model Diagram

Use Case with Use Case Diagram below

Note: a package for each Use Case

Create Actors in Actors Folder

Main is used to define package structure for Use

Case View

Page 12: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Key Abstractions for the business things

Business Domain Class Model Diagram

Note: All classes are entity type static

classes

Page 13: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Robustness Class Diagram

Discovered classes - <<boundary>> and <<control>> types go here, <<entity>> types need to be added to the domain

diagram

Use Case Realization Diagram

Use Case Realization – Sequence Diagram (one for basic flow and

alternative flows)

Design class diagrams for layer

Page 14: Rational Rose Overview Diagrams, Directory Structure, Working with Rose

Working with Rose• Double clicking object brings up diagram or properties depending on

the object• Right clicking a selected item brings up a object specific menu• Choosing plus or minus boxes on browser expands and contracts

folders• Tools palate is to the left of the drawing area (select and then click

on drawing)• All items are objects and have properties• Associations, dependencies and other joining lines have properties

associated with each end• Stereotypes allow the custom definition of objects in Rose• Associations and other object can be displayed per diagram• Adding existing item is drag and drop to new diagrams• Display characteristics for each object can be altered per diagram