lets play scenario based programming von harel david (7 Ergebnisse)

Hardcover. Zustand: Très bon. Ancien livre de bibliothèque. Edition 2003. Ammareal reverse jusqu'à 15% du prix net de cet article à des organisations caritatives. ENGLISH DESCRIPTION Book Condition: Used, Very good. Former library book. Edition 2003. Ammareal gives back up to 15% of this item's net price to charity organizations.

1st edn. 8vo. Original pictorial boards (casing with slight lean - otherwise VG. Pp. xviii + 382, illus with coloured and b&w figures (lacks CD; no inscriptions).

Zustand: New. In.

Zustand: New. In.

Paperback. Zustand: Brand New. 400 pages. 9.45x6.61x0.79 inches. In Stock.

Hardcover. Zustand: Brand New. hardback/cd-rom edition. 382 pages. German language. 9.50x7.00x1.25 inches. In Stock.

Zustand: Hervorragend. Zustand: Hervorragend | Seiten: 404 | Sprache: Englisch | Produktart: Bücher | This book does not tell a story. Instead, it is about stories. Or rather, in technical terms, it is about scenarios. Scenarios of system behavior. It con­ centrates on reactive systems, be they software or hardware, or combined computer-embedded systems, including distributed and real-time systems. We propose a different way to program such systems, centered on inter­ object scenario-based behavior. The book describes a language, two tech­ niques, and a supporting tool. The language is a rather broad extension of live sequence charts (LSCs), the original version of which was proposed in 1998 by W. Damm and the first-listed author of this book. The first of the two techniques, called play-in, is a convenient way to 'play in' scenario­ based behavior directly from the system's graphical user interface (QUI). The second technique, play-out, makes it possible to execute, or 'play out', the behavior on the QUI as if it were programmed in a conventional intra­ object state-based fashion. All this is implemented in full in our tool, the Play-Engine. The book can be viewed as offering improvements in some ofthe phases of known system development life cycles, e.g., requirements capture and anal­ ysis, prototyping, and testing. However, there is a more radical way to view the book, namely, as proposing an alternative way to program reactivity, which, being based on inter-object scenarios, is a lot closer to how people think about systems and their behavior.