Web Site Life Cycle
Web Site Life Cycle
The developer of a well-engineered Web site should prepare a project plan, or follow an existing plan, cover-ing the entire life cycle of the well-engineered Web site, including development, maintenance, and retire-ment. The well-engineered Web site project plan shall incorporate consideration of the implications of bothminimum and maximum Web site life expectancies.The project plan should address Web site maintainability. The plan should address requirements for dates(see 7.4) and contact information (see 4.2.6 for privacy, 5.7 for Webmaster, and 5.11 for site center).Some well-engineered Web pages have as a significant objective the delivery of specific information to indi-viduals who need that information. Well-engineered Web sites shall have an identified set of metrics that canbe evaluated. Ease of access to information by targeted-user communities is an example of one of the possi-ble design goals.17Navigation aids, buttons, user readable body metadata, and other items commonly appearing on multiplewell-engineered Web pages should be consistent across the site. The consistency shall include the commonlook and feel as well as a common location within the well-engineered Web page.18This recommended practice should be reviewed, in its entirety, during the early part of the design stage toidentify all factors that need to be considered for the design, development, and maintenance of a well-engi-neered Web site.Design shall take into consideration the characteristics of the client and server environment. Failure to dothis may interfere with access to the presented material by some of the target-user community. Plans shouldinclude contingencies for technical obsolescence and growth.Test cases shall be designed considering the user interaction with the Web site. Some testing effort shallstress performance and scalability features supported by servers that will be used when the site is inoperation.Recommended security practices for connecting to the Internet are being defined in a draft IEEE Standardwhich currently has a proposed designation of 2002. These recommended practices for Internet operationsare also applicable for Intranets and Extranets. Well-engineered Web site design shall consider the recom-mended security practices contained in IEEE Project 2002 once it is published as an approved IEEEStandard.If a well-engineered Web site is complex or if it implements interactive functionality, it may be useful to consider it as a software product and to apply appropriate standards for software development and mainte-nance.
The delivery of the information to the user is the primary purpose of a Web site. Comprehension and naviga-tion are key engineering design considerations. Non-textual information (e.g. video, graphics, audio) canconsume significant bandwidth, but can also provide advantages in delivering information in a coherent andeasily comprehended way. The low bandwidth environments of some users, the inclusion of an option fortext-only delivery, adaptation for the visually impaired, and delivery in multiple languages are issues thatshould all be considered.Well-engineered Web site design may segment information contents by expiration and/or revision date andincorporate this into the overall Web site design. Well-engineered Web site design shall include a clear wayto identify the areas changed without the need for navigating the whole site. The segmentation should be atthe page level. A policy for the expiration of the changed-pages list should be described.Some information has a limited useful life. Stock quotes, telephone directories, product specifications, orga-nizational charters, and archival background information change at different rates. The nature of the infor-mation and the need of the user to have “current” information affects the contents of well-engineered Webpages, as well as the methods used to deliver these pages.https://arudhrainnovations.com/
The developer of a well-engineered Web site should prepare a project plan, or follow an existing plan, cover-ing the entire life cycle of the well-engineered Web site, including development, maintenance, and retire-ment. The well-engineered Web site project plan shall incorporate consideration of the implications of bothminimum and maximum Web site life expectancies.The project plan should address Web site maintainability. The plan should address requirements for dates(see 7.4) and contact information (see 4.2.6 for privacy, 5.7 for Webmaster, and 5.11 for site center).Some well-engineered Web pages have as a significant objective the delivery of specific information to indi-viduals who need that information. Well-engineered Web sites shall have an identified set of metrics that canbe evaluated. Ease of access to information by targeted-user communities is an example of one of the possi-ble design goals.17Navigation aids, buttons, user readable body metadata, and other items commonly appearing on multiplewell-engineered Web pages should be consistent across the site. The consistency shall include the commonlook and feel as well as a common location within the well-engineered Web page.18This recommended practice should be reviewed, in its entirety, during the early part of the design stage toidentify all factors that need to be considered for the design, development, and maintenance of a well-engi-neered Web site.Design shall take into consideration the characteristics of the client and server environment. Failure to dothis may interfere with access to the presented material by some of the target-user community. Plans shouldinclude contingencies for technical obsolescence and growth.Test cases shall be designed considering the user interaction with the Web site. Some testing effort shallstress performance and scalability features supported by servers that will be used when the site is inoperation.Recommended security practices for connecting to the Internet are being defined in a draft IEEE Standardwhich currently has a proposed designation of 2002. These recommended practices for Internet operationsare also applicable for Intranets and Extranets. Well-engineered Web site design shall consider the recom-mended security practices contained in IEEE Project 2002 once it is published as an approved IEEEStandard.If a well-engineered Web site is complex or if it implements interactive functionality, it may be useful to consider it as a software product and to apply appropriate standards for software development and mainte-nance.
The delivery of the information to the user is the primary purpose of a Web site. Comprehension and naviga-tion are key engineering design considerations. Non-textual information (e.g. video, graphics, audio) canconsume significant bandwidth, but can also provide advantages in delivering information in a coherent andeasily comprehended way. The low bandwidth environments of some users, the inclusion of an option fortext-only delivery, adaptation for the visually impaired, and delivery in multiple languages are issues thatshould all be considered.Well-engineered Web site design may segment information contents by expiration and/or revision date andincorporate this into the overall Web site design. Well-engineered Web site design shall include a clear wayto identify the areas changed without the need for navigating the whole site. The segmentation should be atthe page level. A policy for the expiration of the changed-pages list should be described.Some information has a limited useful life. Stock quotes, telephone directories, product specifications, orga-nizational charters, and archival background information change at different rates. The nature of the infor-mation and the need of the user to have “current” information affects the contents of well-engineered Webpages, as well as the methods used to deliver these pages.https://arudhrainnovations.com/
Comments
Post a Comment