I have nothing to do during this period of time. I summarized my previous project experience and then wrote a blog to record it. This article on “IT software personnel learning series of articles” do a start.

For IT software development, there is nothing more than B/S, C/S and Android, iOS (the last two are also C/S). In the B/S space, there are no other camps than PHP, JAVA and ASP.NET. While in the C/S field, JAVA development is more complex, need to write some repetitive and low-level code, compared with C# visualization and similar syntax, or Microsoft development tools and language is easier to use.

But we’re not talking about code today, we’re talking about the entire software process, which falls under the umbrella of software engineering. As we know, to do a software project is to convert user requirements into requirements, and then requirements into design, and then design into code. In general, it is to divide large projects into smaller projects and large modules into smaller modules. The requirement and design for any project to do this, especially a large project, is always to break it up into smaller modules so that different project participants can take responsibility for each module and then integrate it for testing.

According to the author’s experience in project management, the analysis method model of any project (waterfall model, prototype model, iterative model, etc.) can be divided into small waterfall models. That is, all project functions can be broken down into small waterfall processes for processing. Because the waterfall model is the most simple and direct among all models. That is, all function points are milestones at the end of each waterfall process. The following describes the entire process of a software project.

I. Project approval

At the beginning of the project, the project needs to be approved. The project manager talks to the client about what needs to be done for the entire project. In this stage, the project needs to carry out a series of activities such as market research and feasibility analysis to ensure that the value of the project is desirable and feasible. In general, every project has its feasibility and value, but for enterprise projects, almost every project is desirable, a business system for a business area. For Internet projects, such as e-commerce projects, it is necessary to do market research to determine that the project has social value at present.

Ii. Project Launch Meeting

After the project is approved, the project kick-off meeting will be held. The project initiation meeting is mainly to determine the project tenderee and project bidder of the project. The project tenderee determines the responsible persons and users of the client side of the project; The project bidder identifies project manager, product manager (if necessary), technical manager, project developer and other project team members. The project launch meeting is also a milestone of the project, which indicates that the project will start and determines the responsible person of both sides.

3. Project demand survey

After the project kick-off meeting, the project manager will start to communicate with the project client and investigate the needs of the project. Project managers need to do some homework on the project’s demand field, so that they can have a certain understanding of the project field knowledge, so that they can understand the demand more quickly when talking with customers when conducting demand research. At the same time, the project team should also hold the project domain knowledge training, so that the project team members know which field of business system to do. At this stage, the project manager needs to confirm the summarized requirements with the customer to ensure the correctness and stability of the project requirements.

Iv. Project design

After mastering certain knowledge of the project domain, and the project manager has determined the overall requirements of the project, the project enters the design stage. At this time, the project team needs to select and determine the architecture selection, design, development tools, development language, development platform and operation platform of the project. Then, led by the project manager, architect or technical manager for system architecture design, technical manager and project team members for outline design and detailed design. At this stage, each design of the project needs to be reviewed to determine the correctness from requirements to design.

5. Project development

After part or all of the design phase of the project is completed, the code development phase of the project is entered. In this stage, the technical manager is responsible for controlling the overall code of the project, and the software engineer transforms the project design into code for development. At this stage, the project manager needs to constantly adjust the project plan to keep up with the progress of the project as a whole. At the same time, the developed system should be put on trial by the customer, so as to constantly adjust the problems in the project development and prevent major changes in demand.

6. Test of the project

After the project system has developed some or all of its functionality, the project tester needs to step in to test the project system. This phase involves black box and white box testing. Unit testing, integration testing, and so on. To ensure that the system requirements and design of the development of the correctness.

Vii. Trial operation of the project

After the overall test of the project system is passed, the project manager should contact the project client for a trial run of the system. The commissioning stage is mainly the confirmation of requirements to design and design to code. Ensure the correctness of system functions. At the same time, it is also the stage of large demand changes. In this stage, the project manager should control and plan the time well to avoid large demand changes as far as possible.

Viii. Project acceptance

After the end of the trial operation, the project has reached the acceptance stage. Project acceptance stage is the project closure stage, including project closure and contract closure. At this stage, the project manager should contact the project client to organize an expert group to evaluate and review the project system to ensure the correctness of the project.

It should be emphasized here that the three, four, five and six stages mentioned above are a repetitive process. Here we just use waterfall model to describe the whole process of the project system. In fact, in many companies, there is the problem of project team members holding multiple jobs, because the project personnel are not fully equipped, the size of the company, the scale of the project are related. Therefore, we should not complain that the company’s conditions are not up to the requirements in the project. In general, you can learn more in a small company.

Etc. Finally, project team members should actively improve their own abilities, one is for their own development requirements, on the other hand, is also the requirements of the project team itself. Therefore, the project manager should make a plan for team building, so that project team members can carry out systematic, standardized, standardized training.