First, the needs analysis:
Related systems analyst to a preliminary understanding of the needs of the user, and then use the relevant software tools which are listed small functional modules function modules to be developed system, each module has a large function, clear when comparing the relevant requirements for some interface, in this a preliminary step which may define a small amount of good interface.
Systems analysts insight and analysis needs, based on their experiences and needs and then make the system functional requirements document with a document WORD or related tools. This document will clearly set out what little function module general function modules, function modules have, and also lists the relevant interface and interface functions.
Systems analyst needs to confirm once again to the user.
Second, the outline design
First, developers need to conduct preliminary design of the software system, that system design.
Design outline design software system needs to be considered,
including the basic process flow of the system (including the system logic, business logic), the organizational structure of the system (a function, the second function, etc.), divided into modules (different functional modules Analysis) , function allocation, design the interface (public interface, private interface, class inheritance, etc.), designed to operate, the data structure design (data table) and a design error handling, provide the basis for the detailed design software.
Third, the detailed design
On the basis of the outline design, detailed design of software developers need to be systematic. In the detailed design, particular algorithms described achieve the main modules involved, data structures, and calls the hierarchical relationship classes, a description of the software system at all levels of each program (each module or subroutine) design considerations, for coding and testing. It should ensure that the needs of the software is fully allocated to the software. Detailed design sufficient detail can be encoded in accordance with the detailed design report.
Fourth, Coding
In the software coding stage, the developer according to design requirements "software system detailed design report" data structures, algorithms, analysis, and modules implement other aspects of the beginning of specific programming work, respectively, to achieve the function of each module, in order to achieve the target system aspects of function, performance, interfaces, interface requirements. In the standardized development process, the coding process in the whole project will not exceed a maximum of 1/2, typically 1/3 of the time, the so-called Preparation may quicken the work, good design process is completed, the coding efficiency will be very large increase, schedule coordination and collaboration between the different modules is the need to be careful when coding, perhaps a problem of small modules that may affect the overall progress, so many programmers forced to stop working and wait, the problem in many R & D process have appeared. Microsoft mutual communication and emergency means of settlement when the codes are very important for programmers, bug forever, you never have to face this problem, the famous, it can be had for three consecutive months when not send patches ? there has never been!
Fifth, software testing
Writing good test system. To the user, a confirmation of each function after a user.
There are many software testing:
Performed according to the test side, can be divided into internal and external testing;
according to the test range can be divided into test modules and the overall FBI;
according to the test conditions, the test can be divided into normal and abnormal operating conditions test case;
input range according to the test, It can be divided into full-coverage test and sample tests.
Above it is well understood, not explained. In short, the test project is also a step in a very important development for a large software, 3 months to 1 year of external tests are normal, because there will always be unexpected problems exist. After completion of the test, and complete acceptance of some help to complete the final documents, the overall project be considered an end, of course, ultimately, future upgrades, repair work, etc., as long as do not want to get money through a one-shot deal, we must constantly tracking software operations repair and upgrade situation continued until the software is completely out of date.
Sixth, software delivery
After the software is tested and found to meet the requirements of software, software developers should aim to develop a user submits installer, data dictionary database, the "User Installation Manual", "User's Guide", demand report, design reports, test reports and other parties to the contract product agreement.
"User Installation Guide" should describe in detail the requirements to install the software on the operating environment, installation software definition and content, in particular the installation steps the client, server and middleware, system configuration after installation.
"User's Guide" should include aspects of the use of the various functions of the software process, the steps, the corresponding business reports, tips and special precautions should also illustrated when needed.
Seven, system acceptance and maintenance
According to the completion of the software design of control system functionality requirements, whether there is left behind or style issues. In the process of using the software, the user will appear in the use of various unknown, product designer or programmer, a certain time according to the actual use of the product side of the software maintenance. (Maintenance costs and the cost of the program is generally designed to separate, usually at the beginning of the project carried out, it is best to make it clear to each other)
