UML tutorial, 2 publication (Category Architecture)
Sometimes I clean my bookshelves of old books, usually when there is no room for new books. It is for this purpose that I made a book by Alexander Leonenkova. 2006 The year in which he talked about UML 1.5. This book was a retelling of the standard in Russian in free form. The standard has since run to the version. 2.5.1which came out in December 2017 But the problem with language is much deeper. In this post, I will tell you a little about the book and about my attitude to the UML language.
Around 20 Years ago I started my professional career as a programmer. I was in my third year of Phystech and I was already getting some money for writing code. I was writing code before, it was bad, and I was doing it for free. But when I realized that this is now my profession, I decided to take it seriously and teach the theory. (||This is my standard approach to learning something new.||). It’s funny that I earned my first personal computer from Nix, where I worked on my first year summer vacation. The personal computer made it easier for me to immerse myself in the world of development, and the experience of working in construction helped me to understand that it is better to work with my head rather than with my hands. But back to the study of theory. At university, we taught C++ and assembler (||I confess the assembler passed me by.||). At work, you had to write in html, js, css, php, and also know a little Linux:) Well, for myself, I decided to deal with the architecture and design of systems. So I became the proud owner of several books on UML, as well as the book "Perfect Code" by McConnell. wrote. One of the books on UML was this tutorial Leonenkova, who was tedious, but not bad and in Russian told about the unified UML modeling language. The book consisted of three parts:
- Basics of UML
- Conceptual, logical and physical modeling diagrams Analysis and design using UML and IBM Rational Rose 2002
In the basics of UML, the author talked about procedural programming, then object-oriented programming, and then moved on to object-oriented analysis and design. And all this was accompanied by a historical analysis and an explanation of how different methodologies of different people were then sewn into a unified modeling language. I recommend watching a podcast with Gradi Butch, the creator of the language I’m talking about. told earlier. Then the author immersed himself in the story of real-world models, metamodels from UML, and then moved on to the main types of diagrams, which I will talk about separately in the book. next post. After the charts, the author talks about using IBM Rational Rose 2002It is the work of Gradi Booch and his company Rational, which was bought by IBM. Gradi talks about this interestingly in the above podcast.
In general, this book once helped me structure my understanding of how to decompose a system into parts and think about them separately, which is the analytical part of design. And only later learned not just to disassemble the system into arbitrary parts, but also to collect something meaningful back. And gradually it became clear to me how to think about emergent properties of a system that satisfy both functional and nonfunctional requirements for a system. But that's a story for another post.
P.S. At the moment, this book is just a rarity. There is no point in reading it anymore:) But studying the types of models from UML can be useful, so I’ll talk about them later.
#DistributedSystems #Architecture #Software #Engineering #SystemDesign