Software customization process

demand analysis

1. The relevant system analyst first understands the requirements from the user, and then lists the major functional modules of the system to be developed in word, and what small functional modules are in each major functional module. For some requirements, when the relevant interface is clear, this step A small number of interfaces can be preliminarily defined inside.

2. The system analyst has an in-depth understanding and analysis of the requirements, and then uses WORD or related tools to make a functional requirements document of the file system based on their own experience and requirements. This document will clearly list the major functional modules of the system, what small functional modules the major functional modules have, and also list the related interfaces and interface functions.

3. The system analyst reconfirms the demand to the user.

Outline design

First of all, the developer needs to outline the design of the software system, that is, the system design. The outline design needs to consider the design of the software system, including the basic processing flow of the system, the organizational structure of the system, module division, function allocation, interface design, operation design, data structure design and error handling design, etc., to provide detailed design of the software Base.

detailed design

On the basis of the outline design, the developer needs to carry out the detailed design of the software system. In the detailed design, describe the main algorithms, data structures, class hierarchical structure and call relationships involved in the realization of specific modules. It is necessary to explain the design considerations of each program (each module or subprogram) in each level of the software system. For coding and testing. It should be ensured that the requirements of the software are fully allocated to the entire software. The detailed design should be sufficiently detailed to be able to be coded according to the detailed design report.

coding

In the software coding stage, the developer starts the specific programming work according to the design requirements for data structure, algorithm analysis and module realization in the "Detailed Design Report of Software System", and realizes the functions of each module respectively, so as to realize the target system The function, performance, interface, interface and other aspects of the system. In the standardized R&D process, the coding work will not exceed 1/2 in the entire project process at most, usually in 1/3 of the time. The so-called sharpening of the knife does not cut firewood by mistake, and the design process is completed well, and the coding efficiency will be extremely high. Great improvement. The coordination and collaboration between different modules during coding requires the most care. Perhaps a small module problem may affect the overall progress, and many programmers are forced to stop working and wait. There are many such problems. Have appeared in the development process. Mutual communication during coding and emergency solutions are very important. For programmers, bugs always exist, and you must always face this problem.

test

Test the prepared system. Give it to the user, and the user will confirm each function one by one after use. There are many types of software testing: according to the test execution party, it can be divided into internal testing and external testing; according to the testing scope, it can be divided into module testing and overall joint debugging; according to the test conditions, it can be divided into normal operating condition testing and abnormal condition testing; According to the input range of the test, it can be divided into full coverage test and sampling test. The above is very easy to understand, no longer explain. In short, testing is also a very important step in project development. For a large software, external testing of 3 months to 1 year is normal, because there will always be unpredictable problems. After completing the test, completing the acceptance and completing some of the final help documents, the overall project is considered to be over. Of course, upgrades, repairs, etc. are indispensable in the future. As long as you don't want to cheat money through a hammer, you must keep track of the operation of the software. Condition and continue to patch and upgrade until the software is completely eliminated.

Software delivery

After the software test proves that the software meets the requirements, the software developer should submit the target installation program, database data dictionary, "User Installation Manual", "User Guide", demand report, design report, test report, etc. to the user. The agreed product.

The "User Installation Manual" shall describe in detail the requirements for the operating environment of the installed software, the definition and content of the installed software, the specific installation steps on the client, server and middleware, and the system configuration after installation.

The "User Guide" shall include the use process, operation steps, corresponding business introduction, special prompts and precautions of each function of the software, and it shall also give examples when necessary.

acceptance

User acceptance.

maintain

According to changes in user needs or changes in the environment, all or part of the application program is modified.