Uml Rational Db A

8/3/2019 Uml Rational Db A

1/39

Page 1 Copyright 1997 by Rational Software Corporation

Analysis and Designwith UML


2/39


Agenda

Benefits of Visual Modeling

History of the UML

Visual Modeling with UML

The Rational Iterative Development Process


3/39


Computer System

Business Process

Order

Item

Ship via

Modeling captures essentialparts of the system.

Dr. James Rumbaugh

Visual Modeling ismodelingusing standard graphicalnotations

What is Visual Modeling?


4/39


Use Case Analysis is a technique to capturebusiness process from users perspective

Visual Modeling Captures

Business Process


5/39


Visual Modeling is a

Communication ToolUse visual modeling to capture business objects and logic

Use visual modeling to analyze and design your application


6/39


Visual Modeling

Manages Complexity


7/39


8/39


Multiple Systems

Visual Modeling

Promotes Reuse

ReusableComponents


9/39


What is the UML?

UML stands for Unified Modeling Language

The UML combines the best of the best from

Data Modeling concepts (Entity Relationship Diagrams)

Business Modeling (work flow)

Object Modeling

Component Modeling

The UML is the standard language for visualizing,

specifying, constructing, and documenting the artifacts of asoftware-intensive system

It can be used with all processes, throughout thedevelopment life cycle, and across different implementationtechnologies


10/39


History of the UML

Nov 97 UML approved by the OMG


11/39


Putting the UML to Work

The ESU University wants to computerize their registrationsystem

The Registrar sets up the curriculum for a semester

One course may have multiple course offerings

Students select 4 primary courses and 2 alternate courses

Once a student registers for a semester, the billing system isnotified so the student may be billed for the semester

Students may use the system to add/drop courses for a period oftime after registration

Professors use the system to receive their course offering rosters

Users of the registration system are assigned passwords which areused at logon validation


12/39


Actors

An actor is someone or some thing that must interact withthe system under development

Student

Registrar

Professor

Billing System


13/39


Use Cases

A use case is a pattern of behavior the system exhibits

Each use case is a sequence of related transactions performed byan actor and the system in a dialogue

Actors are examined to determine their needs Registrar -- maintain the curriculum

Professor -- request roster

Student -- maintain schedule

Billing System -- receive billing information from registration

Maintain ScheduleMaintain Curriculum Request Course Roster


14/39


Use Case Diagram

Use case diagrams are created to visualize the relationshipsbetween actors and use cases

Student

Registrar

Professor

Maintain Schedule

Maintain Curriculum

Request Course Roster

Billing System


15/39


Maintain Curriculum

Flow of Events

1 This use case begins when the Registrar logs onto the RegistrationSystem and enters his/her password. The system verifies that thepassword is valid (E-1).

2 The system prompts the Registrar to select the current semester or afuture semester (E-2). The Registrar enters the desired semester.

3 The system prompts the professor to select the desired activity: ADD,DELETE, REVIEW, or QUIT.

4 If the activity selected is ADD, the S-1: Add a Course subflow isperformed.

5 If the activity selected is DELETE, the S-2: Delete a Course subflow is

performed.6 If the activity selected is REVIEW, the S-3: Review Curriculum

subflow is performed.

7 If the activity selected is QUIT, the use case ends.

Steps 3 to 7 are repeated until QUIT.


16/39


Uses and Extends Use

Case Relationships

As the use cases are documented, other use caserelationships may be discovered

A uses relationship shows behavior that is common to one ormore use cases

An extends relationship shows optional behavior

Register for courses

Logon validation

Maintain curriculum


17/39


Class Diagrams

A class diagram shows the existence of classes and theirrelationships in the logical view of a system

UML modeling elements in class diagrams

Classes and their structure and behavior Association, aggregation, dependency, and inheritance

relationships

Multiplicity and navigation indicators

Role names


18/39


Classes

A class is a collection of objects with common structure,common behavior, common relationships and commonsemantics

Classes are found by examining the objects in sequence andcollaboration diagram

A class is drawn as a rectangle with three compartments

Classes should be named using the vocabulary of thedomain

Naming standards should be created

e.g., all classes are singular nouns starting with a capital letter


19/39


Classes

RegistrationForm

RegistrationManager

Course

Student

CourseOffering

Professor

ScheduleAlgorithm


20/39


Operations

The behavior of a class is represented by its operations

Operations may be found by examining interactiondiagrams

registrationform

registrationmanager

3: add course(joe, math 01)

RegistrationManager

addCourse(Student,Course)


21/39

Page 21

Copyright 1997 by Rational Software Corporation

Attributes

The structure of a class is represented by its attributes

