The general process of project development is rough

You are a software development boss, and I am a software development employee. However, your company has many people engaged in other businesses. The day's work begins.
A customer comes to our company, and is first received by the receptionist, asking please What kind of software (type) he wants to develop and submit his questions to the program planner, it's not enough, the next day, the planner has to interview the customer, the content is what kind of function the software needs, and give a reasonable Suggestions, and evaluation for a certain function, (whether it can be met, because the customer's requirements are sometimes impossible to complete, after all, he is a layman). After he understands the customer's requirements, he decomposes the software in detail, and finally decides whether to accept the development of the software. The decomposition process is as follows:
1 List the function table of the software: for each problem, there are A detailed description
2 According to the function table, work out several major modules of the software.
And cut according to the complexity of the module, decide whether to continue to divide into more detailed modules
3. Decompose the relationship between modules in detail, and draw a relationship drawing. We call him "Flowchart of Programs".
After completing the above work, each module can be distributed to ordinary programmers. The designers can design their own program modules according to the requirements of the modules. The specific work is: :
1 Decompose the problem of modules and specify a feasible algorithm.
2 According to the algorithm, draw a flow chart,
3 According to the flow chart and the algorithm, write a program code
4 run on the computer.
5 Find out the bug of the program.
6 Go back to step 3, modify the code, continue with steps 4, 5
until the program has no errors,
each programmer has done his job like this,
And submit the code, flow chart, and other security of their own modules to the program planners. After the planners take over the code, they write the main function (that is, the main program). The purpose is to combine the modules together to form a complete program. . There is also the potential for rework and correction of errors during this process. until the program is complete.
The following work has been completed by the testers
to carry out the hey box test and the white box test respectively.
Black box testing: by non-designers, put forward some extreme, demanding, and wrong requirements, to see if the program can run properly. If not, fix the program.
White box testing: There are programmers who provide reasonable, comprehensive requirements to see if the program can run properly, and if not, modify it.
After testing, the program has been designed. The receptionist submits the program to the customer, and the customer debugs, runs, and pays the money after they are satisfied.
The documentation of the program should be kept well, because the customer is likely to continue to put forward higher requirements. Once something happens, the programmer will expand the function of the program according to the historical documentation. This is the common version, such as photoshop v1.2, photoshop v2.0
and so on,
this is the process of developing a program from a human point of view.
How does a program come about? The answer is as follows.
May code - "compiler -" target program
Original code:
text written according to the programming language
Example
main()
{
printf("This is a program, its function is very simple, it is in The screen will print this sentence!");
return(0);
}
Computer hardware cannot understand such a word, and there must be a relevant compiler to translate it into a binary file that the computer hardware can recognize. For example
00110011 00111100 11001010 11001010
00001111 00010001 00011010 00101000 The

target program is the above target program composed of 0 and 1, and such a program can be used.

Software development process is the general process of software design ideas and methods, including algorithms and methods for designing software functions and implementation, overall software structural design and module design, programming and debugging, program joint debugging and testing, and writing, Submit the program.

Development process
Requirement 　　 research and analysis
Relevant system analysts and users have a preliminary understanding of the requirements, and then use WORD to list the major functional modules of the system to be developed, what small functional modules each major functional module has, and when some requirements are relatively clear. , in this step, a small number of interfaces can be initially defined. 　　
●The system analyst has an in-depth understanding and analysis of requirements, and uses WORD or related tools to make a functional requirement document of the document system according to his own experience and requirements. This document will clarify the general large functional modules of the example system, which small functional modules the large functional modules have, and also illustrate the related interfaces and interface functions. 　　
● System analysts and users reconfirm requirements.
Outline design 　　
First of all, developers need to outline the design of the software system, that is, 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 software design. 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 algorithm, data structure, class hierarchy and calling relationship involved in the realization of specific modules, and need 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 detailed enough to be coded according to the detailed design report.
Coding 　　
In the software coding stage, according to the design requirements of data structure, algorithm analysis and module implementation in the "Software System Detailed Design Report", the developer starts to write specific programs to realize the functions of each module respectively, so as to achieve the goals. Requirements for system functions, performance, interfaces, interfaces, etc.　
Test 　　
Test the written system. It is handed over to the user, and the user confirms each function one by one after using it.
Software delivery preparation 　　
After the software test proves that the software meets the requirements, the software developer should submit the developed target installation program, database data dictionary, "User Installation Manual", "User User Guide", requirement report, design report, and test report to the user. and other products agreed upon in the contract between the two parties. The "User Installation Manual" should introduce in detail the requirements of the installation software for the operating environment, the definition and content of the installation 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 tips and precautions of various functions of the software, and shall also give examples when necessary.
Acceptance user acceptance.
The above is the basic software development process.