Your SlideShare is downloading. ×
Intoduction to uml
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Intoduction to uml


Published on

This ppt will provide a brief idea on what is UML, different kind of diagrams in UML and relationships in UML

This ppt will provide a brief idea on what is UML, different kind of diagrams in UML and relationships in UML

Published in: Education, Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. WHAT IS UML ?WHAT IS UML ?• Unified Modeling Language is a modelinglanguage for software blueprint.• It is a standard language for specifying,visualizing, constructing, and documenting theartifacts of software systems.• It was developed by Booch, Jacobson andRumbaugh.
  • 2. WHAT UML IS NOT ?WHAT UML IS NOT ?• It’s not an algorithm specification language..• It’s not a development process.It’s not a development process.• It’s not a programming language.It’s not a programming language.• It’s not a caseIt’s not a case tool.tool.
  • 3. GOALS OF UMLGOALS OF UML• Provide users with a ready-to-use,expressive visual modeling languageso they can develop meaningful model.• Provide extensible and specializationmechanisms to extend the core concept.• Be independent of programming language anddevelopment processes.
  • 4. TYPES OF UML DIAGRAMSTYPES OF UML DIAGRAMSEach UML diagram is designed to letdevelopers and customers view a softwaresystem from a different perspective.1. Use Case Diagram : Displays therelationship among actors and use cases.2. Class Diagram : Models class structure andcontents using design elements such asclasses, packages and objects. It displaysrelationships such as inheritance andassociations etc.
  • 5. 3. Interaction Diagram : Sequence Diagram : Displays the timesequence of the objects participating in theinteraction. Collaboration Diagram : Displays aninteraction organized around the objectsand their links to one another.4. Statechart Diagram : Displays the sequencesof states that an object of an interaction goesthrough during its life in response to receivedstimuli/event.
  • 6. 5. Activity Diagram : Displays a special statediagram where most of the states are actionstates and most of the transitions are triggeredby completion of the actions in the sourcestates. In this diagramFocus is on flows driven by processing.6. Physical Diagrams : Component Diagram : Shows theorganization and dependencies among a setof components. Involves the modeling ofphysical things that reside on a node – suchas executables, libraries, tables, files anddocuments.
  • 7.  Deployment Diagram : Displays theconfiguration of run-time processingelements and the software components,processes and objects that live on them.
  • 9. • Use Case View : It describes the behavior ofthe system typically as seen by the end user.• Design View : It encompasses the classes,interfaces and collaborations that make up thesystem. Shows how functional requirementhave been implemented.• Process View : It encompasses the threads andprocesses that make up the system.
  • 10. • Implementation View : It encompasses thecomponents, files and packages that are usedto assemble the system.• Deployment View : It encompasses nodes thatform the system and addresses thedistributivity and installation of system.
  • 11. ELEMENTS OR THINGS OF UMLELEMENTS OR THINGS OF UMLMany elements or things that must be wellunderstood to draw UML diagrams are brokendown into following categories :• Structural Elements• Behavioral Elements• Grouping Elements• Annotations
  • 12. • STRUCTURAL ELEMENTS :They are the static parts of the model usuallyrepresents the static concepts or physicalentities with system. Classes Interfaces Collaboration Use case Active classes Components Nodes
  • 13. • BEHAVIORAL ELEMENT :These are the dynamic parts of the model.They represent the behaviour of the staticelements of the model. Messages : Represents messagesexchanged between objects and representsflow of the system. States : Represents the state of an object ata particular point in time. States allowobjects to make choices about how torespond to an event.
  • 14. • ANNOTATION ELEMENTS:These are explanatory elements of the UML.These are used to describe other thingsrepresented by a single element. Note
  • 15. RELATIONSHIPS IN UMLRELATIONSHIPS IN UMLThere are 4 types of relationships :1. Dependency2. Association3. Generalization4. Realization
  • 16. 0..1 *employer employee• DEPENDENCY :It is a semantic relationship between two thingsthat represents that a change to the independentelement will affect the dependent element.-------• ASSOCIATION :It represents a structural relationship (usuallyamong the classes). It has name, multiplicity,source and target, role names.
  • 17. • GENERALIZATION :It indicates specialized element is substitutableFor a generalized element. It represents is-a kindOf relationship.• REALIZATION :It is a semantic relationship that specifies acontract between a specifier and a provider. Itexist only between interfaces and classes orcomponents and use cases and collaboration.----------|
  • 18. COMMON MECHANISMSCOMMON MECHANISMS1. NOTES : A note is a graphical symbol forrendering constraints or comments attached toa element.2.STEREOTYPES : Allows to create newkind of building blocks similar to existingones but specific to our problem<<exception>Underflow
  • 19. 3. TAGGED VALUES :Tagged value isdenoted by (name, value) pair that describes theproperty of a model element.Server{Processor = 3}
  • 20. 4. CONSTRAINTS : Graphically, aConstraint is rendered as a string enclosed byBrackets and placed near the associated element.PortfolioBank Account{secure} CorporationPersonGender :{male , female}{or}
  • 21. USE CASE DIAGRAMUSE CASE DIAGRAM• A use case diagram specifies the behavior of asystem or a part of a system and is adescription of a set of sequences of actions.• Components of Use Case Model : Actor Use Case
  • 22. • Relationships in Use Case Model : communicates Relationship :<<communicates>> Use Case uses or includes Relationship :Place order Validate Customer extends Relationship:Base usecasePlace orderOverdraw amount<<uses>> <<extends>>
  • 23. .Get balanceValidate userWithdraw moneyMaintain ATMOverdraw money<<extends>><<extends>><<uses>><<Uses>>MaintenancepersonSave transactionDatabasecustomer
  • 24. CLASS DIAGRAMCLASS DIAGRAM• A class diagram shows a set of classes,interfaces, collaborations and theirrelationships.• Class diagram contains following things : Classes Interfaces Collaboration Dependency, Generalization andAssociation relationships.• It may contain notes and constraints.
  • 25. .CompanyDepartment Officename : Name Address : stringPersonName : StringEid : IntegergetPhoto(P:Photo)getContactInfo()getPersonalInfo()Head Quartersgeneralization0..111..* 1..*Personnel_RecordContact_InfodependencymemberroleTax IDSalary Isecure informationInterface
  • 26. SEQUENCE DIAGRAMSEQUENCE DIAGRAM• Sequence diagram shows, for a particularscenario, the events that external actorsgenerate, their order, and inter-system events.
  • 27. .: System: CashierMake a new saleenterItem( itemID , quantity )Description , total[more items]loopend saletotal with taxesmake payment(amount)receiptProcess Sale Scenario
  • 28. COLLABORATION DIAGRAMCOLLABORATION DIAGRAM• Collaboration diagrams model the interactionsbetween the object.• It is the cross between an object diagram andsequence diagram.• Notations used : Object Actor Message
  • 29. ....1. Find user2. Update user WebApp : userinterfaceUser validator2.1 Validate userUser database1.1 Lookup user2.1 Look userCollaboration Diagram
  • 30. STATE CHART DIAGRAMSTATE CHART DIAGRAM• A State Chart Diagram relates events and states.When an event is received, the next statedepends on the current state as well as the event;a change of state caused by an event is called astransition.• A State Diagram is a graph whose nodes arestates and whose directed arcs are transitionsstates.
  • 31. .State Chart Diagram
  • 32. ACTIVITY DIAGRAMACTIVITY DIAGRAM• Activity diagram shows the flow from activity toactivity within a system.• Activity diagram commonly contains: Activity State Action State Transitions Objects Forks and Join Branching Swimlanes
  • 33. .Customer Sales WarehouseSwimlanes•Request ProductProcess OrderO : order[in progress]Pull MaterialShip OrderReceiveorderBillcustomerPay Billb: bill[paid]b: bill[unpaid]O : order[filled]stateClose order• Final state
  • 34. COMPONENT DIAGRAMCOMPONENT DIAGRAM• A component is a physical replaceable part ofa system that conforms to and provides therealization of a set of interfaces.• COMPONENTS AND CLASSES :1. Class are logical abstraction; whilecomponents represent physical thing.2. Component represent physical packaging oflogical components.3. Classes may have attributes and operations.Component have only operations that arereachable only through their interfaces.
  • 35. THANK YOU…!!!THANK YOU…!!!