Tutorial 1 - Introduction to UML - Structura Modeling and Use Casesl

8/3/2019 Tutorial 1 - Introduction to UML - Structura Modeling and Use Casesl

1/83

Introduction to UML: Structural

Modeling and Use Cases

Cris Kobryn

Co-Chair UML Revision Task ForceNovember 2000

Object Modeling with OMG UML Tutorial Series

1999-2000 OMG and Tutorial Contributors: EDS, IBM, Enea Data, InLine Software,

IntelliCorp, Kabira Technologies, Klasse Objecten, ObjectTime Ltd., Rational Software, Unisys


2/83

Introduction to UML 2

Overview! Tutorial series

! Quick tour

! Structural modeling

! Use case modeling


3/83


Tutorial Series! Lecture 1: Introduction to UML:

Structural Modeling and Use Cases! Lecture 2: Behavioral Modeling with

UML

! Lecture 3: Advanced Modeling with UML

! Lecture 4: Metadata Integration with

UML, MOF and XMI


4/83


Tutorial Goals! What you will learn:

! what the UML is and what is it not! UMLs basic constructs, rules and diagram

techniques! how the UML can model large, complex systems! how the UML can specify systems in an

implementation-independent manner! how UML, XMI and MOF can facilitate metadata

integration

!

What you will not learn:! Object Modeling 101! object methods or processes! Metamodeling 101


5/83


Quick Tour! Why do we model?

! What is the UML?

! Foundation elements

! Unifying concepts

! Language architecture! Relation to other OMG technologies


6/83


! Provide structure for problem solving

! Experiment to explore multiple solutions

! Furnish abstractions to manage complexity

! Reduce time-to-market for businessproblem solutions

!

Decrease development costs! Manage the risk of mistakes

Why do we model?


7/83


Tijuana shantytown:http://www.macalester.edu/~jschatz/residential.html

The Challenge


8/83


Fallingwater:http://www.adelaide.net.au/~jpolias/FLW/Images/FallingWater.jpeg

The Vision


9/83


Why do we model graphically?! Graphics reveal data.

! Edward TufteThe Visual Display of Quantitative Information,1983

! 1 bitmap = 1 megaword.! Anonymous visual modeler


10/83


! The UML is a graphical language for!

specifying! visualizing

! constructing

! documenting

the artifacts of software systems

!Added to the list of OMG adoptedtechnologies in November 1997 as UML 1.1

! Most recent minor revision is UML 1.3,adopted in November 1999

Quick Tour


11/83


! Define an easy-to-learn but semantically rich visualmodeling language

! Unify the Booch, OMT, and Objectory modelinglanguages

! Include ideas from other modeling languages! Incorporate industry best practices! Address contemporary software development issues

! scale, distribution, concurrency, executability, etc.

! Provide flexibility for applying different processes! Enable model interchange and define repository

interfaces

UML Goals


12/83


OMG UML Evolution

UML 1.1

UML 1.2

UML 1.3

UML 1.4

UML 1.5

1997(adopted by OMG)

1998

1999

Q4 2000(planned minor revision)

2001(planned minor revision)

Editorial revision with nosignificant technical changes.

ISO Publicly

AvailableSpecification

[read only]

UML 2.0

[backward compatible]

2002(planned major revision)

The expected result of OMG'sformal liaison with ISO.


13/83


OMG UML ContributorsAonixColorado State University

Computer AssociatesConcept FiveData AccessEDS

Enea DataHewlett-PackardIBMI-LogixInLine Software

IntellicorpKabira TechnologiesKlasse ObjectenLockheed Martin

MicrosoftObjecTime

OraclePtechOAO Technology SolutionsRational Software

ReichSAPSofteamSterling SoftwareSun

TaskonTelelogicUnisys


14/83


OMG UML 1.3 Specification

! UML Summary

! UML Semantics! UML Notation Guide

! UML Standard Profiles

! Software Development Processes! Business Modeling

! UML CORBAfacility Interface Definition

! UML XML Metadata Interchange DTD! Object Constraint Language


