Design methods for reactive systems

Dear colleague,

You might be interested in the book ``Design Methods for Reactive
Systems: Yourdon, Statemate and the UML'' just published by Morgan
Kaufmann.  Reactive systems are systems that must be able to respond
to events in their environment. Examples are control software as well
as communication-intensive applications and information-intensive
applications. The book contains 7 case studies and has a web site
http://www.mkp.com/dmrs with slides and answers to exercises.

Thanks,

--Roel Wieringa

Design Methods for Reactive Systems: Yourdon, Statemate and the UML
R.J. Wieringa
Morgan Kaufmann, 2003. ISBN 1-55860-755-2
http://www.mkp.com/dmrs

Table of contents:

Preface
Forword

PART I REACTIVE SYSTEM DESIGN

1 Reactive Systems
1.1 Examples of Reactive Systems
1.2 Reactive Versus Transformational Systems 
1.3 Four Case Studies And Three Examples 
1.4 Summary 
1.5 Questions and Exercises 

2 The Environment
2.1 External Interactions
2.2 Domains
2.3 The Subject Domain
2.3.1 Physical entities
2.3.2 Conceptual entities
2.3.3 Lexical entities
2.4 The Functions of Reactive Systems 
2.5 The Connection Domain 
2.6 Summary 
2.7 Questions and Exercises 

3 Stimulus-Response Behavior
3.1 Cause-Effect Chains  
3.2 Events, Conditions and Actions 
3.3 Events and Stimuli 
3.3.1 Assumptions about observers 
3.3.2 Event recognition  
3.3.3 Unobservable events  
3.3.4 Observing temporal events  
3.4 Responses and Actions  
3.4.1 Assumptions about actors 
3.4.2 Response computation  
3.4.3 Unrealizable actions  
3.5 Summary  
3.6 Questions and Exercises  

4 Software Specifications  
4.1 The System Engineering Argument  
4.2 Specifications  
4.3 The Role of Assumptions  
4.4 Operational Property Specifications  
4.5 Summary  
4.6 Questions and Exercises  

PART II FUNCTION NOTATIONS

5 Mission Statement  
5.1 Notation  
5.2 Relating System Purpose to Environment Purpose  
5.2.1 Design levels  
5.2.2 Goal analysis  
5.3 Guidelines for Finding a Mission Statement  
5.4 Summary 
5.5 Questions and Exercises  

6 Function Refinement Tree 
6.1 Notation  
6.2 Design Guidelines  
6.3 Summary  
6.4 Questions and Exercises  

7 Service Description  
7.1 Notation  
7.2 Guidelines  
7.3 Summary  
7.4 Questions and Exercises  

PART III ENTITY NOTATIONS  

8 Entity-Relationship Diagrams  
8.1 Entities and Attributes  
8.1.1 Entity types  
8.1.2 Absolute cardinality properties  
8.2 Relationships  
8.2.1 Relative cardinality properties  
8.2.2 Association entities  
8.3 Generalization  
8.4 Summary  
8.5 Questions and Exercises  

9 ERD Modeling Guidelines  
9.1 The Subject Domain Boundary  
9.2 Entities versus Attributes  
9.3 Entity versus Relationships  
9.4 Taxonomic Structures  1
9.4.1 Rules of classification  
9.4.2 Static versus dynamic specialization  
9.4.3 Classification and counting  
9.4.4 Subtypes versus roles  
9.5 Validation  
9.6 Summary  
9.7 Questions and Exercises 
 
10 The Dictionary  
10.1 Domain Ontology  
10.2 Syntactic categories  
10.3 Path expressions  
10.4 Extensional and Intensional Definitions  
10.5 Guidelines  
10.5.1 When to define a term  
10.5.2 Definitions by Genus and Difference  
10.5.3 Operational Definitions  
10.5.4 Abbreviations and correspondence rules  
10.6 Summary  
10.7 Questions and Exercises  

IV BEHAVIOR NOTATIONS  

11 State Transition Lists and Tables  
11.1 Event Lists  
11.2 State Transition Tables  
11.3 Decision Tables  
11.4 Summary  
11.5 Questions and Exercises  

12 State Transition Diagrams  
12.1 Mealy Diagrams  
12.2 Variables  
12.3 Statecharts  
12.3.1 State reactions   
12.3.2 State hierarchy  
12.3.3 Parallelism  
12.4 Summary  
12.5 Questions and Exercises  

