26252990 uml complete

8/9/2019 26252990 UML Complete

http://slidepdf.com/reader/full/26252990-uml-complete 1/163

1

Object Oriented Analysis andDesign Using UML

8/9/2019 26252990 UML Complete


2

Course description:

OBJECTIVE:

The understand the Unified Modeling Language and orient towards Object

Oriented methodology using UML for modeling software systems.

TARGET AUDIENCE:

In particular, it is intended for software professionals who have soundknowledge of object concepts and some experience towards analysis and design.

PREREQUISITES:

Good understanding of object concepts.

Sound knowledge of any object oriented language.

Knowledge of software engineering process.

8/9/2019 26252990 UML Complete


3

Course description:

TABLE OF CONTENTS:

Module1 Introduction

Module2 Use case diagram

Module3 Flow of events

Module 4 Realization of the class diagram

Sequence diagram and Collaboration Diagram

Module5 Class diagram and refinement attributes

Module6 State transition and activity diagram

Module7 Implementation diagram

Component diagram and Deployment diagram

Module8 Understanding project culture

Appendix-A

8/9/2019 26252990 UML Complete


4

Module-1

8/9/2019 26252990 UML Complete


5

Importance of modeling

What is a model?

– A model is a simplification of reality

Why do we model? – help visualizing

– permit specification

– provides a template – document decisions

8/9/2019 26252990 UML Complete


6

4 Principles of Modeling

Choose your models well

Every model may be expressed at various

levels of precisionThe best models are connected to reality

No single model is sufficient

8/9/2019 26252990 UML Complete


7

What is Software Engineering?

DEFINITION:The application of systematic, disciplined andqualifiable approach to the development, operation and maintenanceof a software system is software engineering.

Software development life cycle has following stages:

REQUIREMENT

ANALYSIS

DESIGN

IMPLEMENTATION

TESTING

8/9/2019 26252990 UML Complete


8

Effort Distribution for each stage:

Analysis & design 40 %

Development 20 %

Testing 40 %

Analysis - What is to be done ?

Design - How it is to be done ?

Two Popular methodology approaches are:

Structured Analysis & Design

Object Oriented Analysis & Design-OO model

8/9/2019 26252990 UML Complete


9

Major benefits of OOAD:

The object oriented approach is a way of thinking about a problem using

real world concepts instead using adhoc function concepts.

We intent to learn OOAD approach for the following reason:

– Promotes better understanding of user requirements – Leads cleaner design

– Design flexibility'

– Decomposition of the system is consistent

– Facilitates data abstraction & information hiding

– Software reuse – Easy maintenance

– Implementation flexibility

8/9/2019 26252990 UML Complete


10

Elements of OO Methodology:

Following are three elements for every OO methodology:

Notation

Process / Method

Tool

8/9/2019 26252990 UML Complete


11

What is Notation?

Notation:

It is collection of graphical symbols for expressing model of the

system.

The Unified Modeling Language [UML] provides a very robust setof notation which grows from analysis to design.

This brings end of the method wars as far as notation is concerned

with adoption of the language [UML]

By unifying the notations used by these object oriented methods, the unifiedmodeling language provides the basis for a de facto standard in the domain of

object oriented analysis and design founded on a wide base of user

experience

8/9/2019 26252990 UML Complete


12

What is UML?

It is a Unified Modeling Language, which is mainly a collection of graphicalnotation that methods use to express the designs.

The UML is language for visualizing, specifying, constructing and documentingthe artifacts of software system.

UML is visual modeling language for modeling systems and is non proprietary

UML is not a radical departure from Booch, OMT, OOSE notations but rather legitimate successor to all three.

It is an evolutionary step, which is more expressive and more uniform thanindividual notations.

Whitehead says

“ By relieving the brain of unnecessary work, a good notation, sets it free toconcentrate on more advance and creative problems “ UML is not a method or process but is the means to express the same.

8/9/2019 26252990 UML Complete


13

Where can you use the UML?

System of several different kinds, absolutely anywhere everywhere.

Primarily for software intensive systems like:

Systems software

Business processes

8/9/2019 26252990 UML Complete


14

The Evolution of the UML:

UML1.1

UML1.0

UML0.9

Beta version OOPSLA’96

Public Feedback

Submission of OMG group

OMG vote’97

Submission to OMG, sept’97

Unified Method 0.8

Other method Booch OMT OOSE

8/9/2019 26252990 UML Complete


15

Advantages of UML:

Captures business processes

Enhance communication and ensures the right communication

Capability to capture the logical software architecture independent of the implementation language

Manages the complexity

Enables reuse of design

8/9/2019 26252990 UML Complete


16

UML refers to:

UML things:

Class, component, node, relationship, package etc..

UML diagrams:Use case diagram, interaction diagram, class diagram, State

diagram,deployment diagram

8/9/2019 26252990 UML Complete


17

What is Process?

What is Process?

It is an extensive set of guidelines that address the technical and

organizational aspects of software development focusing on requirements,

analysis and design.

Process basically encapsulates the activities leading to the orderlyconstruction of system model.

OO model supports the iterative and incremental model for the process.

8/9/2019 26252990 UML Complete


18

More about Process?

Guidance as to the order of team’s activities

It specifies what artifacts should be developed

It directs the task of individual developers and team as a whole

It offers criteria for monitoring and measuring project activities

The selection of particular process will vary greatly depending uponthings like problem domain, implementation technology and skills of team

Booch,OMT,OOSE and many other methods have well defined processand UML supports almost all methods

There has been some convergence on development process practices butthere is no consensus for standardization.

Framework for the every stage of software development life cycle.

8/9/2019 26252990 UML Complete


19

Best Practices followed by Rational Unified Process

Develop software iteratively

Manage requirements

Use component based architectures Visually model software

Verify S/W quality

Control changes to software.

8/9/2019 26252990 UML Complete


20

What is a tool?

It is automated support for every stage of software development

life cycle.

Since we are concentrating on requirement, analysis and design phase,

following are the names of few tools which are greatly in use:

1. Rational Rose

2. Cayenne

3. Platinum

4. Select

8/9/2019 26252990 UML Complete


21

Why Tool?

Helps designer for creating designs much more quickly.

