Development Process of small software projects

I. Introduction

Many projects in China are small-sized projects, with fewer participants (two to five people) and fast delivery (one or two months ). to successfully complete such a project, in addition to using mature and skilled technologies, it is also necessary to have a good development process.

 

2. Small software project development process

It is an idea of my development process for small software projects:

 

 

The importance of requirement analysis should be clear to everyone. For projects, meeting users' needs is the first priority.

 

System design is often ignored due to time constraints. this leaves a lot of potential risks. The needs of many domestic projects are usually very simple, and some requirements need to be further clarified in the system design phase. otherwise, some functions that have been developed need to be redone due to unclear requirements in the early stage. in addition, the design is well done and the idea is clear, and the subsequent development will be much smoother.

 

The system design includes three parts: business process design, database design, and interface design. For the interface design, which information is required by the user and which information is not required by the user, consider carefully.

 

When we see the design review, it must be a bit strange: Isn't it a waste of time? In fact, this is not the case. There will be more or less deficiencies in the design of one person by Zhuge Liang and the three stinks. The design scheme will undoubtedly become more mature. during the review process, everyone's design experience was also discussed, and more about the system.

 

The Design Review of small projects is not formal. Move the Chair to the computer of the designer, listen to the explanation, and then ask the question. Then someone will record the question.

 

Many small projects do not have professional testers. Therefore, self-testing is very important during the development process, which is also an important part to ensure the quality of the project.

 

After all the functions are developed and tested by the developer, you can start the cross-test. the Thinking of testing is different from that of development. the test should be based on the user's role to view the problem, treat yourself as a user, and check whether the project meets all the requirements.

 

Before entering the cross-test, the developer should first complete the deployment manual and instructions, and deploy it to a completely new environment (it is best to have a separate test server.

 

The problems detected by the cross-test are recorded in the Excel table respectively, and finally summarized into an Excel file, put it in the public directory. Verify the bug after modification. Before the release, all bugs are verified again.

 

3. Staffing for small projects

One project manager, one to four developers

 

The project manager is responsible for requirement analysis, presiding over the design review, deciding whether the design review is successful, and whether the project can be accessed through a cross-test to determine whether the project can be released.

 

Developers are responsible for system design, development and self-testing, cross-testing, bug modification, and deployment manuals and instructions.