|
 |
>Knowledge |
The current location:Home >Software development
|
|
|
|
Software development process
|
< p > the software development process that is < a href = "https://baike.so.com/doc/5924788-6137709.html" "> < / a > in designing software of general process and methods, including the software requirements analysis first, Design software function and implementation of the overall structure of the algorithm and method, software design and < a href = "https://baike.so.com/doc/2209733-2338156.html" "> < / a > module design, coding and debugging, program alignment and testing, and the < a Written "href =" https://baike.so.com/doc/3161667-3331977.html "" > < / a >, submit application and a series of operations to meet customer demand and solve the problems of the customer, if there is a higher demand, also need to maintain and upgrade the software, Scrap treatment.
< h3 > < a href = "https://baike.so.com/doc/1481332-1566388.html#" > fold < / a > < strong > demand analysis < / strong > < / h3 >
Related < p > 1. < a href = "https://baike.so.com/doc/7563860-7837953.html" "> < / a > systems analyst preliminary understanding to the users needs, and then use the relevant tools software list to develop big function module in the system, What are the small functional modules of each big functional module? For some interfaces that require clear correlation, a small number of interfaces can be initially defined in this step.
2. The system analyst has a deep understanding and analysis of the requirements, and then uses WORD or related tools to make a functional requirements document of the document system according to his own experience and requirements. This document will clearly list the system's general big function modules, big function modules have what small function modules, and also listed the relevant interface and interface functions.
3. The system analyst reconfirms the requirements to the user.
< h3 > < a name = "" 1481332-1566388-1 _2" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > profile design
< p > first of all, on software system developers need to < a href = "https://baike.so.com/doc/5827677-6040496.html" "> < / a > profile design, The < a href = "https://baike.so.com/doc/5715147-5927873.html" "> < / a > system design. The outline design needs to consider the design of the software system, including the basic processing process of the system, the organization structure of the system, module division, function allocation, interface design, operation design, data structure design and error processing design, etc. For the software of < a href = "https://baike.so.com/doc/5437186-5675495.html" "> < / a > to provide basis for detailed design.
< h3 > < a name = "" 1481332-1566388-1 _3" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > detailed design
< p > in < a href = "https://baike.so.com/doc/5827677-6040496.html" "> profile design, on the basis of < / a >, developers need to undertake the detailed design of the software system. In the < a href = "" https://baike.so.com/doc/5437186-5675495.html" "> < / a >, the detailed design Describe the implementation specific modules involved in the main algorithm, data structure, class of < a href = "https://baike.so.com/doc/6571119-6784881.html" "> hierarchy < / a > and the invocation relationship, To explain the procedure of software system at all levels of each (each module or < a href = "https://baike.so.com/doc/6055709-6268742.html" "> subroutine < / a >) design consideration, for coding and testing. You should ensure that the requirements of the software are fully allocated to the entire software. The detailed design should be detailed enough to be coded from the detailed design report.
< h3 > < a name = "" 1481332-1566388-1 _4" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > encoding
< p > in < a href = "https://baike.so.com/doc/5924770-6137691.html" "> code < / a > stage, developers, according to the software system design in detail report of data structure and algorithm analysis and the design requirements of module implements, etc, Start the specific programming work, respectively to achieve the function of each module, so as to achieve the target system function, performance, interface, interface and other aspects of the requirements. The standardization of the development process, coding up to no more than 1/2 in the whole project process, usually in a third of the time, the so-called knife and cutting wood work design process is complete, will greatly improve coding efficiency, when coding the progress of the coordination and collaboration between different modules is the need to be careful, maybe a little module problems may affect the whole progress, This has forced many programmers to stop working and wait, a problem that has occurred in many development processes. Code communication and emergency solutions are quite important, for programmers, bugs are always there, you must always face this problem, the famous Microsoft, have three months in a row without a patch? Never!
< h3 > < a name = "" 1481332-1566388-1 _5" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > test
Test the written system. Give it to the user, and the user confirms each function one by one. There are many kinds of software testing: according to the test execution side, can be divided into internal testing and external testing; According to the testing scope, it can be divided into module testing and overall coordination; According to the test conditions, it can be divided into normal operation test and abnormal condition test; According to the input range of the test, it can be divided into full coverage test and sampling test. All of this is easy to understand. I won't explain it any more. In short, testing is also a very important step in project development. For a large piece of software, 3 months to 1 year of external testing is normal, because there will always be unexpected problems. Completion acceptance after completion of the test and complete the final some help document, the overall project is over, little not upgrade in the future, of course, repair work, and so on, as long as not a fly-by-night operator cheat money, want to pass to keep tracking software operating condition and repair upgrade continuously, until the software is completely eliminated.
< h3 > < a name = "" 1481332-1566388-1 _6" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > software delivery
After the software test proves that the software meets the requirements, The objective of the development of software developers should be submitted to the user installation procedures, database < a href = "https://baike.so.com/doc/2241827-2371998.html" "> the data dictionary < / a >, "user installation manual", "user guide", the reporting requirement, design report, < a href = "https://baike.so.com/doc/6737200-6951612.html" "> < / a > test report, etc. The two sides agreed in the contract products.
< p > "user installation manual" should install software in detail requirement for operating environment, the definition and content, install the software on the client, the server side, and < a href = "https://baike.so.com/doc/2154861-2280034.html" "> middleware Detailed installation steps and system configuration after installation.
The User Guide contains the process for using each software function, operation procedures, service introduction, special tips, and precautions, and provides examples when necessary.
< h3 > < a name = "" 1481332-1566388-1 _7" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > check and accept
User acceptance.
< h3 > < a name = "" 1481332-1566388-1 _8" "> < / a > < a href =" https://baike.so.com/doc/1481332-1566388.html# "> fold < / a > < strong > maintenance
A modification of the application in whole or in part, based on changes in user requirements or changes in the environment. |
|
|
|
 |
|
|
|