Access the full text.

Sign up today, get DeepDyve free for 14 days.

/lp/springer-e-books/a-practical-theory-of-reactive-systems-incremental-modeling-of-dynamic-QGAo0p05gM

- Publisher
- Springer Berlin Heidelberg
- Copyright
- Copyright � Springer Basel AG
- DOI
- 10.1007/b138956
- Publisher site
- See Book on Publisher Site

A man may imagine he understands something, but still not understand anything in the way that he ought to. (Paul of Tarsus, 1 Corinthians 8:2) Calling this a ‘practical theory’ may require some explanation. Theory and practice are often thought of as two di?erent worlds, governed bydi?erentideals,principles, andlaws.DavidLorgeParnas, forinstance,who hascontributedmuchtoourtheoreticalunderstandingofsoftwareengineering and also to sound use of theory in the practice of it, likes to point out that ‘theoretically’ is synonymous to ‘not really’. In applied mathematics the goal is to discover useful connections between these two worlds. My thesis is that in software engineering this two-world view is inadequate, and a more intimate interplay is required between theory and practice. That is, both theoretical and practical components should be integrated into a practical theory. It should beclearfrom theabovethattheintended readership of this book is not theoreticians. They would probably have di?culties in appreciating a book on theory where the presentation does not proceed in a logical sequence from basic de?nitions to theorems and mathematical proofs, followed by - plication examples. In fact, all this would not constitute what I understand by a practical theory in this context.; A man may imagine he understands something, but still not understand anything in the way that he ought to. (Paul of Tarsus, 1 Corinthians 8:2) Calling this a ‘practical theory’ may require some explanation. Theory and practice are often thought of as two di?erent worlds, governed bydi?erentideals,principles, andlaws.DavidLorgeParnas, forinstance,who hascontributedmuchtoourtheoreticalunderstandingofsoftwareengineering and also to sound use of theory in the practice of it, likes to point out that ‘theoretically’ is synonymous to ‘not really’. In applied mathematics the goal is to discover useful connections between these two worlds. My thesis is that in software engineering this two-world view is inadequate, and a more intimate interplay is required between theory and practice. That is, both theoretical and practical components should be integrated into a practical theory. It should beclearfrom theabovethattheintended readership of this book is not theoreticians. They would probably have di?culties in appreciating a book on theory where the presentation does not proceed in a logical sequence from basic de?nitions to theorems and mathematical proofs, followed by - plication examples. In fact, all this would not constitute what I understand by a practical theory in this context.; Prologue.- Components of a Theory.- Fundamentals.- Towards an Action Language.- Formal Properties of Behaviors.- Proving Behavioral Properties.- Building a Practical Theory.- Basic Language Facilities.- Fundamentals of Design Methodology.- Object Orientation Elaborated.- Components and Interfaces.- Distributed and Real-Time Systems.- Distributed Systems.- Real Time.- Epilogue.- Reexamining the Theory.; From the reviews: "Kurki-Suinio’s book aims at developing a practical theory for the development of distributed reactive systems. … The approach presented in the book is the result of many years of research. The design method developed by the author has been successfully used for the construction of many distributed parallel systems. … Potential audience of this book is definitely found among software engineers … . The book is also useful for researchers working in the mentioned area." (Klaus Schneider, The Computer Journal, 2007) "This book deals with reactive systems by first explaining a simple condition action effect language, which is similar to the language Unity or the one used in I/O automata. … The book is usable as an extensive introduction for those who acquire the skill to use and extend it elsewhere. Of course as such it also usable for those who want to know what is going on in the field of concurrency from a TLA perspective." (Jan Friso Groote, Zentralblatt MATH, Vol. 1070, 2005) "It is rare to find a book that answers the questions of software engineers who are working with dynamic systems … where formalisms of actions and behaviors are often answered by abstract theories of artificial intelligence. … . Overall, this is a well-written book, which takes a practical software engineering approach, rather than a philosophical artificial intelligence (AI) one. The book will make a good complementary reading for courses on intelligent agents, showing a practical route for translating theory into software specifications." (Aladdin Ayesh, Computing Reviews, April, 2006) ; Reino Kurki-Suonio has a PhD in mathematics from the University of Helsinki. He entered the field of computing in 1960. In 1965 he moved from industry to the University of Tampere to start the first computer science department in Finland. In 1980 he was invited to develop education in information technology at Tampere University of Technology, where he currently serves as professor emeritus at the Institute of Software Systems. During his career he has held visiting positions at Carnegie Mellon and Stanford Universities, and has served as the Chair of IFIP Technical Committee on Software, Theory and Practice. ; This book presents a practical theory of reactive systems. The theory supports incremental development of operational, object-oriented models in steps that preserve already established properties. Models are given in an action-oriented language, and their modularity relates to aspects in aspect-oriented programming. The emphasis is on theoretical understanding of reactive behaviors and on using horizontal modularity to manage their complexity. Special chapters are devoted to the applicability of the theory to distributed and real-time systems. Incremental specification is illustrated in the book by a number of examples of varying size and complexity. ; DE

**Published: ** Mar 30, 2006

Loading...

Read and print from thousands of top scholarly journals.

System error. Please try again!

Already have an account? Log in

Bookmark this article. You can see your Bookmarks on your DeepDyve Library.

To save an article, **log in** first, or **sign up** for a DeepDyve account if you don’t already have one.

Copy and paste the desired citation format or use the link below to download a file formatted for EndNote

Access the full text.

Sign up today, get DeepDyve free for 14 days.