UML, object-oriented and contractual design
Created: appleleaf
UML and object-oriented programming If you want to learn UML, the UML Reference Manual, "UML User Guide", "UML User Guide" and "UML and Mode Application Object-Oriented Analysis", " "UML and mode application object-oriented analysis and design introduction" should be called "UML instance analysis" is appropriate, it is suitable for object-oriented and UML beginners practicing Craig Larman Applying UML and patterns make me to UML The first time has an intimate, and it is also recognized by the value of UML to a certain extent. However, I haven't started using it yet, so I don't want to say something much about this problem. My UML knowledge is to learn from Rational's CD Tutorial (found in the CD2 of Rational Suite) in Rational Suite, and the CD-ROM of the INSIDE UML you want to ask. Through those pictures and tutorial, I think the effect of learning is still good. For oo, I used to auction from the CHINA-PUB to a small book, called Object Technology: a Manager's Guide, I feel that the narrative inside is relatively clear. Thin book (including more than two hundred pages of index), covering the basic idea of object technology, important concepts of object technology, object-oriented database, object technology in business implementation, etc. As an entry manual to help beginners, the developer's quick-study manual is good. If there is a chance, I hope that domestic publishers can consider introducing the book. I very much agree with Mengyan's statement. This reminds me of Wittgenstein in "Logic Philosophy" in "Logic Philosophy": we can draw a scenario that does not meet the spatial law in the geometric image, but cannot depict the space laws in the spatial image. Or in other words: UML can be painted, the oo language may not be able to implement, and it is not necessary to achieve it. Because UML and C , Java, after all, it is a completely different language, I have been praise that there is a plus, not because it is in OO books, 1999. The status (to be honest, it is too thick, so that I have not confident every time. In fact, I didn't finish it), but the first chapter talked Software Quality, let me for the program The essence has more understanding. I think Bertrand Meyer and the Eiffel genus he represented is the most profound. For more than a decade, they have been in tributing throughout the OO technology, which can't be said to be a regrettable thing. I think that if Eiffel and the Design by Contract concept have been attached to the beginning, the development pattern of software engineering throughout the 1990s may be different. In addition, from the language itself, Eiffel is also very good, I think it is much more meaningful in serious learning from the future, I don't want to use this language development project. I'm looking at it, there are many refreshing views, and I feel surprised by the initial reading, but I think so. For example, to distinguish between COMMAND and Query, the so-called unified access principle, and so on, all feel the feeling of cloud. Eiffel's foothold is scalability, reuse and reliability. I remember that we were discussing with us, these goals were what made us troubled.