Supports validations like:

Consistency checking

Completeness checking

Constrain checking.

Time required for certain operation could be predicted .

Code generation

Reverse engineering.

Round trip engineering Conversion from SSAD to OOAD

Quick documentation…etc

8/9/2019 26252990 UML Complete


22

Triangle for Success:

All three components play equally important role towards the success

of the project.

Notation

MethodTool

8/9/2019 26252990 UML Complete


23

Objective of the first module:

Get introduced with Unified Modeling Language and know the basic

components of software development life cycle.

8/9/2019 26252990 UML Complete


24

Module-2

8/9/2019 26252990 UML Complete


25

OO model:

STATIC MODEL

DYNAMIC MODEL

PHYSICAL MODEL

LOGICAL MODEL

The models of Object Oriented Development

8/9/2019 26252990 UML Complete


26

Models and Views:

4+1 view of OO model.

– Process view

– Deployment view

– Logical view

– Dynamic view+

– Use case view

As shown in the model , for each dimension we define a number of diagrams

that denote a view of the system’s model. The use case view is central since its contents drive the developments of

other views.

8/9/2019 26252990 UML Complete


27

UML diagrams:

1. Use case diagram

2. Class Diagram

3. Behavioral diagrams

- State chart diagrams- Object diagram

- Activity diagrams

- Interaction diagrams

- Sequence diagrams

- Collaboration diagrams

4. Implementation diagrams- Component diagram

- Deployment diagram

8/9/2019 26252990 UML Complete


28

Semantics of Diagrams:

· Use case diagrams represent the functions of a system from the user’s point of view.

· Sequence diagrams are a temporal representation of objects and their

interactions.· Collaboration diagrams are a spatial representation of objects, links,

and interactions.

· Object diagrams represent objects and their relationships, andcorrespond to simplified collaboration diagrams that do not represent

message broadcasts.· Class diagrams represent the static structure in terms of classes and

relationships.

8/9/2019 26252990 UML Complete


29

Semantics of Diagrams:

Contd...

· State chart diagrams represent the behavior of a class in terms of states

· Activity diagrams are to represent the parallel behavior of an operationas a set of actions.

· Component diagrams represent the logical components of anapplication.

· Deployment diagrams represent the deployment of components on particular pieces of hardware.

8/9/2019 26252990 UML Complete


30

What is USE CASE diagram?

A use case diagram establish the capability of the system as a whole.

Components of use case diagram:

Actor

Use case

System boundary

Relationship

Actor relationship

Semantic of the components is followed.

8/9/2019 26252990 UML Complete


31

ACTOR:

What is an actor?

An actor is some one or something that must interact with the system

under development

UML notation for actor is stickman, shown below.

Customer Manager Cashier

8/9/2019 26252990 UML Complete


32

ACTOR:

More about an actor:

It is role a user plays with respect to system.

Actors are not part of the system they represent anyone or anything that must interact with the system.

Actors carry out use cases and a single actor may perform more

than one use cases.

Actors are determined by observing the direct uses of the

system,

8/9/2019 26252990 UML Complete


33

ACTOR:

Contd…

Those are responsible for its use and maintain as well as other systems

that interact with the developed system.

An actor may

- input information to the system.

- receive information from the system.

- input to and out from the system.

8/9/2019 26252990 UML Complete


34

ACTOR:

How do we find the actor?

Ask following questions to find the actors:

– Who uses the system?

– Who installs the system? – Who Starts up the system?

– What other systems use this system?

– Who gets the information from the system?

– Who provides information to the system?

Actor is always external to the system. They are never part of thesystem to be developed.

8/9/2019 26252990 UML Complete


35

ACTOR:

4-Categories of an actor:

Principle : Who uses the main system functions. Secondary : Who takes care of administration & maintenance.

External h/w : The h/w devices which are part of application

domain and must be used.

Other system: The other system with which the system must

interact.

8/9/2019 26252990 UML Complete


36

ACTOR:

Note:

If newly identified actor is using a system in a same way like an

existing actor, then new actor can be dropped. If two actors use system in the same way they are same actors.

8/9/2019 26252990 UML Complete


37

USE CASE:

What is USE case?

A use case is a pattern of behavior, the system exhibits

Each use case is a sequence of related transactions performed by an

actor and the system in dialogue.

USE CASE is dialogue between an actor and the system.

Examples:

Open new account Withdrawal of cash

from ATM

8/9/2019 26252990 UML Complete


38

USE CASE:

More about USE CASE:

It is a snapshot of one aspect of system.

They model a dialog between actor and system.

A use case typically represents a major piece of functionality that

is complete from beginning to end.

Most of the use cases are generated in initial phase, but you find

some more as you proceed.

A use case may be small or large. It captures a broad view of aprimary functionality of the system in a manner that can be easily

grasped by non technical user.

8/9/2019 26252990 UML Complete


39

USE CASE:

Contd…

A use case must deliver something of value to an actor.

The use cases may be decomposed into other use cases. Use cases also present a good vehicle for project planning.

8/9/2019 26252990 UML Complete


40

USE CASE:

How do we find the use cases?

What functions will the actor want from the system?

Does the system store information? What actors will create, read,update. Or delete that information?

Does the system need to notify an actor about changes in its internal

state?

8/9/2019 26252990 UML Complete


41

USE CASE:

Generic format for documenting the use case:

- Pre condition: If any

– Use case : Name of the case.

– Actors : List of actors(external agents), indicating who

initiates the use case. – Purpose : Intention of the use case.

– Overview : Description.

– Type : primary / secondary.

– Post condition: If any

Typical Course of Events:ACTOR ACTION : Numbered actions of the actor.

SYSTEM RESPONSE : Numbered description of system responses.

8/9/2019 26252990 UML Complete


42

USE CASE:

USE CASE documentation example:

The following use case describes the process of opening a new account in

the bank.

Use case :Open new account

Actors :Customer, Cashier, Manager

Purpose :Like to have new saving account.

Description :A customer arrives in the bank to open the new

account. Customer requests for the new account

form, fill the same and submits, along with the

minimal deposit. At the end of complete successfulprocess customer receives the passbook.

Type:Primary use case.

