Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process

( 1 )

Want to read this on your NOOK? Request as NOOK Book from the publisher

Thank you for requesting this book as a NOOK book from the publisher.

Customers Who Bought This Also Bought

More About This Book

Overview
Editorial Reviews
Product Details
Meet the Author
Table of Contents

ADVERTISING

Overview

The first book to cover Agile Modeling, a new modeling technique created specifically for XP projects eXtreme Programming (XP) has created a buzz in the software development community-much like Design Patterns did several years ago. Although XP presents a methodology for faster software development, many developers find that XP does not allow for modeling time, which is critical to ensure that a project meets its proposed requirements. They have also found that standard modeling techniques that use the Unified Modeling Language (UML) often do not work with this methodology. In this innovative book, Software Development columnist Scott Ambler presents Agile Modeling (AM)-a technique that he created for modeling XP projects using pieces of the UML and Rational's Unified Process (RUP). Ambler clearly explains AM, and shows readers how to incorporate AM, UML, and RUP into their development projects with the help of numerous case studies integrated throughout the book.

AM was created by the author for modeling XP projects-an element lacking in the original XP design
The XP community and its creator have embraced AM, which should give this book strong market acceptance

Companion Web site at www.agilemodeling.com features updates, links to XP and AM resources, and ongoing case studies about agile modeling.

Editorial Reviews

From Barnes & Noble

The Barnes & Noble Review
Executives talk about creating agile business processes. Developers increasingly talk about using agile methods -- witness the explosion of interest in Extreme Programming (XP), Scrum, Crystal, and other "light" methodologies. But, until recently, there's been no agile equivalent for the folks who model and document software.

Worse, there's been a widespread perception that careful modeling is the enemy of agility. It needn't be that way. Nor should it be. Even XP creator Kent Beck has written, "Contrary to the claims of some of XP's detractors, you do in fact invest time modeling when taking an XP approach, but only when you have no other choice. Sometimes it is significantly more productive for a developer to draw some bubbles and lines to think through an idea, or to compare several different approaches to solving a problem, than it is to simply start hacking out code."

Agile Modeling aims to show IT professionals how they can gain the benefits of modeling without losing speed and flexibility. In the book by the same name, Scott Ambler -- author of The Object Primer and co-author of classics like Mastering JavaBeans -- explains exactly what AM is, and isn't.

AM begins with the core principles and values of the agile development community: communication, simplicity, feedback, courage, and humility. As the Agile Alliance has put it, "Individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan."

For the modeler, these values translate in many ways. For instance, simplicity means not over-modeling your system. Model based on your current requirements, and refactor when they change. For those accustomed to conventional modeling, that can definitely take courage.

Equally important, "Model With a Purpose." Ever encounter a pile of artifacts whose size is matched only by its irrelevance? Ask: Why are you creating that artifact? For whom? How much complexity do they need and want? (Not sure? Ask.) Once your artifact has met its goals, put it aside and move on.

AM is not a complete replacement for other software processes. It doesn't encompass programming, testing, project management, deployment, system operations, or support. Therefore, folks who implement AM are likely to do so in the context of some other software process. The processes you can use AM with range from XP to behemoths like the Unified Process (UP). In fact, Ambler offers in-depth coverage of integrating AM with both XP and UP.

Ambler points out that UP is more flexible and agile than it's often given credit for, and that many of AM's principles are already part of AM -- including a reliance on testing, the creation of multiple models in parallel, and an openness to iterative modeling. Other principles can be added easily, assuming that project team members are willing.

But, he admits, it's all too easy to go overboard with the paperwork. AM users should "...question every single model that the UP suggests creating because it purposely describes a wide variety of artifacts, many of which your project simply doesn't need... the business modeling set includes a business use-case model, business rules, a business architecture document, and a business supplementary specification. Do you actually need all of these things? Likely not. If you do need them, do you need them as formal documentation? Likely not."

Along the way, Ambler introduces the essential practices of Agile Modeling. Many of these focus on transforming teamwork from talk to reality: modeling with others ("modeling is a group activity"), collective ownership (anyone can work on any model) and publicly displaying all your models. Others focus on staying grounded in reality. "Prove It with Code": think you understand the logic of a complex business rule? Try coding it. "Apply Patterns Gently": Suspect a design pattern applies to your situation? Don't incorporate that pattern's "overhead" until you're more confident (if you're iterating constantly, it won't be long).

