The 78th chapter of the Road to Jane

At the beginning of the seventh chapter, the author cites IBM 's example of how large companies operate in software engineering. The real reason why rational was bought by IBM is that IBM needs to build a complete software engineering system, and for IBM, Rational has a very rich practical experience in UML language, and the position of RUP as the founder and leader of the theoretical framework, which IBM is establishing The industry image of large-scale software engineering application Solution provider is greatly supported. Another developer: Borland does not have any advantage in ALM as an engineering theory. As a result, Borland began to purchase and implement the ALM system-related companies, including the acquisition process improvement consulting firm Teraquest and the formation of process optimization of the real department, as well as the acquisition of TogetherSoft to develop tools to strengthen the model building capacity, are a considerable number of initiatives. Through these efforts, Borland quickly complements the theoretical shortcomings of ALM as an engineering system. Microsoft, which is at the cusp of Borland and IBM, is not the same way of buying and reaching the end of the spectrum, and there is enough power to take the initiative. So today's software world is a result of the mutual constraints between big companies. It is not necessarily the "software implementation" that big companies take away from the competition for standards, theories, and languages. To unify the theory, the Unification tool, the unification process the attempt, its ultimate goal is in the entire software engineering system the overall victory.

The development of software engineering system is driven by two aspects, one is the essential power and the other is the promotion of business factors. The commercial factors drive the software engineering from the original"self-Birth evolution"State, gradually advancing to"it stimulated the development"of the state. Although its development may affect the speed of software engineering development, but at the various engineering level of concern does not change. As you can see from the software engineering layered model, the"program"with the"Method"level, is focused on"(specific to)Implement", and in"Process"and the"Engineering"level, the most important consideration is team issues. From a role perspective: the development manager thinks about the project implementation plan and manages the specific development behavior, while the project manager guarantees the team's stability and consistency.

The process is accompanied by engineering, and how does the project arise? The root cause is the increasing size of the software. As the size of the software increases, the time that only one person spends is huge, and in reality there is no such opportunity for software companies. The "complexity" of the project may require the participation of different areas of knowledge, while "large" requires more resources. As a model of development behavior, "team" is the result of the gradual accumulation of software scale and complexity. Teams are getting bigger because the size of the software is becoming more complex. A software company without team awareness will be aurra in the face of a highly procedural, methodology-savvy army with a large number of tools.

Methods, processes, tools are the three elements of software engineering, but these three are not isolated three levels, but the interaction, like Taiji figure, Yin and yang intersection, so we should not divide these three elements, but should be back to the ontology of software engineering thinking problem. RUP like a glove box, everything inside is available, but the key is how you look at the value of a thing.

Language as a communication tool, in the development process is very important, simple and understandable language can be developed to solve a lot of problems. Although if you can understand the words even with the development of Oracle, but after all, software development and maintenance is not you a person's things, so, everyone can understand the language is the real mainstream, but, after all, language is just a tool, is connected between you and the computer bridge, so it is not good or bad points, There is only the difference between the applicable scope. Contradictions are ubiquitous, and so is the case in development. The contradiction between achieving the goal and guaranteeing quality is unavoidable, the time, the resources and the function are always the contradiction source in the software development process, the three are difficult to reconcile at any time. If there is a good project manager, it may reduce the occurrence of contradictions. In fact, software development is not a rigid project, some of the details of the problem can be ignored, flexible neglect of some unimportant issues, will not affect the quality of software, on the contrary, will speed up the development of speed, for themselves to win better opportunities.

The 78th chapter of the Road to Jane