Website Development Life Cycle
Web development although very flexible and dynamic can follow the time-honed and tested methods used in systems development. Here we have identified which phases are applicable and added those are that unique to the esoteric world of the web.
Note: All throughout this document, the words web sites, web applications, web-based applications and intranet/extranets will be used interchangeably.
1. Analysis
This is the phase that most of the higher management and the ROI-concerned folks do not fully appreciate since there is no tangible output in this stage. The analysis phase is very vital as this is when you answer the tough questions: How will the web application help the present system? How is it going to help the business? Equally important is the question: How will the website complement or be integrated into the current or existing system?
Analyzing the pros and cons, setbacks and pay-offs of the website need not be too time-consuming and resource-intensive. Focus should be given to the identification of target audience, existing resources that can be utilized (e.g. a database, an excel file of customers, etc.) and ways that the website could be fully exhausted. For example, a client plans on publishing their product catalogue online; why not employ an online shopping cart and payment system? This way traffic to the site is fully monetized.
At the end of this stage, the team should be able to come up with complete cost-benefit analysis and the identified goals should be realistic. The analyst should consult the website designers, developers and testers to gauge the effectiveness and viability of the plan.
2. Specification Building
Preliminary specifications are drawn up to cover each and every element of the requirement. For example, if the product is an online store then the modules of the site such as the general layout, site navigation, and other dynamic parts are identified. Feature-rich projects will require various levels of consultation to assess additional business and technical requirements. This is the stage where you identify the who, what and when: what technology to use; who among the group is best suited to do the codes for each and every module; when is the expected delivery of the product.
After reviewing and approving the preliminary document, a written proposal is then presented to the client. The document should outline the scope of the project including the responsibilities, timeline and cost.
3. Website Design and Development
After the specification of the project has been identified and the proposal signed by the client, work on the web site commences. Normally, the site layout and navigation will be designed during this phase as prototype.
Two to three study designs are offered for client viewing and approval. Some client might demand to see the full functional prototype – then the team has to show them the interactivity of the site’s various features.
In most cases, the client will give suggestions and require a lot of changes on the prototype. Once a final version of the design, layout and navigation has been achieved with the client’s approval, of course, you should freeze the prototype before you start the codes.
We need a quick definition of FREEZE here. It is a method to make both parties to agree on how the web site will look like and function on the launch day.
The development team during this phase will start the database structure. All necessary information should be had from the client, such as access to test servers and database, ftp login, sample data, and images they would like displayed in the site.