Want agility? Don't want to sacrifice the clarity that modeling can deliver? With AM, you can have both -- and this book is the place to start. (Bill Camarda)

Bill Camarda is a consultant, writer, and web/multimedia content developer with nearly 20 years' experience in helping technology companies deploy and market advanced software, computing, and networking products and services. He served for nearly ten years as vice president of a New Jerseybased marketing company, where he supervised a wide range of graphics and web design projects. His 15 books include Special Edition Using Word 2000 and Upgrading & Fixing Networks For Dummies®, Second Edition.

Agile Modeling (AM) is defined as a practices-based process for effective software development modeling and documentation. Following an introduction to AM methodology, the author treats AM in the practical contexts of its principle of using the simplest tools possible, work areas, modeling teams, eXtreme programming, and barriers to developing an "agile culture." Includes a glossary. A companion Web site is available. Ambler is a computer consultant and contributor to such publications as Software Development magazine. Annotation c. Book News, Inc., Portland, OR

Product Details

ISBN-13: 9780471202820
Publisher: Wiley, John & Sons, Incorporated
Publication date: 3/21/2002
Pages: 404
Sales rank: 772,440
Product dimensions: 9.25 (w) x 7.50 (h) x 0.83 (d)

Meet the Author

SCOTT W. AMBLER is President and a senior consultant of Ronin International (www.ronin-intl.com), a software services consulting firm that specializes in software process mentoring and object/component-based software architecture and development. Scott is the author and/or coauthor of numerous books and also coeditor, with Larry Constantine, of the Unified Process series from CMP Books. Scott is a contributing editor with Software Development magazine and a columnist with IBM developerWorks. Scott has spoken at UML World, Software Development, OOPSLA, Object Expo, Java Expo, and Application Development.

	Foreword
	Preface
Pt. 1	Introduction to Agile Modeling	1
Ch. 1	Introduction	3
Ch. 2	Agile Modeling Values	19
Ch. 3	Core Principles	27
Ch. 4	Supplementary Principles	38
Ch. 5	Core Practices	44
Ch. 6	Supplementary Practices	60
Ch. 7	Order from Chaos: How the AM Practices Fit Together	73
Pt. 2	Agile Modeling in Practice	81
Ch. 8	Communication	83
Ch. 9	Nurturing an Agile Culture	89
Ch. 10	Using the Simplest Tools Possible?	101
Ch. 11	Agile Work Areas	118
Ch. 12	Agile Modeling Teams	124
Ch. 13	Agile Modeling Sessions	134
Ch. 14	Agile Documentation	143
Ch. 15	The UML and Beyond	168
Pt. 3	Agile Modeling and eXtreme Programming (XP)	175
Ch. 16	Setting the Record Straight	177
Ch. 17	Agile Modeling and eXtreme Programming	184
Ch. 18	Agile Modeling Throughout the XP Lifecycle	190
Ch. 19	Modeling During the XP Exploration Phase	199
Ch. 20	Modeling During an XP Iteration: Searching for Items	207
Ch. 21	Modeling During an XP Iteration: Totaling an Order	214
Pt. 4	Agile Modeling and the Unified Process	223
Ch. 22	Agile Modeling and the Unified Process	225
Ch. 23	Agile Modeling throughout the Unified Process Lifecycle	232
Ch. 24	Agile Business Modeling	246
Ch. 25	Agile Requirements	254
Ch. 26	Agile Analysis and Design	269
Ch. 27	Agile Infrastructure Management	292
Ch. 28	Adopting AM on an UP Project	304
Pt. 5	Looking Ahead	309
Ch. 29	Adopting Agile Modeling or Overcoming Adversity	311
Ch. 30	Conclusion: Choose to Succeed	325
App. A	Modeling Techniques	330
	Glossary of Definitions and Abbreviations	358
	References and Suggested Reading	369
	Index	375

Customer Reviews

Average Rating 4

( 1 )

Rating Distribution

( 0 )
( 1 )
( 0 )
( 0 )
( 0 )

If you've bought this product, tell the world how you liked it.

Write a Review

Anonymous

Posted October 31, 2008

No text was provided for this review.

If you find inappropriate content, please report it to Barnes & Noble

Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process

Overview

Customers Who Bought This Also Bought

More About This Book

Overview

Related Subjects

Editorial Reviews

From Barnes & Noble

Product Details

Meet the Author

Table of Contents

Rating Distribution