Enterprise Java with UML
Author: C. T. Arrington
List Price: $49.99
Our Price: Click to see the latest and low price
ISBN: 0471386804
Publisher: John Wiley & Sons (26 January, 2001)
Sales Rank: 23,719
Average Customer Rating: 4.5 out of 5
Customer Reviews
Rating: 5 out of 5
UML by Example - thanks C.T.
"Enterprise Java with UML" (John Wiley & Sons, ISBN 0-471-38680-4) ) by C.T. Arrington is an excellent book covering the topic of Software Development using UML.This book is about modeling all phases of the software lifecycle using the Unified Modeling Language (UML) to build the artifacts. The author describes the modeling process for requirements gathering, Object Oriented Analysis, technology selection, software architecture, software design and implementation. The author demonstrated the advantage of participants utilizing a common language (UML notation) for communication. The author stressed viewing each phase from the proper perspective. For example, requirements gathering must emphasize viewing the model from the customer's perspective as the model is developed while Object Oriented analysis is a view from the developers perspective. The author also identified diagrams that are used for each phase. For requirements gathering the diagrams will include use case diagrams, text descriptions of each use case, and activity diagrams. During Object Oriented analysis, diagrams will include class diagrams, state charts, package diagrams, sequence diagrams, and collaboration diagrams. The author also provided useful steps and evaluation criteria to identify when a phase is successfully completed and when entry to the next phase was premature. The book is organized in pairs of chapters. One chapter discusses theory followed by a chapter that uses the theory to implement a sample project. The sample project is an example of a time recording system and demonstrates the phases of modeling as the book progresses through each phase. Experienced developers will want to focus on the chapters that model the sample. These chapters contain tips and evaluation criteria that are not found in the chapters on theory. Two observations that would improve the usability of this book: a quick reference for UML notation, and a list of diagrams for each phase with references to the figures in the text. This book is an easy read and practical enough that it makes an excellent textbook on implementing software projects using UML.
Rating: 4 out of 5
Excellent Book for OO Analysis
This book takes you through the development of an application from proposal to implementation. In alternating chapters the authors explain the use of UML for a particular step in the development lifecycle and then demonstrate what they just explained to develop a sample timecard system. The best part of the book, which is not significantly different than the first edition, is the first half in which the authors discuss requirements gathering and object oriented analysis. The book is worth the price for this first part alone.The second half of the book has been expanded to discuss new J2EE technologies. The chapters on evaluating technologies are good as far as discussing how to evaluate technologies but the actual analysis is weak as they ignore candidate technologies such as Struts in favor of their own homegrown HTML production framework. They also fail to explain why EJBs are a better choice for their sample application than simply using Servlets/JSPs/JDBC. The final section on design gets bogged down with too many pages of code listings and not enough explanations for the code.
Arrington and Rayhan have done a very good job explaining UML although some familiarity with UML notation (or at least a handy manual) would be helpful. If you already own the first edition then you can ignore this edition. If you don't own it then you will definitely want to read this book. This is a must have book for any Java architect/developer doing OOAD.
Rating: 4 out of 5
Great first UML book for a Java developer
This is a very good book for someone who has a worked with java at the developer level and is thinking about making the jump to the architect level. Arrington is an experienced teacher and his teaching proficiency shows all along the book. His style is very clear and sometimes repetitive, but that makes sure you get the idea through.
Being a "hands on type of guy" I like the fact that the book explains the theory in the context of developing and example application.
The UML & Object Oriented Analysis section of the book is truly outstanding, while the implementation part leaves a bit to be desired. It is also outdated as it still uses HTML production classes inside Servlets and not JSP. The second edition should fix this.
Overall the best book on UML for a Java developer I have read so far. Similar Products
Expert One-on-One J2EE Design and Development
Book Index