Rating: 
Summary: Mini projet Magistère
Review: il est bien conçu et il convient bien à mettre en oeuvre UM
Rating:
Summary: Not as bad as many think
Review: In my opinion, I think this book is quite good. One review which I perused through, which states that this book is only reiteration of the obvious, I do not quite agree. The reasons are: a) Some software engineers do not come from a background in which they are familiar with the usage of UML. It's one thing to know the notations of UML and quite another to apply it to designing of systems(I am going through that). Therefore, this book provides a comprehensive view on "how-to" apply UML to developing a software, hence termed "Unified Software Development Process". (Remember the time when one has to do analysis or design work when one begins to frequently ask many 'why's) b) Reinteration has its good points as well. Reiteration of concepts, which you will find frequently in this book will enable the concepts to find their way into the membranes of the brain cells of reader sufficiently emough to burn holes. This is especially true for one who has just stepped into the arena of system analysing and designing. The conveying of the unified development concepts is so crystal clear that there are no holes by which reader has to assume. Everything is laid bare. c) The reader would be in a strong position to understand nitty gritty of the process, for example, what Analysis is, what it entails, the differences between analysis and designs/implementation and the pros and cons. Therefore, if you think you're a pro and extremely well versed(as in you know the ins and outs at a quick snap of finger) with the Unified Process just as Laotse was well versed and in touch with the nature, then you can forget this book. But if you want to be truly professional in this kind of work, this book is something you cannot do without.
Rating: 
Summary: Repetitious and disorganized
Review: Like many software developers with good ideas, the trio of Jacobson/Booch/Rumbaugh can't write to save their souls. There's good material in here if you can filter out the tedious repetitions, redundancies, and points of misplaced emphasis. The book completely fails to communicate the authors' important methodological insights. Sigh. I'm disappointed. But I'm keeping the book; it's good enough to stay in my library for a while.
Rating: 
Summary: Solid framework for standardized software development
Review: Many organizations continue to look for silver bullets to answer the aliments of their software delivery capabilities. While this book is not the complete answer (as clearly recognized by the authors "A complete account of a comprehensive, full life-cycle process is beyond the scope of any one book."), it is a solid and useful description of the software development process. The Unified Software Development Process is a significant piece of work that can be used as the basis for standardization by any software agency. With the Unified Software Development Process's flexibility and inherent continuity as the general definition, a number of very specific and precise development cases can be created. The advantage in building these development cases under the Unified Software Development Process is the tractability and traceability of the artifacts, and thus the consistency required for increasing maturity of the software practices in an organization. The authors have provided an enormous service to software agencies of large corporations by publishing this book to the public. However, the agencies themselves, through good process management and engineering practices, will need to provide the necessary extensions and integration to the practices of Project Management, Business Engineering and Governance to make this process directly applicable and capable of delivering true value. Nevertheless, as a person who dealt with this problem for many years in a large telecommunication company and now interacts with dozens of companies still wrestling with this problem, I strongly recommend this book.
Rating:
Summary: THE Software Development Process book.
Review: 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.
Rating:
Summary: Good content -- presented like a dry lecture.
Review: Remember in college how you had some professors who would lecture and some who would teach? This book, unfortunately, isn't about teaching. The authors have written "The Unified Software Development Process" to the academic OO community, not to students eager to learn OO techniques from the masters. Every reference in this book is footnoted, every historical precedent mentioned, every alternative way of doing something is brought up so it can properly be dismissed. It reads like a Ph.D. thesis. In other words, the authors seem more interested in pleasing OO academicians than in transferring their experience to OO disciples eager to learn from their years of experience. Still, I can't fault the actual content of the book. It's a good book, with good content. I just spent way too much time struggling to pull the content out of this book that reads like academic lecture notes.
Rating:
Summary: Excellent - if you're willing to put in the immense effort
Review: 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 (the book can and probably will give you a headache), what you'll get out of it is i think is worth it.
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.
Rating:
Summary: An excellent reference for the software development process
Review: The arriving of UML has had a tremendous impact on the software world. With the speed of its acceptance UML has everyone talking in the same notation (if not the same language). This book takes the debate to the next logical level, which is the process of actually building complex software systems. The Unified Process has the correct focus of building software for the users (requirements driven) in a given framework (architecture centric). It also emphasizes iterative development, which is a key success factor in today's market. The book is well organized and extremely adept at tackling such a complex issue. By identifying artifacts, workers and workflow for every phase of software development, the book delivers actionable advice to project managers and software developers. It is important to identify the book's focus and not confuse it with other topics, such as Business Process Reengineering and Object Reuse. It is obvious that the Unified Process is a distillation of years of experience and should be a reference point for anyone who is trying to tackle software development
Rating: 
Summary: An Unpleasant book about OO process
Review: The first reason for which I only gave 2 stars to this book is its weight. I'm sure that all this stuff can be given in at least the half size. To stay in drawbacks, we even have no effective guidelines for the activities, but only dry and "outside" description of activities. Moreover, the organisation with deeply nested sub-sections make the reading difficult. In the Unified Process itself, we had an interesting and detailled picture, with a lot of activities, workers and artifacts, but in fact it is a very classical approach (maybe it is a quality ?). But when the authors said that the method intagrates a component approach and patterns, it sound like a joke. I found painfull to read this book, because it's written in an unpleasant maneer, whatever the stuff inside. I hope to do not have to read such a dry book more than once per 5 year.
Rating:
Summary: Must-read - going to be the default OO process
Review: The hard thing to understand is how this is any different than the Rational Unified Process documented in another book. My conclusion is that it isn't. This book is just longer. It should be pointed out that this is not a neutral book as it is written by the co-owners of Rational Software and their process relays on using tools which they sell. However, on the positive side, at least, it doesn't beat this to death. The book is unusual in that it has parts that are appropiate for developers as well as project managers. Both are handled equally well. Project manages will like the book because it describes the phases, iterations, and risk managements. Designers will like the technical step-by-step information. The book is very easy to read and easy to understand. The sentence structure at times gets very repetitive, but actually that is the worst weakness of the book, which says a lot (that the explanations are not the core problem). This book is a must read for any serious OO designer or project manager. Even if it wasn't a good book, which it is, it is going to be the default process used in many companies.
| 
