@Book{Clements2003,
AUTHOR = {Clements, Paul and Bachmann, Felix and Bass, Len and Garlan, David and Ivers, James and Little, Reed and Nord, Robert and Stafford, Judith},
TITLE = {Documenting Software Architectures: Views and Beyond},
YEAR = {2003},
PUBLISHER = {Addison-Wesley},
ABSTRACT = {<center>
<br><img src='http://www.cs.cmu.edu/~able/publications/DSA/cover.jpg'>
</center>
For all but the most trivial software systems, you must pay close
attention to its architecture?the conceptual glue that holds every
phase of a project together for its many stakeholders. Without an
architecture that is appropriate for the problem being solved, the
project will at the very least stumble along, or most likely,
fail. Even with a superb architecture, if it is not well
understood and well communicated?in other words, well
documented?the project cannot be considered a complete
success.Although architecture is now widely recognized as a
critical element in software development, there has been little
guidance independent of language or notation about how to capture
it. Based on the authors' extensive experience, Documenting
Software Architecture, helps you to decide what information to
document and then, with guidelines and examples (in various
notations, including UML), shows you how to express an
architecture in a form that everyone can understand. If you go to
the trouble to create a strong architecture, you must also be
prepared to describe it in enough detail, without ambiguity, and
to organize it so that others can quickly find the information
they need. As a guide for practitioners, the book covers:Seven
rules for sound documentation The uses of software architecture
documentation, including goals and strategies Architectural views
and styles, with general introductions and specific examples
Documenting software interfaces and software behavior Templates
for capturing and organizing the information to generate a
coherent package.<br>
'This book is of immense value. It should save you
months of trials and errors, lots of undeserved hassle, and many
costly mistakes that could potentially jeopardize the whole
endeavor. It will become an important reference on the shelf of
the software architect.'<br>
?From the Foreword by Philippe Kruchten,
Rational Software Canada.},
NOTE = {<a href=http://www.cs.cmu.edu/~able/publications/DSA/Jolt.pdf>2003 Jolt Productivity Award Winner</a>},
ANNOTE = {<a href=http://www.amazon.com/exec/obidos/ASIN/0201703726/002-2443472-2680023>Available from Amazon.com</a>},
KEYWORDS = {Software Architecture}
}
|
|
