Data room charging system-document Learning Overview

After the acceptance of the computer room charging system, the study of "Software Engineering", and then refer to the GB8567-88 standards, and try to write a document on the entire life process of the computer room charging system, have a preliminary understanding of the document.
The purpose of providing documents can be divided into three parts: development, management, and guidance.


 

1. The feasibility study report is a document to discuss whether the system to be developed has development value from a social, legal, and especially economic perspective. The most important thing to discuss is whether the expected system functions and performance, as well as the operating conditions can meet the expectations of users, and whether the investment in the project has considerable benefits. The feasibility study is generally subject to approval and decision-making.

Key Points of learning:

1. Give a macro description of the system's functions, performance, and operation requirements.

2. A detailed calculation of the system development fee and expenditure and income after system operation

3. It is best to list the two in the description method or draw a column chart.

2. The software requirement specification is prepared to give both users and software developers a common understanding of the initial provisions of the software and to make it the basis of the entire development work. This document mainly defines the expected system requirements from the perspectives of developers and users, so that the system development solution can meet the user's needs in use, developers can be satisfied with the technical issues of development, and the two can begin the next system design.

Key Points of study: the research report on the system's functions, requirements, and performance relative feasibility is more detailed, requiring a master of the IPO diagram, and then 'using list description' is an exercise.

3. after completing the software requirements in the Outline Design Manual, the developers will mainly design the outline of the expected system, focusing on functional description, interpretation and integration of requirements, and overall functional modules, the detailed graphic description of each function module should give readers a general understanding of the structure and operation mode after the system is completed.

Key Points of learning: developers are required to translate the needs of software personnel into objects that can be processed by computers, such as input and output, functional division, and data design.

4. the detailed design manual focuses on describing the implementation method of the system. Each module describes the classes and methods required to implement the function, including the involved SQL statements. In general, is detailed description of the specific data and operations to achieve the summary design.

Learning key points: Overview design and detailed design comparison

Differences:

The software design adopts the top-down and successive functional expansion design method. First, the overall design is completed, and then the design of each organic component is completed.

Depending on the nature and content of the work, software design can be divided into brief design and detailed design. The outline design implements the overall design, module division, user interface design, database design, and so on of the software. The detailed design is based on the module division made by the outline design to implement the algorithm design of each module, the user interface design and data structure design are refined.

Contact:

The outline design is the basis of the detailed design. It must be completed before the detailed design, and can be started after the summary design is reviewed and confirmed. The outline design document must be completed, including the overall design documents of the system and the summary design documents of each module. The design documents of each module should be written independently.

The detailed design must follow the outline design. Changes to the detailed design scheme do not affect the outline design scheme. If you need to change the outline design, it must be approved by the Project Manager. Detailed design documents should be completed, mainly the detailed design scheme description of the module. Like the outline design, detailed design documents for each module should be written independently.

The Database Design in the outline design should focus on describing the data relationship to explain the ins and outs of the data. Here we should combine our results data to explain the source points of these results data, the purpose and cause of this design. The Database Design in the detailed design should be a complete data structure document, which is a data dictionary that includes the type, name, accuracy, field description, table description, and other content.

The features in the outline design should focus on functional description, interpretation and integration of requirements, overall division of functional modules, and detailed graphic description of each functional module, readers should be given a general understanding of the structure and operation mode after the system is completed.

The detailed design focuses on describing the implementation method of the system. Each module describes the classes and methods required to implement the function, including the involved SQL statements.

5. The Database Design Manual provides external design, structure design, and operation design for the database from the professional knowledge of the database. This is a large part of system development. This document plays an important role in data processing performance and maintenance.

Key Learning Points: database design and data view

6. The data requirements Manual guides the types and conventions of the input and output data. The Design of Data Types, precision, length, and null value is the core of this document,

7. The software project of the test plan includes black box testing and white box testing. With these two knowledge, prepare a series of test data, test system input and output, and discover system vulnerabilities.

8. The test analysis report summarizes the test results, describes system defects and limitations, and evaluates the system to determine whether the software meets the design requirements. Completed or modified.

9. The project opening plan schedules the project development progress to ensure the efficiency of project development.

Key Points of learning: Gantt chart application

10. The monthly development progress report provides financial feedback, work hours, and task completion information on a monthly basis during the development process, plans the work of the next month, or adjusts the project development plan.

11. The project development summary report is a self-feedback on project development, including production efficiency and product quality, to help the development team summarize progress.

12. The "Operation Manual" is equivalent to the instructions for installation and use of the system in the TV or mobile phone user manual.

13. The user manual is more detailed than the operation manual. Each input and output of the system, as well as error reminders and handling are described in detail.