软件工程课件：09-Uniform Modeling Language (UML).pptx

Why requirements engineering is criticalThe basic concepts Uniform Modeling Language (UML)Behavior-driven analysis SummaryOutlineWhy UML?Software Development……The diversity of OOAD Notations …….OOD, Booch [91]OOA, Coad/Yourdon [90]HOODRobinson [92]CRC, Wirfs [90]OMT,Rumbaugh [91]OODLE, Shlaer [92]UML IS…Unified Modeling Language：A graphical language for SpecifyingVisualizingConstructingDocumentingThe artifacts of software systemsThree AmigosBooch (Grady Booch) OMT (Janes Rumbaugh) OOSE (Ivar Jacobson)A Brief HistorySchlaer/MellorOMG RFPUML 1.0OMG Stand.UML 1.xUML 2.0Fusion first tryUnified Method 0.8BoochRumbaugh199519961994200319972004JacobsonBooch and RumbaughJoin RationalJacobsonJoin RationalUMLIndustry StandardCoad/YourdonArchitecture: “4+1” View UML Building BlocksModeling ElementsStructural elements: Class, Interface, use case, etc.Behavioral elements: action, state, etc.Grouping elements: packageAnnotational elementsRelationshipsDependency, association, aggregation, generalization, realization, composition, containment.DiagramStructural diagram: static modelingClass diagram, component diagram, deployment diagram, object diagram, package diagram, composite structure diagramBehavior diagram: dynamic modelingActivity diagram, interaction diagram (sequence, communication, interaction overview, timing), use case diagram, statechart diagram. Use Case DiagramRequirements ElicitationThe difficulties of requirement elicitationProblems of scopeThe boundary of the system is ill-definedSpecify unnecessary technical details that may confuse, rather than clarify, overall system objectives.Problems of understandingUnclear of what is neededTrouble communicating needs to engineersConflicting needs from different customer representativesAmbiguous or untestable requirementsProblems of volatilityRequirements change overtimeUse Case ModelPurposeSpecify the context of a systemShow interactions between the system and the entities external to the systemCapture the requirements o