UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis ModelOutlineSlide 3Slide 4Slide 5What is Requirements Engineering ?What is Requirements Engineering?Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Importance of Sequence DiagramsRules of Sequence DiagramsSlide 16Slide 17Slide 18Slide 19Rules of Sequence Diagrams‘included’ sequence diagramsShowing alternate behavior in a sequence diagramShowing Extension PointSpecifying Timing RequirementsSlide 25Slide 26Requirements Elicitation Process Step 4. Refining Use CasesSequence Diagrams and Use Cases System Sequence DiagramUML Use Case Diagrams: The Requirements ModelUML Use Case Diagrams: The Requirements Model Digital Sound Recorder Case StudySlide 31Slide 32Slide 33Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Slide 40A Simple Example of Using UML2Slide 42A Simple Example Using UML2UML Diagrams:Sequence DiagramsThe Requirements Model, andThe Dynamic Analysis ModelInstructor: Dr. Hany H. AmmarDept. of Computer Science and Electrical Engineering, WVUOutlineReview of previous LectureThe Requirements Model and the Analysis modelIntroduction to Requirements EngineeringImportance of Sequence DiagramsRules of sequence diagramsUse Cases and Sequence DiagramsThe System Sequence DiagramsThe Sound Recorder ExampleThe E-Commerce ExampleOther ExamplesReview of Previous lecture Review of development phases and UML Development - OverviewIntroduction and importance of Use Case DiagramsUse Case Diagram RulesExamples of Use Case diagramsRequirements Elicitation Process1. Identify Actors2. Identify Scenarios3. Identify Use Cases4. Refine Use Cases5. Identify Relationships between actors and Use Cases6. Identify Initial Analysis Objects7. Identify Non-functional requirementsUML Development - OverviewPROGRAMACTORSANALYSISSpecify Domain ObjectsDetailed DESIGNIMPLEMENTATIONDATADICTIONARYTimeUSE CASESANALYSISCLASS DIAGRAM(S)IMPLEMENTATIONActivity DIAGRAMSSystem/ObjectSEQUENCEDIAGRAMSOPERATION CONTRACTSStateChart DIAGRAMsDEPLOYMENT DIAGRAMSUBSYSTEM CLASS/OR COMPONENTDIAGRAMSArchitectural DesignIncludeDesign ObjectsObjectDesignSCENARIOSREQUIREMENTSELICITATIONDESIGN DIAGRAMSIMPLEMENTATIONCHOICESDESIGN SEQUENCE DIAG.RequirementsEngineeringThe Requirements Model and the Analysis ModelStatic Analysis Dynamic AnalysisFunctional/ NonfunctionalRequirementsUse Case Diagrams/Sequence Diagrams(the system level)- Class Diagrams- State Diagrams/Refined Sequence Diagrams (The object level)The Requirements ElicitationProcessThe Object-OrientedAnalysisProcessWhat is Requirements Engineering ?Requirements EngineeringWhat is Requirements Engineering?Requirements Management:Requirements management activities include evaluating the impact of proposed changes, tracing individual requirements to downstream work products, and tracking requirements status during developmentSeveral Requirements management tools are available in industryWhat is Requirements Engineering?Major Requirements Management Tools:1. Caliber-RM by Technology Builders, Inc.; www.tbi.com2. RequisitePro by Rational Software Corporation; www.rational.com3. RTM Workshop by Integrated Chipware, Inc.; www.chipware.comWhat is Requirements Engineering?Requirements Elicitation – is the process of gathering the different types of requirements from suitable stakeholders. Business requirements describe why the product is being built and identify the benefits for both the customers and the business. User requirements, describe the tasks or business processes a user will be able to perform with the product. (Developing use-cases) Functional requirements describe the specific system behaviors that must be implemented (Developing usage scenarios)Non-functional requirements, describe the non-functional features such as quality attributes of Reliability, Performance, availability, and maintainability.What is Requirements Engineering?Requirements analysis:Requirements analysis includes decomposing high-level requirements into detailed functional requirements, constructing graphical requirements models or logical models (structured Analysis models, or Object-Oriented Analysis models) (for developers), and building prototypes. Analysis models and prototypes provide alternative views of the requirements, which often reveal errors and conflicts that are hard to spot in a textual SRS.What is Requirements Engineering?Requirements SpecificationSpecification key practice is to write down the requirements in some accepted, structured format as you gather and analyze them. The objective of requirements development is to communicate a shared understanding of the new product among all project stakeholders. Historically, this understanding is captured in the form of a textual Software Requirements Specification document written in natural language, augmented by appropriate analysis models. (to be discussed in detail)What is Requirements Engineering?Requirements VerificationVerification involves evaluating the correctness and completeness of the requirements, to ensure that a system built to those requirements will satisfy the users’ needs and expectations. The goal of verification is to ensure that the requirements provide an adequate basis to proceed with designPrototyping (or executable specifications) is a major technique used in verification. Examples include GUI development for user requirements verification, and Formal requirements specification environmentsOutlineThe Requirements Model and the Analysis modelIntroduction to Requirements EngineeringImportance of Sequence DiagramsRules of sequence diagramsUse Cases and Sequence DiagramsThe System Sequence DiagramsThe Sound Recorder ExampleThe E-Commerce ExampleOther ExamplesImportance of Sequence DiagramsDepict object interactions in a given scenario identified for a given Use CaseSpecify the messages passed between objects using horizontal arrows including messages to/from external actorsTime increases from Top to bottomRules of Sequence DiagramsSequence Initiation updateStatus( )Click Update ButtonUserObject1:C1 Object2:C2Rules of Sequence DiagramsIdentify objects needed to support use case, determine sequence of internal events following the external initiating eventDiagrams that are not initiated with an external actor represent only a partial sequence Partial sequence diagrams should clearly identify
or
We will never post anything without your permission.
Don't have an account? Sign up