UML (Unified Modeling Language) is a graphical modeling language used to specify, visualize, construct, and document applications and software systems, which are implemented with components and object-oriented programming languages, such as Java, C++, and Visual Basic. UML incorporates the object-oriented community's consensus on core modeling concepts and provides a standard way for developers to communicate the details of system design and development. In addition to object-oriented modeling of applications, UML is also used for business-process modeling, data modeling, and XML modeling. Models for software systems are as important as having a blueprint for a large building or an outline for a book. Good models enhance communication among project teams and assure architectural soundness. The more complex the software system, the more important it is to have models that accurately describe the system and can be understood by everyone. UML helps provide this via a standard for graphical diagrams. About The Author: Michael J. Chonoles is the Chief of Methodology at the Advanced Concepts Center (ACC), where he leads the technological and methodological direction of the ACC technology transfer and training practice and is the lead author of the ACC's popular OOAD with UML suite of courses. When the ACC was part of Lockheed Martin, he was Lockheed's OMG representative. He is a member of the OMG's Revision Task Force (RTF). There, he is responsible for Use Cases and is an official reviewer of the UML Version 2 specification. Michael has co-authored a book on object-modeling technology, tech edited UML books by various publishers, and written articles for the Journal of Object-Oriented Programming and Journal of Object-Oriented Development, among other publications. James A. Schardt is the Chief Technologist at the Advanced Concepts Center (ACC), where he is involved with object-oriented development, data warehousing, and distributed systems. He teaches
This has good explanations of different diagrams. I got to know about this book when browsing thru OMG site. It was good read though rating for 4 because I was expecting some exercises at the end which I can practice. Yes, I can get them from project but still getting it from different domains from different perspective matters. Hope that justifies. I recommend reading this for those who want to get know how about UML.
Interesting read, clear explanations, lots of examples. I would have liked some questions at the end of each chapter to test your knowledge of the subject.