

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.
Price now:
From
To
Price History:
Details: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.
Price now:
From
To
This site contains affiliate links for which we may be compensated.
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.
General | |
|---|---|
Brand | Springer |
artist | not specified |
format | hardcover |
Language | english |
type | textbook |
Sellers offer a range of delivery options, so you can choose the one that’s most convenient for you. Many sellers offer free delivery. You can always find the postage cost and estimated delivery date in a seller’s listing. You'll then be able to see a full list of delivery options during checkout. These can include: Express delivery, Standard delivery, Economy delivery, Click & Collect, Free local collection from seller.
Your options for returning an item vary depending on what you want to return, why you want to return it, and the seller's return policy. If the item is damaged or doesn't match the listing description, you can return it even if the seller's returns policy says they don't accept returns. If you've changed your mind and no longer want an item, you can still request a return, but the seller doesn't have to accept it. If the buyer changes their mind about a purchase and wants to return an item, they may need to pay return postage costs, depending on the seller's return policy. Sellers can provide a return postage address and additional return postage information for the buyer. Sellers pay for return postage if there's a problem with the item. For example, if the item doesn't match the listing description, is damaged or defective or is counterfeit. By law, customers in the European Union also have the right to cancel the purchase of an item within 14 days beginning from the day you receive, or a third party indicated by you (other than the carrier) receives, the last good ordered by you (if delivered separately). This applies to all products except for digital items (e.g. Digital Music) that are provided immediately to you with your acknowledgement, and other items such as video, DVD, audio, video games, Sex and Sensuality products and software products where the item has been unsealed.
Sellers have to offer a refund for certain items only if they are faulty, such as: Personalised items and custom-made items, Perishable items, Newspapers and magazines, Unwrapped CDs DVDs and computer software. If you used your PayPal balance or bank account to fund the original payment, the refunded money will go back to your PayPal account balance. If you used a credit or debit card to fund the original payment, the refunded money will go back to your card. The seller will effect the refund within three working days but it may take up to 30 days for Paypal to process the transfer. For payments funded partially by a card and partially by your balance/bank, the money taken from your card will go back to your card and the remainder will return to your PayPal balance.