What is web design-building a Web site

web| Design | Site Building Web site is very difficult. Although some core technologies such as H T M are easy to master, developers still make a lot of mistakes. This is mainly due to the lack of developer experience, the confusion of processes, and the unrealistic scheduling. Because of time constraints and lack of experience, developers often go to extremes, regardless of the successor steps, and attempt to one-step, direct implementation. For example, some Web professionals start building sites directly from their skins. Use visual design tools to try to do a page, and then consider the next step, resulting in the design of the page multicolored, looks like a fine brochure. Today, some of the appearance-oriented site is often fully developed using Macromedia Flash, the effect is like playing some movie head but do not introduce the film. This approach, in addition to showing the creators of the design of the art, the site to achieve the goal of no help. For those famous sites, this may be the intent, but what about other types of sites? First of all consider the appearance of those sites often difficult to update, in addition to dazzling effects, there is no major technology, lack of functionality, and download speed is very slow. Many people refer to this site as brochure software (b r o c h u r E w a r e) or title software (i n t r o w a r e), mainly because these sites are not as informative as those brochures, entertainment software or movie presentations. Examples of such sites are shown in Figure 1-2. The other extreme, of course, is to focus on implementing technology at the outset, which, while adopting the latest and best technology, often lacks a holistic design. Looks very clumsy and the interface is very confusing. Sometimes these sites also adopt a design method called "Christmas Tree". Once the basic functionality is achieved, developers start to decorate the tree like a ball or paper-cut, doing everything they can to modify the page with G I F, but in vain. In this case, the appearance is in a secondary position relative to technology. Similarly, in the case of "appearance first", technology is used to show the developer's skills rather than meeting the needs of the users. Excessive use of Java applets and Plug-ins, and require browsers to support the latest version of D H T m L, X m L or C s, this is the "technology first" logo. The pursuit of "technology first" site attempts to adopt a unique design, using the latest version of the browser, often lack of support for site functionality. An example of an overly tech-highly-acclaimed site is shown in Figure 1-3.

Web development Process Model

Technology and appearance effects provide the foundation of the Web Pyramid, which is closely related to the implementation of the site intent. It is better to discuss the intention of the site first and then determine the way to implement it before discovering the problem in haste. This deductive or "top-down" approach to web development is well understood. First of all, it is very important to consider the intention of the site. Before building a site, you should carefully understand the site design problems encountered and to strive to achieve the goal. Clear understanding and definition of objectives can reduce the risk of project failure and help determine the rationality of site design. In determining the goal of a good site, you should create a good specification, the specification document records all the requirements of the site, and seriously consider the needs of users. Then you should produce the site's design book. These designs include prototypes of technology and appearance. Once the design is complete, you should start implementing and testing. Finally, all parts of the site should be set up as a whole and tested further. You must finish the procedure above before you can publish it. Once users begin to feedback, they should proceed with the correction and modification. Many disciplines such as software engineering have defined a process model that is very similar to the one described earlier, most notably the waterfall model, which describes the entire software lifecycle from project planning to final release and maintenance. This process is divided into several phases, from general requirements to concrete implementation, and so help guide the design. Figure 1-4 is an example of a waterfall model partitioning phase.

It is worth pointing out that for the names and numbers of steps in the various process models, the programmers are different. Further, the basic waterfall model is not the only use model, there are other models, such as the modified waterfall (M o d i f i e D W a T e R f a l) model, the spiral (s P i r a l) model, the Joint Application development (joint application Design, JAD) model is also used.

It is important to remember that the ultimate goal of the process model is to help guide the development of the site. The ideal Web process model helps developers deal with site complexity, reduce site risk of failure, properly handle changes encountered in projects, and provide feedback in management to quickly and easily track feedback. In fact, the requirements for an ideal web model are rather harsh, especially given that most web developers are unfamiliar with the formal principles of software engineering, and that the web is not even 1 0 years old.