Main description:

Behavioral Specifications of Businesses and Systems deals with the reading, writing and understanding of specifications. The papers presented in this book describe useful and sometimes elegant concepts, good practices (in programming and in specifications), and solid underlying theory that is of interest and importance to those who deal with increased complexity of business and systems. Most concepts have been successfully used in actual industrial projects, while others are from the forefront of research. Authors include practitioners, business thinkers, academics and applied mathematicians. These seemingly different papers address different aspects of a single problem - taming complexity. Behavioral Specifications of Businesses and Systems emphasizes simplicity and elegance in specifications without concentrating on particular methodologies, languages or tools. It shows how to handle complexity, and, specifically, how to succeed in understanding and specifying businesses and systems based upon precise and abstract concepts. It promotes reuse of such concepts, and of constructs based on them, without taking reuse for granted.
Behavioral Specifications of Businesses and Systems is the second volume of papers based on a series of workshops held alongside ACM's annual conference on Object-Oriented Programming Systems Languages and Applications (OOPSLA) and European Conference on Object-Oriented Programming (ECOOP). The first volume, Object-Oriented Behavioral Specifications, edited by Haim Kilov and William Harvey, was published by Kluwer Academic Publishers in 1996.

Contents:

Preface. 1. Object-oriented transformation; K. Baclawski, et al. 2. Being served: The purposes, strengths and limitations of formal service modelling; B. Cohen. 3. What vs. how of visual modelling: The arrow-diagram logic of visual modelling; Z. Diskin, et al. 4. Meta-modelling semantics of UML; A. Evans, et al. 5. Combining JSD and Cleanroom for object-oriented scenario specification; M. Frappier, R. St-Denis. 6. What is behind UML-RT; R. Grosu, et al. 7. Applying ISO RM-ODP in the specification of CORBA(R) interfaces and semantics to general ledger systems; J. Hassall, J. Eaton. 8. Component-based algebraic specifications; S. Iida, et al. 9. A meta-model semantics for structural constraints in UML; S. Kent, et al. 10. On the structure of convincing specifications; H. Kilov, A. Ash. 11. Formalising the UML in structured temporal theories; K. Lano, J. Bicarregui. 12. JML: A notation for detailed design; G. Leavens, et al. 13. Agents: Between order and chaos; J. Odell. 14. UML, the future standard software architecture description language? A. Schurr, A. Winter. 15. Using information modelling to define business requirements; M. Shafer. 16. A layered context perspective on enterprises and information systems; I. Simmonds, D. Ing. 17. 30 Things that go wrong in object-oriented modelling with UML 1.3; A. Simons, I. Graham. 18. Formalizing association semantics in terminologies; H.Solbrig.19. On the specification of the business and economic foundations of electronic commerce; A. Thalassinidis, I. Sack. 20. Embedding object-oriented design in system engineering; R. Wieringa. Index.