![Association: Model to Implementation
Class Student {
Course enrolls[4];
}
Class Course {
Student have[];
}
Student Course
enrolls
has
* 4](https://image.slidesharecdn.com/umlpresentation-140519151641-phpapp02-241123182809-b57073ec/85/umlpresentation-140519151641-phpapp02-ppt-19-320.jpg)
![Sequence Diagram
User Catalog Reservations
1: look up ()
2: title data ()
3: [not available] reserve title ()
4 : title returned ()
5: hold title ()
5 : title available ()
6 : borrow title ()
6 : remove reservation ()
Issuing a book from library](https://image.slidesharecdn.com/umlpresentation-140519151641-phpapp02-241123182809-b57073ec/85/umlpresentation-140519151641-phpapp02-ppt-27-320.jpg)
![Collaboration diagrams of earlier made sequence diagram of issuing of book
from library
User
Catalog
Reservations
start
1: look up
2: title data
3 : [not available] reserve title
4 : title returned
5 : hold title
6 : borrow title
6: remove reservation
5: title available](https://image.slidesharecdn.com/umlpresentation-140519151641-phpapp02-241123182809-b57073ec/85/umlpresentation-140519151641-phpapp02-ppt-29-320.jpg)
Ad
More Related Content
Similar to umlpresentation-140519151641-phpapp02.ppt (20)
Recently uploaded (20)
Ad
umlpresentation-140519151641-phpapp02.ppt
- 1. Overview • What is UML? • Understanding the basics of UML • Why UML? • UML diagrams • UML Modeling tools
- 2. What is UML? • UML stands for “Unified Modeling Language” • Modeling is describing system at a high level of abstraction • It is a industry-standard graphical language for specifying, visualizing, constructing, and documenting the artifacts of software systems • The UML uses mostly graphical notations to express the analysis and design of software projects. • Simplifies the complex process of software design
- 3. Why UML for Modeling/Benefits of UML • Use graphical notation to communicate more clearly than natural language and code • Quick understanding • Help acquire an overall view of a system. • Lessens chances of conflicts. • UML is not dependent on any one language or technology. • Necessary to manage complexity. • UML moves us from fragmentation to standardization.
- 4. Types of UML Diagrams • Use Case Diagram • Class Diagram • Activity Diagram • Sequence Diagram • Collaboration Diagram • State Diagram • Deployment Diagram
- 5. Use Case Diagram • Used for describing a set of user scenarios • Illustrates functionality provided by the system • Mainly used for capturing user requirements • Work like a contract between end user and software developers
- 6. Use Case Diagram (core components) Actors: A role that a user plays with respect to the system,including human users and other systems. e.g.,inanimate physical objects (e.g. robot); an external system that needs some information from the current system. Use case: A set of scenarios that describing an interaction between a user and a system, including alternatives. System boundary: rectangle diagram representing the boundary between the actors and the system.
- 7. Use Case Diagram(core relationship) Association: communication between an actor and a use case; Represented by a solid line. Generalization: relationship between one general use case and a special use case (used for defining special alternatives) Represented by a line with a triangular arrow head toward the parent use case.
- 8. Use Case Diagram(core relationship) Extend: a dotted line labeled <<extend>> with an arrow toward the base case. The extending use case may add behavior to the base use case. The base class declares “extension points”. <<extend>> Include: a dotted line labeled <<include>> beginning at base use case and ending with an arrows pointing to the include use case. The include relationship occurs when a chunk of behavior is similar across more than one use case. Use “include” in stead of copying the description of that behavior. <<include>>
- 9. Use Case Diagrams Library System Borrow Order Title Fine Remittance Client Employee Supervisor • A generalized description of how a system will be used. • Provides an overview of the intended functionality of the system Boundary Actor Use Case
- 11. Use Case Diagrams(cont.) •Pay Bill is a parent use case and Bill Insurance is the child use case. (generalization) •Both Make Appointment and Request Medication include Check Patient Record as a subtask.(include) •The extension point is written inside the base case Pay bill; the extending class Defer payment adds the behavior of this extension point. (extend)
- 12. Class diagram • Used for describing structure and behavior in the use cases • Provide a conceptual model of the system in terms of entities and their relationships • Used for requirement capture, end-user interaction • Detailed class diagrams are used for developers
- 13. Class representation • Each class is represented by a rectangle subdivided into three compartments – Name – Attributes – Operations • Modifiers are used to indicate visibility of attributes and operations. – ‘+’ is used to denote Public visibility (everyone) – ‘#’ is used to denote Protected visibility (friends and derived) – ‘-’ is used to denote Private visibility (no one) • By default, attributes are hidden and operations are visible.
- 14. An example of Class Account_Name - Customer_Name - Balance +addFunds( ) +withDraw( ) +transfer( ) Name Attributes Operations
- 15. Relationships • There are two kinds of Relationships – Generalization (parent-child relationship) – Association (student enrolls in course) • Associations can be further classified as – Aggregation – Composition
- 16. Subtype2 Supertype Subtype1 Relationships: Generalization - Generalization expresses a parent/child relationship among related classes. - Used for abstracting details in several layers Regular Customer Loyalty Customer Customer Example: Regular Customer Loyalty Customer Customer or:
- 17. Relationships: Association • Represent relationship between instances of classes – Student enrolls in a course – Courses have students – Courses have exams – Etc. • Association has an end – Multiplicity (e.g. One course can have many students)
- 18. Association: Multiplicity and Roles University Person 1 0..1 * * Multiplicity Symbol Meaning 1 One and only one 0..1 Zero or one M..N From M to N (natural language) * From zero to any positive integer 0..* From zero to any positive integer 1..* From one to any positive teacher employer Role Role “A given university groups many people; some act as students, others as teachers. A given student belongs to a single university; a given teacher may or may not be working for the university at a particular time.” student
- 19. Association: Model to Implementation Class Student { Course enrolls[4]; } Class Course { Student have[]; } Student Course enrolls has * 4
- 20. Relationships: Composition Class W Class P1 Class P2 Composition: expresses a relationship among instances of related classes. It is a specific kind of Whole-Part relationship. It expresses a relationship where an instance of the Whole-class has the responsibility to create and initialize instances of each Part-class. It may also be used to express a relationship where instances of the Part-classes have privileged access or visibility to certain attributes and/or behaviors defined by the Whole-class. Composition should also be used to express relationship where instances of the Whole-class have exclusive access to and control of instances of the Part-classes. Composition should be used to express a relationship where the behavior of Part instances is undefined without being related to an instance of the Whole. And, conversely, the behavior of the Whole is ill-defined or incomplete if one or more of the Part instances are undefined. Whole Class Part Classes Automobile Engine Transmission Example
- 21. Class Diagram Example Hotel Management System
- 22. Activity Diagram • Procedural flow of control between two or more class objects • Activities are grouped into swim lanes. • Activity is modeled by drawing a rectangle with rounded edges, enclosing the activity's name. • Connected to other activities through transition lines • Activities that terminate the modeled process are connected to a termination point
- 23. Activity diagram, with two swim lanes to indicate control of activity by two objects: the band manager, and the reporting tool
- 24. Sequence Diagram • Two dimensional • Vertical dimension shows sequence of messages in the time order that they occur. • Horizontal dimension shows the object instances to which the messages are sent. • Self-Call can also be there in which a message that an object sends to itself.
- 25. Sequence Diagram(make a phone call) Caller Phone Recipient Picks up Dial tone Dial Ring notification Ring Picks up Hello
- 26. Sequence Diagrams – Object Life Spans • Creation – Create message – Object life starts at that point • Activation – Symbolized by rectangular stripes – Place on the lifeline where object is activated. – Rectangle also denotes when object is deactivated. • Deletion – Placing an ‘X’ on lifeline – Object’s life ends at that point Activation bar A B Create X Deletion Return Lifeline
- 27. Sequence Diagram User Catalog Reservations 1: look up () 2: title data () 3: [not available] reserve title () 4 : title returned () 5: hold title () 5 : title available () 6 : borrow title () 6 : remove reservation () Issuing a book from library
- 28. Collaboration Diagram • Shows the relationship between objects and the order of messages passed between them. • The objects are listed as rectangles and arrows indicate the messages being passed • Convey the same information as sequence diagrams, but focus on object roles instead of the time sequence.
- 29. Collaboration diagrams of earlier made sequence diagram of issuing of book from library User Catalog Reservations start 1: look up 2: title data 3 : [not available] reserve title 4 : title returned 5 : hold title 6 : borrow title 6: remove reservation 5: title available
- 30. State Diagrams State Diagrams show the sequences of states an object goes through during its life cycle in response to stimuli, together with its responses and actions; an abstraction of all possible behaviors. Unpaid Start End Paid Invoice created payin g Invoice destroying (Billing Example)
- 31. Deployment Diagram • System will be physically deployed in the hardware environment • System's production staff makes its considerable use • Purpose is to show where the different components of the system will physically run and how they will communicate with each other
- 32. Deployment for ATM Machine
- 33. UML Modeling Tools • Rational Rose (www.rational.com) by IBM • TogetherSoft Control Center, Borland ( http://www.borland.com/together/index.html) • ArgoUML (free software) (http://argouml.tigris.org/ ) OpenSource; written in java written in java • Others (http://www.objectsbydesign.com/tools/umltools_byCompany.html )
- 34. Thank You!