"Boulevard to Jane" younger brother seven or eight chapters

the seventh chapter title is the real software engineering, divided into four sections, the title is: 1, the big companies in the hands of the Abacus, 2, back to the key points of the project, 3, thinking about the project cost manager; 4, examine aop;5, examine MDA/MDD. The eighth chapter is divided into seven subsections: 1, the value of three elements of software engineering; 2, in fact, RUP is a clutter box; 3, the similarities and differences between UML and Oracle, 4, the operator is far from the developer, and vice versa; 5, contradiction: Achieve the goal and guarantee the quality, 6, the side and the detail;

In the first section of the seventh chapter, the author introduces us to the development of IBM, and from this to other large software companies, reveals their strengths in suppressing their opponents, while relying on the strength of their opponents and allies to weaken their weaknesses or add to the reality of strength. And the software industry today, not some people (such as programmers or critics) the outcome of the quarrel, but the result of checks and balances between the big companies.

The second section of the seventh chapter describes the model of software development, and points out that in the "process" and "method" level, is concerned about "(concrete) realization", and in the "Processes" and "engineering" level, the first consideration is the team problem. From a role perspective, the development manager thinks about the project's implementation plan and manages the specific development behavior, while the project manager guarantees the team's stability and consistency. However, this is just the basic pattern, or, the ideal mode.

The seventh chapter of the third section of the author tells us what the project manager should be concerned about, the project manager should jump out of the details, the question should be the completion of the project "method", and the evaluation of the success of this method is the standard is whether to save costs. As a project manager should learn to think about costs, regardless of the cost of the project plan will not be supported by the operator, the cost of non-destination is a chronic poison project, the most deadly risk is the depletion of costs.

The seventh Chapter 45th section tells us about AOP and MDA/MDD. AOP is not a language, it is a methodology. The data structures on which OOP is based are objects (object), and the data structure on which AOP is based is the facet (Aspect). A segmentation point is a tool that AOP needs as a framework: a set of indexes that identify acpects and objects. As for MDA/MDD. MDA (Model driven Architecture) is also a methodological aspect of the noun. It discusses the method of "creating machine-readable and highly abstract models". In engineering, "What drives development" is actually a process problem. Although a complete set of technologies and methodologies are proposed for MDA, the project implementers cannot find an applicable software process model in this system. --mda not discuss the process.

     the eighth chapter of the first section of the value of software engineering three elements. The so-called three elements are: tools, methods and processes. They are actually interacting with each other. For example, "process" problem, there are both the implementation of the process tools, there are related process method theory. The overall problem of the project is still "realization".

     The third section of the eighth chapter describes the similarities and differences between UML and Oracle. Before you really plan to use Oracle to write project documents, make clear the similarities and differences between UML and Oracle. Both uml  and Oracle are symbolic characters, both of which have pictographic meanings. However, this does not mean that the UML notation itself can express how rich the meaning. If we want to explain it in the same way as Oracle, with a few generations of thousands, then the value of the UML diagram will remain symbolic. And in the use of UML diagram should be related to the text to describe, or the next person to read UML will face will be the same as the Oracle unearthed the dilemma.

     Eighth chapter fifth describes the contradiction: to achieve the goal and quality assurance. In the demand phase, we will face the "goal" problem. However (most of the time), on the contrary, we will meet the customer's quality complaints when the project is delivered and tested. Anyway, no one will jump out and say: we were wrong. But it may actually be at the source: we set the target wrong.

The eighth chapter of the seventh section tells us to do engineering should learn to be flexible, we can not expect to die read a "software engineering" will be the real program, but to learn to adapt, because the dead read a book is unable to do the project, only to learn to work, to do the project.

"Boulevard to Jane" younger brother seven or eight chapters