1, book name
Translated into "object-oriented software development tutorial", if it is not a Scott Ambler name, it is necessary to miss this more than 10 books on the old book stall. Although there is not much impact on it.
2, UML vs. Programming Language
If graphics and text are based on the same object model, they can seamless conversion between them; such as elements that can be stored as an XML document, XML documents, and primitives are based on XML Schema, any kind of representation can not The conversion of any information is another representation; however UML does not with any programming language based on the same object model, and the more the gap between the graphics, and the code is, the sequence diagram obtained by the code reverse engineering is almost no Any value, thus reducing this gap method is: a, either modify the metallic model, semantics, change it into another programming language, and develop the corresponding compiler B, or use the UML as a sketch ( UML AS Sketch, don't be treated as a blueprint (UML As Blueprint), because in the sketch phase, the gap with the programming language is not large
I don't know how the original text, there is a section title to "a picture", this also shows the use of UML: You can summarize a lot of code in one picture, and the picture is basically There is no use, at least in the current; actually Scott Ambler holds views on MDA, similar to his views, similar to Martin Fowler
3, software and hardware
There is a small section to give examples of hardware production chips and motherboards, explaining the scalability and reusability of object-oriented software, usually take hardware to metaphorics software, which is as good as the hardware can bring. This, chips and motherboards do not know that they are assembled together, this assembly process is also reused, scalable, metaphor to software is the program without explicitly creation chips and motherboards and associates them The code together, but IOC; staying, staying like this
4, use case and case example
Scott said: "Drawing case is easy, but determines the use case and participant is part of the difficulty"; how many people can hold the chicken feather to make arrows, take the case as an example of use, it is recommended to use the example in the book. , Only use case, the top is in the appendix.
5, extension point
The extension of the use case is really ancestors of the PointCut of AOP. This conclusion has been accepted, and Ivar Jacobson's paper on the exemption point is even considered AOP early thesis.
6, UML style
Some provisions mentioned in "UML style" are mentioned in this book, huh, huh, one top two
7, do not need to be encoded prototype
Want to verify the needs? Be a original! Don't you want to encode? That plays it! Going to foreign teachers, singing and jumping, don't take yourself, this country is almost, I don't know if there is any development team to collect, verify demand, etc .; the same is that management is not too Accept this method, this is the contradiction between conservative and freedom, rule and the rule, all in the inside and outside
8, information hidden, data hidden
It is really "hidden" to express the concept of essential
9, coupling
Just simply say "loose coupling" does not mean any meaning, now distinguish "intrusion" and "non-invasive"
10, components
Scott Ambler: modular components, good packaging unit, separate components may be deployed Ralph Johnson: Components are not a technology Technology people seem to find this hard to understand Components are about how customers want to relate to software They want... to be able to buy their software a piece at a time, and to be able to upgrade it just like they can upgrade their stereo. They want new pieces to work seamlessly with their old pieces, and to be able to upgrade on their own schedule NOT THE MANUFACTURER'S SCHEDULE. THEY WANT to Be Able To Mix and Match Pieces from Various Manufacturers. This Is A Very Reasonable Requirement. It is just hard to satisfy.11, analysis
Demand decisions request the contents of the request, and the analysis determines the content that will be built.
12, ui
I am more inclusive as "user interaction layers", "user interface layer", not "user interface layer", because the interface lets people think of screen, graphics, windows, etc., can also include command line, voice, etc. When IP phone card, step by step is a UI layer, but there is no screen, graphic, window.
13, Java style
Some provisions mentioned in "Java Style" mentioned in the "Java style", huh, huh, a top three
14, CTOR & SETER
Scott says that try to use the setter setting attribute, and the ctorleference setting attribute is a bad practice, but the CTOR role is to ensure that the object is in a good state before use, if a more important attribute must be used before the object is used Set, then the best in the CTOR
15, source code
SCOTT said source code includes the source code and SQL scripts of the programming language, and now you have to add a variety of configuration files, they are "source code" of various containers.
16, iteration and increment
Most of the projects I have seen are actually incremental development. It is "increment", which is more popular than "iteration", even if each incremental development project is iterative, but accurate expression Will subtle the influence of people's thoughts
17, get started
"The Object Primer Se" "UML DISTILED 3rd Edition" "The Java Programming Language 3rd Edition" is currently more object-oriented programming, just two months.
