More Process Patterns: Delivering Large-Scale Systems Using Object Technology (SIGS: Managing Object Technology)

You looking to find the "More Process Patterns: Delivering Large-Scale Systems Using Object Technology (SIGS: Managing Object Technology)" Good news! You can purchase More Process Patterns: Delivering Large-Scale Systems Using Object Technology (SIGS: Managing Object Technology) with secure price and compare to view update price on this product. And deals on this product is available only for limited time.

   

Product Description

With his new book, More Process Patterns, Scott Ambler picks up where Process Patterns left off. Here, the author presents process patterns for the second half of the development lifecycle. He covers the Deliver phase and the Maintain and Support phases of large-scale, object-oriented system development. Each presented pattern is based on proven, real-world techniques and is geared toward medium to large-size organizations that need to develop software internally to support their main line of business. The book covers major management issues, such as people and risk management, and quality assurance. The final chapter presents strategies for using process patterns to introduce and/or mature one's software process. Developers and project managers who have just taken their first OO development course will find this book essential. Ambler takes the true needs of software development and delivery into consideration, covering cross-project, maintenance, operations, and support issues. This book uses the Unified Modeling Language (UML).

More Process Patterns: Delivering Large-Scale Systems Using Object Technology (SIGS: Managing Object Technology) Review

I was really impressed with this book. When you first read the description of it - it's about releasing software and then maintaining and supporting it - you wouldn't guess how valuable it really is to developers. Writing the greatest software in the world won't do you any good if you can't get it in the hands of your users, and the author tells you exactly how to do this. Gems of wisdom permeate the book, for example you need to plan to rework your software once you've tested it and that you should take the time to do an assessment, what I would consider a post-mortem, to learn from your mistakes (the author says experiences but call it like it is). The material in the book isn't rocket science, which the author is quick to point out, but it is something that is key to the success of your project. I really liked his idea of assessing your staff once your software is baselined for his "testing in the large." I think its exactly as he says, that developers will stick it out until the current release is ready to go out the door and then leave for greener pastures. By assessing them and investing the time to do career management you increase the chance of keeping your staff. I also liked his treatment of how to release the software, he's one of the few people that seem to recognize that you have to release software to your operations department, your support department, and to your end users. Once again, not rocket science but something that is often overlooked until the last minute.A strength of the book is the Maintain & Support phase. I've done software support before and it's a bitch. It's about time somebody finally wrote about it and told people how hard it actually is. Including Maintenance & Support in your software process is really important in my mind. Just like the author points out, the best developers take maintenance into consideration, the best project managers must also take into consideration how their software will be supported too. This philosophy is a big strength over the Unified Process in my mind because the full spectrum of the software lifecycle is taken into account, not just development. The author's "Identify Defects and Enhancement" stage process pattern is really just basic change control once your software is out the door but once again he did a really good job of saying how to do it. Another strength of the book is that it is based on real-world experience -- this stuff sounds to me like it would actually work. The book also has a solid foundation in theory, bringing both proven and theoretical practices together in an effective manner. I also liked chapter 10 because it summarizes key project management issues, such as training and education of your staff, risk management, metrics, quality assurance, and risk management from both Process Patterns and this book, More Process Patterns. These are all important issues that must be taken into account to succeed. In fact, for many people this book is a good buy just to get this chapter alone.The one thing that I don't like is that you really do need to buy two books, this one and the one before it, Process Patterns, to get a full picture of the overall software process. However, both books are pretty big and they both contain excellent information so its not such a bad thing in the end. Help other customers find the most helpful reviews Was this review helpful to you?�Yes No Report abuse | PermalinkComment Comment

Most of the consumer Reviews tell that the "More Process Patterns: Delivering Large-Scale Systems Using Object Technology (SIGS: Managing Object Technology)" are high quality item. You can read each testimony from consumers to find out cons and pros from More Process Patterns: Delivering Large-Scale Systems Using Object Technology (SIGS: Managing Object Technology) ...