"Boulevard to Jane" Software engineering

From the earliest focus on software development tools to the present, the software industry's giants have been in the endless ideas of nirvana in the back and back. 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 vast majority of people on the abacus are just an operator to calculate the outcome.

The development of software engineering requires commercial factors in addition to itself. Therefore, the final result of the Battle of the big companies, has begun to the software engineering, from the original "self-evolution" state, gradually advanced to "it stimulated development" state. In this development process, the formation of a software engineering layered model called EHM. And this model is just a basic pattern, which means it is an ideal model.

Behind a soft foundation project, in addition to the technical staff and the project manager, he needs to do is to manage the entire team, master the process and efficiency of the team. If the "capital" used to maintain team operations is in the drain. If there is no capital, there is no operation, there is no necessity and possibility of the existence of the team. Then the project dies, so it's the equivalent of nothing.

AOP is not a language. AOP is first and foremost a methodology, as OOP is the "object-oriented programming approach". And delphi/c++ is the language, is a tool for the realization of this methodology. The data structures on which OOP is based are objects (object), and the data structure on which AOP is based is the aspect (Aspect), which is represented by Delphi as a set of "record" ② with (inherited) relationships. Java will use classes (class) to implement aspect. And no matter what language to program, it will have a constant law that is: programming = algorithm + Structure + method.

Aside from the technical details of the implementation regardless, in the project, "What drives development" is actually a process problem. The choice (or formulation) of this process depends on your engineering needs, its applicability in the relevant application areas, the adequacy of process tools, and the degree to which the process theory is perfected. So in the process is to rely on their own, which companies are still unreliable.

Tools, methods and processes are called three elements of software engineering, and they need to interact to complete a project, but no matter how perfect the three elements are, there will be only one result that will be the whole project.

In the project, the middle role of the project manager has a mission: to coordinate the communication between the operator and the developer. Because few operators understand programming languages, they need a translator to translate the programming language into their familiar language. Sometimes when a team finally completes their project to give the customer only to find that they have completed the different requirements of the customer, this can only be attributed to our "goal" is wrong, even if the completion of the good and what is the use of it.

This only means that when we re-customize the target, we ignore the details. "Details determine success or failure" but note a premise: this is a technical or methodological detail. So the procedure is not only to pay attention to the details but also to avoid unnecessary side. Finally, remember to master the principles of skills, techniques and methods, but also to know the flexibility, but also know avoidance errors.

"Boulevard to Jane" Software engineering