Discussion on the development process of small software project

A Introduction

Many projects in the country are small projects, with fewer participants (two to five), to be delivered quickly (a couple of months). In order to successfully complete this project, it is necessary to have a good development process, in addition to the use of mature and skilled team members to use the technology.

Two Small software project development process

The following figure is my vision for a small software project development process:

The importance of demand analysis must be clear to everyone, for the project, to meet the needs of users is the first.

Because time is tight, system design is often neglected. This will leave a lot of hidden trouble, the needs of many domestic projects is usually very simple, but also need to be in the system design phase to further clarify some requirements. Otherwise it will appear because some of the early requirements are not clear, some of the features have been developed to redo the situation. In addition, the design is done, the idea is clear, the next development will be much smoother.

The system design includes the business process design, the database design, the interface design three parts. Regarding the interface design, which information is the user needs, which information is the user does not need, must consider carefully.

See the design review, we must be a bit strange: small projects also do what review, not a waste of time? In fact, it is not so, heads the top of a Zhuge Liang, a person's design, more or less there will be some deficiencies, everyone brainstorming, design out of the plan will undoubtedly be more mature. In the process of review, everyone's design experience has also been virtually exchanged, the understanding of the system more.

The design review of the small project not very formal, put on a chair to sit next to the designer computer, first listen to explain, then ask questions, and then someone to write down the question of the good.

Many small projects do not set up professional testers, therefore, the development process of the self-test is very important, which is to ensure the quality of the project is an important link.

Features are developed and developers are ready to go through the cross testing process after they have completed their own tests. The thought of testing is different from the thought of development. Test to stand in the user's role to see the problem, as a user, to see whether the project to meet all the needs.

Before you go into the cross test, the developer should complete the deployment manual and instructions and deploy to a completely new environment (preferably with a separate test server) for your presentation.

Cross-Test the problems found in each of the first in the Excel table records below, the final summary to an Excel file, put into the public directory. Verify the bug after you change it. All bugs are verified once before publishing.

Three Small Project personnel configuration

One project manager, one to four developers

The project manager is responsible for the requirements analysis, conducting the design review, deciding whether the design review is passed, and deciding whether or not to enter the cross test to determine whether the project can be published.

The developer is responsible for system design, development and self-test, cross testing, bug modification, deployment manuals and usage instructions.