Opening: The whole process of software projects-IT software staff Learning series articles

This is a time when there is nothing to do, just summarize the previous project experience, and then write it in the form of a blog to record. This article on the "It Software staff Learning series article" to do a first.

For IT software development, no outside the B/S, C/S and Android, IOS (the latter two are also C/s). In the B/s field, no outside of PHP, Java and ASP. In the C/S field, Java development is more complex, need to write some repetitive and low-level code, compared to C # visual and similar syntax, or Microsoft's development tools and language is relatively easy to get started.

However, what we are talking about today is not code, but the entire software process, which belongs to the scope of engineering. We know that the software project is to translate the user requirements into requirements, then the requirements into the design, and then the design into code. In general, the big projects are divided into small projects, large modules are divided into small modules. Any project is required and designed to do so, especially for large projects, which are always divided into small modules that allow different participants in the project to take charge of their respective modules and then integrate them for testing.

According to the author's experience in Project management, the analysis method model of any project (waterfall model, prototype model, iteration model, etc.) can be divided into small waterfall model eventually. In other words, all project functions can be divided into small waterfall processes for processing. Because waterfall models are the simplest and most straightforward of all models. In other words, all function points are a milestone at the end of each waterfall process. The entire process of the software project is described below.

First, the project establishment

At the beginning of the project, the project needs to be set up. The project manager is going to talk to the project client about the whole project that needs to be done. At this stage, the project needs to conduct market research, feasibility analysis and a series of activities to ensure that the value of the project is desirable and feasible. In general, each project has its feasibility and value, but for enterprise projects, basically every project is desirable, is for a business area to do business systems. For Internet projects, such as e-commerce projects, this would have to do market research to determine that the project is currently socially valuable.

Second, the project start-up meeting

After the project has been approved, the project will have to be launched. Project initiation will be primarily to identify project bidders for project tenders and projects. The project Tenderer determines the owner and user of the project's client, and the project bidder determines the project manager, the product Manager (if required), the technical manager, the project developer, and other project team members. Project start-up is also a milestone for the project, stating that the project is to begin and identify the responsible and responsible persons of both sides.

Third, the project needs research

After the project starts, the project manager will begin to communicate with the project client to investigate the project requirements. The project manager needs to do some homework on the project's requirement field, let himself have a certain understanding of the project domain knowledge, so that when conducting the demand research, we can understand the demand more quickly. At the same time, the project team will also be held in the field of project knowledge training, so that the project team members know what to do in which area of the business system. At this stage, the project manager needs to confirm with the customer the summary requirements to ensure the correctness and stability of the project requirements.

Iv. Design of the project

After having mastered certain project domain knowledge, and the project manager has determined the project requirement overall, the project has entered the design stage. At this time, the project team needs to select the project's architecture selection, design, development tools, development language, development platform and the project's operating platform. Then, the project manager is the lead, the architect or the technical manager for the system architecture design, the technical manager and the project team members for the summary design and detailed design. At this stage, each design of the project needs to be reviewed to determine the correctness of the requirements to the design.

V. Development of the Project

At the end of the project's design phase, part or overall, the code development phase of the project is entered. At this stage, the technical manager is responsible for the project's overall code control, the software engineer to the project design into code for development. At this stage, the project manager needs to constantly adjust the project plan so that the project can keep up with the progress, while the developed system allows the client to try to constantly adjust the project development problems, and to prevent large changes in requirements.

VI. Testing of the project

After the project system has developed some or all of its functions, the project's testers need to intervene to test the project system. This stage includes black box white box testing. Unit testing and integration testing, and more. To ensure the correctness of system requirements and design development.

Vii. Commissioning of the project

After the overall test of the project system has been carried out, the project manager will contact the project client for a systematic trial run. Commissioning phase is mainly to the requirements to design, design to the code of confirmation. Ensure the correctness of the function of the system. At the same time, the need to change the relatively large stage, at this stage, the project manager to control and plan the time, as far as possible to avoid large changes in demand.

Viii. Project Acceptance

After the commissioning of the project is completed, it is time for the project acceptance phase. The project acceptance phase is the project closure phase, which includes project closure and contract closure. At this stage, the project manager should contact the Project client organization Expert group to evaluate and review the project system to ensure the correctness of the project.

It is emphasized here that the above three or four and five or six phases are a repeating process. We are simply using the waterfall model to describe the entire process of the project system. In fact, in many companies, there are the project team personnel and multi-job issues, this is because the project personnel are not aligned, the size of the company, the size of the project has a relationship. Therefore, we should not complain about the condition of the company in the project is not up to the requirement. In general, there are more things to learn in a small company.

ETC. Finally, the project team members should actively improve their ability, one for their own development requirements, on the other hand is the project team itself requirements. Therefore, the project manager should make a plan for team building so that the project team members can conduct systematic, normative and standardized training.

Opening: The whole process of software projects-IT software staff Learning series articles