The dispersion and interaction of web development determines that Web development must comply with certain development specifications and technical conventions. Only every developer is designed, communicated, develops, tests, deployed in accordance with a common norm, and can guarantee the entire development team. Coordinating and consistent work, thereby increasing development efficiency and enhances the quality of the project project.
First, the role of the project
If you don't include the pre-periods and later marketing and sales staff, the development team can generally be divided into three roles of the project leader, programmer, and art.
The project leader is used to calling the project manager, responsible for the project's personnel coordination, time progress, etc., and handles some other things related to the project. The programmer is mainly responsible for the needs of the project, planning, design, code writing, website integration, testing, deployment, etc. Artists are responsible for the interface design, layout planning, and grasp the overall style of the website. If the item is relatively large, you can group people according to three characters.
The role division is an objective requirement of the technical dispersibility of web projects and even geographic dispersibility, and the results of division of labor can also clarify the responsibility and ultimately guarantee the quality of the project. The negative effects brought by division of labor are to increase the team communication, coordination cost, bringing certain risks to the project. Therefore, the coordination capacity of the project manager is very important. The initial and late stage of program developers and the United States in the project development must have sufficient exchanges to complete the planning and testing of the project.
Second, the selection of development tools
Not like the C / S structural program development, you can go from head to tail in a language, you use delphi, you are Delphi programmers, you use VC , you are VC programmers. The B / S structure web development work, the choice of tools is a painful thing. From Windows to Linux, from IIS to Apache, from J2EE to .NET, from EJB to COM to .NET Components ... Also include ASP, ASP.NET, JSP, PHP, Perl, JavaScript, VBScript ......
The beauty is not too much, what "Web Sanju" "New Website", FrontPage, Photoshop, CorelDraw ... No one said that you are the most powerful!
Our experience is that it is best to unify it when choosing tools, but it is not necessary to deliberately consistent. It is the diversity of web development tools that has achieved colorful situations today. As long as the programmer's pure HTML code is too hard enough, it generally does not affect the final integration of the website.
Third, the project development process
Lead by the project manager, the programmer is focused, discussed together, complete user needs analysis, generates the list of websites (represented by tree chart), which is a static page, which is a dynamic page. Dynamic pages must be implemented. Develop the interface framework of the website, including the first page composition, and the hook relationship between each page. Generate structural diagrams of each column folder (some public folders such as images, scripts, styles, etc. need to be fixed, co-calls).
Then design a static web page and other dynamic page interface framework based on the description of the content, and the segmentation is cut according to the size cut. Give the page reserved page space for the page you need to dynamically implement. Forming fonts, font numbers, hyperlinks, etc. CSS style, etc.
At the same time as the art design page, the programmer starts to develop the background program code and do some necessary tests.
After the US worker interface is completed, add the program code, combined website, co-tested by the project group, discovers BUG, and improve some specific details. Finally, the website is deployed.
Each of the above will produce some phased outcomes, and the project manager needs timely review, supervision, and finds the problem even if it is corrected.
Fourth, some technical rules
1, database naming conventions
Table naming conventions: The length of the table name cannot exceed 30 characters, the word premniction letter is uppercase, and multiple words are not used. Field naming conventions: Field names Try to use English words, word first letters, words with "_", named rules are "table class alias _ words", such as user_info, news_content.
View Naming Convention: Using Rules View_ Table A_ Table B_ Table C, where view represents "view". This view is generated by several tables that connects several tables in the name of the character, if excessive table can be properly simplified.
Store procedure naming conventions: P_ table name _ access process name (abbreviation), such as p_user_deleted.
2, folder naming agreement
Public folder:
/ images public picture
/ styles style sheet
/ scripts script
/ ftps download
/ DOC website related material, document
/README.TXT Website Description Documentation
/Helps.htm website help documentation
/MYLOGS.TXT website maintenance record
Naming of other columns, you can use the first letter of the pinyin, you can also use English words. The meaning of all folders is described in the readme.txt file.
3, objects and variable naming conventions
Each variable name must be defined first, then use. The top addition of the ASP file <% OPTION Explicit%> can force the variable definition. Class blocks must be used in indentation format. You must indicate the function of the function, enter the parameters, and return values.
Variable type abbreviation prefix
String Str or S
Integer Int
Date DT
Object obj or o
Boolean BOL or B
Byte Byt
Double DBL
Error ERR
Long LNG
Single SNG
Five, some little experience
1. Use the contents of static web page, try to dynamically implement the program code.
2. Design phases, you must fully exchange, completely and accurately understand the needs of users with users. Never distort users, you can't give it to the non-aggregated needs of users, and you can't boast the technology that you don't have to grasp the technology or even impossible. Demand analysis is a process of communicating, communicating, guiding, education, struggle, compromise. Demand analysis results must have text data archive.
3, technical parameters must be accurate. For example, the user's software platform is the Linux series, then your system has developed with Java Apache, this time your ASP.NET technology is not used.
4. When necessary, let the user signed the contents of the already determined demand, stamp.