15/83


Tutorial Focus: the Language! language = syntax + semantics

! syntax = rules by which language elements(e.g., words) are assembled intoexpressions (e.g., phrases, clauses)

! semantics = rules by which syntactic

expressions are assigned meanings

! UML Notation Guide defines UMLsgraphic syntax

! UML Semantics defines UMLssemantics


16/83


! Building blocks

! Well-formedness rules

Foundation Concepts


17/83


! The basic building blocks of UML are:! model elements (classes, interfaces, components,

use cases, etc.)! relationships (associations, generalization,

dependencies, etc.)

! diagrams (class diagrams, use case diagrams,interaction diagrams, etc.)

! Simple building blocks are used to create large,complex structures! cf. elements, bonds and molecules in chemistry! cf. components, connectors and circuit boards in

hardware

Building Blocks


18/83


Diagram: Classifier View

Element

Carbon Hydrogen

C

C

C H


19/83


Diagram: Instance View

:Carbon :Carbon

:Hydrogen

:Hydrogen

:Hydrogen

:Hydrogen

:Hydrogen:Hydrogen


20/83


Well-Formedness Rules! Well-formed: indicates that a model or model

fragment adheres to all semantic and syntactic rules

that apply to it.! UML specifies rules for:

! naming

! scoping

! visibility

! integrity

! execution (limited)

!

However, during iterative, incremental developmentit is expected that models will be incomplete andinconsistent.


21/83


Well-Formedness Rules (contd)! Example of semantic rule: Class [1]

! English: If a Class is concrete, all the Operations of

the Class should have a realizing Method in the full

descriptor.

! OCL: not self.isAbstract implies

self.allOperations->forAll (op | self.allMethods->

exists (m | m.specification->

includes(op)))


22/83


Well-Formedness Rules (contd)! Example of syntactic rules: Class

! Basic Notation: A class is drawn as a solid-outline

rectangle with three compartments separated by

horizontal lines.

! Presentation Option: Either or both of the attribute

and operation compartments may be suppressed.

! Example of syntactic guideline: Class! Style Guideline: Begin class names with an

uppercase letter.


23/83


Unifying Concepts! classifier-instance dichotomy

! e.g., an object is an instance of a class OR

a class is the classifier of an object

! specification-realization dichotomy

! e.g., an interface is a specification of a class OR

a class is a realization of an interface

! analysis-time vs. design-time vs. run-time

! modeling phases (process creep)

! usage guidelines suggested, not enforced


24/83


Language Architecture! Metamodel architecture

! Package structure


25/83


Metamodel Architecture

metaclassAttribute

metaclassClass

metaclassOperation

instanceOf

UML Metamodel

Analysis Model

The attribute fareofthe PassengerTicketclass is an instance ofthe metaclassAttribute.

The operationissueof thePassengerTicketclass is aninstance of themetaclassOperation.

instanceOfinstanceOf

instanceOf

Represents theUser Objectlayerof the 4-layermetamodelarchitecturepattern.

metaclassClass

MOF Meta-Metamodel

metaclassOperation

metaclassAttribute

PassengerTicket

+total()+issue()+surrender()+refund()

+issuedBy : Airline+issuingAgent : TravelAgent+fare : Currency+tax : Currency

45723990550: PassengerTicket

+issuedBy : Airline = AcmeAirlines+issuingAgent : TravelAgent = TerrificTravel+fare : Currency = 1050.00+tax : Currency = 57.56

instanceOf

From Modeling CORBA Applications withUML chapter in [Siegel 00].


26/83


Package Structure

UML

ModelManagement

BehavioralElements

Foundationpackage

dependency


27/83


Relation to Other OMG Technologies

OMG UML

UML XMLDocument Type

Definition

XML MetadataInterchange

(XMI) Facility

UML Profile forCORBA

UML Profiles forBusinessDomains

Meta Object

Facility

Specification Layer

Metadata Layer

Customization Layer

PlatformTechnologyprofiles***

DomainTechnologyprofiles***

*** In process, not yet adopted

UMLCORBAfacility