8/9/2019 26252990 UML Complete


43

Grouping USE CASES:

Those use case functionality which are directly dependent on the

system environment are placed in interface objects

Those functionality dealing with storage and handling of information

are placed in entity objects

Functionality's specific to one or few use cases and not naturally

placed in any of the other objects are placed in control objects

By performing this division we obtain a structure which helps us to

understand the system from logical view

8/9/2019 26252990 UML Complete


44

OOAD --- USE CASE driven

Capture,clarify

& validate use cases

Analysis Design &

Implementation

Implementuse cases

Use cases make up the glue

Test

Verify that use cases

are satisfied

8/9/2019 26252990 UML Complete


45

SYSTEM BOUNDARY:

What is System Boundary?

It is shown as a rectangle.

It helps to identify what is external verses internal, and what the

responsibilities of the system are.

The external environment is represented only by actors.

8/9/2019 26252990 UML Complete


46

RELATIONSHIP:

What is Relationship?

Relationship between use case and actor.

Communicates

Relationship between two use cases

Extends

Uses

Notation used to show the relationships:

<< >>

8/9/2019 26252990 UML Complete


47

RELATIONSHIP:

Relationship between use case and actor is often referred as

“communicates” .

Relationship between two use cases is refereed as either uses

or extends.

USES:

- Multiple use cases share a piece of same functionality.

- This functionality is placed in a separate use case rather thandocumenting in every use case that needs it.

8/9/2019 26252990 UML Complete


48

RELATIONSHIP:

Contd...

A uses relationship shows behavior that is common to one or

more use cases.

EXTENDS:

It is used to show optional behavior, which is required only

under certain condition.

8/9/2019 26252990 UML Complete


49

USE CASE diagram:

Use case diagram for the shown functionality.

Balance status

report

Withdraw cash

Validation

uses

CustomerClerk

Manager

extends

ATM

8/9/2019 26252990 UML Complete


50

Objective of the second module

To understand and capture the detailed specification of a system to be

developed, from user perspective.

8/9/2019 26252990 UML Complete


51

Module-3

8/9/2019 26252990 UML Complete


52

Beginning Analysis and Design

Completion of first version of use case diagram initiates the processes

of analysis and design.

UML provides the framework to carry out the process of analysis and

design in form of set of diagrams.

Every diagram and notation used in the diagram carries the semantics.

First step towards analysis and design is to specify the flow of events.

8/9/2019 26252990 UML Complete


53

Flow of Events:

A flow of events document is created for each use case.

Details about what the system must provide to the actor when the use isexecuted.

Typical contents

– How the use case starts and ends – Normal flow of events

– Alternate flow of events

– Exceptional flow of events

Typical Course of Events has:

Actor Action(AA)

System Response(SR)

8/9/2019 26252990 UML Complete


54

Normal Flow of Events:

For withdrawal of cash:

1.(SR) The ATM asks the user to insert a card.

2.(AA) The user inserts a cash card.

3.(SR) The ATM accepts the card and reads its serial number.

4.(SR) The ATM requests the password.

5.(AA) The user enters 1234.

6.(SR) The ATM verifies the serial number and password with the

bank and gets the notification accordingly.

7.(SA)The ATM asks the user to select the kind of transaction.

8.(AA)User selects the withdrawal.

8/9/2019 26252990 UML Complete


55


Contd...

9.(SR)The ATM asks for the amount of cash; user enters Rs. 2500/-

10.(SR)The ATM verifies that the amount of cash is within predefined

policy limits and asks the bank, to process the transaction which

eventually confirms success and returns the new account balance.

11.(SR) The ATM dispenses cash and asks the user to take it.

12.(AA) The user takes the cash.

13.(SR) The ATM asks whether the user wants to continue.

14.(AA) The user indicates no.

8/9/2019 26252990 UML Complete


56


Contd...

15.(SR) The ATM prints a receipt, ejects the card and asks the user to

take them

16.(AA) The user takes the receipt and the card.

17.(SR) The ATM asks a user to insert a card.

8/9/2019 26252990 UML Complete


57

Alternative Flow of Events:

For withdrawal of cash use case:

9. The ATM asks for the amount of cash; the user has change of mind

and hits the “cancel”.

8/9/2019 26252990 UML Complete


58

Exceptional Flow of Events:

For withdrawal of cash use case:

3 Suspicious pattern of usage on the card.

10 The machine is out of cash.

11 Money gets stuck in the machine.

8/9/2019 26252990 UML Complete


59

Why flow of events?

It helps in understanding the functionality of a system to be developed.

Flow of events helps in finding objects of the system to be developed.

Happens to be most important and very first step towards analysis and

design.

8/9/2019 26252990 UML Complete


60

What is Scenario?

The functionality of the use case is captured in flow of the

events.

A scenarios is one path through the flow of events for the use

case.

Scenarios are developed to help identify objects, classes and

object interactions for that use case.

8/9/2019 26252990 UML Complete


61

Objective of the third module

To understand the flow of each functionality and find out the objects

and methods required to build the system.

8/9/2019 26252990 UML Complete


62

Module-4

8/9/2019 26252990 UML Complete


63

USE CASE Realizations:

The use case diagram presents an outside view of the system

Interaction diagrams describe how use cases are realized as

interactions among societies of objects.

Two types of interaction diagrams

– Sequence diagrams

– Collaboration diagrams

8/9/2019 26252990 UML Complete


64

What is Interaction diagram?

Interaction diagrams are models that describe how groups of objects

collaborate in some behavior

There are 2 kinds of interaction diagrams

• Sequence diagram

• Collaboration diagram

Sequence diagrams are a temporal representation of objects and their

interactions

Collaboration diagrams are spatial representation of objects, links and

interrelations

8/9/2019 26252990 UML Complete


65

What is sequence diagram?

Typically these diagrams capture behaviors of the single

scenario.

Shows object interaction arranged in time sequence.

They show sequence of messages among the objects.

It has two dimensions, vertical represents time & horizontal

represents objects.

Components of sequence diagram:

-objects

-object lifeline

-Message

-pre/post conditions.

8/9/2019 26252990 UML Complete


66

OBJECT & OBJECT LIFE LINE:

