The unified modeling language (UML) has been a standard in software development since the 1990s because it supports most modeling environments, including Java, C++, Object Pascal, C#, and Visual Basic, as well as object-oriented programming (OOP) when designing a system to be applied to a particular domain. A topological approach to OOP enables in-depth, systematic, and thorough analysis of some specific software properties or components, also called blocks, which under certain circumstances are crucial to a prognosis of the real system behavior. If this is not modeled, the system could react unpredictably, which could result in costly consequences. Topological modeling provides an opportunity to enhance unified blocks according to specific end-user needs. In other words, a software company sells numerous systems for a variety of applications, each of which relies on a set of components remaining always invariable despite transformation of all the others.
The book is structured in three parts. The first three chapters cover the foundations of UML, such as characteristics of the diagrams, modeling formalism, and advantages and limitations of OOP. For those familiar with UML, this overview can be skipped.
Part 2, only two chapters, is more interesting because it introduces the topological UML--“what it is ... and how to use it.” Model-driven methods such as software design, object-oriented analysis, business object-oriented analysis, conceptual modeling, component-based development, and topological functioning modeling for model-driven architecture are presented. The authors evaluate these methods against four criteria: analysis and design models, problem domain and design, requirements management, and usage.
The last part (six chapters) is dedicated to more detailed topological UML modeling. It first analyzes the topological functioning model of an enterprise data synchronization system, and then covers workflow and messages analysis using use case diagrams. Chapter 8 introduces structure analysis for modeling system snapshots with topological class diagrams. In chapter 9, the authors introduce object state change to highlight the results of such a transition. The last two chapters deal with designing packages and system components, also called code blocks. Both the components and deployment planning refer to nonfunctional requirements defined by the SWEBOK Guide [1], which was proposed by the Institute of Electrical and Electronics Engineers (IEEE) Computer Society Board of Governors and approved by the Association for Computing Machinery (ACM) Council.
Out of 126 references, most are from 2000 or even older, some are from 2008, and only a few of the newest ones are from 2012. The UML language has been popular for many years, and new diagram types have been developed that should have been included here. Another problem is the wide range of application areas not covered. Furthermore, it would have been thought-provoking to see how the topological UML is practically used in some working systems. Finally, as there are so many environments for building prototypes with UML, why not mention at least some of them or provide readers with the environment that the authors used while working on this book?
In spite of the quite straightforward presentation, which is valuable, the book tends to be verbose rather than concise. Perhaps it can be recommended as a textbook for those interested in the theoretical background of UML diagrams, their formalism, and mathematical formulas that explain the association rules between the diagram components.
