Professional Documents
Culture Documents
1
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 sound
knowledge 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.
2
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
3
Module-1
4
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
5
4 Principles of Modeling
✔ Choose your models well
✔ Every model may be expressed at various
levels of precision
✔ The best models are connected to reality
✔ No single model is sufficient
6
What is Software Engineering?
✔ DEFINITION:The application of systematic, disciplined and
qualifiable approach to the development, operation and maintenance
of a software system is software engineering.
✔ Software development life cycle has following stages:
REQUIREMENT
ANALYSIS
DESIGN
IMPLEMENTATION
TESTING 7
Effort Distribution for each stage:
Analysis & design 40 %
Development 20 %
Testing 40 %
8
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.
9
Elements of OO Methodology:
Following are three elements for every OO methodology:
✔ Notation
✔ Process / Method
✔ Tool
10
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
set
of 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]
Systems software
Business processes
13
The Evolution of the UML:
OMG vote’97
Public Feedback Submission to OMG, sept’97 UML1.1
UML0.9
15
UML refers to:
✔ UML things:
Class, component, node, relationship, package etc..
✔ UML diagrams:
Use case diagram, interaction diagram, class diagram, State
diagram,deployment diagram
16
What is Process?
What is Process?
17
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 upon
things like problem domain, implementation technology and skills of
team
✔ Booch,OMT,OOSE and many other methods have well defined
process and UML supports almost all methods
✔ There has been some convergence on development process practices
but there is no consensus for standardization.
✔ Framework for the every stage of software development life cycle.
18
Best Practices followed by Rational Unified Process
19
What is a tool?
✔ It is automated support for every stage of software development
life cycle.
1. Rational Rose
2. Cayenne
3. Platinum
4. Select
20
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
21
Triangle for Success:
✔ All three components play equally important role towards the success
of the project.
Notation
Tool
Method
22
Objective of the first module:
✔ Get introduced with Unified Modeling Language and know the basic
components of software development life cycle.
23
Module-2
24
OO model:
DYNAMIC MODEL
STATIC MODEL
LOGICAL MODEL
PHYSICAL MODEL
25
Models and Views:
✔ 4+1 view of OO model.
– Process view
– Deployment view
– Logical view
– Dynamic view
+
– Use case view
26
UML 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, and
correspond to simplified collaboration diagrams that do not represent
message broadcasts.
➲ Class diagrams represent the static structure in terms of classes and
relationships.
28
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 operation
as a set of actions.
➲ Component diagrams represent the logical components of an
application.
➲ Deployment diagrams represent the deployment of components on
particular pieces of hardware.
29
What is USE CASE diagram?
✔ A use case diagram establish the capability of the system as a whole.
30
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.
32
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.
33
ACTOR:
✔ Actor is always external to the system. They are never part of the
system to be developed.
34
ACTOR:
4-Categories of an actor:
35
ACTOR:
Note:
36
USE CASE:
38
USE CASE:
Contd…
39
USE CASE:
40
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.
41
USE CASE:
42
Grouping USE CASES:
43
OOAD --- USE CASE driven
44
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.
45
RELATIONSHIP:
What is Relationship?
<< >>
46
RELATIONSHIP:
USES:
✔ - Multiple use cases share a piece of same functionality.
✔ - This functionality is placed in a separate use case rather than
documenting in every use case that needs it.
47
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.
48
USE CASE diagram:
Use case diagram for the shown functionality.
Balance status
report
extends
Withdraw cash
Clerk
Customer
uses
Validation
ATM
Manager
49
Objective of the second module
✔ To understand and capture the detailed specification of a system to be
developed, from user perspective.
50
Module-3
51
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.
52
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
is executed.
✔ 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)
53
Normal Flow of Events:
54
Normal Flow of Events:
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.
55
Normal Flow of Events:
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.
56
Alternative Flow of Events:
57
Exceptional Flow of Events:
58
Why flow of events?
59
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.
60
Objective of the third module
✔ To understand the flow of each functionality and find out the objects
and methods required to build the system.
61
Module-4
62
USE CASE Realizations:
63
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
64
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.
65
OBJECT & OBJECT LIFE LINE:
66
MESSAGES:
✔ The sender will send the message and receiver will receive the
message.
67
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.
68
Sequence diagram [for withdrawal of cash, normal flow]
Request amount
Transaction
:Transaction
Enter the amount
Update transaction
Transaction commit
Transaction
Dispense cash complete
Request take cash
Take cash
Request continuation
Terminate
Print receipt ,eject card
Request take card
Take card 69
Display main screen and prompt for the card.
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 by
numbering 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.
70
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.
71
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
72
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
73
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() Parallel
iteration
74
Collaboration diagram [for withdrawal of cash, normal flow.]
1. Insert card
Enter password, Enter kind
Enter amount,
Take cash, Take card
cancel,Terminate, Continue Create Transaction
Transaction complete
CUST- TRANSA-
OMER Display main screen
unreadable card message,
ATM CTION
request password,
request kind, request amount,
canceled message, eject card, failure message,
dispense cash, request take cash
Transaction succeed
request continuation,
Transaction failed
print receipt, request take card
account o.k.
bad account message, Verify account, bad account,
bad bank account message process transaction bad password,
bad bank code
BANK
75
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.
76
Module-5
77
What is Class diagram?
✔ A class diagram shows the existence of classes and their relationships
in the logical view of a system
78
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.
79
RELATIONSHIP:
✔ Association
✔ Aggregation
✔ Composition
✔ Inheritance
✔ Dependency
✔ Instantiation
80
ASSOCIATION:
CUSTOMER
ATM system
81
AGGREGATION:
82
AGGREGATION:
Example:
83
COMPOSITION:
84
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
CurrentAccount SavingAccount
85
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 relationship
between 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
86
INSTANTIATION
Queue<int>
87
What is Cardinality? :
This complete procedure brings the minimal class diagram [for withdraw cash
use case, normal flow.]
89
Class diagram [for withdrawal of cash, normal flow]
Customer
1
1..*
1..*
ATMSystem
0..*
Transaction 1
1
1..* Bank[Branch]
1
90
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 fine
details. 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.
91
OOAD---Iterative & Incremental Approach
Identify objects
Group Objects
Group classes into classes
into domains
Stereotypes:
✔ It permits user to add new model element classes on top of the kernel
predefined by UML
93
Refinement attributes:
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.
94
Refinement attributes:
Example:Constraints
✔Number of withdrawal transaction should be less than five per day.
Constraint on the same class.
Transaction
Qualifier:
✔ UML provides a role of constraint notation to indicate different kind
of collections that may be inherent in the analysis model
96
Refinement attributes:
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 programming
concept 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.
97
Refinement attributes:
98
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.
99
Refined Class diagram [for withdrawal of cash]
1..* Cash
BankComputer
1
Bank[Branch]
<<abstract>>
AccountAccessor
1 1 <<abstract>>
person
Transaction
CashierStation
1..*
1 ATMScreen
Slips Customer BankAssociates
1..*
1
<<abstract>> TellerScreen
Account
1 0..1
BankCard NoteHelpForBankCard
1
CurrentAccount SavingAccount
100
Module-6
101
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
102
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.
103
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
104
State Transition Diagram [for Account class. ]
request and fill the form for new saving account[ validate ] / process
Open
Dormant
no transaction / Transfer_to_Dormant_Ledger
close
seized
fill_the_request_form / update()
105
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
106
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
diagrams can handle parallel process.
✔ Activity diagrams are recommended in the following situations:
Analyzing use case
Dealing with multithreaded application
Understanding workflow across many use cases.
107
Consistency Checking
108
Objective of the sixth module
✔ Understand the dynamic behavior of a class
109
Module-7
110
What is component diagram?
COMPONENT DIAGRAM:
✔ A component may be
• A source code component
• A run time components
• An executable component
• Dependency relationship.
111
Component Diagram [for withdrawal of cash]
policy.dll
Bank
Server.exe
Branch
customer.dll Bank.dll
Branch
Bank.exe
ATM.exe
112
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 will interact.
✔ 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.
113
Deployment diagram
Branch
Bank_
Bank.exe
Ethernet
Ethernet
Bank_
ATM_ server
machine
BankServer.exe
ATM.exe
114
Objective of the seventh module:
✔ To understand the organization of software modules and their
deployment on the respective hardware.
115
Module-8
116
Understanding the project culture
It may be:
1.Calendar Centric
2.Requirement Centric
3.Documentation Centric
4.Quality Centric
5.Architecture Centric
117
Understanding the project’s culture
✔ Architecture driven projects represent the most mature style of
development.
119
OOAD---Architecture Centric
120
ESSENCE OF OOAD AND UML
121
Desire for good Architecture
122
Appendix-A
123
Strong recommendation
✔ 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
124
REFERENCES
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
125
THANK-U!
126
Course description:
✔ SESSION BREAKUP:
The course will be offered in series of fourteen hours theory session.
One demonstration session on the tool like Rational Rose can be
accompanied.The following is the suggested agenda for the course.
Session Duration
Module-1,2 2-hours demonstration lecture
Module-3 2-hours
Module-4 2-hours
Module-5 4-hours
Module-6 2-hours
Module-7,8 2-hours
Demonstration 2-hours
127
Course description:
✔ REFERENCE AND READING MATERIALS:
Refer to Appendix-A
✔ TEST:
Case study given for exercise can be evaluated as part of the test.
128
Course description:
✔ INSTRUCTION TO THE FACULTY:
Course should emphasize on OO modeling.
Focus should be primarily on understanding UML[1.2] and UML
diagrams and then applying to a problem.
Note: UML toolkit should be refereed for UML notations,their syntax and semantics.
Object oriented analysis and design with applications should be refereed for OO concepts.
129