Find the specification for the programming part of a software

Detailed Design Phase:

At this stage, the modules can be assigned to different people to design in parallel. In the detailed design stage, the working object of the designer is a module, and the algorithms, processes, and state transitions of the module are designed and expressed according to the local tasks and external interfaces assigned by the outline design. It should be noted here that if it is found that there is a need for structural adjustment (such as decomposing submodules, etc.), it is necessary to return to the outline design stage and reflect the adjustment into the outline design document.

The most important part of the detailed design document is the flow chart, state diagram, local variables and corresponding text descriptions of the module. One detailed design document for each module.

A summary design document is equivalent to an assembly drawing in a mechanical design, while a detailed design document is equivalent to a part drawing in a mechanical design. The arrangement, binding and selling methods of documents can also refer to the method of mechanical drawings.

Different understandings of modules differ from traditional definitions, and it is believed that only larger software functional units can be called modules. This perception has led to a confused understanding of the division of labour between outline and detailed design, which has reduced the usability of documentation and should be corrected. 、

The higher-level part of the outline design is the so-called scheme. The role of the scenario document is to maintain the rationality of the design from a macro perspective.

Some projects adopt an object-oriented approach to analysis and design. There may be more questions about the division of labor between outline design and detailed design. In fact, object-oriented analysis and design methods do not emphasize the phased nature of structured methods, so the concepts of summary and detailed design are generally not introduced.

If there is no such division of labor according to the company's documentation system, the division of packages, the relationship between classes and objects, the external properties of classes, methods and collaborative design can be regarded as summary design; The internal implementation of class properties and methods is considered as a detailed design.

In other words, in the object-oriented design method, the general design refers to what classes there are, and the auspicious design refers to the methods and entry and exit parameters in the class (which can be pseudo**).

1.Requirements analysis - to produce software functional specifications, it is necessary to determine the user's needs for the software, and to make it clear and unambiguous. There is no specific implementation method involved. Users can see it, and developers can do the following work (high-level design) based on it.

2.Outline design - generate a software outline design specification, explain the division of system modules, the selected technical route, etc., and explain the overall implementation ideas of the software. And it is necessary to point out the key technical difficulties, etc.

3.Detailed design - generate a detailed design specification of the software, and further refine the outline design, which is generally completed by the person in charge of each part according to the outline design, and then integrated, which is the specific implementation details. Theoretically, it is required to be encoded in this way.

a Approved plan, assignment or contract for the project, and approval from the superior authority;

b Other published documents belonging to this item;

c.The documents referenced throughout this document, including the software development standards to be used. List the titles, document numbers, publication dates, and publishers of these documents, and indicate the availability of these documents.

The structure of the program system.

A series of charts that list the names, identifiers, and hierarchical relationships between each program within the program system, including each module and subprogram.

Procedure 1 (Identifier) Design Description.

Beginning with this chapter, the design considerations for each program in each level are given one by one. The outline given below is for the general situation. For a specific module, especially a low-level module or subroutine, many of its entries tend to have the same content as the corresponding entries of the previous module to which it belongs, in which case it is sufficient to simply state this.

Description of the program. Give a brief description of the program, mainly explaining the purpose and significance of arranging the design of the program, and also explain the characteristics of the program (e.g., resident memory or non-resident?). Is it a subroutine? Is it reentrant or non-entrancy?

Are there any coverage requirements? Whether it is sequential or concurrent processing. etc.).

Function. Explain the functions that the program should have, which can be in the form of an IPO diagram (i.e., an input-processing-output diagram).

Performance. Describe the full performance requirements for the program, including the requirements for accuracy, flexibility, and time characteristics.

Inputs. The characteristics of each input are given, including the name, identity, type and format of the data, the valid range of the data values, and the input method. Quantity and frequency, inputs, data inputs, and security conditions, etc.

f. 3.5. Output items.

The characteristics of each output item are given, including the name, identity, type and format of the data, the valid range of data values, the form, quantity and frequency of the output, the output **, the description of the output graphics and symbols, the security and confidentiality conditions, etc.

f 3 6 algorithm.

Describe in detail the algorithms, specific calculation formulas and calculation steps used in this program.

f 3 7 process logic.

Diagrams (e.g., flowcharts, decision tables, etc.) supplemented by necessary explanations to represent the logical flow of the program.

f interface. Explain the previous module and the next module and subprogram of the program in the form of a diagram, explain the parameter assignment and invocation mode, and explain the data structure (database, data volume) directly related to the program.

f Storage allocation.

Describe the storage allocation for this program as needed.

f 3 10 annotated design.

Software task book: What functions does the software complete? What kind of performance it has, as well as the delivery conditions, maintenance conditions, etc., are usually initiated by the proposer.

Software requirements specification: in order to complete the above functions, how to design, including the understanding of the task book, function division, module division, etc., the key process, but also for the next level of software writers, software management personnel write;

Software design specification: The coder writes it himself, and not many people read it for testing, maintenance, etc.

Summary. Hello, a program specification is a written document that annotates the program flow diagram to help the program designer further understand the program's functions and design requirements. It is a companion document to the program flow diagram and a companion document to deal with the process design.

The program specification is written by the system designer and handed over to the programmer for use.

Hello, the program specification is a written document that annotates the program flow diagram to help the program lead mining designer further understand the functions and design requirements of the program. It is a supporting document for the flow chart of the barred program, and it is also a supporting document for the process design of the simplified and exciting Youli. The program specification is written by the system designer and handed over to the programmer for use.

Therefore, the program specification must be written clearly and unambiguously, so that the program designer can increase his understanding of the processing process and design requirements of the program to be designed.