1. CS48704-1/47 Illinois Institute of Technology CS487 Software Engineering Requirements II- part B Instructor David Lash

2. CS48704-2/47 Example of Modality and Cardinality

3. CS48704-3/47 Example of ERD

4. CS48704-4/47 Creating ERDs u Take each “things” (e.g., car, contact list) mentioned in requirements and ask about relationships to other things u Object-relationship pairs and therefore identified – Explore the carinality and modality of that relationship u Repeat for each object identified u Review the objects and establish attributes u Form the ERD and review

5. CS48704-5/47 ERD II example - Homesafe u Enables homeowner (HW) to config security system (SS), during install u HS monitors all sensors connected to SS u HS interacts with HW via Keypad on cntl panel (CP) u CP is used to program system u Each sensor (SEN) is assigned a # and type u A master passwd is programmed, Tel number are input for dialing on Sensor event (SEN) u on SEN event, alarm invoked & SS dials phone number, and gives info to (MS) monitoring Service u CP has keyboard input stuff

6. CS48704-6/47 ERD II example - Homesafe

7. CS48704-7/47 ERD II example - Derived Relationships u SS monitors sensor u SS enables/disables sensor u SS tests sensor u SS program sensor u Attributes of Sensor has type, internal id, zone location, alarm level

8. CS48704-8/47 ERD II example - Homesafe

9. CS48704-9/47 High-Level Modeling Tools u System Modeling – System Context Diagram – Partitioning u Data Modeling – Entity-Relation - Data objects and their relationships u Information flow diagrams – Data flow diagrams - how data transforms in system- how functions transform data u Control Specifications – State diagrams - how system behaves as result of external events.

10. CS48704-10/47 Data Flow Diagrams ( Information Flow ) u A graphical technique that depicts information flow and the transforms that are applied as data moves from input to output. – Input can be sensor, human operator, web page input, hardware – Transformation can be logical comparison, numerical algorithm, graphic algorithm, – Output can be LED, web page, report, effect on hardware

11. CS48704-11/47 Data Flow Diagram (Divide Operation) Level 0 DF (fundamental) diagram represents system with 1 bubble

12. CS48704-12/47 Data Flow Diagram (Symbols) Process (Data Transformation) External Entity (I/O Src/Dest) Data Store (all or part of the information store) System External Thing External Thing External Thing

13. CS48704-13/47 Data Flow Diagram (Data Flows or Connectors)

14. CS48704-14/47 Level 0 Data Flow Input Data

15. CS48704-15/47 Level 0 Data Flow

16. CS48704-16/47 Level 0 Data Flow (Interactive System)

17. CS48704-17/47 Data Flow Diagram (Divide Operation)

18. CS48704-18/47 Level 1 - Data Flow (Major Process Operators)

19. CS48704-19/47 Guidelines for building a Data Flow Diagram 1.Show the first level (level 0) as a single process with all of its external inputs and outputs sources. 2.Primary input and output should be carefully noted. 3.Refinement begins by isolating candidate processes. 4.All data flows and symbols should be labeled with meaningful names. 5.Information flow continuity must be maintained. (within the refinement) 6.One bubble at a time is expanded. 7.Record all components in the data dictionary.

20. CS48704-20/47 Level N Data Flow (Detailed Process to Transform)

21. CS48704-21/47 Data-Flow Example R.S. Pressman, Ph.D. Software Engineering: A Practitioner’s Approach. McGraw-Hill, New York, New York. 1997. p. 377

22. CS48704-22/47 Level 1 - introduce process and data store R.S. Pressman, Ph.D. Software Engineering: A Practitioner’s Approach. McGraw-Hill, New York, New York. 1997. p. 378

23. CS48704-23/47 Level 2 - Show more detail for each level 1 process (monitor sensors) R.S. Pressman, Ph.D. Software Engineering: A Practitioner’s Approach. McGraw-Hill, New York, New York. 1997. p. 379

24. CS48704-24/47 Behavioral Modeling u Behavior is the observable effects of an event, including its results. u Control flow diagramming – An extension to data flow diagramming – Adds events to the data model u State transition diagrams – More traditional behavior model. – Useful for a variety of applications.

25. CS48704-25/47 State Diagram u A state diagram illustrates how the system moves from state to state. For example – monitoring state -> alarm state -> monitoring state (homesafe) – What events trigger the change in state? u Sense danger, reset alarm u A state diagram shows the state machine – State Machine u A behavior that specifies the sequences of states an object goes through during its lifetime in response to events, together with its responses to those events

26. CS48704-26/47 What is the scientific base for state-machine? Conservation of Momentum Law When the resultant external force acting on a system is zero, the total momentum of the system remains constant.

27. CS48704-27/47 What are the components of a state machine? u States – Any observable mode of behavior. – A condition or situation during the life of an object during which it satisfies some condition, performs some activity or waits for some event. – Description is contained in a data dictionary. Name

28. CS48704-28/47 What are the components of a state machine? u Transitions – A relationship between two states indicating that an object in the first state will perform certain actions and enter the second state when a specified event occurs and specified conditions are satisfied. (Event & Conditions)

29. CS48704-29/47 Types of state transition diagrams u Action on transition – Actions are performed on event transition – On the diagram that is where the actions are defined. – Events, Conditions and Actions are described in the data dictionary. (Event & Conditions): Action(s)

30. CS48704-30/47 Example of action on transition

31. CS48704-31/47 Types of state-transition diagrams. u Action on state entry – Actions are performed when a state is entered. – Transitions carry optional data and not actions. – States, events, conditions and data are described in the data dictionary. State Name Action(s) (Event & Condition): Data

32. CS48704-32/47 Parser Example Given a text (stored on a file) consisting of words separated by SPACE characters or by CR (new line) characters, a program is supposed to read the text and suppress all extra SPACE characters according to the following rules: – Words should be separated only by one SPACE character, – Between a word and CR character there should be no SPACE character, – New line cannot start with a SPACE character, – Program terminates on EOF (End of File) character.

33. CS48704-33/47 Example u Processing States – New Line. Last character was a CR or beginning of process. – Word. Last character is not a space or CR. – Space. Last character is a space. – End-of-file.

34. CS48704-34/47 Example u Events (must be account for in each state) – End-of-file indicator – NL Character – Space Character – Text Characters

35. CS48704-35/47 Example u Actions – Read Next – Store Word – Set Error – List Stored Words

36. CS48704-36/47 State Diagram Example

37. CS48704-37/47 Analysis Modeling u Software models must represent: – the information that the sftwr acts on – the function that enable action – and overall system behavior u Requirements Models Roles: – Understand the information, function, behavior and information in the system – Focal Point for the review - Avoids lots of wrds help deal with complexity of problem – Become foundation for design process

38. CS48704-38/47 High-Level Modeling Tools u System Modeling – System Context Diagram – Partitioning u Data Modeling – Entity-Relation - Data objects and their relationships u Information flow diagrams – Data flow diagrams - how data transforms in system- how functions transform data u Control Specifications – State diagrams - how system behaves as result of external events.