Object are represented by rectangles and name of the objects are

underlined.

Object life line are denoted as dashed lines. They are used to

model the existence of objects over time.

Name:Class

8/9/2019 26252990 UML Complete


67

MESSAGES:

They are used to model the content of communication between objects.

They are used to convey information between objects and enable objects

to request services of other objects.

The message instance has a sender, receiver, and possibly other

information according to the characteristics of the request.

Messages are denoted as labeled horizontal arrows between life lines.

The sender will send the message and receiver will receive the message.

8/9/2019 26252990 UML Complete


68

MESSAGES:

Contd…

May have square brackets containing a guard conditions. This is a Boolean

condition that must be satisfied to enable the message to be sent.

May have have an asterisk followed by square brackets containing an iteration

specification. This specifies the number of times the message is sent.

May have return list consisting of a comma -separated list of names that designate

the values of returned by the operation.

Must have a name or identifier string that represents the message.

May have parentheses containing an argument list consisting of a comma separated

list of actual parameters passed to a method.

8/9/2019 26252990 UML Complete


69

:Customer :ATM :Bank

Request password

Verify accountEnter the password

Account o.k.Request option

Enter option

Request amount

Enter the amountUpdate transaction

Transaction commit

Insert card

Dispense cash

Request take cash

Take cash

Request continuation

Terminate

Print receipt ,eject card

Request take cardTake card

Display main screen and prompt for the card.

:Transaction

Create

Transaction

Transaction

complete

Sequence diagram [for withdrawal of cash, normal flow]

8/9/2019 26252990 UML Complete


70

What is Collaboration diagram?

Collaboration diagrams illustrate the interaction between the objects,

using static spatial structure.

Unlike sequence diagram the time is not explicitly represented in these

diagrams

In collaboration diagram the sequence of messages is indicated bynumbering the messages. The UML uses the decimal numbering

scheme.

In these diagrams, an actor can be displayed in order to represent the

triggering of interaction by an element external to the system.

This helps in representing the interaction, without going into the

details of user interface.

8/9/2019 26252990 UML Complete


71

Components of collaboration diagram:

Named objects

Links: Links are represented by a continuous line between objects, and

indicates the exchange of messages.

Messages has following attributes:

• Synchronization --thread name, step within thread.

• Sequence number

• Message labels : The name of the message often corresponds to an operation

defined in the class of the object that is the destination of the message.

Message names may have the arguments and return values.

• *[iteration].

• It uses decimal notation.

• Message direction.

8/9/2019 26252990 UML Complete


72

Semantics of components:

Object names identify which objects are participating and the links

show which objects collaborate

A link between two objects must exist for one object to send message

to another and vice a versa. Messages in the collaboration diagram get transformed to more

detailed signature.

They use the decimal notation system for numbering the messages.

The direction of the message defines the sender and receiver of

the message

8/9/2019 26252990 UML Complete


73

The elements of message:

Predecessor

Role names

Message qualifiers

– Iteration expression

– Parameters – Return values

– Guard

– Message stereotypes

Concurrent thread sequencing

Thread dependencies

Message expression

[Pre] A1:*(expression):doIt(p,r):return value

8/9/2019 26252990 UML Complete


74

The examples of message:

4:Display(x,y) Simple

message

3.3.1:Display(x,y) Nested

message

4.2:subtract[Today,Birthday]:age Nested

message with

return value

[Age >=18] 6.2:Vote() Conditional

message

4.a,b.6/c.1:Turnon(Lamp) Synchro. with

other flow of

execution

1*:wash() Iteration

3.a,3.b/4*||[i:=1..n]:Turnoff() Paralleliteration

8/9/2019 26252990 UML Complete


75

Collaboration diagram [for withdrawal of cash, normal flow.]

1. Insert card

Enter password, Enter kind

Enter amount,

Take cash, Take card

cancel,Terminate, Continue

Display main screenunreadable card message,

request password,

request kind, request amount,

canceled message, eject card, failure message,

dispense cash, request take cash

request continuation,

print receipt, request take card

bad account message,

bad bank account messageVerify account,

process transaction

Transaction succeed

Transaction failed

account o.k.

bad account, bad password,

bad bank code

Create Transaction

Transaction completeCUST-

OMER

BANK

ATM

TRANSA-

CTION

8/9/2019 26252990 UML Complete


76

Objective of the fifth module

To know the interaction among the objects in temporal and spatial

form.

To know how objects collaborate among each other and hence

delegate the responsibility to the respective objects.

To understand how the messages get matured with more information.

8/9/2019 26252990 UML Complete


77

Module-5

8/9/2019 26252990 UML Complete


78

What is Class diagram?

A class diagram shows the existence of classes and their relationshipsin the logical view of a system

UML modeling elements in class diagrams are: – Classes, their structure and behavior.

– relationships components among the classes like association,aggregation, composition, dependency and inheritance

– Multiplicity and navigation indicators – Role names or labels.

8/9/2019 26252990 UML Complete


79

Major Types of classes:

Concrete classes

A concrete class is a class that is instantiable; that is it can have different

instances.

Only concrete classes may be leaf classes in the inheritance tree.

Abstract classes An abstract class is a class that has no direct instance but whose descendants

classes have direct instances.

An abstract class can define the protocol for an operation without supplying a

corresponding method we call this as an abstract operation.

An abstract operation defines the form of operation, for which each concrete

subclass should provide its own implementation.

8/9/2019 26252990 UML Complete


80

RELATIONSHIP:

Association

Aggregation

Composition

Inheritance

Dependency

Instantiation

8/9/2019 26252990 UML Complete


81

ASSOCIATION:

These are the most general type of relationship:

It denotes a semantic connection between two classes

It shows BI directional connection between two classes

It is a weak coupling as associated classes remain somewhat

independent of each other

Example:

CUSTOMER ATM system

8/9/2019 26252990 UML Complete


82

AGGREGATION:

This is a special type of association

The association with label “contains” or “is part of” is an

aggregation

It represents “has a “ relationship

It is used when one object logically or physically contains other

The container is called as aggregate

It has a diamond at its end

The components of aggregate can be shared with others It expresses a whole - part relationships

8/9/2019 26252990 UML Complete


