Wednesday, November 11, 2009

8.8 For Further Reading











Team-Fly

 

 

















Documenting Software Architectures: Views and Beyond
By
Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Robert Nord, Judith Stafford
Table of Contents

Chapter 8. 
Documenting Behavior







8.8 For Further Reading


A rich source for behavior descriptions can be found in the UML definition that is publicly available from the OMG. At http://www.omg.org/uml/ you can find definitions, descriptions, and examples of sequence and collaboration diagrams as well as example use cases and statecharts. You can also find several books that explain UML and its usage in detail. Two seminal books that you will find to be valuable references are The Unified Modeling Language User Guide by Booch, Jacobson, and Rumbaugh [Booch+ 99] and The Unified Software Development Process by Jacobson, Booch, and Rumbaugh [Jacobson+ 99].


A good reference for statecharts is Modeling Reactive Systems with Statecharts: The Statemate Approach by Harel and Politi [HarelPoliti 98].


Message sequence charts, especially combined with SDL diagrams, are broadly used by the telecommunication industry. Both languages are standardized by the International Telecommunication Union (ITU). Their Web site, http://www.itu.int, has all the references to resources, such as documentation and tool vendors, needed to understand and use MSC and SDL. Additional information and pointers to events, tools, and papers can be found at the SDL Forum Society's Web site: http://www.sdl-forum.org/. The SDL Forum Society currently recommends SDL Formal Object-Oriented Language for Communicating Systems by Ellsberger, Hogrefe, and Sarma [Ellsberger+ 97] as the best practical guide to the use of SDL.


Many books have been written about use cases. The book from Ivar Jacobson that started the whole use case discussion is Object-Oriented Software Engineering: A Use Case Driven Approach [Jacobson 92]. This book can serve as a starting point to understand what was originally meant by use cases and their underlying concepts.


Use case maps are still in the research domain, although there is a user group that tries to show the value of use case maps by applying the method to several projects. You can find much interesting information at their Web site at http://www.usecasemaps.org, including a free download of the book Use Case Maps for Object-Oriented Systems by Buhr and Casselman [BuhrCasselman 96]. At that Web site you can also find a free tool that supports use case maps.


Z was originally developed at Oxford University in the late 1970s and has been extended by a number of groups since then. A large number of support tools, to help create and analyze specifications, have been developed by various groups and are available freely over the Internet. A great resource for information and pointers is the Web archive found at http://archive.comlab.ox.ac.uk/z.html. There are a number of books available through your local bookseller to guide you in the use of J. M. Spivey's book, The Z Notation: A Reference Manual, 2d ed. [Spivey 88] is available both in print and online at http://spivey.oriel.ox.ac.uk/~mike/zrm/. It provides a good reference in terms of a standard set of features.


For more information on Object Z and TCOZ, extensions to the notation, see [Duket 95] and [Mahoney Dong 00].


A MetaH user manual, instructions for obtaining an evaluation copy of the tool for use on NT 4.0, and other associated information about MetaH is available at the MetaH Web site: http://www.htc.honeywell.com/metah/.


In addition to this site Honeywell has a Web site that describes both ControlH and MetaH in terms of their relationship to domain-specific software architecture. Publications that may be of interest include [Feiler+ 00], [Honeywell 00], and [Lewis 99].


A good Rapide tutorial along with other information and manuals associated with Rapide are available from the Rapide Web site at Stanford University: http://pavg.stanford.edu/rapide/. Publications containing information on specific aspects of Rapide include [Luckham+ 95], [LuckhamVera 95], and [PerrochonMann 99].


Architecture description languages (ADLs) have been developed within the research community to support description, in textual form, of both the structure and the behavior of software systems. See Stafford and Wolf [StaffordWolf 01] for a discussion of ADLs including a table containing references to and brief descriptions of several languages.


Useful Web Sites


This list of pointers below is alphabetized by diagram type for quick reference.


Collaboration Diagrams

OMG Web site: http://www.omg.org/uml/


Message Sequence Charts

International Telecommunication Union Web site: http://www.itu.int


SDL Forum Society's Web site: http://www.sdl-forum.org/


MetaH

Honeywell site for MetaH: http://www.htc.honeywell.com/metah/


Honeywell site for ControlH and MetaH: http://www.htc.honeywell.com/projects/dssa/dssa-tools.html


Rapide

The Rapide site at Stanford University: http://pavg.stanford.edu/rapide/


The Rapide online tutorial: http://pavg.stanford.edu/rapide/examples/teaching/dtp/index.html


Sequence Diagrams

OMG Web site: http://www.omg.org/uml/


SDL

SDL Forum Society's Web site: http://www.sdl-forum.org/


International Telecommunication Union Web site: http://www.itu.int


Statecharts

International Telecommunication Union Web site: http://www.itu.int


Use Case Maps

Use Case Maps Web site including manuscript of seminal book [BuhrCasselman 96]: http://www.usecasemaps.org


Z

J. M. Spivey's book [Spivey 88]: http://spivey.oriel.ox.ac.uk/~mike/zrm/


A collection of pointers: http://archive.comlab.ox.ac.uk/z.html












    Team-Fly

     

     





    Top



    No comments: