1. Winter 2007, rev. 2008SEG2101 - Chapter 21 Chapter 2 Basic Principles

2. Winter 2007, rev. 2008SEG2101 - Chapter 22 Basic Principles Introduction to the system example Systems Techniques to manage complexity Approaches to behavior description Some description approaches The methodology presented here The SOON notation

3. Winter 2007, rev. 2008SEG2101 - Chapter 23 2.1: Introduction to the System Example Access Control System (AC-System) Access point: controlled by local station, physically distributed to where the services are needed Local station: control unit, a door lock mechanism, one or two panels, each contains a card reader, a display unit, and a keypad Central station: keeps information about the users, their access rights, their cards, and their secret PINs, performs authentication and authorization.

4. Winter 2007, rev. 2008SEG2101 - Chapter 24 Panel and Card

5. Winter 2007, rev. 2008SEG2101 - Chapter 25 System Structure

6. Winter 2007, rev. 2008SEG2101 - Chapter 26 2.2: Systems What is a system? Behavior Structure Real time systems

7. Winter 2007, rev. 2008SEG2101 - Chapter 27 What is a System? A system is part of real world that a person or group of persons during some time interval and for some purpose choose to regard as a whole, consisting of interrelated components, each component characterized by properties that are selected as being relevant to the purpose. A system is a purposeful collection of interrelated components that work together to achieve some objective.

8. Winter 2007, rev. 2008SEG2101 - Chapter 28 What is a System (2) A system is part of the real world. What constitutes a system is a matter of definition. Each component of a system may also be regarded as a system. A system is not just any unordered collection of components. A system has purpose.

9. Winter 2007, rev. 2008SEG2101 - Chapter 29 System Hierarchy

10. Winter 2007, rev. 2008SEG2101 - Chapter 210 A Simple Intruder Alarm System

11. Winter 2007, rev. 2008SEG2101 - Chapter 211 System Description Two purposes –To describe the functional behavior so that it can be fully understood –To describe the realization so that the system may be produced System vs system description

12. Winter 2007, rev. 2008SEG2101 - Chapter 212 System and System Description

13. Winter 2007, rev. 2008SEG2101 - Chapter 213 Behavior The behavior of a system is the development of states and state transitions generated by actions of the system during the time interval in which it is studied. Behavior is a dynamic development over time. Actually occurring in real world. Approximation: behavior consists of actions that change state (value) of variables.

14. Winter 2007, rev. 2008SEG2101 - Chapter 214 A Segment of Behavior

15. Winter 2007, rev. 2008SEG2101 - Chapter 215 Structure The structure of a system is the aspects of the system which stay invariant during the time interval in which it is studied. Structure is the way things hold together for some time. pp 30-31

16. Winter 2007, rev. 2008SEG2101 - Chapter 216 Real Time Systems A system is a real time system if it has a role with time constraints. A real-time system is a system that is required to react to stimuli from the environment within time intervals dictated by the environment.

17. Winter 2007, rev. 2008SEG2101 - Chapter 217 A Simple Fluid Control System (real-time) Pipe Flow meter Valve Interface Computer Time Input flow reading Processing Output valve angle

18. Winter 2007, rev. 2008SEG2101 - Chapter 218 A Grain-Roasting Plant (real-time) Fuel Tank Furnace Bin Pipe fuel grain

19. Winter 2007, rev. 2008SEG2101 - Chapter 219 A Process Control System (real-time) Process Control Computer Chemicals and Materials Valve Temperature Transducer Stirrer Finished Products PLANT

20. Winter 2007, rev. 2008SEG2101 - Chapter 220 2.3: Techniques to Manage Complexity Abstraction Projection Aggregation and partition Generalization and specialization

21. Winter 2007, rev. 2008SEG2101 - Chapter 221 Abstraction To ignore some aspects of a phenomenon in order to describe (and understand) others more clearly. Opposite of concrete or physical The abstractions should be clear and precise, lead to efficient implementation, and support the continuing development and reuse.

22. Winter 2007, rev. 2008SEG2101 - Chapter 222 Projection In projections we look at the system from different angles. A projection is a description of a system as it is observed at subset of its interfaces. Only the observable interfaces are visible, while the others are hidden.

23. Winter 2007, rev. 2008SEG2101 - Chapter 223 Aggregation and Partitioning (I) All non-trivial systems are composed from components. The process of lumping components together to form a whole is called aggregation. The opposite process of decomposing a whole into parts is called partitioning.

24. Winter 2007, rev. 2008SEG2101 - Chapter 224 Aggregation and Partitioning (II)