83

AGGREGATION:

Example:

Customer ATM card

8/9/2019 26252990 UML Complete


84

COMPOSITION:

This is a strong form of aggregation

It expresses the stronger coupling between the classes

The owner is explicitly responsible for creation and deletion of

the part

Any deletion of whole is considered to cascade its part

The aggregate has a filled diamond at its end

Window Client Area

8/9/2019 26252990 UML Complete


85

INHERITANCE:

The inheritance relationship helps in managing the complexity by

ordering objects within trees of classes with increasing levels of

abstraction. Notation used is solid line with arrowhead,shown below.

Generalization and specialization are points of view that are based on

inheritance hierarchies.Account

SavingAccountCurrentAccount

8/9/2019 26252990 UML Complete


86

DEPENDENCY:

Dependency is semantic connection between dependent and

independent model elements.

This association is unidirectional and is shown with dotted

arrowhead line.

In the following example it shows the dependency relationshipbetween client and server.

The client avails services provided by server so it should have

semantic knowledge of server.

The server need not know about client.

Client Server

8/9/2019 26252990 UML Complete


87

INSTANTIATION

This relationship is defined between parameterized class and

actual class.

Parameterized class is also referred as generic class.

A parameterized class can’t have instances unless we first

instantiated itExample:

Queue<int>

Queue

Element

8/9/2019 26252990 UML Complete


88

What is Cardinality? :

Definition: Number of instances of each class involved in the dialogue is

specified by cardinality.

Common multiplicity values:

Symbol Meaning

1 One and only one

0..1 Zero or one

M…N From M to N (natural integer)

0..* From zero to any positive integer

1..* From one to any positive integer

Also thought can be given about navigability to every applicable relationship.

8/9/2019 26252990 UML Complete


89

Reaching the class diagram:

In collaboration diagram we have shown the objects, their interaction and

detailed message signature.

This information is carried forward to the class diagram.

At this point,we group the similar objects and form classes.

Messages get mapped to responsibilities for respective classes. Find the attributes for every class.

Transform the links to appropriate relationships.

Relationship is further refined with respect to multiplicity and navigability.

This complete procedure brings the minimal class diagram [for withdraw cash use

case, normal flow.]

8/9/2019 26252990 UML Complete


90

Class diagram [for withdrawal of cash, normal flow]

Customer

Transaction

1

0..*

1

0..*ATMSystem

1..*

1..*

1..*

1..*

Bank[Branch]1

1..*

1

1..*1

11

1

8/9/2019 26252990 UML Complete


91

What more to the Class Diagram?

Till this slide we have worked out the essentials of class diagram for

withdrawal of cash use case, normal flow of events.

Similar exercise required to be carried out for every scenario and clubbed all

in the class diagram.

At this point, we refine this integrated class diagram to add further finedetails. Approximate sketch for this class diagram has been shown at the end

of this module.

Refinement attributes should be updated right from sequence diagram to

class diagram.

Next few slides will take into the discussion of refinement attributes.

This process of iterative and incremental development will continue till there

is no change in two consecutive iteration.

8/9/2019 26252990 UML Complete


92

OOAD---Iterative & Incremental Approach

Identify objects

Identify Messages

Group Objects

into classes

Identify & classify

Class relationshipsIdentify class

behavior

Group classes

into domains

Validate Classes

& Objects

8/9/2019 26252990 UML Complete


93

Refinement attributes:

Stereotypes:

Stereotypes are part of the range of extensibility mechanism provided

by UML

It permits user to add new model element classes on top of the kernel

predefined by UML

8/9/2019 26252990 UML Complete


94


Contd…

Constraints:

Constraints are functional relationship between the entities and object

model. The entities include objects, classes, attributes, association,

links. A constraint restricts the values that entities can assume.

UML doesn't specify a particular syntax for constraints, other than

they should appear between braces, so they may therefore be

expressed using natural language, pseudo code, navigation expression

or mathematical expression

UML1.2 does prefer the use of a constraint language OCL i.e. Object

Constraint Language, which is subset of UML.

8/9/2019 26252990 UML Complete


95


Transaction

Window

length/width

{No. of transaction <=5 /day}

{0.8<=length/width <= 1.5}

Constraint on the same class.

A constraint between the

properties of the same object

No window will have an aspect ratio i.e. (length/width) of less than 0.8 or > 1.5

Number of withdrawal transaction should be less than five per day.Example:Constraints

8/9/2019 26252990 UML Complete


96


Qualifier:

UML provides a role of constraint notation to indicate different kind

of collections that may be inherent in the analysis model

Common role constraints for multi valued roles include

{ordered} Collection is maintained in sorted manner

{bag} Collection may have multiple copies of same item.

{set} Collection may have at most one copy of given item.

Some constraints may be combined such as: {ordered set}

8/9/2019 26252990 UML Complete


97


Qualifier:

Another common design scheme is to use a key value to retrieve an

item from the collection. This is called as qualified association and the

key value as qualifier.

A qualified association is the UML equivalent of a programmingconcept variously known as associative arrays, maps,dictionaries

A qualified association relates two object classes and a qualifier

The qualifier is a special attribute that reduced the effective

multiplicity of an association.

One to many and many to many association may be qualified.

8/9/2019 26252990 UML Complete


98


Check for many to many relationship, if any, normalize with qualifier

or association class.

Check for the scope forming abstract classes and template classes.

Check for helper functions.

Thought can be given for using the design patterns.

8/9/2019 26252990 UML Complete


99

Objective of the fifth module:

Learn to build the architecture, which contains the entire information

of the system to be developed.

It is this architecture which is called as BLUE PRINT is handed over

for coding.

8/9/2019 26252990 UML Complete


100

Refined Class diagram [for withdrawal of cash]

SavingAccount

AccountAccessor

<<abstract>>

TellerScreen

ATMScreenBankAssociates

CashierStation

person<<abstract>>

Cash

BatchJob

NoteHelpForBankCard

ATMSystem

BankComputer

Area

BankCard

Bank[Branch]11

1..*1..*

Customer

1

0..1

1

0..1

11

Account<<abstract>>

1

1

1

1

1..*

1

1..*

1

Transaction

11..*

