Web Site Engineering
Web Site Engineering
The World Wide Web is expanding and its value is increasing as a method for locating and delivering infor-mation. This creates a significant engineering challenge. Locating applicable information requires thatindexing information be incorporated into Web page development. Once an applicable page has beenlocated, essential information may not be present, resulting in user frustration and a failure of the Web appli-cation to meet its purpose.This is a revision of the 1999 accumulation of Web site management “recommended practices.” This revi-sion is based on IEEE Std 2001-1999, extending it based on recommendations since it was developed,addressing “site-wide” issues as well as “managed” Web sites (as opposed to just Intranet and Extranetsites). These can serve to improve the effectiveness of Web pages for users, Web page developers, and thevalue of the Web in corporate and organizational applications. This recommended practice is focused onmanaged Web sites, Intranet (within an organization), and Extranet (between a group of collaborating orga-nizations).
Other projects are being evaluated by the Internet Best Practices working group (IBPwg) withinthe IEEE Computer Society. See http://dx.doi.org/10.1041/standard/2001 for current details.Web page engineering often is done with little consideration for the immediate or ongoing implications ofWeb site design or implementation. Some sites reflect “state of the art” delivery that can only be accessedwith the most recent tools. This may be inconsistent with the business objectives for that site. Some sites willlanguish beyond their applicable life, occupying valuable resources (particularly as these are incorporatedinto organizational indexes, and delivered as prospective “query returns” by indexing and search services).Poor Web page engineering results in lost productivity and user frustration, and can result in legal liabilities Aruthra innovations
There is no clear prediction of when the World Wide Web or a specific site will be obsolete. There is a legit-imate engineering concern that this lifespan may be significantly underestimated or disregarded entirely inmany Web site designs. Vendor products—past and future versions, format preferences, or selection ofimplementation languages—may require future re-engineering as vendors and products fade. Corporate Websites may not need to live beyond the life of the corporation, however, public sector and other institutionalsites may well span centuries. A significant portion of the content of these sites may not require updating,except in cases of shortsighted design. The Magna Carta and the works of Shakespeare are examples offairly stable content.The recommended practices and requirements set forth in this recommended practice are aimed to reducethe risks associated with Web page investments. Further revision of this recommended practice is expected,partially to reflect changes in the Web environment, but also to reflect increased understanding of “recom-mended practices” in Web page engineering.
There is a popular awareness of “Web years,” characterized byrapid advances in the platform technology for clients and servers. There is a potentially expensive, misin-formed conclusion that might be drawn from this, which is that Web pages (and more directly, informationcontent and services delivery) either are, or should, move forward at this same rate. Some of today’s Webpages will warrant long-term retention, and within the context of business operations (which is the core ofmanaged sites), re-engineering of last year’s Web pages is an investment that requires justification. The valueof Web-based operations is the delivery of the right information and services to the right persons at the righttime with the least amount of effort. Success in Web-based operations is based more on engineering designin response to an understanding of the target-user community and information, than it is on the rapidlyevolving technology for Web platforms.
https://arudhrainnovations.com/
The World Wide Web is expanding and its value is increasing as a method for locating and delivering infor-mation. This creates a significant engineering challenge. Locating applicable information requires thatindexing information be incorporated into Web page development. Once an applicable page has beenlocated, essential information may not be present, resulting in user frustration and a failure of the Web appli-cation to meet its purpose.This is a revision of the 1999 accumulation of Web site management “recommended practices.” This revi-sion is based on IEEE Std 2001-1999, extending it based on recommendations since it was developed,addressing “site-wide” issues as well as “managed” Web sites (as opposed to just Intranet and Extranetsites). These can serve to improve the effectiveness of Web pages for users, Web page developers, and thevalue of the Web in corporate and organizational applications. This recommended practice is focused onmanaged Web sites, Intranet (within an organization), and Extranet (between a group of collaborating orga-nizations).
Other projects are being evaluated by the Internet Best Practices working group (IBPwg) withinthe IEEE Computer Society. See http://dx.doi.org/10.1041/standard/2001 for current details.Web page engineering often is done with little consideration for the immediate or ongoing implications ofWeb site design or implementation. Some sites reflect “state of the art” delivery that can only be accessedwith the most recent tools. This may be inconsistent with the business objectives for that site. Some sites willlanguish beyond their applicable life, occupying valuable resources (particularly as these are incorporatedinto organizational indexes, and delivered as prospective “query returns” by indexing and search services).Poor Web page engineering results in lost productivity and user frustration, and can result in legal liabilities Aruthra innovations
There is no clear prediction of when the World Wide Web or a specific site will be obsolete. There is a legit-imate engineering concern that this lifespan may be significantly underestimated or disregarded entirely inmany Web site designs. Vendor products—past and future versions, format preferences, or selection ofimplementation languages—may require future re-engineering as vendors and products fade. Corporate Websites may not need to live beyond the life of the corporation, however, public sector and other institutionalsites may well span centuries. A significant portion of the content of these sites may not require updating,except in cases of shortsighted design. The Magna Carta and the works of Shakespeare are examples offairly stable content.The recommended practices and requirements set forth in this recommended practice are aimed to reducethe risks associated with Web page investments. Further revision of this recommended practice is expected,partially to reflect changes in the Web environment, but also to reflect increased understanding of “recom-mended practices” in Web page engineering.
There is a popular awareness of “Web years,” characterized byrapid advances in the platform technology for clients and servers. There is a potentially expensive, misin-formed conclusion that might be drawn from this, which is that Web pages (and more directly, informationcontent and services delivery) either are, or should, move forward at this same rate. Some of today’s Webpages will warrant long-term retention, and within the context of business operations (which is the core ofmanaged sites), re-engineering of last year’s Web pages is an investment that requires justification. The valueof Web-based operations is the delivery of the right information and services to the right persons at the righttime with the least amount of effort. Success in Web-based operations is based more on engineering designin response to an understanding of the target-user community and information, than it is on the rapidlyevolving technology for Web platforms.
https://arudhrainnovations.com/
Comments
Post a Comment