InterfaceDefinition


28/83


Structural Modeling! What is structural modeling?

! Core concepts

! Diagram tour

! When to model structure

! Modeling tips! Example: Interface-based design


29/83


What is structural modeling?! Structural model: a view of an system

that emphasizes the structure of theobjects, including their classifiers,relationships, attributes and operations.


30/83


Construct Description Syntax

class a description of a set of objectsthat share the same attributes,operations, methods, relationshipsand semantics.

interface a named set of operations that

characterize the behavior of anelement.

component a physical, replaceable part of asystem that packagesimplementation and provides the

realization of a set of interfaces.node a run-time physical object that

represents a computationalresource.

interface

Structural Modeling: Core Elements


31/83


Structural Modeling: Core Elements (contd)


constraint a semantic condition or restriction.

{constraint}

An extension mechanism useful for specifying structural elements.


32/83



association a relationship between two or more

classifiers that involves connectionsamong their instances.

aggregation A special form of association thatspecifies a whole-part relationshipbetween the aggregate (whole) and

the component part.generalization a taxonomic relationship between a

more general and a more specificelement.

dependency a relationship between two modeling

elements, in which a change to onemodeling element (the independentelement) will affect the other modelingelement (the dependent element).

Structural Modeling: Core Relationships


33/83



realization a relationship between a specificationand its implementation.

Structural Modeling: Core Relationships (contd)


34/83


! Show the static structure of the model! the entities that exist (e.g., classes, interfaces,

components, nodes)! internal structure! relationship to other entities

! Do not show! temporal information

! Kinds! static structural diagrams

! class diagram! object diagram

! implementation diagrams! component diagram! deployment diagram

Structural Diagram Tour


35/83


Static Structural Diagrams! Shows a graph of classifier

elements connected by staticrelationships.

! kinds

! class diagram: classifier view

! object diagram: instance view


36/83


Classes

Fig. 3-17, UML Notation Guide

Window

display ()

size: Areavisibility: Boolean

hide ()

Window

Window

+default-size: Rectangle#maximum-size: Rectangle

+create ()

+display ()

+size: Area = (100,100)#visibility: Boolean = invisible

+hide ()

-xptr: XWindow*

-attachXWindow(xwin:Xwindow*)

{abstract,

author=Joe,status=tested}


37/83


Classes: compartments with names


bill no-shows

Reservation

operationsguarantee()cancel ()change (newDate: Date)

responsibilities

match to available rooms

exceptions

invalid credit card


38/83


Classes: method body


report ()

BurglarAlarm

isTripped: Boolean = false

PoliceStation

1 station

*

{ if isTrippedthen station.alert(self)}

alert ()


39/83


Interfaces


HashTable

Hashable

Comparable

String. . .

isEqual(String):Booleanhash():Integer

contents*

Comparableinterface

isEqual(String):Booleanhash():Integer

. . .

use


40/83


Associations


Person

Manages

JobCompany

boss

worker

employeeemployer

1..

0..1

Job

Account

Person

Corporation

{Xor}

salary


41/83


Association Ends


Polygon PointContains

{ordered}

3..1

GraphicsBundle

colortexturedensity

1

1

-bundle

+points


42/83



PlayerTeam

Year

Record

goals for

goals againstwinslosses

goalkeeper

season

team

ties

Ternary Associations


43/83


Composition


Window

scrollbar [2]: Slider

title: Headerbody: Panel

Window

scrollbar title body

Header Panel

21 1

Slider

111


44/83


Composition


scrollbar:Slider

Window

2

title:Header1

body:Panel

1


45/83


Generalization


Shape

SplineEllipsePolygon

Shape

SplineEllipsePolygon

Shared Target Style

Separate Target Style

. . .

. . .


46/83


Generalization


Vehicle

WindPowered

Vehicle

MotorPowered

VehicleLand

Vehicle

Water

Vehicle

venue

venuepower

power

SailboatTruck

{overlapping} {overlapping}


47/83


Dependencies


friendClassA ClassB

ClassC

instantiate

call

