Avenue to Jane ⑦+⑧ (end)

The seventh chapter at the beginning quoted the "Warring States policy" in the warring of the sentence: Wang as far as the close to the attack, the Inch, the King inch, the ruler, also king ruler. The meaning of this sentence is: the King than to take and distant to make and attack near, so that, every inch of the land, will belong to the king.

The first section, the abacus in the hands of large companies, the software industry has never been calm, even quiet, but also secretly bloody. Rational was acquired by IBM because IBM wanted to build a complete software engineering system, language to choose Java, while choosing the open source world, offset the disadvantage of their own language, seize the power, which is more than the creation of power, he can rely on this and micosoft. The same is true of Borland, who wants to build a system whose strength lies in language, so in order to make up for the shortfall, he began acquiring ALM-related companies to build on. But the difference is that Borland, while developing himself, is helping his opponent sharpen his sword and not just an opponent. He helps his opponent's opponents, but he can develop himself better. As the big head, Micosoft but unlike them, he has his own products in all aspects, theory, practice, and continue to develop, to the other companies. This is true of the software industry, where big companies counterbalance each other, suppressing rivals and complementing themselves with alliances. WHO stands on the cusp, who will be regarded as the target, of course, risks and opportunities coexist. And this endless battle, in fact, is a big company of a delicate abacus.

The second section returns to the key point of the project. The development of software engineering has been driven from simple essential force, that is, "self-development", transformed into a commercial factor at the same time, the impact of "it stimulated growth." Software engineering develops faster, but the focus of engineering is not changing. Procedures and methods are focused on "implementation", however "process" and "engineering", more consider the team. In terms of roles, different roles have different operational tasks. This is the ideal model.

The third section is the manager who thinks about the project cost. Project management should put the cost issue in the most critical position. Project managers should learn to jump out of the details, jump out of the plan, listen to the report and listen to the details of the meeting, the organization of the team is also not guaranteed success, just like the ant team, if the operation of the team's capital-the ant itself is passing, then the team will not exist necessary, will die. The project manager should learn to grasp the cost to get the project's success at a small cost. Then a small example is to warn us that the cost of thinking is the first priority.

The fourth section examines AOP. It is not a language, but a method. Just like "OOP". AOP is based on the aspect of the data structure and is not implemented unless described.

The fifth section examines MDA/MDD, which is also a method-level noun. Anything can be "drive development", which is a process problem that stems from the engineering needs and applicability in related fields, the readiness and perfection of process tools. If there is no mature software support, ultimately its practical value is still limited.

The eighth chapter, also is the last chapter of this article, is thinking or thinking. The beginning refers to the words in Jin's book: "This lang is also glimpse, met." It means that the teenager can also see the whole story by looking at small things.

The first section, the value of three elements of software engineering. Tools, methods, and processes are considered to be three elements. They interact with each other, and the methods play a role in the process, so the tools that guarantee the methods will appear everywhere. Therefore, the software engineering model diagram will become different. To get the final result, the key is a comprehensive view, the return to the Software engineering ontology, the whole problem is still "implementation."

In the second section, RUP is a clutter box. RUP is highly inclusive of the predecessors of the software process thinking, inclusive of all known theories. Whether or not RUP can be used well depends on the ability to take things from the inside and your organization to recognize them.

In the third section, the author once mentioned using Oracle to write UML. They are the tools used to communicate, so someone needs to be able to read it, be accurate enough, and be detailed enough. Therefore, in the use of UML, matching text interpretation is extremely important.

In the fourth quarter, there is a far cry between operators and developers. The understanding between the two is difficult, and it is harder to do the other, at which point the project manager becomes very important. The level of attention of different roles is completely different.

The fifth section, the contradiction that achieves the goal and guarantees the quality. The contradiction between the customer and the development team is likely to originate from the source and the target is wrong. Goals and quality sometimes do not really achieve unity.

In the sixth quarter, we need to grasp the details and jump out of the side. The side effect does not affect the behavior itself, but a minor branch. If you can't feel it, the best way is to feel it and not just to think about it, to feel it.

The seventh section, the last section, flexible software engineering. The Ancients wrote the ancient poetry is pay attention to change, and we modern people feel different, in order to temperament, poetry becomes very flexible, can fluent, can taste, style quaint is the best. Software engineering is also the case, should not conform to the rules of the project is alive, there are infinite changes, the modern unknown this way, so can not fill out good words. Also know the principle, only know its reason, can clear its way. So Yue: the Boulevard to Jane. Laugh

Avenue to Jane ⑦+⑧ (end)