Specification | The dispersibility and interactivity of developing and standardizing WEB development decided that WEB development must comply with a certain development specifications and technical conventions, only each developer in accordance with a common specification to design, communication, development, testing, deployment, in order to ensure that the entire development team to work together to improve the efficiency of development, Improve the quality of the project.
The role division of the project
If not including the Prophase and later marketing and sales staff, the development team can generally be divided into project leaders, programmers, art three roles.
The project manager is accustomed to be called the project managers, responsible for the project personnel coordination, schedule and other arrangements, and to deal with some of the project related to other things. Programmers are mainly responsible for project requirements analysis, planning, design, code writing, website integration, testing, deployment and other aspects of the work. Art is responsible for the site's interface design, layout planning, grasp the overall style of the site. If the project is larger, you can group people into three different roles.
Role Division is the objective requirement of Web project technology decentralization and even geographical dispersion, the result of division of labor can clear the responsibility of work, and finally ensure the quality of the project. The negative effect of division of labor is to increase the team communication, coordination costs, to the project to bring certain risks. Therefore, the coordination ability of the project manager is very important, the program developers and artists in the initial stage of project development and later, must have sufficient communication, together to complete the project planning and testing, acceptance.
Second, the selection of development tools
Unlike C/s structure program development, you can a language from beginning to end, you use Delphi, is the Delphi programmer, you use VC + +, you are VC programmer. b/S structure of web development work, the choice of tools is a painful thing. From Windows to Linux, from IIS to Apache, from Java EE to. NET, from EJB to COM to. NET components ... There are Asp, ASP.net, Jsp, Php, Perl, Javascript, Vbscript ...
Art also relaxed not much, what "Web Three Musketeers" "New Web Page Three Musketeers", FrontPage, Photoshop, CorelDraw ... Everyone says that they are the most powerful!
Our experience is that it's best to be unified when choosing tools, but there's no need to be consistent. It is the diversity of web development tools that makes the Internet a colorful situation today. As long as the programmer's Pure HTML code Kung Fu is strong enough, generally will not affect the final site integration work.
III. Process of project development
Led by the project manager, with the programmer as the center of gravity, the discussion, the completion of user needs analysis, the production site of the column planning (with tree), marked out which are static pages, which are dynamic pages. Dynamic pages require program implementation. Develop the interface frame of the website, including the composition of the homepage, and the 钩稽 relationship between the pages. Create the structure of each column folder (some public folders such as images, scripts, styles, etc. need to be fixed storage, common call).
Then by the art according to the needs of the content performance, design static Web pages and other dynamic page interface frame, the segmentation of the picture to be cut from the size. Page space is reserved for pages that require dynamic implementation of the program. Develop CSS styles such as font, font size, hyperlink, etc.
At the same time as the Graphic design page, the programmer started to develop the background code, do some necessary tests.
After the completion of the art interface, add the program code, combined with the site, by the project team together to test, find bugs, improve some specific details. Finally, the site is deployed.
Each of the above will produce a number of phased results, the project manager needs to be timely audit, supervision, and found problems even if corrected.
.
Iv. some technical rules
1, database naming convention
Table naming convention: Table name length can not exceed 30 characters, the word first letter uppercase, multiple words without connecting symbols.
Field naming convention: The field name as far as possible in English words, the first letter of the word, the word "_" separated, the naming rule is "Table class name _ word", such as: User_info,news_content.
View naming convention: Use Rules view_ table A_ table C, where view represents "view". This view is generated by a few tables with the hyphen "_" to connect the names of several tables, and if the table is too much, the table name can be simplified appropriately.
Stored procedure naming convention: P_ Table Name _ Access Procedure name (abbreviated), such as p_user_deleted.
2, folder naming convention
Public folder:
/images Public Pictures
/styles style Sheet
/scripts Script
/ftps Download
/DOC website Related Materials, documents
/readme.txt website Description Document
/helps.htm Web site Help document
/mylogs.txt Website Maintenance Record
Other column naming, you can use pinyin initials, can also use English words. The meaning of all folders is described in the Readme.txt file.
3, object and variable naming convention
Each variable name must be defined first and then used. Add a statement <%option explicit%> at the beginning of the ASP file to enforce the variable definition. The code block must be in indented format. Each function must indicate the function, input parameters, and information about the return value.
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 or one minor experience
1, can use static Web page performance content, as far as possible without the program code dynamic implementation.
2, the design phase, must communicate with the user fully, complete, accurate understanding of user needs. Can not distort the meaning of the user, also can not blindly cater to the user's improper needs, nor can not grasp the technology is not even possible to achieve technical bombast. Demand analysis is a process of communication, communication, guidance, education, struggle and compromise. The result of requirement analysis should be archived by text data.
3, technical parameters must be understood accurately. For example, the user's software platform is the Linux series, then your system has to use java+apache development, at this time your asp.net technology will not be used.
4, when necessary, let the user to the identified requirements of the content signed, sealed.
