Life cycle of a web page, site and projects

Posted on by : admin Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Web pages, Web sites, and Web projects have a lifetime—a life cycle. The well-engineered Web site developer should estimate the duration of the life cycle and should plan for well-engineered Web site maintenance during its active life cycle. Some well-engineered Web pages will be “permanent archival” material, with little maintenance, and with an unbounded life span. The well-engineered Web site project plan, if prepared, shall document requirements for scheduled wellengineered Web site maintenance and/or well-engineered Web site expiration. Some well-engineered Web pages will require ongoing maintenance (for example, due to a legal or regulatory mandate). Permanent archival content should be implemented following strict adherence to standards and minimal dependence on vendor-specific or immature technology. This will facilitate access over an extended period of time, and minimize maintenance requirements.

Life cycle management

In some cases, a well-engineered Web site may approach the complexity of a software project, particularly if the site implements interactive functionality. In these cases, one or more projects should be initiated to execute the responsibility to plan and manage the well-engineered Web site throughout its entire life cycle from conception through retirement. The software life cycle processes of IEEE/EIA Std 12207.0-1996 [B15] should be considered for acquisition, supply, development, operation, and maintenance of well-engineered Web sites.

Web site life cycle plan

A plan should be prepared for managing appropriate life cycle processes for the Web site—acquisition, supply, development, operation, and maintenance. The plan for the Web site should define when, how, and by whom specific activities are to be performed, including options and alternatives, as appropriate. The plan should include, at least, the following generic items:

a) Date of issue and status

b) Scope

c) Issuing organization

d) References

e) Approval authority

f) Planned activities and tasks

g) Macro references (policies or laws that give rise to the need for this plan)

h) Micro references (other plans or task descriptions that elaborate details of this plan)

i) Schedules

j) Estimates

k) Resources and their allocation

l) Responsibilities and authority

m) Risks

n) Quality control measures

o) Cost

p) Interfaces among parties involved

q) Environment/infrastructure (including safety needs)

r) Training

s) Glossary

t) Change procedures and history

u) User support needs (help desk, end-user documentation, telephone line)

v) Target community descriptions