13 Behavioral Semantics  
13.1 Discretization  
13.2 Wait States and Activity States  
13.3 Pre- and Postconditions  
13.4 Triggering  
13.5 Step Semantics Versus Single-Transition Semantics  
13.6 Multistep Semantics  
13.7 Action Semantics 
13.8 Time  
13.9 Summary  
13.10 Questions and Exercises  

14 Behavior Modeling and Design Guidelines  
14.1 Two Examples  
14.2 Guidelines 
14.2.1 The system engineering argument  
14.2.2 Finding a behavior description
14.2.3 From the environment to the system
14.3 Summary 
14.4 Questions and Exercises  

V COMMUNICATION NOTATIONS  

15 Data Flow Diagrams  
15.1 External Entities  
15.2 Flows  
15.3 Stores  
15.4 Processes  
15.4.1 Kinds of processes 
15.4.2 States of a process  
15.4.3 Data process specification  
15.4.4 Control process specification  
15.5 Parameterized DFDs  
15.6 Summary  
15.7 Questions and Exercises  

16 Communication Diagrams 
16.1 Requirement-Level Components 
16.2 Communication Channels  
16.3 Decomposition  
16.4 Allocation and Flowdown  
16.5 Summary  
16.6 Questions and Exercises  

17 Communication Semantics 
17.1 Component Behavioral Semantics  
17.2 Communication Channels  
17.3 The Network  
17.4 The Environment 
17.5 Summary  
17.6 Questions and Exercises  

18 Context Modeling Guidelines 
18.1 The System Boundary 
18.2 Context Diagrams 
18.3 The Context Boundary 
18.4 Structuring the Context  
18.5 Summary  
18.6 Questions and Exercises  

19 Requirements-Level Decomposition Guidelines  
19.1 Architectures  
19.2 Encapsulation Versus Layering  
19.3 Architectural Styles  
19.4 Requirements-level Architecture Guidelines  
19.4.1 Functional decomposition  
19.4.2 Subject-oriented decomposition  
19.4.3 Communication-oriented decomposition 
19.4.4 Behavior-oriented decomposition  
19.4.5 Choosing decomposition guidelines  
19.5 Evaluation 
19.6 Summary  
19.7 Questions and Exercises  2

VI SOFTWARE SPECIFICATION METHODS  

20 Postmodern Structured Analysis (PSA)  
20.1 Notations  
20.2 Coherence rules  
20.3 Choosing Notations 
20.4 Summary  
20.5 Questions and Exercises  

21 Statemate  
21.1 Notations  
21.1.1 Temporal events  
21.1.2 Starting, suspending, resuming and stopping activities  
21.2 Choosing Notations  
21.2.1 Placing activity in a statechart or in an activity chart  
21.2.2 Representing parallelism in statecharts or in activity charts  
21.3 Execution Semantics  
21.4 Summary  
21.5 Questions and Exercises  

22 The Unified Modeling Language (UML)  
22.1 Notations  
22.2 Activity Diagrams  
22.3 Static Structure Diagrams  
22.4 Behavior Specification  
22.5 Communication and Coherence  
22.6 Static Structure Design Guidelines  
22.7 Execution Algorithm  
22.8 Collaboration and Sequence Diagrams  
22.9 Summary  
22.10 Questions and Exercises  

23 Not Yet Another Method (NYAM)  
23.1 Software Design Context  
23.2 From Flyweight to Heavyweight Use of Notations  
23.3 Design Approach  
23.4 Engineering Arguments  
23.5 Formality and precision  
23.6 Summary  

APPENDICES

A A Training Information System  
B An Electronic Ticket System  
C A Heating Control System  
D An Elevator Control System  
E Answers to Selected Exercises

Glossary  
Bibliographic Remarks
Bibliography  
Index  

Online Materials (www.mkp.com/dmrs/)

E Answers to Selected Exercises (Continued), (pass protected)
F A Controller for a Compact Dynamic Bus Station
G A Cruise Control System
H A Logistics Information System

Slides for Teachers
Handout of the Slides
Notes for Teachers
--------------------------------------------------------------------------
To subscribe or unsubscribe yourself from
dbworld, send a msg to majordomo-hcNo3dDEHLuVc3sceRu5cw@xxxxxxxxxxxxxxxx with 
one of these lines:
subscribe dbworld OR unsubscribe dbworld
To find out more options send a msg with the line:
help
To post messages, go to URL www.cs.wisc.edu/dbworld
--------------------------------------------------------------------------