ClassD

operationZ()friend

ClassD ClassE

refineClassC combines

two logical classes


48/83


Dependencies


Controller

Diagram

Elements

DomainElements GraphicsCore

access

access

access

access

access


49/83


Objects


trian g le : P olyg on

ce n te r = (0 ,0 )

vertice s = ((0 ,0 ),(4 ,0),(4,3 ))

bo rd erC olo r = bla ck

fillC o lo r = wh ite

tria ng le: P o lyg o n

tria ng le

:Polygon

s c he d u le r


50/83


Composite objects


horizontalBar:ScrollBar

verticalBar:ScrollBar

awindow : Window

surface:Pane

title:TitleBar

moves

moves


51/83


Links


downhillSkiClub:Club Joe:Person

Jill:Person

Chris:Person

member

member

member

treasurer

officer

president

officer


52/83


Constraints and Comments


Mem be r-of

Chai r -of

{s ubs e t}P e rs o n Co m m itte e

P e rs o n C o m pa ny

b o s s

{P e rs o n.em ploye r =P e rs o n. bo s s . e m p lo y e r}

employe re m p lo y e e

0 . .1

0 . .1

1

R e p r e s e n t s

a n in co rpo ra te d en tity.


53/83


Implementation Diagrams! Show aspects of model

implementation, including sourcecode structure and run-timeimplementation structure

! Kinds! component diagram

! deployment diagram


54/83


! Shows the organizations anddependencies among softwarecomponents

! Components include

! source code components

! binary code components

! executable components

Component Diagram


55/83



ComponentsDictionary

Spell-check

Synonyms

mymailer: Mailer

+Mailbox+RoutingList

-MailQueue


56/83



Component Diagram

Planner

Scheduler

GUI

Reservations

Update

D l Di


57/83


Deployment Diagram

! Shows the configuration of run-timeprocessing elements and the softwarecomponents, processes and objectsthat live on them

! Deployment diagrams may be used toshow which components may run onwhich nodes

D l t Di


58/83


Deployment Diagram


AdminS e rve r:Hos tMach ine

Joe sM a c h i ne : P C

: S c he du l e rrese rva t ions

: P l a n n e r

d a t a b a s e

m e e t i n g s D B

D l t Di


59/83


Deployment Diagram (contd)


Node1

Node2

cluster

x y

cluster

x y

become

database

w z


60/83


When to model structure

! Adopt an opportunistic top-down+bottom-up approachto modeling structure

! Specify the top-level structure using architecturally significantclassifiers and model management constructs (packages,models, subsystems; see Tutorial 3)

! Specify lower-level structure as you discover detail re classifiersand relationships

! If you understand your domain well you can frequentlystart with structural modeling; otherwise! If you start with use case modeling (as with a use-case driven

method) make sure that your structural model is consistent

with your use cases! If you start with role modeling (as with a collaboration-driven

method) make sure that your structural model is consistentwith your collaborations

St t l M d li Ti


61/83


Structural Modeling Tips

! Define a skeleton (or backbone) that can beextended and refined as you learn more about yourdomain.

! Focus on using basic constructs well; add advancedconstructs and/or notation only as required.

! Defer implementation concerns until late in themodeling process.

! Structural diagrams should! emphasize a particular aspect of the structural model

! contain classifiers at the same level of abstraction

! Large numbers of classifiers should be organized intopackages (see Lecture 3)

E l I t f b d d i


62/83


Example: Interface-based designmodule POS

{

typedef long POSId;

typedef string Barcode;

interface InputMedia

{

typedef string OperatorCmd;

void BarcodeInput(in Barcode Item);void KeypadInput(in OperatorCmd Cmd);

};

interface OutputMedia

{..};

interface POSTerminal

{..};

};

Ch. 26, CORBA Fundamentals and Programming(2nd ed.), [Siegel 00]

From Modeling CORBA Applications with UML chapter


63/83


Point-of-Sale

POSterminal

+outputText()

IDLinterfaceIOutputMedia

InputMedia+initialization()+barcodeInput()+keypadInput()

