Chapter 8Analysis Modeling.ppt

* Building a State Diagram A state is represented by a rounded rectangle A transition i.e., event is represented by a labeled arrow leading from one state to another Syntax: trigger-signature [guard]/activity The active state of an object indicates the current overall status of the object as is goes through transformation or processing A state name represents one of the possible active states of an object The passive state of an object is the current value of all of an objects attributes A guard in a transition may contain the checking of the passive state of an object * Example State Diagram Empty Stack Partially Filled Stack Full Stack push [n 0] pop [n 1] push [n - 1 max] push [n – 2 max] pop [n 1] pop [n max] pop / set n to 0; return error push / set n to max; return error * Summary:Elements of the Analysis Model Use case text Use case diagrams Activity diagrams Swim lane diagrams Scenario-based modeling Class diagrams Analysis packages CRC models Collaboration diagrams Class-based modeling Data flow diagrams Control-flow diagrams Processing narratives Flow-oriented modeling State diagrams Sequence diagrams Behavioral modeling Structured Analysis Object-oriented Analysis ? Chapter 8Analysis Modeling Requirements analysis Flow-oriented modeling Scenario-based modeling Class-based modeling Behavioral modeling Source: Pressman, R. Software Engineering: A Practitioner’s Approach. McGraw-Hill, 2005 * Goals of Analysis Modeling Provides the first technical representation of a system Is easy to understand and maintain Deals with the problem of size by partitioning the system Uses graphics whenever possible Differentiates between essential information versus implementation information Helps in the tracking and evaluation of interfaces Provides tools other than narrative text to describe software logic and policy * A Set of Models Flow-oriented modeling – provides an indication of how data objects are transformed by a set of processing func