The Unified Software Development Process

The "Unified Software Development Process" is still probably the best book yet on software process. Yes, it's difficult to read and it's not an introduction by any means (it reads like a textbook). but, if you're willing to put in the time and effort, what you'll get out of it is i think is worth it. I often had to go over a page many times to understand exactly what they saying, and routinely ended up with a headache. but, I really think it pays off. The process they present just makes sense, and seems to be the right way to make software. The main ideas (iterative AND phased development, and architecture centric while being use case driven) blends the best from the software development world. I feel that on my successful projects, these same ideas just seem to intuitively happen. Unlike most process books, this one goes into detail. It shows you what deliveribles you should be creating, what types of workers should be working on the deliverbles and when. These details, for me gave me a much, much clearer understanding about how a process should work. Things aren't so high-level. You can apply them (once you've figured them out) by just following the workflows. To me, this book has as its foundation in one of Ivar Jacobson's previous software books: "Object-Oriented Software Engineering" (if you think his current book is hard to read, you should see this one, ugh). Also, an excellent book and should be read by every software architect. I think if you read both these books, you'll have a very solid foundation for what you need to know about Software Engineering. A previous reviewer is right, this is not a introductory text. It's better to read an intro book on the rational unified process first before moving on to this one.

If all you want to do is to throw together a dog kennel, then avoid this book.If you want to create a repeatable development process that is capable of continuous improvement, then look no further. The USDP stands the test of time.The book deals with all aspects of a Software Construction Process in a frank, logical and full manner. It must be the seminal work on the subject.

This book defines a process for object oriented software development. Essentially, it could do for the software engineering community, what UML has already done, that is draw together from the best methods and create a well thought out and vivid process. As a book, it clearly explains each essential aspect of the process (Use Case Driven, Architecture Centric, Iterative and Incremental), the steps needed to carry out the process and the 'artifacts' that are the result of each iteration of work. There are plenty of diagrams that back up each explanation, allowing the reader to get the whole picture. The book does require reading from cover to cover if you are not familiar with object oriented development. The book does not cover the software project management aspects in very much detail, leaving the reader to find details of the management aspects (eg Change control and Risk Management) to find in another book that covers these topics (Software Project Management by Royce, which is another book in the Addison Wesley Object Technology Series).

Most of us use a process to software development. Most of us do not use a formal process to do it. This book describes a formal process to software development. It is not the first book in its class nor is the last one. But it is one of the best I have ever read. Ivar's describes the Unified Software Development Process from top to bottom (the workflows) and from minute 0 to project delivery (the phases) in great detail.Be aware that this is not a object oriented analysis and design book. It is a software development process book. He explains what is the role that every developer should have in every workflow (requirements, analysis, design, implementation) and also the list of deliverables in every phase.The author explains in great detail what to look for (the goals) in every step on the software development. This is something that I have found really valuable.

For those looking for a comprehensive model for a disciplined software development process, this book is it. In this latest in the series of volumes from the Rational troika, Ivar Jacobson assumes the lead and takes us on a grand tour of the Unified Process. The book is a historical turning point. Far and away the best on the subject, it fills in many of the details missing from the earlier overview volume by Philippe Kruchten. For those familiar with the original object-oriented software engineering process developed by Jacobson at Ericsson and popularized under the Objectory rubric, the ancestry will be apparent, but the Unified Process has been elaborated through experience and the integration of other perspectives into a more comprehensive and universal model.If the undertaking were to be faulted at all, it would be in the ambitiousness of its premise, and only time and more experience will determine how close to a truly unified approach the authors have come. Although it is at times difficult to get a real overall picture of how all the various models and activities in the process fit together; the information is all there in the book.I commend this well-written and readable book to all managers and serious professionals who want a deeper understanding of how the sundry steps that lead to good software can be organized into a highly disciplined and manageable process.