Uml
-
Upload
janas-khan -
Category
Documents
-
view
215 -
download
0
description
Transcript of Uml
![Page 1: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/1.jpg)
Name: Janas KhanPresentationGeneral Discussion With Friends
Sample Activity Diagram
1
![Page 2: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/2.jpg)
2
![Page 3: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/3.jpg)
Sequence diagram
3
![Page 4: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/4.jpg)
Synchronous Messages
Nested flow of control, typically implemented as an operation call.
The routine that handles the message is completed before the caller
resumes execution.
:A :B
doYouUnderstand()
Caller Blocked
return (optional)yes
![Page 5: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/5.jpg)
Asynchronous
In this type of message the flow is not interrupted and response is not
awaited.
An asynchronous message is drawn with a half-arrowhead, that
(one with only one wing instead of two) as shown below
5
![Page 7: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/7.jpg)
Example with Self Call
7
![Page 8: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/8.jpg)
Example of Sequence Diagram
8
![Page 9: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/9.jpg)
Sample Sequence Diagram
a : Assembly part : CatalogEntry
getNumber()
: Client
count(part)
return number
Lifeline
Activation(
optional)
Messages
control returns to the
sender of the message
(optional)
![Page 10: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/10.jpg)
Conditional Message: Sequence Diagram
: Client: Order : CatalogEntry
[s>=qty] OrderLine(qty,part)
add(qty,part)
: OrderLine
getCost()
return cost
getStockLevel(part)
return s
![Page 11: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/11.jpg)
Combined Fragment
Combined fragment is an interaction fragment which defines a
combination (expression) of interaction fragments.
A combined fragment is defined by an interaction operator and
corresponding interaction operands
For every option there will be corresponding action11
![Page 12: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/12.jpg)
Scenario
i. The user will submit the cheque for withdraw.
ii. Bank will check the amount of cheque to be withdrawn.
iii. Bank will check the amount available in the account.
iv. If balance >amount to be withdrawn then debit transaction is
performed and photo of cheque is stored
v. Otherwise the cheque will be returned with message of insufficient
fund.
12
![Page 13: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/13.jpg)
13
![Page 14: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/14.jpg)
Deployment Diagram
Deployment diagrams are used for describing
the hardware components where software
components are deployed
Deployment diagrams are used to describe
the static deployment view of a system14
![Page 15: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/15.jpg)
Purpose of the Diagram The purpose of deployment diagrams can be
described as:
i. Visualize hardware topology of a system.
ii. Describe the hardware components used to
deploy software components.
iii. Describe runtime processing nodes.
15
![Page 16: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/16.jpg)
Target Audience
Deployment diagrams are useful for system engineers.
An efficient deployment diagram is very important
because it controls the following parameters
i. Performance
ii. Scalability
iii. Maintainability
iv. Portability
16
![Page 17: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/17.jpg)
Artifacts in Deployment Diagram
Nodes:
Nodes are nothing but physical hardwares used
to deploy the application.
Deployment diagrams consist of nodes and their
relationships.17
![Page 18: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/18.jpg)
Sample Scenario
The following deployment diagram is a sample togive an idea of the deployment view of ordermanagement system.
Monitor
Modem
Caching server
Server
18
![Page 19: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/19.jpg)
Application Flow• The application is assumed to be a web based
application which is deployed in a clustered
environment using server 1, server 2 and server
3. The user is connecting to the application using
internet. The control is flowing from the caching
server to the clustered environment.
19
![Page 20: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/20.jpg)
Proposed Component Diagram
20
![Page 21: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/21.jpg)
21
![Page 22: Uml](https://reader034.fdocuments.us/reader034/viewer/2022042817/559c1c541a28ab0f158b462c/html5/thumbnails/22.jpg)
Deployment diagram