Enterprise Java with UML

By C.T. Arrington

* The first book to show Java programmers how to utilize UML when building applications is now completely up-to-date with new coverage on UML 2.0, JCP UML to EJB Mappings, J2EE 1.4, and Web services * Breaks down common situations that a development team will most likely face in the field and discusses the tradeoffs of using different technologies in different combinations * Companion Web site includes the code for the full working sample application used in the book as well as third-party software

• Format: Paperback
• Language: English
• ISBN: 0471267783
• ISBN13: 9780471267782
• Release Date: June 2003
• Publisher: John Wiley & Sons
• Length: 688 Pages
• Weight: 2.35 lbs.
• Dimensions: 1.5" x 7.4" x 9.2"

Customer Reviews

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.

real UML for real projects, from a real Architect

Now I really know what UML is, finally I have a clear idea on how to apply it in real projects (not only J2EE ones), and I can appreciate its value as a great way to communicate ideas. The Author's *real* experience really shines through: everything is explained in practical terms, the examples are of a quality that can rarely be found in books (simple but not trivial, rich in details but not verbose, and thoroughly discussed and carefully engineered), quality that can only be the product of clear and sound understanding of the matters, understanding made in the trenches of complex projects. Need to know UML ? Here I've found the clearest explanation of the various UML diagrams, with simple examples to convey the fundamental features of every diagram; forget the "UML in 24 hours" books! Another great value of this book is the discussion of how to map the UML diagrams in Java: it was invaluable for me, since I could immediately use my OOP experience to get a practical feeling of the diagrams, in so reinforcing my understanding; an UML association, at the end, it's just a member variable, and I wonder why this is one of the few books that tells you that immediately, without filling the pages with a dozen of Academic words and acronyms.And everything applied to J2EE, that hot technology that only a few have had experience with ... with the usual high quality, especially the discussions of the strong and weak points of every J2EE sub-technology.Five stars!

Finally a book on UML that is useful

I've bought a number of books on UML but none of them have really been all that useful in actually designing real world systems. This book covers a real world application from the conceptual stage through design and implementation. Throughout the book, the designer/developer is introduced to important concepts covering many aspects of J2EE design using UML.

Excellent Resource

I too agree that this book is an excellent resource. It does an excellent job of combining many aspects of the software life cycle as it pertains to enterprise java. The author's style is easy to read and the book is organized in a fashion that allows the user to progress through each new level of the design and implementation phase as if they were working on the project themselves. It covers enough of the UML basics to allow you to build strong software requirement and design docs that can be understood by developers and testers. I have found it to be an invaluable resource.

An excellent UML-centric resource for Java architects

This book is an excellent resource for advanced Java architects and developers trying to learn the UML paradigm. It weeds out the UML that you dont want to know and concentrates on Java-applicable UML. As the title itself specifies, this is neither for non-Java readers nor for those Enterprise Java developers who don't need UML. All technologies related to Enterprise Java are here: EJB, XML, CORBA, RMI-IIOP and Servlets.