1 Database Use Specification 1.1 All operations on the database on the server can only be performed by server managers. 1.2 Use a unified user, unified connection file to access the database when accessing the database. 1.3 In principle, each channel can only build a library, the library name is consistent with the English name of each channel, and the library contains several tables. Bugful, key columns can consider a single construction library, the library name is consistent with the English name of the column. 1.4 Name: (1) Database, Table, Field, Index, View, etc. A series of databases related to the database must be naming with the content related to content (try to avoid using Chinese Pinyin), for a word is difficult to express, you can consider Use multiple words to add a line (_) connection (not more than four words) named. (2) All names must be unified to use English lowercase letters. (3) All names start and ends cannot be used underline (_). (4) All names cannot contain 26 English lowercase letters and other characters other than the underscore (_). 1.5 The database that is no longer used, the table should be deleted, and must be backed up (including structure and content) before deleting.
2 Document Specification All items must have a related document description (which can be an electronic document). The documentation should contain the following: (1) The project name. (2) List of project team, project leader. (3) Project development initial time and end time. (4) Project content description. (5) Project position. (Which channel, which section) (6) describes the program file name (including path name), file content and implementation of the file content and implementation. (7) Complete procedure flowchart. (8) Database, table, view, index name, use. The name, type, length, and use of the field must be attached to the relevant SQL statement.
3 Source Codes and Page Nesting Specifications 3.1 Sourcecodes: (1) Use custom variables (including global variables, local variables), must first declare the variables, and indicate the type of variables, use. (2) Custom function must use the annotation statement to indicate the purpose of the function, the data type, meaning, and return value of the parameters. (3) Important processes or lessons in programs should use the comment statement to indicate the starting line and end rows of the process and indicate the function of the process. (5) All comments text will be used in Simplified Chinese.
3.2 HTML Page Nested: (1) The HTML page designed by the web design unit determines the position, width, number of rows (or heights), etc. used to dynamically display the execution result of the dynamic display, and text descriptions in the corresponding position. Pictures, text, linkages, etc. (2) Software developers and editors can register the page files and pictures in their respective servers based on the situation, and the page changes and modifies independently. (3) Use include technology to embed the program code separately, request to modify the HTML page, without having to overwrite the program, and the program does not affect the HTML page effect, change the page and modify the program. independent. (4) Pages and programs cannot destroy the overall display effects, fonts, font numbers, colors, etc. of the original HTML page, and the style of the original HTML page should be kept as much as possible. (5) Dynamically generated page indicators (such as image size, page width, height, page file number, etc.) should comply with the company's web design requirements. 4 Test Specification (Software Part) For larger projects, the corresponding test team should be established, and the team members consist of software developers, web designers, technicians, and editors. The test process should refer to the original HTML page provided by the web design unit for the project. The test content includes the following: (1) Page width, height (number of lines). (2) Page text, picture, color is unified. (3) The picture of the page shows whether it is normal, there is no deformation. (4) The effect of pop-up the page. (5) Whether the page is connected correctly. (6) Dynamically generated page meets the requirements of the above aspects, the page size (byte, including the picture of the page, *. JS, *. CSS, *. Class and other related files) comply with the requirements of web design. (7) Whether the function of software is implemented. If the database is queried, modified, deleted, the file is uploaded, downloaded is normal. (8) After the test is over, according to the "Software Development Demand" in the "Test Report", in the "Test Report", in the test results, including the test pass, not passed, pointed out the error pages and related program files, and attached the test in the test Error message.
