Rating: 
Summary: This is a dumb book.
Review: I think you guys need to get lives and but out some better books then this one.
Rating: 
Summary: A great quick reference and introduction to the RUP
Review: I've been using the RUP since it's inception ( no pun intended ) and this is by far the most valuable reference I have on my desk at all times, ok the RUP web based product from Rational is better but that cost me $800 so if you can't get your hands on that just yet, get this book, you will be satisfied even if your are a seasoned RUPer like myself. For beginers, this is a MUST read, no other book will jump start you into the RUP like this one will. I will be putting up tons of articles and references as well as my own writings on the RUP on my website ( just type in my last name into your browser ;o) ) so check it out on Sep 1, 2000 when I release the new version. One more quick point, don't get Jacobson's "Unified Software Development Process" until you have read this book, even then I'd wait til the next edition comes out because the current one is somewhat out of date, but still useful if you're really into this stuff. Also, a great companion to this book is "eXtreme Programming explained, embrace change" by Kent Beck, for people who work at the forefront of technology such as myself, combining these two ways of developing applications will yield great results, I'll be writing several articles on this topic so check out my site for them...
Rating:
Summary: good book on OO process
Review: It documents the Object-oriented design process used by the Rational Corporation. In case you are not aware, the authors of UML work for Rational and they are the company that makes Rational Rose, the market leader in OO design tools. The book outlines the process, which has many good features. One example is that the process uses the spiral methodology instead of waterfall. The book covers all phases of processes you might want to put in place in an OO project. Unlike many OO process books for the past, this book keeps it feet on the ground and stays readable. Others in the past have usually drafted into obscure technical details. The book has two problems. The first is that the prose is pretty stilted. Way too many sentences start with "The Rational Unified Process is". The other problem is that the book is geared around using the tools from Rational. However, it is possible to use most of the process without using the tools from Rational. In summary, this book documents a pretty good OO design process in a very easy to understand way. If you are looking for an OO process to follow or are looking for ways to improve your existing one, this book is an excellent starting book.
Rating: 
Summary: A Much-Needed Summary
Review: Kruchten has written what amounts to an excellent summary of the main points of what is in many ways an alarmingly large list of costly books that present an over-worked, extremely detailed methodology that is said to be a reliable guide for software engineering and technical business management. The great virtue of Kruchten 's summary view is that it allows engineers and technical managers to see that much of what is offered as a guide for technology and business management is, in reality, little more than a sophistical reworking of the AI theory of the mid-1970's. Such a summary has long been needed, and this book, for this reason, is a welcome sight. Kruchten has been an employee of Rational Software, so the implications of the summary view he offers are in some ways unexpected. The explanation may be that it is evident from the first that author maintains reservations about the methodology he describes. While skepticism reveals a level of realism (or perhaps cynicism) that is interesting, the general impression may be a bit discouraging. If one of the primary evangelists of a management method reveals skepticism toward the method, then what is to become of all those managers who have advocated paying all that money to educate their employees in the use of the method? The answer is, of course, to be expected. Pay equal or greater amounts of money to seek education in alternative methods (possibly marketed by the same vendor). If this is, indeed, the action proposed, then any hint of skepticism ends up being a brave (if not offensive) gesture, to say the least, and it is understandable that it is not explicitly asserted. This book may represent what may be a significant crack in insular mysticism maintained by one of the major vendors of methodology in today's technical sector. The fact revealed is simply this: no technical method of management can replace the culture that a business creates by having bright people, successful products and good services. Certainly, a failing company seeking an image of success may benefit by purchasing classes on "rational business and technology management methods," but a genuinely successful company has its own culture, its own business vision, and ultimately its own managerial and production practices. These are the simple imperatives of the free market, which thrives, not on ideological conformity or fixed, enforced methodologies, but on innovation, creativity, and a common sense of professional purpose. Kruchten 's book may bring light to a dark area of the world at a moment when many companies must seek innovation in order to survive the economic downturn that is sweeping the technology industries. Probably the only qualification is that such a book ultimately brings about the conditions of its own demise. If we see the myth for what it is, then why do we continue to invest in it? Obviously, we don't, and the over-priced books summarizing outmoded AI theories go out of print.
Rating: 
Summary: A good reference
Review: Okay. I haven't read this book cover to cover. I never intended to - I got my job to purchased it as a reference for me. Lightweight processes are more appropriate in my professional circumstances (we don't use RUP), and I have been particularly interested in Rosenberg (and Scott)'s Iconix process. (See my reviews) However, I find Krutchen's book a good fat-free reference on how the heavy-weights do it. Sometimes one needs a bit of extra depth. The book is well illustrated, and it helps me to put processes such as Iconix (and maybe even XP) in context. The book covers the overall dimensions of the Rational Unified Process well. Issues such as best practice, iteration, team make-up, etc are also discussed. There is a big section on process workflow (more than 50%). It also adds the architectural viewpoint of the process, a section that I found quite useful. Philippe Kruchten is behind the 4+1 view model of architecture, so it is good to get it from the source. Should you buy this book? Like anything else, first decide how much you need it.
Rating:
Summary: Good introduction to RUP for beginners
Review: One thing's for sure: it's impossible for any one person to "know" the Rational Unified Process in and out. So, stop right there if you're looking to get the printed documentation of RUP, because it's logistically impossible to bundle it all into a paperback book. These titles give a bird's eye view of what RUP is and how it can be leveraged for optimal productivity in the vein of software development.
This book gives you great high-level insight on how your organization can benefit by adopting and implementing RUP in your developmental projects.
"The Rational Unified Process: An Introduction" is an overview into the theory behind RUP. Great chart and graphics describe the processes RUP is rooted in, and the title is written in such a way as to indirectly hammer home the concepts into your subconscious, without being too blatantly redundant. Essentially, you'll get the jist of RUP - iterations, that the waterfall process isn't efficient, the importance of establishing diversity in team-based development, and the importance of architecture.
Basically, the book also enforces the concept that self-organization and communication within an organization (within the team, throughout the company, and with clients) is key. It reads more like a business journal than a technical guide, so hands-on examples are left out.
Also, the poster summarizing the key RUP activities that's included with the book is really great. I would have liked a case study at the end of the book to tie together the concepts with a practical example, but the book is great otherwise. I also found the fact that samples of RUP templates to be a bit disappointing. A helpful appendix listing some (not all) of the key artifacts used in RUP planning is also appreciated.
Rating:
Summary: Good introduction to RUP for beginners
Review: One thing's for sure: it's impossible for any one person to "know" the Rational Unified Process in and out. So, stop right there if you're looking to get the printed documentation of RUP, because it's logistically impossible to bundle it all into a paperback book. These titles give a bird's eye view of what RUP is and how it can be leveraged for optimal productivity in the vein of software development.
This book gives you great high-level insight on how your organization can benefit by adopting and implementing RUP in your developmental projects.
"The Rational Unified Process: An Introduction" is an overview into the theory behind RUP. Great chart and graphics describe the processes RUP is rooted in, and the title is written in such a way as to indirectly hammer home the concepts into your subconscious, without being too blatantly redundant. Essentially, you'll get the jist of RUP - iterations, that the waterfall process isn't efficient, the importance of establishing diversity in team-based development, and the importance of architecture.
Basically, the book also enforces the concept that self-organization and communication within an organization (within the team, throughout the company, and with clients) is key. It reads more like a business journal than a technical guide, so hands-on examples are left out.
Also, the poster summarizing the key RUP activities that's included with the book is really great. I would have liked a case study at the end of the book to tie together the concepts with a practical example, but the book is great otherwise. I also found the fact that samples of RUP templates to be a bit disappointing. A helpful appendix listing some (not all) of the key artifacts used in RUP planning is also appreciated.
Rating:
Summary: The book is quite good.
Review: Pros: * It is a good introduction and starter-kit. * The methodology is reasonable and functional. * The organization is easily-followed. * The writing is clear and not overly technical. Cons: * It is not detailed enough in some places. * It is a little over-priced (for the length). * It should have artifact-templates. * It tends towards product-specificity in places. Overall, this book is well-worth the time. After reading it and some of the supporting materials from Rational, I was able to implement a scaled version right away. I mapped the "outline" of the process into a MS Project file, hooked the artifacts into a web page, and "bang" I now have a process in place that... * defines common terminology; * organizes our current system quickly; * provides a process-model "shell"; * serves as a common-reference for the team; * removes many management details; and, * focuses the team on development. Thank you.
Rating:
Summary: A good overview of the entire RUP framework...
Review: Target Audience
IT professionals who need to learn about the Rational Unified Process (RUP) Contents
This book is a relatively high-level overview of the entire RUP process. The book is divided into the following chapters: Software Development Best Practices; The Rational Unified Process; Static Structure: Process Description; Dynamic Structure: Iterative Development; An Architecture-Centric Process; A Use-Case-Driven Process; The Project Management Discipline; The Business Modeling Discipline; The Requirements Discipline; The Analysis and Design Discipline; The Implementation Discipline; The Test Discipline; The Configuration and Change Management Discipline; The Environment Discipline; The Deployment Discipline; Typical Iteration Plans; Implementing the Rational Unified Process; Summary of Roles; Summary of Artifacts; Acronyms; Glossary; Bibliography; Index Review
The Rational Unified Process, or RUP, is a software engineering methodology that attempts to map out and document all parts of a software development project. It's extremely comprehensive, but it's also adaptable to whatever level of effort is appropriate for your situation. This book, The Rational Unified Process - An Introduction, is a good start to begin your understanding of RUP. First off, let me say this is not an easy read. It's a good book with all the information you need to know to start using RUP, but the information is dense and highly detail oriented. Like most developers, I'm more oriented towards coding and testing. But realistically, you need to know what the system should do before you get to the coding piece. RUP helps to put all that into a formal framework so that the necessary things will get done in the proper order. While the entire RUP framework might feel overwhelming, the author makes sure to let you know that you can adapt the RUP to meet your situation. If you are adding a function to an existing system, you will be more focused on use cases, development, and deployment processes. The author does a good job in segmenting the information so that you can more easily focus on your needs. You should also not consider this the end-all volume on RUP that you will ever need. Kruchten doesn't try to detail specific techniques like use cases or UML. You will learn where they fit in to RUP, but you will need additional information on how to implement use cases or UML diagrams. Consider this the volume that allows you to place everything in a mental framework so that you can figure out what you will need to know going forward. Conclusion
If you are considering or in the process of implementing RUP, this is a book you should be studying. It's not an easy read, but it will give you the overview you need to understand the process and concepts.
Rating:
Summary: A good overview of the entire RUP framework...
Review: Target Audience
IT professionals who need to learn about the Rational Unified Process (RUP) Contents
This book is a relatively high-level overview of the entire RUP process. The book is divided into the following chapters: Software Development Best Practices; The Rational Unified Process; Static Structure: Process Description; Dynamic Structure: Iterative Development; An Architecture-Centric Process; A Use-Case-Driven Process; The Project Management Discipline; The Business Modeling Discipline; The Requirements Discipline; The Analysis and Design Discipline; The Implementation Discipline; The Test Discipline; The Configuration and Change Management Discipline; The Environment Discipline; The Deployment Discipline; Typical Iteration Plans; Implementing the Rational Unified Process; Summary of Roles; Summary of Artifacts; Acronyms; Glossary; Bibliography; Index Review
The Rational Unified Process, or RUP, is a software engineering methodology that attempts to map out and document all parts of a software development project. It's extremely comprehensive, but it's also adaptable to whatever level of effort is appropriate for your situation. This book, The Rational Unified Process - An Introduction, is a good start to begin your understanding of RUP. First off, let me say this is not an easy read. It's a good book with all the information you need to know to start using RUP, but the information is dense and highly detail oriented. Like most developers, I'm more oriented towards coding and testing. But realistically, you need to know what the system should do before you get to the coding piece. RUP helps to put all that into a formal framework so that the necessary things will get done in the proper order. While the entire RUP framework might feel overwhelming, the author makes sure to let you know that you can adapt the RUP to meet your situation. If you are adding a function to an existing system, you will be more focused on use cases, development, and deployment processes. The author does a good job in segmenting the information so that you can more easily focus on your needs. You should also not consider this the end-all volume on RUP that you will ever need. Kruchten doesn't try to detail specific techniques like use cases or UML. You will learn where they fit in to RUP, but you will need additional information on how to implement use cases or UML diagrams. Consider this the volume that allows you to place everything in a mental framework so that you can figure out what you will need to know going forward. Conclusion
If you are considering or in the process of implementing RUP, this is a book you should be studying. It's not an easy read, but it will give you the overview you need to understand the process and concepts.
| 
