This book starts with requirements gathering & ends with implementation. In the process, you’ll learn how to analyze and design classes, their relationships to each other in order to build a model of the problem domain. You’ll also use common UML diagrams throughout this process, such as use-case, class, activity & other diagrams. This book is also suitable for use in postgraduate and graduate courses as well as in professional seminars and individual study. Because it deals primarily with a method of software development, it is most appropriate for courses in software engineering and as a supplement to courses involving specific object-oriented programming languages.
To understand and use UML as intended by its authors, software architects and developers should be familiar with general concepts and methods of Object Oriented Modeling and Design and/or of the object-oriented development (OOD), and how those were applied to UML itself. There is one problem with this requirement: though OOMD/OOD is being used for several decades, there is still no concensus on what is OOMD and even what are the fundamental concepts (“quarks”) of the OOMD. Ok, so we are really in trouble: UML specifications use OOMD concepts which have no clear and generally accepted definitions without providing own interpretations or definitions of those concepts.Homepage