|Get your FREE Diabetes Recipes eBook!|
Bought this book for some time, but recently has truly had it again, the book is not thick, 300 pages or so, but learned a lot after reading feeling.
This book does not teach you specific modeling techniques, such as UML, models such as the use, or teach you an example of hands-on, but first put forward the principles of Agile Modeling, Agile practices to explain what is modeling and its key part. And then expand the products that agile modeling, and the Unified Process, XP and combination.
For me, reading this book is not the biggest gain access to some of the technology, but understand a truth, in the software development process, “degree” of the master key, from the traditional heavy-duty software development process to the present agile development, the most important thing is not test-driven, not pair programming, the most important thing in software development is the “degree” of the re-definition of the balance between too little too much. We often mention the “over-design”, “too much documentation,” and so on, and both are on the “degree” of control is a problem, but do not fault these things themselves, instead their role is irreplaceable.
On the “degree” of control directly extended to the “appropriate”, “no best, only better”, according to their own project size, team composition, administrative organizations, find their own process. Otherwise, you are immediately “agile”, but the project still faces the risk of loss of control.
“Too far”, “extremes meet”, to maintain the balance point is really an ideal, in software development can only be adjusted from time to time direction, although not the most in the right direction, but to ensure that we do not drift too far.
Sorry, the comment form is closed at this time.