Reactive Internet programming : State Chart XML in action /
| Main Author: | |
|---|---|
| Format: | eBook |
| Language: | English |
| Published: |
[New York] : [San Rafael, California] :
Association for Computing Machinery ; Morgan & Claypool,
2016.
|
| Edition: | First edition. |
| Series: | ACM books ;
#10. |
| Subjects: | |
| Online Access: | Connect to the full text of this electronic book |
Table of Contents:
- 1. Introduction
- 1.1 Software engineering in the Internet era
- 1.2 Expected benefits of model-driven software development
- 1.3 Programming with events and states
- 1.4 Model execution or interpretation
- 1.5 Architectural issues of Internet programming
- 2. Event and state-based modeling and programming
- 2.1 States are universal and everywhere
- 2.2 States are abstract and discrete
- 2.3 "Event" as dual notion of state
- 2.4
- Harel's Statecharts
- 2.5 Discovering state chart XML
- 2.6 Statechart execution
- 3. Applying State Chart XML
- 3.1 Startup of Barbados crisis management system
- 3.2 Business case: "route negotiation"
- 3.3 Timing constraints
- 3.4 Introduction to the run-to-completion execution mode
- 3.5 Variations on modeling: the power of Statecharts
- 3.6 Evaluation
- 4. Programming State Chart XML models
- 4.1 Programming "my device"
- 4.2 Setup of entry and exit actions
- 4.3 Setup of activities
- 4.4 Sending events internally
- 4.5 Action parameters
- 4.6 State machine kick-off
- 4.7 State machine shutdown
- 4.8 State machine tracing
- 4.9 Transition programming
- 4.10 Guard programming
- 4.11 Event processing
- 4.12 Communication programming
- 5. Execution semantics
- 5.1 Example of execution semantics potential defects
- 5.2 Run-to-completion cycles
- 5.3 Action and activity execution sequencing
- 5.4 Execution sequencing and orthogonality
- 5.5 Execution sequencing and nesting
- 5.6 Event consumption principle
- 5.7 Deferred events
- 5.8 Transition conflicts
- 6. Advanced programming with PauWare engine
- 6.1 Completion transitions
- 6.2 Timer services
- 6.3 State and event naming
- 6.4 Single nesting
- 6.5 The notion of "internal transition" in State Chart XML
- 6.6 Allowed events at large
- 6.7 Unicast vs. multicast calls/communications
- 6.8 Cached transitions vs. contextual transitions
- 6.9 Data consistency checking through state invariants
- 6.10 History facilities
- 6.11 Concurrency
- 7. Programming the "Internet of things"
- 7.1 Characterization of "Internet of things" applications
- 7.2 Application requirements (home automation system)
- 7.3 Analysis
- 7.4 Design
- 7.5 Implementation issues
- 8. Programming web enterprise applications
- 8.1 Characterization of web enterprise applications
- 8.2 Application requirements (railcar control system)
- 8.3 Analysis
- 8.4 Design
- 8.5 Implementation issues
- 9. Software component management
- 9.1 Dynamical (Re)configuration
- 9.2 Extended management framework
- 9.3 Pushing state machine data outside
- Appendix A. Internal structure of PauWare engine
- A.1. Organization of a state machine's states in memory
- A.2. Organization of a state machine's transitions in memory
- Appendix B. Acronyms
- Appendix C. Downloadable software resources
- References
- Author's biography.