Agile Modeling and over one million other books are available for Amazon Kindle. Learn more
CDN$ 41.37
  • List Price: CDN$ 65.99
  • You Save: CDN$ 24.62 (37%)
Only 1 left in stock (more on the way).
Ships from and sold by Amazon.ca.
Gift-wrap available.
Quantity:1
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process Paperback – Apr 4 2002


See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
Paperback
"Please retry"
CDN$ 41.37
CDN$ 34.81 CDN$ 2.74

Best Canadian Books of 2014
Margaret Atwood's stunning new collection of stories, Stone Mattress, is our #1 Canadian pick for 2014. See all

Customers Who Bought This Item Also Bought



Hero Quick Promo
Boxing Day Kindle Deals
Load your library with over 30 popular fiction books and more, today only. Learn more

Product Details

  • Paperback: 400 pages
  • Publisher: Wiley; 1 edition (April 4 2002)
  • Language: English
  • ISBN-10: 0471202827
  • ISBN-13: 978-0471202820
  • Product Dimensions: 19.2 x 2.3 x 23.5 cm
  • Shipping Weight: 816 g
  • Average Customer Review: 3.7 out of 5 stars  See all reviews (22 customer reviews)
  • Amazon Bestsellers Rank: #208,781 in Books (See Top 100 in Books)
  • See Complete Table of Contents

Product Description

Review

“…I would not hesitate in recommending this book…” (CVu, October 2004)

“…easy-to-follow…enjoyable writing style…overall the book is impressive…valuable reading…” (Software Testing, Verification & Reliability, March 2003)

From the Back Cover

"In Agile Modeling, Scott Ambler captures the spirit of skillfully applying the UML, patterns, and more-the balance between too much and too little."
-Craig Larman

Extreme Programming (XP) and the Unified Process (UP) have both caused quite a sensation in the software development community. Although XP offers a methodology for faster software development, many developers find that it does not explicitly include modeling time, which is crucial to ensure that a project meets its proposed requirements. UP developers, on the other hand, have found that the UP approach to modeling is too documentation-intensive and top heavy, thus impeding progress.

Enter Agile Modeling (AM)-- a unique methodology specifically designed to enhance your modeling efforts on software development projects.

In this innovative book, Scott Ambler reviews how to:
* Model on an XP project without detracting from its fast-moving and agile software development approach
* Simplify the modeling disciplines/workflows of the UP without losing any of the true benefits of those disciplines
* Use modeling to explore an issue or to facilitate communication
* Effectively apply the UML, and extend it with other methodologies, to meet your real-world development needs
* Reduce the documentation burden on your project by writing agile documents
* Use simple modeling tools, such as index cards and whiteboards, and know when to use complex CASE tools
* Rethink your approach to work areas, modeling teams, and modeling sessions

The companion Web site includes updates to the book, links to XP and AM resources, and ongoing case studies about AM.

Wiley Computer Publishing
Timely. Practical. Reliable.

Visit our Web site at www.wiley.com/compbooks/
Visit the companion Web site at www.wiley.com/compbooks/ambler
Visit the author's Web site at www.agilemodeling.com

Inside This Book (Learn More)
First Sentence
When I first read Extreme Programming Explained (Beck 2000), one of the most poignant things about XP for me was how Kent first defined a foundation for his methodology. Read the first page
Explore More
Concordance
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Customer Reviews

3.7 out of 5 stars

Most helpful customer reviews

Format: Paperback
One of the values of the agile movement is simplicity, which the author kindly spends about two pages explaining it to us mere mortals. And it seems only logical that this high principle would also imply brevity. Unfortunately, this book in itself is a violation of that principle. The only useful lesson that one can possibly distill from this three hundred and fifty pages tome is the following: Keep it simple, lose it if you don't use it, and don't hesitate to ditch your expensive modeling software when it becomes too restrictive. A wonderful and very effective advice if I may add, but there is definitely no need for an entire book to explain it.
This book is neither a modeling tutorial nor an introduction. And if you have had any decent amount of practical modeling experience then chances are you have already learned the above lesson. As such, the book fails to hit the mark for both experts and novice modelers. Nevertheless, the lesson it contains is important, thus the two stars. The book itself, however, receives a flat zero rating.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Paperback
An adept application of common sense--and the author's significant experience--to the use of models in software development.
A model can be almost anything that developers make to describe the software that they build--just like an architect's drawings.
A given software development effort might call for any number of different types of models including data models, class models, sequence diagrams, dataflow diagrams, statechart diagrams, etc. The set of models used on any particular project will depend partly on the nature of the project and partly on the preferred methodology of the software developers.
Agile Modeling (AM) is not itself a software development methodology. It is a collection of principles and practices to follow when using models to develop software according to a methodology like Rational Unified Process (RUP) or eXtreme Programming (XP). Many of the practices derive from an application of XP concepts.
AM challenges a number of practices widely followed (or at least preached) in organizations developing software:
1. Specializing personnel in producing a single type of model
2. Dedicating work sessions to producing a single type of model
3. Saving models after the software is developed
4. Keeping models up-to-date during and after the development project
5. Using sophisticated software to assist in modeling
6. Finishing models before coding software
AM does not in all cases prohibit these practices, but it emphasizes that the purpose of a software development project is to develop software--not just to develop models. The practices of AM help to keep models in their proper subordinate relation to the working software that is the true goal of any development project.
Read more ›
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Paperback
In this book, Scott Ambler provides a practical approach to modeling that allows you to successfully deploy best practices on your agile software development project. From use case modeling to deployment diagrams, agile modeling defines these best practices for rapidly moving from requirements to code in a single, easy to read book. Additionally, Scott presents many of the nuances of software modeling that cannot be found in any other book.
Perhaps the most interesting part of Agile Modeling is that it is not only a book about a great software development methodology; it also suggests cultural changes to the way that we view modeling. These changes blur the line between traditional approaches such as those espoused by the Unified Process and the new culture espoused by XP. These ideas are very much in line with the way that software is successfully produced.
This book is not an entry-level UML book. If you are looking for basic UML, look at some of the entry level UML books. Instead, this book geared toward those who are actively producing customer grade software applications. It hits the mark squarely for those who want to be more successful in this endeavor.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Paperback
My first impression on receiving "Agile Modeling" was that there is lots of information which could be condensed into tighter passages or sometimes omitted.
I have read Scott Ambler's work before and am an admirer of his contribution to software development. I found the book helpful, as with most of Scott's work, despite the sometimes redundant information.
Despite my cautionary introduction above, I recommend this book to developers and project managers.
In this book the reader can expect to find information on how to implement development processes with Agile Modeling (AM).
This book discusses the processes for development - it does not go into the details on how to use the tools.
There is a comparison chapter on AM and XP which is helpful. AM, like all development processes, is a mixture of art and science. It is not carved in stone - although many may disagree with this statement. This book will help the reader decide what is appropriate to utilize for the project, given the real-world scenarios.
Hope this helps - please let me know if you have any questions or suggestions.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.

Most recent customer reviews



Feedback