On a row, I'm going to watch the ASP code of my colleague. I almost be crazy: CWBSJTJTIJIAOCHULI.ASP This is the financial report data submission processing page ..., like there is more, a small system, there is more than 100 Page, take a closer look at the code to find N more repetition, I am dizzy ~~~~~~~ Everyone talks about this development standard, such as named standard, directory name, and included standards, module classification standards, There is also a commonly used custom function (verification such as page permissions, etc.). Don't deliberately go to the code, why do people know so comfortable? Well, the Chinese software ...
Before the recommendation of the development, the standard consensus, write into a standard document, strictly abide by the proposed multi-integration, a functional module handled in a file,
I think the consensus should be reached in potential consciousness. That is to say, not just a company, you should have a default rules or standard in an industry, so that software development is more cool!
Work plan, write demand, unified code standard
In the unified point of view, we can only better develop procedures, and only this can write a good program, which can shorten the development cycle, and the code is reused.
This problem must be resolved in the design phase. After the interface design is complete, the function must have a detailed description, the function explains one person, the programmer must prioritize the use of public functions, the code is not used, the public function is not used, must be rewritten ,Develop good habits. The company must have corresponding specifications, such as design specifications, coding specifications (coding conventions), etc. The program's design documentation must be complete and complete.
The ASP itself is not too strict. This is all dedicated to the writer. Create a class good name, or the private variable / function puts the object even if it is closed
Although there is no strict specification, programmers often have potential specifications, but they have not fully unified. Everyone can download "Snitz Forum 2000" to see people's 1, code writing specification 2, file clips and naming rules 3, and file name naming rules are very particular. If you have a little thing in a small company, the front people are gone, the people behind will be maintained, there is no such potential consciousness, then don't be mad ~~~~~~~~~~~~! !
This should be deeply concerned! I have my own standard, I don't know if you do this: 1, folder: / inc, / js, / images, / data ... 2, file name: a_b_c.asp A: Module name B, function name C, logo name (best to understand English) 3, basic document: index.htm (no specific content, which contain main.htm / main.asp) /login.asp...... A person of course Not all, how are you coming to participate?
4, database table name A1_AASDF, A1_BASDF, A1_CASDF B1_AASDD, B1_SDFSD, B4DD, A1_ID, A1_BASDF, A1_CASDF B1_BASDF, A1_CASDF B1_ID, B1_SDFSD, B1_CADFE5, page Database Package 6, big database operations try to use storage processes to do 7, unified And optimized code editing page (pay attention to adding if you need two or more people to participate)
Be sure to force the definition variable, strictly control the lesson of size. . . .
Not talking about me, I don't seem to have used the ASP to have a financial statement, etc., but before those things are constantly complement, rather than starting with good planning and then developing, is the development side according to the requirements The content, file name is generally not in Chinese, a module a folder, in English, then build a file for a Chinese module in each folder, and the A file sorted in the forefront, the module Chinese name can be found in the module The file name corresponding to each function is recorded, and the public function can be placed in the included file. For some functions, especially for the database, you can divide 4 parts, input and modify, browse, and print, homepage Display, delete, these four parts correspond to the 3-class database operation, increase, modify, delete, write a function in a file. In short, I don't think there are not a lot of specifications. There is no specific standard. For those who develop code, code efficiency is divided into global efficiency, local efficiency, time efficiency, spatial efficiency, and to ensure the correctness of the software, Under the premise of readability, stability, and testability, any of the efficiency has an impact on other efficiency. See how you go to go, but there is one, local efficiency is to serve global efficiency, these Not a few words can be clear, especially when a system is completed, it is the most headache when the module is required. 1. Require parameters (provided by customers, system analysts) 2. System demand analysis (system analysts determine) 3, the technology adopted by the architecture (system analyst determined, according to customer requirements) 4, database dictionary ( Development programmer fills in the respective projects) 5, function module description and public function definition (development programmer fill in items) 6. Use instructions (developer fill in the project) 7, Administrator operation guide (development programmer Project 8, test report (program tester filled in) 9, data backup description (project leader and programmer
Strictly followed by the above steps
