<< 1 >>
Rating:  Summary: Shows how to use RUP in real life Review: Easily approachable and good. The book talks not just about RUP, but also about its roots (OMT, Fusion, objectory etc), and about UML. It also guides the reader through the maze of workflows in the RUP and gives advice on how to configure RUP as a lightweight process for web development. This book is a great contrast to all the other RUP books that are too theoretical to be of any use except for those who already are using RUP.
Rating:  Summary: The book really is for practitioners... Review: Its good. Once you get over his British writing style, its a good read. I'm only 1/2 way through, but I have found it very accessible so far. Not only does he talk about the UML diagraming, he talks about the Unified Process (in like 250 pages! - now thats a refreshing break). The book delivers what it promises. Its not a reference guide, but it is definitly *teaching* me some practical stuff.
Rating:  Summary: The book really is for practitioners... Review: Its good. Once you get over his British writing style, its a good read. I'm only 1/2 way through, but I have found it very accessible so far. Not only does he talk about the UML diagraming, he talks about the Unified Process (in like 250 pages! - now thats a refreshing break). The book delivers what it promises. Its not a reference guide, but it is definitly *teaching* me some practical stuff.
Rating:  Summary: A practical and useful approach to O-O projects, UML and UP. Review: This is a rare find. It is a useful combination of many related software engineering topics, with enough O-O history to provide some perspective, and enough detail on the Unified Process & the Unified Modeling Language to provide both an understanding and a practical series of steps for project success.If your department tries to balance doing things right with doing things quickly, if you're wondering why the UML has become the de facto notation, if you're using Java and want your group to do more object-oriented approaches, if you're thinking you'd like to use Java, or you'd like to use the UML for your design notations, if you've heard object-oriented engineering can provide some benefit.. then you'll probably find this book to move to the top of your 'must read and must share' list. If you're moving your architecture towards distributed objects and Enterprise JavaBeans, there's some useful advice on designing Java-specific objects. It is clearly written and easy to follow, and can be read chapter by chapter or as a reference text. I would have only one suggestion for the author. He briefly mentions the similarity between O-O and the Spiral Model or the UP and the Spiral Model. Mr. Hunt would have done well to include an overview of the Spiral Model in his work. [Search the Software Engineering Institute at Carnegie Mellon for more info. Our design team considers the Spiral Model an important and practical and even useful approach to software engineering projects. Combine the Spiral Model methodology for projects, the Unified Process approach to designs, and the Unified Modeling Language for design notations, and you've got what we consider to be a winning approach to object-oriented software development. Mr. Hunt provides a valuable book on the UP and the UML with a real world perspective. We're going to buy copies of his book for our entire team.
Rating:  Summary: A practical and useful approach to O-O projects, UML and UP. Review: This is a rare find. It is a useful combination of many related software engineering topics, with enough O-O history to provide some perspective, and enough detail on the Unified Process & the Unified Modeling Language to provide both an understanding and a practical series of steps for project success. If your department tries to balance doing things right with doing things quickly, if you're wondering why the UML has become the de facto notation, if you're using Java and want your group to do more object-oriented approaches, if you're thinking you'd like to use Java, or you'd like to use the UML for your design notations, if you've heard object-oriented engineering can provide some benefit.. then you'll probably find this book to move to the top of your 'must read and must share' list. If you're moving your architecture towards distributed objects and Enterprise JavaBeans, there's some useful advice on designing Java-specific objects. It is clearly written and easy to follow, and can be read chapter by chapter or as a reference text. I would have only one suggestion for the author. He briefly mentions the similarity between O-O and the Spiral Model or the UP and the Spiral Model. Mr. Hunt would have done well to include an overview of the Spiral Model in his work. [Search the Software Engineering Institute at Carnegie Mellon for more info. Our design team considers the Spiral Model an important and practical and even useful approach to software engineering projects. Combine the Spiral Model methodology for projects, the Unified Process approach to designs, and the Unified Modeling Language for design notations, and you've got what we consider to be a winning approach to object-oriented software development. Mr. Hunt provides a valuable book on the UP and the UML with a real world perspective. We're going to buy copies of his book for our entire team.
<< 1 >>
|