Attributes may be found by examining class definitions, theproblem requirements, and by applying domain knowledge

Each course offering

has a number, location

and time

CourseOffering

number

location

time


22/39

Page 22


Classes

RegistrationForm

RegistrationManager

addStudent(Course, StudentInfo)

Course

namenumberCredits

open()

addStudent(StudentInfo)

Studentname

major

CourseOfferinglocation

open()addStudent(StudentInfo)

Professorname

tenureStatus

ScheduleAlgorithm


23/39


24/39

Page 24


Relationships

An association is a bi-directional connection between classes

An association is shown as a line connecting the related classes

An aggregation is a stronger form of relationship where the

relationship is between a whole and its parts An aggregation is shown as a line connecting the related classes

with a diamond next to the class representing the whole

A dependency relationship is a weaker form of relationshipshowing a relationship between a client and a supplier

where the client does not have semantic knowledge of thesupplier

A dependency is shown as a dashed line pointing from theclient to the supplier


25/39

Page 25


RegistrationManager

Math 101:Course

3: add student(joe)

RegistrationManager

Course

Finding Relationships

Relationships are discovered by examining interactiondiagrams

If two objects must talk there must be a pathway forcommunication


26/39

Page 26


Relationships

RegistrationForm

RegistrationManager

Course

Student

CourseOffering

Professor


namenumberCredits

open()

addStudent(StudentInfo)name

major

location


nametenureStatus

ScheduleAlgorithm


27/39

Page 27


Multiplicity and Navigation

Multiplicity defines how many objects participate in arelationships

Multiplicity is the number of instances of one class related toONE instance of the other class

For each association and aggregation, there are two multiplicitydecisions to make: one for each end of the relationship

Although associations and aggregations are bi-directionalby default, it is often desirable to restrict navigation to onedirection

If navigation is restricted, an arrowhead is added toindicate the direction of the navigation


28/39

Page 28


Multiplicity and Navigation

RegistrationForm

RegistrationManager

Course

Student

CourseOffering

Professor


namenumberCredits

open()

addStudent(StudentInfo)major

location


tenureStatus

ScheduleAlgorithm

10..*

0..*

1

1

1..*

4

3..10

0..41


29/39

Page 29


Inheritance

Inheritance is a relationships between a superclass and itssubclasses

There are two ways to find inheritance:

Generalization Specialization

Common attributes, operations, and/or relationships areshown at the highest applicable level in the hierarchy


30/39

Page 30


Inheritance

RegistrationForm

RegistrationManager

Course

Student

CourseOffering

Professor


namenumberCredits

open()

addStudent(StudentInfo)major

location


tenureStatus

ScheduleAlgorithm

name

RegistrationUser


31/39

Page 31


Use Case Realizations

The use case diagram presents an outside view of the system

Interaction diagrams describe how use cases are realized asinteractions among societies of objects

Two types of interaction diagrams Sequence diagrams

Collaboration diagrams


32/39

Page 32


Sequence Diagram

A sequence diagram displays object interactions arrangedin a time sequence

: Student registrationform

registrationmanager

math 101

1: fill in info

2: submit

3: add course(joe, math 01)

4: are you open?5: are you open?

6: add (joe)7: add (joe)

math 101section 1


33/39

Page 33


: Registrar

course form :CourseForm

theManager :CurriculumManager

aCourse :Course

1: set course info

2: process

3: add course

4: new course

Collaboration Diagram

A collaboration diagram displays object interactionsorganized around objects and their links to one another


34/39

Page 34


The State of an Object

A state transition diagram shows

The life history of a given class

The events that cause a transition from one state to another

The actions that result from a state change State transition diagrams are created for objects with

significant dynamic behavior


35/39

Page 35


State Transition Diagram

InitializationOpen

entry: Register student

exit: Increment count

Closed

Canceled

do: Initialize course

do: Finalize course

do: Notify registered students

Add Student /Set count = 0

Add student[ count < 10 ]

[ count = 10 ]

Cancel

Cancel

Cancel


36/39

Page 36


The Physical World

Component diagrams illustrate the organizations anddependencies among software components

A component may be

A source code component A run time components or

An executable component


37/39

Page 37


Course Course

Offering

Student Professor

Component Diagram

Course.dll

People.dll

CourseUser

Register.exeBilling.exe

BillingSystem


38/39

Page 38


Deploying the System

The deployment diagram shows the configuration of run-time processing elements and the software processes livingon them

The deployment diagram visualizes the distribution ofcomponents across the enterprise.


39/39

Page 39


Deployment Diagram

Registration Database

Library

Dorm

MainBuilding

Uml Rational Db A

Documents

Transcript of Uml Rational Db A