000 06197nam a2200601 i 4500
001 011452872585
005 20260528133338.0
006 m eo d
007 cr cn |||m|||a
008 160511s2016 nyua fob 000 0deng d
020 _a9781970001778
_qebook
020 _z9781970001785
_qePub
020 _z9781970001761
_qpaperback
020 _z9781970001792
_qhardcover
024 7 _a10.1145/2872585
_2doi
035 _a(OCoLC)949774405
040 _aCaBNVSL
_beng
_erda
_cCaBNVSL
_dCaBNVSL
050 4 _aQA76.625
_b.B277 2016
082 0 4 _a005.276
_223
035 _a(CaBNVSL)swl00406470
100 1 _aBarbier, Franck.,
_eauthor.
245 1 0 _aReactive Internet programming :
_bState Chart XML in action /
_cFranck Barbier.
250 _aFirst edition.
264 1 _a[New York] :
_bAssociation for Computing Machinery ;
_a[San Rafael, California] :
_bMorgan & Claypool,
_c2016.
300 _a1 PDF (xv, 224 pages) :
_billustrations.
336 _atext
_2rdacontent
337 _aelectronic
_2isbdmedia
338 _aonline resource
_2rdacarrier
490 1 _aACM books,
_x2374-6777 ;
_v#10
504 _aIncludes bibliographical references (pages 223-224).
506 _aAbstract freely available; full-text restricted to subscribers or individual document purchasers.
588 _aTitle from PDF title page (viewed on May 11, 2016).
538 _aMode of access: World Wide Web.
538 _aSystem requirements: Adobe Acrobat Reader.
505 0 _a1. 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 --
505 8 _a2. 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 --
505 8 _a3. 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 --
505 8 _a4. 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 --
505 8 _a5. 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 --
505 8 _a6. 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 --
505 8 _a7. 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 --
505 8 _a8. 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 --
505 8 _a9. Software component management -- 9.1 Dynamical (Re)configuration -- 9.2 Extended management framework -- 9.3 Pushing state machine data outside --
505 8 _aAppendix 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.
520 3 _aIs Internet software so different from "ordinary" software? This book practically answers this question through the presentation of a software design method based on the State Chart XML W3C standard along with Java, Web enterprise, Internet-of-Things, and Android applications, in particular, are seamlessly specified and implemented from "executable models." Internet software puts forward the idea of event-driven or reactive programming, as pointed out in Bon�er et al.'s "Reactive Manifesto" (http://www.reactivemanifesto.org). It tells us that reactiveness is a must. However, beyond concepts, software engineers require effective means with which to put reactive programming into practice. This book's purpose is to outline and explain such means. The lack of professional examples in the literature that illustrate how reactive software should be shaped can be quite frustrating. Therefore, this book helps to fill in that gap by providing in-depth professional case studies that contain comprehensive details and meaningful alternatives. Furthermore, these case studies can be downloaded for further investigation. Internet software requires higher adaptation, at run time in particular. After reading Reactive Internet Programming, the reader therefore will be ready to enter the forthcoming Internet era.
530 _aAlso available in print.
650 0 _aInternet programming.
650 0 _aSCXML (Document markup language)
650 0 _aStatecharts (Computer science)
776 0 8 _iPrint version:
_z9781970001792
_z9781970001761
830 0 _aACM books ;
_v#10.
_x2374-6777
856 4 8 _3Abstract with links to full text
_uhttp://dx.doi.org/10.1145/2872585
999 _c357
_d357