11..*

Slips

CurrentAccount

Few more relationship can be further added to the shown diagram:

8/9/2019 26252990 UML Complete


101

Module-6

8/9/2019 26252990 UML Complete


102

What is state transition diagram?

A state transition diagram shows the states of a single object, the

events or the messages that cause a transition from one state to another

and the action that result from a state change.

A state transition diagram will not be created for every class in the

system. Components of State Diagram:

– Start State

– Stop state

– State Transition

8/9/2019 26252990 UML Complete


103

Semantics of every components:

State: A state is a condition during the life of an object when it satisfies

some condition, performs some action, or waits for an event.

The UML notation for a state is a rectangle with rounded corners.

Special states:There are two special states.Start state: Each state diagram must have one and only one start

state. Notation for start state is “filled solid circle”.

Stop State: An object can have multiple stop states. Notation for stop

state is bull’s eye.

S ti f t

8/9/2019 26252990 UML Complete


104

Semantics of every components:

Contd...

State transition: A state transition represents a change from an

originating to a successor state.

Transition label: event name[guard condition] / action

State Transition Diagram

8/9/2019 26252990 UML Complete


105

State Transition Diagram [for Account class. ]

Operational

Dormant

Open

seized

transaction request[ validate ] / update()

close

no transaction / Transfer_to_Dormant_Ledger

fill_the_request_form / update()

Fraud or authorized instruction[Validate]

/ lockAccount()

matter_resolved[ validate ] / unlockAccount()

request and fill the form for new saving account[ validate ] / process

fill_the_request_form/update(

)

transactionStrart / Transfer_to_main_ledger ()

Note:Account can be closed from open state as well

8/9/2019 26252990 UML Complete


106

More about State Diagram:

A state diagram will not be created for every class.

state diagrams are used only for those classes that exhibit interesting

behavior.

State diagrams are also useful to investigate the behavior of user

interface and control classes. State diagram are used to show dynamics of a individual class

h i i i di ?

8/9/2019 26252990 UML Complete


107

What is activity diagram?

It is a special kind of state diagram and is worked out at use case level.

These are mainly targeted towards representing internal behavior of a a

use case.

These may be thought as a kind of flowchart.

Flowcharts are normally limited to sequential process; activity diagramscan handle parallel process.

Activity diagrams are recommended in the following situations:

Analyzing use case

Dealing with multithreaded application

Understanding workflow across many use cases.

Consistency Checking

8/9/2019 26252990 UML Complete


108

Consistency Checking

Consistency checking is the process of ensuring that,information in both static view of the system(class diagram)and the dynamic view of the system(sequence andcollaboration diagram) is telling the same story.

Obj i f h i h d l

8/9/2019 26252990 UML Complete


109

Objective of the sixth module

Understand the dynamic behavior of a class

Way to find the parallel processes at use case level.

8/9/2019 26252990 UML Complete


110

Module-7

Wh i di ?

8/9/2019 26252990 UML Complete


111

What is component diagram?

COMPONENT DIAGRAM:

Component diagrams illustrate the organizations and dependencies

among software components.

A component may be

• A source code component

• A run time components

• An executable component

• Dependency relationship.

Component Diagram

8/9/2019 26252990 UML Complete


112

Component Diagram [for withdrawal of cash]

policy.dll

BranchBank.dllcustomer.dll

ATM.exe

BranchBank.exe

BankServer.exe

Wh t i d l t di ?

8/9/2019 26252990 UML Complete


113

What is deployment diagram?

A deployment diagram shows the relationship among software and hardware

components in the delivered system.

These diagram include nodes and connections between nodes.

Each node in deployment diagram represents some kind of computational unit, in most

cases a piece of hardware.

Connection among nodes show the communication path over which the system willinteract.

The connections may represent direct hardware coupling line RS-232 cable, Ethernet

connection, they also may represent indirect coupling such as satellite to ground

communication.

D l t di

8/9/2019 26252990 UML Complete


114

Deployment diagram

ATM_ machine

Bank_ server

BranchBank_

EthernetEthernet

Bank.exe

BankServer.exeATM.exe

Obj ti f th th d l

8/9/2019 26252990 UML Complete


115

Objective of the seventh module:

To understand the organization of software modules and their

deployment on the respective hardware.

8/9/2019 26252990 UML Complete


116

Module-8

Understanding the project culture

8/9/2019 26252990 UML Complete


117

Understanding the project culture

It may be:

1.Calendar Centric

2.Requirement Centric

3.Documentation Centric

4.Quality Centric

5.Architecture Centric

U d t di th j t’ lt

8/9/2019 26252990 UML Complete


118

Understanding the project’s culture

Architecture driven projects represent the most mature style of development.

These projects are characterized by a focus on creating a frame work that satisfies all

known requirement, yet is resilient enough to adapt to those requirements, that are not yet

known or well understood.

In every sense of the word, architect-driven policies are in evolutionary step beyond

requirement driven policies.

Architecture driven style of development is usually the best approach for the creation of most

complex software intensive systems

Understanding the project’s culture

8/9/2019 26252990 UML Complete


119

Understanding the project s culture

Architecture driven style of development typically observe thefollowing process:

1. Specify the system’s desired behavior through a collection of

scenarios. (Analysis)2. Create, then validate, an architecture. (Design)

3. Evolve that architecture, making mid-course corrections as

necessary to adopt to new requirements as they are uncovered.

OOAD Architecture Centric

8/9/2019 26252990 UML Complete


120

OOAD---Architecture Centric

What exactly is nature of the well structured object oriented

architecture??

1. A set of classes, typically organized into multiple hierarchies.

2. A set of collaboration that specify how those classes co-operate

to provide various system function.

ESSENCE OF OOAD AND UML

8/9/2019 26252990 UML Complete


121

ESSENCE OF OOAD AND UML

Use case driven

Architecture centricIncremental and iterative approach.

Desire for good Architecture

8/9/2019 26252990 UML Complete


122

g

Those of us who have been trained as architects have this desire

perhaps at the very center of our lives,that one day, some where

somehow, we shall build one building which is wonderful, beautiful,

breathtaking, a place where people can walk and dream for centuries.

CHRISTOPHER ALEXANDER

