Software System EngineeringSlide 2Slide 3The Value of the UMLContributions to the UMLOverview of the UMLBuilding Blocks of the UMLThings in the UMLRelationships (1)Relationships (2)Diagrams in UMLDiagramsUse Case DiagramSlide 14Class Diagram (1)Class Diagram (2)Object Diagram (1)Object Diagram (2)Component Diagram (1)Component Diagram (2)Deployment Diagram (1)Deployment Diagram (2)Activity Diagram (1)Activity Diagram (2)Sequence Diagram (1)Sequence Diagram (2)Collaboration Diagram (1)Slide 28Statechart Diagram (1)Statechart Diagram (2)Architecture and the UMLUML Software Development Life Cycle (1)UML Software Development Life Cycle (2)Lifecycle PhasesDiscussion QuestionsQuestions for the Next Lecture© M.E. Fayad 2000 -- 2006SJSU -- CmpESoftware System Engineering Dr. M.E. Fayad, ProfessorComputer Engineering Department, Room #283I College of EngineeringSan José State UniversityOne Washington SquareSan José, CA 95192-0180 http://www.engr.sjsu.edu/~fayad© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S2 UML Overview2Lesson 6:Unified Modeling Language (UML) Overview© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S3 UML Overview Lesson ObjectivesObjectives3 The value of the UML Contribution to the UML Building Blocks of the UML Diagrams in the UML© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S4 UML OverviewIs an open standardSupports the entire software development lifecycle – DebateSupports diverse applications areasIs based on experience and needs of the user communitySupported by many tools4The Value of the UML© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S5 UML Overview5Contributions to the UMLGuess who?© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S6 UML OverviewThe UML is a language for–visualizing–specifying–constructing–documentingthe artifacts of a software-intensive system6Overview of the UML© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S7 UML OverviewThingsRelationshipsDiagrams7Building Blocks of the UML© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S8 UML OverviewStructural things–mostly static parts of a model•class, interface, collaboration, use case, active class, component, nodeBehavioral things–dynamic parts of UML models•interaction, state machineGrouping things–organizational parts of UML•package, subsystemOther things–explanatory parts of UML•noteThings in the UML© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S9 UML OverviewDependency–a semantic relationship between two things in which a change to one thing (the independent thing) may affect the semantics of the other thing (the dependent thing)Association–a structural relationship that describes a set of linksRelationships (1)9© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S10 UML OverviewGeneralization–a specialization/generalization relationship in which the child shares the structure and the behavior of the parentRealization–a realization is a relationship in which one classifier, such as an interface or a use case, specifies a "contract" that another classifier, such as a class or a collaboration, guarantees to carry out10Relationships (2)© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S11 UML Overview11Diagrams in UMLUse CaseDiagramsUse CaseDiagramsUse CaseDiagramsScenarioDiagramsScenarioDiagramsCollaborationDiagramsStateDiagramsStateDiagramsComponentDiagramsComponentDiagramsComponentDiagramsDeploymentDiagramsStateDiagramsStateDiagramsObjectDiagramsScenarioDiagramsScenarioDiagramsStatechartDiagramsUse CaseDiagramsUse CaseDiagramsSequenceDiagramsStateDiagramsStateDiagramsClassDiagramsActivityDiagramsModels+© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S12 UML OverviewA diagram is a view into a model–Presented from the aspect of a particular stakeholder–Provides a partial representation of the system–Is semantically consistent with other viewsIn the UML, there are nine standard diagrams–Static views: use case, class, object, component, deployment–Dynamic views: sequence, collaboration, statechart, activity12Diagrams© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S13 UML OverviewShows a set of use cases and actors and their relationships13Use Case Diagram© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S14 UML OverviewCaptures system functionality as seen by usersBuilt in early stages of developmentPurpose–Specify the context of a system–Capture the requirements of a system–Validate a system’s architecture–Drive implementation and generate test casesDeveloped by analysts and domain experts14Use Case Diagram© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S15 UML OverviewShows a set of classes, interfaces, and collaborations and their relationships15Class Diagram (1)© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S16 UML OverviewCaptures the vocabulary of a systemAddresses the static design view of a systemBuilt and refined throughout developmentPurpose–Name and model concepts in the system–Specify collaborations–Specify logical database schemasDeveloped by analysts, designers, and implementers16Class Diagram (2)© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S17 UML OverviewShows a set of objects and their relationships17Object Diagram (1)© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S18 UML OverviewRepresents static snapshots of instances of the things found in class diagramsAddresses the static design view or static process view of a systemBuilt during analysis and designPurpose–Illustrate data/object structures–Specify snapshotsDeveloped by analysts, designers, and implementers18Object Diagram (2)© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S19 UML OverviewShows the organizations and dependencies among a set of components19Component Diagram (1)© M.E. Fayad 2000 -- 2006SJSU – CmpE M.E. Fayad L3-2-S20 UML OverviewAddresses the static implementation view of a systemBuilt as part of architectural specificationPurpose–Organize source code–Construct an executable release–Specify a physical