25. Winter 2007, rev. 2008SEG2101 - Chapter 225 Generalization and Specialization In the real world there are huge amounts of similar subjects. Rather than describing and understanding all individuals in full detail, we may describe and understand them in terms of similarity. Type are conceptual entities that we use to structure our descriptions and thoughts. Individual or subtype is an instance of a type.

26. Winter 2007, rev. 2008SEG2101 - Chapter 226 A Generalization Hierarchy

27. Winter 2007, rev. 2008SEG2101 - Chapter 227 Type and Subtype

28. Winter 2007, rev. 2008SEG2101 - Chapter 228 Inheritance and Specialization

29. Winter 2007, rev. 2008SEG2101 - Chapter 229 2.4: Behavior Description: the Problem The quality of a real-time system is determined to a very large extent by its behavior. Behavior is the most difficult system aspect to describe, due to its dynamic and transient nature. How can we represent a dynamic and possibly infinite behavior in a static and finite way?

30. Winter 2007, rev. 2008SEG2101 - Chapter 230 Behavior Description: Example

31. Winter 2007, rev. 2008SEG2101 - Chapter 231 Behavior Description: Focus State-oriented –focus on states and action instances –each state is represented by a node –each action instance is represented by a branch Action-oriented –focus on action types and variables –states need not be described at all –the states may be found by analyzing the actions

32. Winter 2007, rev. 2008SEG2101 - Chapter 232 2.5: Some Description Approaches Abstract description Entity relationship description SOON notation Data flow diagrams Finite state machine

33. Winter 2007, rev. 2008SEG2101 - Chapter 233 Abstract Description Many different approaches to abstract system description Conflict between the need to formalize and the need to understand The abstract description methods that have had the strongest penetration so for have been those that emphasize the needs of human audience.

34. Winter 2007, rev. 2008SEG2101 - Chapter 234 Entity Relationship Description

35. Winter 2007, rev. 2008SEG2101 - Chapter 235 Entity Relationship Diagram Legend

36. Winter 2007, rev. 2008SEG2101 - Chapter 236 Another Entity Relationship Diagram

37. Winter 2007, rev. 2008SEG2101 - Chapter 237 SOON Notation (used in book by Braek)

38. Winter 2007, rev. 2008SEG2101 - Chapter 238 The SOON notation has a clear separation between types and instances it allows us to represent individuals and types explicitly and not implicitly as in ER diagrams. Type Definition

39. Winter 2007, rev. 2008SEG2101 - Chapter 239 UML Class Diagram

40. Winter 2007, rev. 2008SEG2101 - Chapter 240 Data Flow Diagrams

41. Winter 2007, rev. 2008SEG2101 - Chapter 241 UML Activity Diagram (related to Dataflow Diagrams)

42. Winter 2007, rev. 2008SEG2101 - Chapter 242 Use Case Maps A notation (with roots in Ottawa) which is semantically similar to Activity Diagrams. Here is the same example: Receive Order Fill Order Send Invoice Ship Order Make Payment Acccept Payment Close Order Warehouse Office Client [ Order rejected ] [ Order accepted ]

43. Winter 2007, rev. 2008SEG2101 - Chapter 243 Concepts describing requirements Each Use Case is a scenario –Actions done by actors in some given order Action: Activity / Responsibility Actor: Swimlane / Component Order: sequence, alternatives, concurrency, arbitrary control flows (similar to Petri nets) Abstraction: refinement of activity / Plug-in Data-Flow: Object flow / not in UCMs. Question: what type of data is exchanged (an extension of control flow) –Input assertions for input data flow –Output assertions for output data flow –Conditions for alternatives (also in UCMs)

44. Winter 2007, rev. 2008SEG2101 - Chapter 244 Finite State Machine

45. Winter 2007, rev. 2008SEG2101 - Chapter 245 FSM A finite set of inputs, I : A finite set of outputs, O ; A finite set of state, S ; A next state function, F S : S  I  S ; An output function, F O : S  I  O* ; A designated initial state, Initial.

46. Winter 2007, rev. 2008SEG2101 - Chapter 246 2.6: The Methodology Presented Here

47. Winter 2007, rev. 2008SEG2101 - Chapter 247 Summaries of Notations

48. Winter 2007, rev. 2008SEG2101 - Chapter 248 2.7: The SOON Notation SISU Object-Oriented Notation Used to describe structures where SDL is not appropriate Less formal and does not enforce SDL semantics

49. Winter 2007, rev. 2008SEG2101 - Chapter 249 SOON Symbols

50. Winter 2007, rev. 2008SEG2101 - Chapter 250 SOON Syntax