Same desire should also be applicable in creating software architecture aswell .

8/9/2019 26252990 UML Complete


123

Basic Structural Modeling

Object-Oriented Programming

Aline Yurik

Classes and Types

8/9/2019 26252990 UML Complete


124

Classes and Types

Class is a user-defined type

They can be used as built-in types

Objects are variables

Objects can contain other objects

Two Views of a Class

8/9/2019 26252990 UML Complete


125

Two Views of a Class

Interface (outside view)

– specification of operations

– hides structure and

implementation

Implementation (inside

view)

– state information

– all details – can change without

affecting interface

customer LName

FName

Address

IDGetName( )

GetAddress( )

customer

Database pointer

ID

GetName( )

GetAddress( )

Multiple Implementations

8/9/2019 26252990 UML Complete


126

Multiple Implementations

A single interface mayhave multiple

implementations

Implementations can be

changed withoutchanging interfaces

Implementations can be

improved without

affecting rest of system

Examples:Complex Numbers

– Cartesian coordinates

– Polar coordinates

Set Representation – array

– linked list

– hash table

Sort Algorithms

– insertion sort

– quick sort

Polymorphism

8/9/2019 26252990 UML Complete


127

Polymorphism

Instances of classes

with superclasses are

polymorphic

They have more thanone type

Person

Employee

Manager

Chris

Polymorphic Operations

8/9/2019 26252990 UML Complete


128

Polymorphic Operations

Operations defined for

arguments of a class type

also accept arguments of

subclass type

Operation marry(Person)

– expects an arguments of

type Person

– also accepts Employee or

Manager

Person

Employee

Manager

Class Modeling Notation

8/9/2019 26252990 UML Complete


129

Class Modeling Notation

Person

name: string

age: integer

Class with Attributes:

(Person)

Joe Smith

24

(Person)

Mary Sharp

52

Objects with Values:

change-job

change-address

Class Modeling Notation cont

8/9/2019 26252990 UML Complete


130

Class Modeling Notation - cont.

Class-Name

attribute-name-1: data-type-1 = default-value-1

attribute-name-2: data-type-2 = default-value-2

…

operation-name-1(argument-list-1): result-type-1

operation-name-2(argument-list-2): result-type-2

…

Class Relationships

8/9/2019 26252990 UML Complete


131

Class Relationships

Relationships are connections between classes

Dependencies

– one class uses another

Generalizations

– connect generalized classes to more specialized ones

Associations

– structural relationships among instances

Example: Relationships

8/9/2019 26252990 UML Complete


132

Example: Relationships

Window

open()

close()

move()

display()

handleEvent()

ConsoleWindow DialogBox Control

Event

Generalization Generalization

Dependency

Association

Dependency

8/9/2019 26252990 UML Complete


133

Dependency

“Using” relationship

Change in one class may effect another

One class may use another as an argument in an

operation

FilmClip

name

playOn(c : Channel)start()

stop()

reset()

Channel

Generalization

8/9/2019 26252990 UML Complete


134

Generalization

Relationship between ageneral class and a more

specific class

General class:

– super-class, parent

Specific class:

– subclass, child

is-a relationship

– is-a-kind-of

Child inherits properties of parents

Child may inherit some or all attributes and

operations of parents

Child may have its own

attributes and functions Single parent - single

inheritance

More than one parent -

multiple inheritance

Example: Generalization

8/9/2019 26252990 UML Complete


135

Example: Generalization

Shape

origin

move()resize()display()

Rectangle

corner : Point

Circle

radius : Float

Polygon

points : List

display()

Square

Is-a Relationships

8/9/2019 26252990 UML Complete


136

Superclasses and SubclassesClasses are related via

is-a relationships

– employee is-a person

– manager is-a employee – car is-a vehicle

– truck is-a vehicle

Superclasses (base classes)

– more general classes

– Person is a superclass of

Employee

Subclasses (derived

classes)

– more specialized classes

– Manager is a subclass of

Employee

Example: Superclasses and

8/9/2019 26252990 UML Complete


137

Subclasses

Person

Employee Student

Manager

Inheritance (is-a relationship)

8/9/2019 26252990 UML Complete


138

Inheritance (is a relationship)

Bank account balance

holder

account #

list of deposits

list of withdrawals

deposit(amt)withdraw(amt)

balance?

transactions?

savings account

post_interest(int_rate)

overload:

transactions?

checking accountlist of checks

Check(num, amt)

overload:

transactions?Int-checking account

interest earned

Inheritance - cont

8/9/2019 26252990 UML Complete


139

Inheritance cont.

Classes inherit data and operations of their

superclasses

Inheritance allows software to be organized

the way people think

– people organize things hierarchically

– generalization and specialization are common

ways to manage complexity

Inheritance leads to software reuse

Inheritance of Specification vs.

8/9/2019 26252990 UML Complete


140

Inheritance of Implementation Sometimes inherited

operations need to be

redefined

Inheritance of specification

– idea behind the field

– mandatory inheritance

– leads to reuse of design

Inheritance of

implementation

– sometimes desirable

– sometimes needs to beredefined for

correctness or

efficiency

Association

8/9/2019 26252990 UML Complete


141

Association

Structural relationship

How objects are connected to each other

Binary association

– between two classes

Unary association

– within the same class

N-ary association

– multiple classes

Association Attributes

8/9/2019 26252990 UML Complete


142

Association Attributes

Name and direction

– e.g., works for

Role

– what role each class plays

Person CompanyWorks for

Person Company

+employer +employee

Association Attributes - cont.

8/9/2019 26252990 UML Complete


143

Association Attributes cont.

Multiplicity

– how many object are involved on each side of the

association

Aggregation

– whole/part relationship

Person Company*1..*

+employer +employee

*1..*

Department

Company

1

*

1

*

Aggregation: a-part-of

R l i hi

8/9/2019 26252990 UML Complete


144

Relationship

document paragraph sentence

microcomputer

monitor system box mouse keyboard

chassis CPU RAM fan

1 * 1 *

1

* 0..1

* 0..1

Aggregation and Generalization

8/9/2019 26252990 UML Complete


145

Aggregation and Generalization

Aggregation

– several components