+POSref : POSterminal

IDLinterfaceIinputMedia

OutputMedia

Store

+initialization()+findPrice()

+depotRef : Depot+taxRef : Tax+storeMarkup : float+storeId : Integer

IDLinterfaceIStoreAccess

+initialization()+calculateTax()+findTaxablePrice()

+rate : float

IDLinterfaceITax

+initialization()+login()+printPOSsalesSummary()+printStoreSalesSummary()+setItemQuantity()+sendBarcode()+endSale()

+storeRef : Store+storeAccessRef : StoreAccess+outputMediaRef : OutputMedia+taxRef : Tax

+POSid : Integer+itemBarcode : Integer+itemQuantity : Integer+itemInfo : ItemInfo+itemPrice : Currency+itemTaxPrice : Currency+itemExtension : Currency+saleSubtotal : Currency+taxableSubtotal : Currency+saleTotal : Currency+saleTax : Currency

+POSlist : List

IDLinterfaceIPOSterminal

+initialization()+login()

+getPOStotals()+updateStoreTotals()

+totals : Totals+POSlist : List

IDLinterfaceIStore

StoreAccess

Tax

g pp pin [Siegel 00].

Use Case Modeling


64/83


Use Case Modeling

! What is use case modeling?

! Core concepts

! Diagram tour

! When to model use cases

! Modeling tips

! Example: Online HR System

What is use case modeling?


65/83


What is use case modeling?

! use case model: a view of a system thatemphasizes the behavior as it appears

to outside users. A use case modelpartitions system functionality intotransactions (use cases) that aremeaningful to users (actors).

Use Case Modeling: Core Elements


66/83


Use Case Modeling: Core Elements


use case A sequence of actions, including

variants, that a system (or otherentity) can perform, interacting withactors of the system.

actor A coherent set of roles that users

of use cases play when interactingwith these use cases.

systemboundary

Represents the boundary betweenthe physical system and the actors

who interact with the physicalsystem.

UseCaseName

ActorName

Use Case Modeling: Core Relationships


67/83



association The participation of an actor in a usecase. i.e., instance of an actor andinstances of a use case communicatewith each other.

extend A relationship from an extensionuse

case to a baseuse case, specifyinghow the behavior for the extensionuse case can be inserted into thebehavior defined for the base usecase.

generalization A taxonomic relationship between amore general use case and a morespecific use case.

Use Case Modeling: Core Relationships

Use Case Modeling: Core Relationships ( d)


68/83



include An relationship from a baseuse caseto an inclusionuse case, specifyinghow the behavior for the inclusion usecase is inserted into the behaviordefined for the base use case.

Use Case Modeling: Core Relationships (contd)

Use Case Diagram Tour


69/83


! Shows use cases, actor and theirrelationships

! Use case internals can be specified bytext and/or interaction diagrams (see

Lecture 2)! Kinds

! use case diagram! use case description

Use Case Diagram Tour

Use Case Diagram


70/83



Cus tomer

Supervisor

SalespersonPlace

Establis hcredit

Check

Telephon e Catalog

Fill orders

Shipping Cle rk

s tatus

order

Use Case Diagram

Use Case Relationships


71/83



Use Case Relationships

additional requests :

OrderProduct

SupplyArrange

includeincludeinclude

RequestCatalog

extendExtension points

PaymentCustomer Data

after creation of the order

Place Order

1 * the salesperson asks forthe catalog

Actor Relationships


72/83



Actor Relationships

EstablishCredit

Place

OrderSalesperson

Supervisor

1 *

1 *

Use Case Description: Change Flight


73/83


Use Case Description: Change Flight

sActors: traveler, client account db, airline reservation system

sPreconditions:

Traveler has logged on to the system and selected change flightitinerary option

sBasic course

System retrieves travelers account and flight itinerary from clientaccount database

System asks traveler to select itinerary segment she wants tochange; traveler selects itinerary segment.

System asks traveler for new departure and destinationinformation; traveler provides information.

If flights are available then

System displays transaction summary.sAlternative courses

