Categories
Uncategorized

Web Development Lifecycle (WDL)

The web development lifecycle (WDL) is a more specific variation on the general framework for developing any application development project. Unlike general application development, all web design and development projects follow a similar structure, so the web development lifecycle / process can be drawn upon as a point of reference for both the web development team and the client to determine the status of any given project and the area of activity to address next.

The Web Development Lifecycle is made up of eight identifiable stages described as follows:

1. Initial Consultation

The Initial Consultation seeks to understand the high level business requirements, the scale of the web development, required delivery schedule, and the overall feasibility, web design and cost of the project.

2. Project Specification

The business requirements of the proposed website are iteratively established between the Client and the web design team, and documented in the form of a High Level Requirements Specification. Focus here is on the relevant business rules and outputs. Implementation of the system, how the requirements are actually delivered, is reserved for later. Once agreed, this document will form the basis of the subsequent stages of the Web Development Lifecycle.

3. Web Site Architecture

Here the software and hardware requirements for delivery of the web application are established, such as the most appropriate web and application development language, operating system, database management system (DBMS), and hardware / hosting environment that are most appropriate to support the final website in a robust and reliable manner; taking account of the likely growth of data volumes, visitor numbers web traffic, and functionality.

4. Web Site Design Cycle

Deliverables out of this phase have a particular focus on the web design of the system, include mock-ups or prototypes of the screens that make up the system, combined with system walkthroughs which will enable both the Client and the software developers, designers and project management team to clearly understand how the website will work from the user and administrators perspective. The design of the CRM would also be full considered here also. This web application functionality is considered in the context of the defined outputs and business rules, and may result in the High Level Requirement Specification being updated or changed. Following this, a key deliverable here is a Low Level Website Design Specification / Document precisely defining the required implementation of the web design and forming a blue print of the project for the software developers.

5. Content Collation

Any required textual and graphical content for the web application is developed or acquired by the Client (or the software development company, depending on the relevant situation). Admin functionality which enables the Client to amend the full content of the site from system launch, and on an ongoing basis, is assumed to have been included and defined within the High Level Requirements Specification, as mentioned.

Leave a Reply

Your email address will not be published. Required fields are marked *