make up an aggregate

– a-part-of relationshipGeneralization

– superclasses and

subclasses

– is-a relationship

lamp

base shade switch

lamp

fluorescent

lamp

incadescent

lamp

Abstract vs. Concrete Class

8/9/2019 26252990 UML Complete


146

Abstract vs. Concrete Class

Abstract class

– has no direct instances

– subclasses have direct

instances – logical superclass

Concrete class

– has direct instances

employee

year-to-date earnings

compute pay {abstract}

hourly employee

hourly rate

overtime pay

compute pay

salaried employee

weekly rate

compute pay

Modeling Simple Dependencies

8/9/2019 26252990 UML Complete


147

ode g S p e epe de c es

Connection between a class and another

class, used as a parameter in an operation

CourseSchedule

add(c : Course)

remove(c : Course)

Course

Iterator

<<friend>>

Modeling Single Inheritance

8/9/2019 26252990 UML Complete


148

g g

Put common attributes and operations in thegeneral class Security

presentValue()

history()

CashAccount

interestRate

presentValue()

Stock

presentValue()

Bond

presentValue()

Property

assessments

presentValue()

SmallCapStock LargeCapStock

Modeling Structural

R l ti hi

8/9/2019 26252990 UML Complete


149

Relationships

School

Student

1..*

*

1..*

*

member

Course

** **

attendsInstructor

* 1..** 1..*

teaches

Department

1 1..*1 1..*

Has

1..*

1..*

1..*

1..*

0..1

0..1

0..1

+chairperson0..1

1..*

1..*

assignedTo

1..*

1..*

Multiple Inheritance

8/9/2019 26252990 UML Complete


150

p

Class can inherit features from more than

one superclass

Feature from the same ancestor found among

multiple paths is inherited once

Any ambiguities should be resolved in

implementations

– need to explicitely spell out which feature to use

Example: Multiple Inheritance

8/9/2019 26252990 UML Complete


151

p p

vehicle

land vehicle water vehicle

car amphibious vehicle boat

Example: Multiple Inheritance

8/9/2019 26252990 UML Complete


152

p p

Brand X

Products

Brand Y

ProductsComputers

Brand X

Computers

Brand Y

Computers

Brand X

Mainframes

Brand X

PCs

Brand YMinicomputers

Structural Diagrams

8/9/2019 26252990 UML Complete


153

g

Class Diagram

– shows classes, interfaces, collaborations and their

relationships

Object Diagram – shows objects and their relationships

Component Diagram

– shows components and their relationships

Deployment Diagram

– shows nodes and their relationships

Diagrams

8/9/2019 26252990 UML Complete


154

g

Structural Diagrams:

Class diagrams

Object diagrams

Component diagrams

Deployment diagrams

Behavioral Diagrams:

Use case diagrams

Sequence diagrams

Collaboration

diagrams

State chart diagrams

Class Diagrams

8/9/2019 26252990 UML Complete


155

g

Contents:

Classes

Interfaces

Collaborations Relationships

– dependency

– generalization

– association

Common Uses:

Model vocabulary of a

system

Model simplecollaborations

Model logical

database schema

Example: Class Diagram

8/9/2019 26252990 UML Complete


156

p gCompany

Headquarters

Office

address : String

voice : Number

Department

name : Name

** **

Location

0..1

*

0..1

*

Person

name : Name

employeeID : Integer

title : String

getPhoto(p : Photo)

getSoundBite()

getContactInfo()

getPersonalRecords()

1..*

*

1

*

+member 1..*

*

+manager 1

*

ContactInfo

address : String

PersonnelRecord

taxID

employmentHistory

salaryISecureInfo

Modeling Simple Collaborations

8/9/2019 26252990 UML Complete


157

g p

Collaboration: – class works together with

others to carry out bahavior

Identify function or

behavior to model

Identify classes, interfaces

that participate in

collaboration

Use scenarios

CollisionSensor

PathAgent*1 *1

SteeringMotor MainMotor

Driver 1

1

1

1

1 11 1

Motor

move(d : Di rect ion, s : Speed)

stop()

resetCounter()

status() : Status

distance() : Integer

-- seek path

-- avoid obstacles

Modeling a Logical Database

Schema

8/9/2019 26252990 UML Complete


158

SchemaClass diagrams are a superset of entity relationship

diagrams used for DB modeling

Identify classes representing DB data as persistent

Avoid cyclic, 1-to-1 and N-ary associations – create intermediate classes to simplify structure

Move business rules to a layer of classes separate

from persistent classes

Example: Modeling a Schema

8/9/2019 26252990 UML Complete


159

p g

School

name : Name

address : String

phone : Number

addStudent()

removeStudent()

getStudent()getAllStudents()

addDepartment()

removeDepartment()

getDepartment()

getAllDepartments()

<<persistent>>

Student

name : Name

studentID : Number

<<persistent>>

*

1..*

*

1..*

Member

Course

name : Name

courseID : Number

<<persistent>>

** **

Attends

Instructor

name : Name

<<persistent>>

1..*

*

1..*

*

Teaches

Department

name : Name

addInstructor()

removeInstructor()getInstructor()

getAllInst ructors()

<<persistent>>

1 1..*1 1..*

Has

1..*

1..*

1..*

1..*

1..*

1..*

1..*

1..*

AssignedTo

0..1

0..1

0..1

+chairperson0..1

8/9/2019 26252990 UML Complete


160

Appendix-A

Strong recommendation

8/9/2019 26252990 UML Complete


161

Object Technology

– David A. Taylor

Object Oriented Analysis and design with Applications

– Grady Booch

UML distilled

– Martin Fowler Instant UML

– Pierre - Alain Muller Software Engineering

– Roger S Pressman

REFERENCES

8/9/2019 26252990 UML Complete


162

Contd...Object Oriented Modeling and Design

– James Rumbaugh

Object Oriented Software Engineering

– Ivar Jacobson

Clouds to code

– Jesse Liberty

Applying use cases

– Geri Schneider

– Jason p. Winters

UML Toolkit

– Hans-Eriksson and Magnus Penker

Version1.1

8/9/2019 26252990 UML Complete


THANK-U!

26252990 uml complete

Documents