View
214
Download
1
Category
Preview:
Citation preview
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
UML NOTATION
ClassesIllustrate classes with rectangles divided into compartments. Place the name of the class in the first partition (centered, bolded, and capitalized), list the attributes in the second partition, and write operations into the third.
Active Class
Active classes initiate and control the flow of activity, while passive classes store data and serve other classes. Illustrate active classes with a thicker border.
VisibilityUse visibility markers to signify who can access the information contained within a class. Private visibility hides information from anything outside the class partition. Public visibility allows all other classes to view the marked information. Protected visibility allows child classes to access information they inherited from a parent class.
AssociationsAssociations represent static relationships between classes. Place association names above, on, or below the association line. Use a filled arrow to indicate the direction of the relationship. Place roles near the end of an association. Roles represent the way the two classes see each other.
Note: It's uncommon to name both the association and the class roles.
1
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Multiplicity (Cardinality) Place multiplicity notations near the ends of an association. These symbols indicate the number of instances of one class linked to one instance of the other class. For example, one company will have one or more employees, but each employee works for one company only.
Complex Constraint
Constraint Place constraints inside curly braces {}.
Simple Constraint
Composition and AggregationComposition is a special type of aggregation that denotes a strong ownership between Class A, the whole, and Class B, its part. Illustrate composition with a filled diamond.
Use a hollow diamond to represent a simple aggregation relationship, in which the "whole" class plays a more important role than the "part" class, but the two classes are not dependent on each other. The diamond end in both a composition and aggregation relationship points toward the "whole" class or the aggregate.
2
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
GeneralizationGeneralization is another name for inheritance or an "is a" relationship. It refers to a relationship between two classes where one class is a specialized version of another. For example, Honda is a type of car. So the class Honda would have a generalization relationship with the class car.
In real life coding examples, the difference between inheritance and aggregation can be confusing. If you have an aggregation relationship, the aggregate (the whole) can access only the PUBLIC functions of the part class. On the other hand, inheritance allows the inheriting class to access both the PUBLIC and ROTECTED functions of the super class.
Composition and aggregation
Associations in which an object is part of a whole are aggregations. Composition is a strong association in which the part can belong to only one whole -- the part cannot exist without the whole. Composition is denoted by a filled diamond at the whole end.
Symbol Access
+ Public
- Private
# Protected
3
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Basic Use Case Diagrams and Symbols
SystemDraw your system's boundaries using a rectangle that contains use cases. Place actors outside the system's boundaries.
Use Case
Draw use cases using ovals. Label with ovals with verbs that represent the system's functions.
ActorsActors are the users of a system. When one system is the actor of another system, label the actor system with the actor stereotype.
4
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Basic Sequence Diagram Symbols and NotationsClass rolesClass roles describe the way an object will behave in context. Use the UML object symbol to illustrate class roles, but don't list object attributes.
ActivationActivation boxes represent the time an object needs to complete a task.
5
RelationshipsIllustrate relationships between an actor and a use case with a simple line. For relationships among use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates that one use case is needed by another in order to perform a task. An "extends" relationship indicates alternative options under a certain use case.
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
MessagesMessages are arrows that represent communication between objects. Use half-arrowed lines to represent asynchronous messages. Asynchronous messages are sent from an object that will not wait for a response from the receiver before continuing its tasks.
Various message types for Sequence and Collaboration diagrams
LifelinesLifelines are vertical dashed lines that indicate the object's presence over time.
6
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Destroying Objects
Objects can be terminated early using an arrow labeled "< < destroy > >" that points to an X.
LoopsA repetition or loop within a sequence diagram is depicted as a rectangle. Place the condition for exiting the loop at the bottom left corner in square brackets [ ].
Basic Collaboration Diagram Symbols and Notations
Class roles
Class roles describe how objects behave. Use the UML object symbol to illustrate class roles, but don't list object attributes.
Association roles
Association roles describe how an association will behave given a particular situation. You can draw association roles using simple lines labeled with stereotypes.
7
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
MessagesUnlike sequence diagrams, collaboration diagrams do not have an explicit way to denote time and instead number messages in order of execution. Sequence numbering can become nested using the Dewey decimal system. For example, nested messages under the first message are labeled 1.1, 1.2, 1.3, and so on. The condition for a message is usually placed in square brackets immediately following the sequence number. Use a * after the sequence number to indicate a loop.
Basic Statechart Diagram Symbols and NotationsStatesStates represent situations during the life of an object. You can easily illustrate a state in SmartDraw by using a rectangle with rounded corners.
TransitionA solid arrow represents the path between different states of an object. Label the transition with the event that triggered it and the action that results from it.
Final State
An arrow pointing to a filled circle nested inside another circle represents the object's final state.
Synchronization and Splitting of Control
A short heavy bar with two transitions entering it represents a synchronization of control. A short heavy bar with two transitions leaving it represents a splitting of control that creates multiple states.
8
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Basic Activity Diagram Symbols and Notations
Action states
Action states represent the noninterruptible actions of objects. You can draw an action state in SmartDraw using a rectangle with rounded corners.
Action Flow
Action flow arrows illustrate the relationships among action states.
Object Flow
Object flow refers to the creation and modification of objects by activities. An object flow arrow from an action to an object means that the action creates or influences the object. An object flow arrow from an object to an action indicates that the action state uses the object.
Initial State
A filled circle followed by an arrow represents the initial action state.
Final State
An arrow pointing to a filled circle nested inside another circle represents the final action state.
9
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
BranchingA diamond represents a decision with alternate paths. The outgoing alternates should be labeled with a condition or guard expression. You can also label one of the paths "else."
SynchronizationA synchronization bar helps illustrate parallel transitions. Synchronization is also called forking and joining.
SwimlanesSwimlanes group related activities into one column.
10
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Basic Component Diagram Symbols and Notations
ComponentA component is a physical building block of the system. It is represented as a rectangle with tabs.
InterfaceAn interface describes a group of operations used or created by components.
DependenciesDraw dependencies among components using dashed arrows.
Basic Deployment Diagram Symbols and Notations
11
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
NodeA node is a physical resource that executes code components.
AssociationAssociation refers to a physical connection between nodes, such as Ethernet.
Components and Nodes
Place components inside the node that deploys them.
12
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
USE CASE VIEW
USE CASE DIAGRAMS
Use case diagram can be created in the use case view.
To create a new use case diagram the following steps are to be followed:
1. Click the + next to the Use Case View in the browser to expand the view.
2. Right click on the use case view and select the new use case diagram from the
menu.
To create an actor or use case on the diagram:
1. Click to select the actor icon or the use case icon from the toolbar.
2. Click on the diagram to place the actor or use case.
3. While the actor or use case is still selected, enter its name.
The actor or use case is automatically added to the browser.
To add an actor or use case to the diagram:
1. Click to select the actor or use case in the browser.2. Drag the actor or use case to the diagram.
The actors in the ATM are identified as the Debit/Credit card holders are users of the system.
The use cases in the ATM system are as follows:
View Balance Cash Withdrawal Deposits Funds Transfer
13
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
USECASE DIAGRAM
Use case Diagram of ATM System
In the above Use case Diagram it is clear that there are four cases
1. View Balance 2. Cash Withdrawal 3. Deposit and 4. Funds
And in the above Use case there are two actors
1. Customer 2. Central Server
14
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
LOGICAL VIEW
CLASS DIAGRAMS
To create a class diagram:
1. Right-click to select the owning package and make the shortcut menu visible.
2. Select the New: Class Diagram menu command. This will add a class diagram
called New Diagram to the browser.
3. While the new class diagram is still selected, enter its name.
4. To open the class diagram, double-click on it in the browser.
Classes may also be created using the class diagram toolbar. To create a class using the toolbar:
1. Click to select the icon (class) on the class diagram toolbar.
2. Click on the class diagram to place the class.
3. While the new package or class is still selected, enter its name.
4. Multiple classes may be created by depressing and holding the Shift key.
Classes created on class diagrams are automatically added to the browser.
15
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
CLASS DIAGRAM
Class Diagram of ATM System
In the above class diagram it is illustrated that we need six classes to build ATM System. The following are the class with it attributes and operations:
1. ATM Class which is the main class which runs firsta. CardNo attributeb. PinNo attributec. Menu Class Object: mn
i. main() operation
2. Menu Class will be invoked after checking all the validations needed in ATM Class. The following are the attributes and operations of Menu Class:
a. View Balance Class Object : vbb. Cash Withdrawal Class Object : cwc. Deposit Class Object : depd. Funds Transfer Class Object : ft
i. viewButton()ii. withdrawalButton()
16
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
iii. depositButton()iv. fundsButton()
3. View Balance Class will be invoked when the Customer/User clicks the View Balance Button in Menu.
a. Amount attribute which is of type floati. displayBalance()
4. Cash Withdrawal Class will be invoked when the Customer/User clicks the Cash Withdrawal Button in Menu.
a. Amount attribute which is of type floati. dispenceCash()
ii. displayBalance()5. Deposit Class will be called when the Customer/User Clicks the Deposit Button in
Menu.a. Amount attribute which is of type floatb. Account attribute which is of type integer
i. depositCash()ii. displayBalance()
6. Funds Transfer Class will be called when the Customer/User clicks Funds Transfer Button from Menu.
a. vAmount attribute which is of type floatb. Account attribute which is of type integer
i. transferCash()ii. displayBalance()
17
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
SEQUENCE DIAGRAM
To create a new sequence diagram:
1. Right-click on the use case in the browser to make the shortcut menu visible.
2. Select the New: Sequence Diagram menu command. This will add a new
sequence diagram called New Diagram to the browser.
3. While the new diagram is still selected, enter the name of the diagram.
4. Double-click on the diagram in the browser to open it.
5. Re-size the sequence diagram as needed.
Sequence diagrams contain actors, objects and messages. To add an actor to a sequence
diagram:
1. Click to select the actor in the browser.
2. Drag the actor onto the diagram.
To add an object to the sequence diagram:
1. Click to select the object icon from the toolbar.
2. Click on the diagram to place the object.
3. While the object is still selected, enter its name.
To create a message:
1. Click to select the message icon from the toolbar.
2. Click on the object representing the client (sender of the message).
18
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
3. Drag the message to the object representing the supplier (receiver of the
message).
4. While the message line is still selected, enter the name of the message.
SEQUENCE DIAGRAMS
Sequence diagram of Cashwithdrawal
In the above diagram it is clearly depicted that the user/customer interacts with the ATM interface withdraw cash from his/her account using the source ATM.
19
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Deposit Sequence diagram
The above Illustration explain how the Customer/user interacts with the ATM to deposit cash into his/her account or others account
20
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Funds Transfer Sequence diagram
In the above drawn Sequence diagram it is clearly explained what is the sequence customer/user has to follow to transfer funds from one account to the other account.
21
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
View Balance Sequence diagram
The above diagram shows the flow of actions to check the balance available in the account of the custome/user.
22
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
COLLABORATION DIAGRAM
To create a collaboration diagram directly from a sequence diagram:
1. Select the Browse: Create Collaboration Diagram menu command or use the F5
accelerator.
2. Re-size the diagram as needed.
3. Re-arrange the objects as needed.
Collaboration diagrams may also be created from scratch. To create a new collaboration
diagram:
1. Right-click on the use case in the browser to make the shortcut menu visible.
2. Select the New: Collaboration Diagram menu command. This will add a new
collaboration diagram called New Diagram to the browser.
3. While the new diagram is still selected, enter the name of the diagram.
4. Double-click on the diagram in the browser to open it.
5. Re-size the collaboration diagram as needed.
Collaboration diagrams contain actors, objects, links, messages, and optional data flows.
To add an actor to a collaboration diagram:
1. Click to select the actor in the browser.
2. Drag the actor onto the diagram.
To add an object to the sequence diagram:
1. Click to select the object icon from the toolbar.
2. Click on the diagram to place the object.
23
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
3. While the object is still selected, enter its name.
To add a link:
1. Click to select the link icon from the toolbar.
2. In the collaboration diagram, click on one actor or object that participates in the
link.
3. Drag the link to the other participating actor or object.
An object may be linked to itself. This is called a reflexive link. To create a link
message:
1. Click to select the message to self icon from the toolbar.
2. Click on the object in the collaboration diagram.
To create a message:
1. Click to select the message icon from the toolbar.
2. Click on the link between the communicating objects
3. While the message line is still selected, enter the name of the message.
To create a data flow:
1. Click to select the data flow icon from the toolbar.
2. Click to select the message it modifies.
24
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
3. While the data flow is still selected, enter the data flow information.
Collaboration diagram of View Balance
Collaboration diagram of CashWithdrawal
25
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Collaboration diagram of Cash Deposit
Collaboration diagram of Funds Transfer
26
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
STATE CHART DIAGRAM
To create a state transition diagram:
1. Right-click to select the class in the browser and make the shortcut menu visible.
2. Select the State Diagram menu command.
To open a state transition diagram:
1. Click the + next to the class to expand the tree
2. Double-click on the State Diagram for the class
View Balance State Chart Diagram
27
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Cash Withdrawal State Chart Diagram
Deposit State Chart Diagram
28
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Funds Transfer State Chart Diagram
29
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
30
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
ACTIVITY DIAGRAM
To create a state transition diagram:
1. Right-click to select the class in the browser and make the shortcut menu visible.
2. Select the Activity Diagram menu command.
To open a state transition diagram:
1. Click the + next to the class to expand the tree
2. Double-click on the Activity Diagram for the class
View Balance Activity Diagram
31
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Cash Withdrawal Activity Diagram
Deposit Activity Diagram
32
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
Funds Transfer Activity Diagram
33
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
34
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
DEPLOYMENT DIAGRAM
The deployment diagram contains nodes and connections. Rose provides two icons that
can be used to draw a node – the processor and the device. A processor is a node that has
processing capacity.
To open the deployment diagram:
1. Double-click on the Deployment View in the browser.
To create a node:
1. Click to select the processor icon from the toolbar.
2. Click on the deployment diagram to place the node.
3. While the node is still selected, enter its name.
To create a connection:
1. Click to select the connection icon from the toolbar.
2. Click on the node representing the client.
3. Drag the connection line to the node representing the supplier
35
N Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxx ID No:xxxxxxxxxxxxxxxxxxxx
Physical Design and Implementation with Emerging Environment
ATM System Deployment Diagram
36
Recommended