The unified modeling language user guide (UML. User manual) (Category Architecture)

This is again a book from my past when I first became familiar with software design. She went out. 2007 During her year at DMK Press, she talked about the second version of UML, a unified modeling language. Interestingly, the book was written by three creators of the language: Gradi Butch, James Rambo and Aivar Jacobson. Each of them had their own notation modeling and then they made the unification and molded them into UML. Going back to the book itself, the authors wrote a guide to use in seven separate parts.

1) Introduction to the modelling process This part explains the fundamental concepts of modeling and introduces the reader to the UML language. Includes chapters “Why We Model,” “Introduction to UML,” and “Hello World!” explaining the basic principles and rationale behind using UML to develop software systems. 2) Basics of structural modeling This part discusses the basic elements of structural modeling: classes, relationships between them, general UML mechanisms, and class diagrams. It lays the foundation for understanding the static aspects of a system that represent its structure and organization. 3) Advanced Structural Modeling This part deepens knowledge of structural modeling, including a detailed study of classes, relationships, interfaces, types, roles, packages, instances, and object diagrams. Components are also considered as structural elements of the system. 4) Basics of behavior modeling Dynamic aspects of the system are considered: interactions, use cases (precedent) and related diagrams. This part focuses on how elements of a system interact with each other over time. 5) Advanced behavior modeling This part deepens understanding of the dynamic aspects of the system, including more complex interactions and behavioral patterns. Extended concepts of behavior modeling are considered, which allow to describe in detail the functioning of the system. 6) Architecture modelling This part is devoted to modeling the overall architecture of the system, combining structural and behavioral aspects into a holistic view. It examines how the various components and their interactions form the complete architecture of a software system. 7) Outcomes The final part summarizes the use of UML, including recommendations for using the language in real projects. It contains the chapter "Upplication of UML" with the sections "Transition to UML" and "What's Next", which summarizes the entire material of the book and offers directions for further study.

P.S. I've talked about UML in some posts before. Modeling Levels in UML and Why They Are All 4Not more-- explanation How many levels of modeling in UML

• UML tutorial, 2 A book by a Russian author from about the same year post I remember how I got to know UML and how it helped me learn how to design.
• List of useful UML charts - in post I talk about charts that I find useful. Developing Web Applications Using UML (Building Web Applications with UML) - posture novel
• Flexible technology: Extreme Programming and Unified Development Process (Agile Modeling: Effective practices for XP) - posture novel
• Introduction to RUP (The Rational Unified Process. An Introduction) - posture novel
• Applying Use Case Driven Object Modeling With Uml: An Annotated E-Commerce Example (Application of UML Object Modeling and Case Analysis) - posture novel

#Software #Architect #SystemDesign #SoftwareArchitecture #Processes