If no flights are available then

When to model use cases


74/83


When to model use cases

! Model user requirements with use cases.

! Model test scenarios with use cases.

! If you are using a use-case driven method! start with use cases and derive your structural and

behavioral models from it.

! If you are not using a use-case drivenmethod! make sure that your use cases are consistent with

your structural and behavioral models.

Use Case Modeling Tips


75/83


Use Case Modeling Tips

! Make sure that each use case describes a significant chunk ofsystem usage that is understandable by both domain expertsand programmers

!

When defining use cases in text, use nouns and verbsaccurately and consistently to help derive objects and messagesfor interaction diagrams (see Lecture 2)

! Factor out common usages that are required by multiple usecases

! If the usage is required use ! If the base use case is complete and the usage may be optional,

consider use

! A use case diagram should! contain only use cases at the same level of abstraction

! include only actors who are required

! Large numbers of use cases should be organized into packages(see Lecture 3)

Example: Online HR System


76/83


Online HR System

LocateEmployees

UpdateEmployee

Profile

Update Benefits

Access TravelSystem

Access PayRecords

Employee

Manager

Healthcare Plan System

{if currentMonth = Oct.}

{readOnly}

Insurance Plan System

Online HR System: Use Case Relationships


77/83


y p

Update MedicalPlan

Update DentalPlan

Update Benefits______________

Extension pointsbenefit options:

after required enrollments

UpdateInsurance Plan

Employee

ElectReimbursementfor Healthcare

Elect StockPurchase

employee requestsstock purchase option

employee requestsreimbursement option

extensioncondition

extension pointname andlocation

Online HR System: Update Benefits Use Case


78/83


sActors: employee, employee account db, healthcare plan system,insurance plan system

sPreconditions:

Employee has logged on to the system and selected update benefitsoption

sBasic course

System retrieves employee account from employee account db

System asks employee to select medical plan type; include UpdateMedical Plan.

System asks employee to select dental plan type; include UpdateDental Plan.

sAlternative courses

If health plan is not available in the employees area the employee isinformed and asked to select another plan...

Wrap Up


79/83


p p

! Ideas to take away

! Preview of next tutorial

! References

! Further info

Ideas to Take Away


80/83


! UML is effective for modeling large, complex softwaresystems

!

It is simple to learn for most developers, but providesadvanced features for expert analysts, designers andarchitects

! It can specify systems in an implementation-independent manner

! 10-20% of the constructs are used 80-90% of thetime

! Structural modeling specifies a skeleton that can berefined and extended with additional structure and

behavior! Use case modeling specifies the functional

requirements of system in an object-oriented manner

y

Preview - Next Tutorial


81/83


! Behavioral Modeling with UML

! Behavioral modeling overview

! Interactions

! Collaborations

! Statecharts

!Activity Graphs

References


82/83


! OMG UML Specification v. 1.3, OMG doc# ad/06-08-

99

! [Kobryn 99] UML 2001: A Standardization Odyssey,

Communications of the ACM, Oct. 1999.

! [Kobryn 00] Modeling CORBA Applications with

UML, chapter contribution to [Siegel 00] CORBA 3

Fundamentals and Programming(2nd ed.), Wiley,

2000.

Further Info


83/83


! Web:! UML 1.4 RTF: www.celigent.com/omg/umlrtf

! OMG UML Tutorials:www.celigent.com/omg/umlrtf/tutorials.htm

! UML 2.0 Working Group:www.celigent.com/omg/adptf/wgs/uml2wg.htm

! OMG UML Resources: www.omg.org/uml/

! Email! [email protected]

! [email protected]

! Conferences & workshops!

OMG UML Workshop: UML in the .com Enterprise, PalmSprings, California, Nov. 2000

! UML World 2001, location and dates TBA

! UML 2001, Toronto, Canada, Oct. 2001

Date post:	06-Apr-2018
Category:	Documents
Upload:	aalvesaquino
View:	231 times
Download:	0 times

Tutorial 1 - Introduction to UML - Structura Modeling and Use Casesl

Documents