UML and Rational Rose

UML with Rational Rose
Sandip M Vaniya
January 2, 2012
UML and Rational Rose
Outline
Traditional Approach Introduction of UML Use case diagram Sequence diagram Collaboration diagram Class diagram Component diagram Deployment diagram
UML and Rational Rose 2
January 2, 2012
Traditional Approach
Structure analysis (SA)
Data Flow Diagram (DFD)
Structure Design (SD)

Structure Chart WBS
January 2, 2012
Data Flow Diagram Notation
Function symbol:
-It call as Function or bubble.
External Entity Symbol:Librarian, member Etc.it represent external entity who is Interact with system by inputting data Into system or consume outputting data.
January 2, 2012
Data flow symbol data store symbol
Output symbol:- it is used when

the hard Copy is produce and there are Several user of the output.
January 2, 2012
Important concept
1. 2. 3. 4. 5. 6. Synchronization and ASynchronization. Data dictionary:-list all the data item appearing in DFD. Data definition:+:-denotes composition of two data item. [ , ,]:-denote selection. ( ):-denote optional data which may or may not appear. { }:-iterative data definition. =:-represent equivalence. /* represent Comment
January 2, 2012
Example of SC
UML
What is Visual Modeling? Developing object oriented software. Graphical notations Developers and customers view software system from a different perspective.
UML is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems.
January 2, 2012 UML and Rational Rose 8
Software Design
Steps for analysis & design of object oriented system

Use case Diagrams

-- represents what happens when actor interacts with a system. -- captures functional aspect of the system. --Use Cases are for what the system is , not how the system will be designed
Actor -- Actors appear outside the rectangle.
Use Case
Relationship between actors and use case and/or between the use cases.
--Use cases within rectangle providing functionality. --Relationship association is a solid line between actor & use cases.
Use case for ATM System

Transfer fund
Change PIN
Bank officer
Make Payment
Customer
View Balance
Credit System
Withdraw money
January 2, 2012
11
Use case specification
January 2, 2012
12
Activity Diagram
Show the flow of activities through the system. Describe the workflow behavior of a system. An activity diagram shows the flow of events within our system.
January 2, 2012
13
January 2, 2012
14
January 2, 2012
15
Create curriculum Select courses to teach Create catalog
Place catalog in bookstore
Mail catalog to students
Open registration [ Registration time period expired ] Close registration
January 2, 2012
16
Swimlane Diagrams
January 2, 2012
17
What Is a Sequence Diagram?

A sequence diagram shows step by step what must happen to accomplish a piece of functionality provided by the system. The diagram shows
The objects participating in the interaction. The sequence of messages exchanged.
Sequence Diagrams
Sequence diagram-Example
January 2, 2012
19
Joe : Custom er
Card Reader : CardReader
ATM Screen : ATMScreen
Joe's Account : Account
1. Accept Card
readCardNo( )
InitializeScreen( )
prom ptPIN( )
Enter PIN no
openAccount( ) verifyPIN( )
January 2, 2012
20
What Is a Collaboration Diagram?

A collaboration diagram emphasizes the organization of the objects that participate in an interaction. The collaboration diagram shows
The objects participating in the interaction. Links between the objects. Messages passed between the objects.
Collaboration Diagrams
Collaboration Diagram
6: 6:Enter PIN(1234) 9: 9:Select Transaction(Withdraw) 11: 11:Enter Amount 13: 13:Verify Fund 14: 14:Deduct Fund ATM Screensd 7: 7:Verify the PIN 12: 12:Withdraw Fund
5: 5.Prompt for PIN 8: 8:Promt for Transaction 10: 10:Promt for Amount sandip : Customer
Sandip's Account
3: 3.Intialized Screen 4: 4.Open Account 1: 1.Accept Card 17: 17:Eject Card 2: 2. Read Card No 15: 15:Provide Cash 16: 16:Provide Receipt
January 2, 2012
Card Reader
Cash Dispacher
22
Class diagram
The class diagram is a static model that shows the classes and the relationships among classes in the system.
class name attributes operations

UML Class symbol has three parts: 1) Name 2) List of attributes 3) List of operations
January 2, 2012
24
Elements of class diagram

Class name compartment Attributes compartment Operations compartment
January 2, 2012
Client - companyAddress - companyEmail - companyFax + companyName # companyTelephone + getClientInfo( ) - updateClientInfo( )
private public protected

25
Types of Attributes
Simple attributes contain single data item Identifiers connect unique key value Multi valued attributes contain multiple values simultaneously Composite attributes group of related attributes
January 2, 2012
26
January 2, 2012
27
January 2, 2012
28
Composite attributes have multiple sections (sub attributes). They are treated as separate classes in conceptual data models.
UML and Rational Rose 29
January 2, 2012
Operation
Actions or function that a class can perform in manipulating the attributes Example: insertInfo(), verifyPassword()
January 2, 2012
30
January 2, 2012
31
State Chart Diagrams

Withdrawal( Balance <0 )
Overdrawn Open
Deposite( [Balance<0] )
Customer Request Closure check balance( balance <0 for >30 days )
NewState
January 2, 2012
32
Component Diagram
ATM.exe
Cash Dispenser Card Reader
ATM Screen
card reader
Cash Dispenser
ATM Screen
January 2, 2012
33
Deployment Diagrams
Oracle Server Banking Database Server
<<LAN>>
ATM Server.exe
Regional ATM Server
Printer
<<Private Network>>
<<Private Network>> 12 Anand ATM 100 V.V.Nagar ATM
ATM Client.Exe
ATM Client.Exe
January 2, 2012
34
Summary
Use Case Diagram displays the relationship among actors and use cases. Class Diagram models class structure and contents using design elements such as classes, packages and objects. It also displays relationships such as containment, inheritance, associations and others. Interaction Diagrams Sequence Diagram displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects). Collaboration Diagram displays an interaction organized around the objects and their links to one another. Numbers are used to show the sequence of messages. State Diagram displays the sequences of states that an object of an interaction goes through during its life in response to received stimuli, together with its responses and actions.1 Activity Diagram displays a special state diagram where most of the states are action states and most of the transitions are triggered by completion of the actions in the source states. This diagram focuses on flows driven by internal processing. Physical Diagrams Component Diagram displays the high level packaged structure of the code itself. Dependencies among components are shown, including source code components, binary code components, and executable components. Some components exist at compile time, at link time, at run times well as at more than one time. Deployment Diagram displays the configuration of run-time processing elements and the software components, processes, and objects that live on them. Software component instances represent run-time manifestations of code units
January 2, 2012
35
Thank You
January 2, 2012
36

UML and Rational Rose

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UML and Rational Rose

Uploaded by

Copyright:

Available Formats

UML with Rational Rose