A business trip in Lianyungang: a brief description of the problems caused by the project

The process is interpreted in the encyclopedia as a combination of multiple persons and activities in an orderly manner. It cares about who did what, what results were produced, and who passed what information. In my first process, there were three roles (Platform Users, Program Management Engineers, and department managers) involved in the activity with more than five users, at the end of the process, other processes are called based on conditions.

At the beginning of implementation, the most labor-consuming is to find out the information required to implement this process and understand the IBM internal framework (a substitute for cairngorm) from the requirements document of this process ), people with high requirements are an indispensable step to accept the process. They need to repeatedly obtain the true appearance and Implementation ideas of the software from their mouths.

After the development requirements are clear, start development again. Otherwise, a large amount of counterattack is required. Of course, to understand this, do not stop lab. It may take some time to understand the framework and system architecture. It may take more than a decade to get familiar with how to use all the frameworks and architectures of the system.

What is software architecture and what should the software architect do.

"The software architecture represents the organizational structure of the system. This includes breaking down the system into different parts, defining the connections between them, determining the exchange mechanism between them, and providing guiding principles for subsequent design. "-three musketers

An architect of a software system is a person responsible for the definition, implementation, implementation, evolution, and evolution of the software system. In other words, it is a person responsible for the entire lifecycle of the system ."

Of course, I found a lot of architecture. You don't think it's all about software architecture, on different occasions, you may encounter different architects-solution architects, System Architects, software architects, Enterprise Architects, chief architects, Java architects, Microsoft architects, and.. Net architect.

Of course, I heard that many architects of IBM do not understand development technology, but I think software architects must come from developers and have experience in managing large projects.

Of course, when designing software, we may use a general framework and buy tools from another company, but as stated in the book "no silver bullets"-there is no panacea in the world, most of the time, we use a general architecture (such as J2EE and CORBA) or a framework that cannot solve or be the most suitable solution to our problems. As an architect, we should solve the problem by ourselves.

Currently, the project team's architect is well versed in flex, and he has made the architecture and replaced the cairngorm framework. Although he still cannot understand it well, but at least I see that an architect is trying to think about a project, rather than moving it out. Of course, it is wise not to use mature products or tools in the project, so that the project uses the JPA project.

In the end, let's just say a few other words without a smile.

The program must dare to guess, debug and verify carefully, and constantly optimize the code.

What architects need to do includes ensuring the controllability of the project programming style, improving the team development efficiency, and ensuring the tonality of demand changes.

The customer's requirements change from time to time, and as the development goes deeper, the customer's needs may increase explosively. The original requirement may be a peach, but when the peach is made almost, the customer may suddenly feel that what he originally wanted was watermelon.

The most important thing to do is to see which Party A needs most urgently.

It is difficult for large projects to be launched immediately.