CSE 201 Lecture Notes - Lecture 10: State Diagram, Software Requirements Specification, Sequence Diagram
13 Mar 2019
School
Department
Course
Professor
Document Summary
Cse 201 - lecture 10 - sequence diagrams and state diagrams. Functionality model: functionality of the system using use-case diagrams. Object model: structure of the system using class diagrams. Dynamic behavior: behavior of the system using sequence diagrams and statechart diagrams. Team developing srs (software requirements specification) may not be same team developing the software. Different skill sets and levels of people. Requirements analysts are often more experienced with capturing behavior than developers. Dynamic modeling: statechart diagram or one sequence chart diagram for each class with important dynamic behavior. Purpose: detect and supply methods for the object (structural) model. Model interaction between objects => sequence diagram. Model dynamic behavior of single object => statechart diagram. Depict communication between objects during a use-case. Bars are used to represent lifetime of particular object. Lines are used to show method invocation. Start with the flow of events from the use case model when attempting to generate a sequence diagram.
