Architectural design
This stage will define the basic building blocks for the project. The design must ensure the following.

All tests within the Test Plan are met.

Offer scalable future expansion, as agreed with the client.

Be maintainable, i.e. be clear and in accordance with accepted design principles.

Prototyping
In this stage we do a number of very important tasks, to minimize the risk of a costly re-design later on in the project.

Firstly, we will do a rough design of the overall user interface and create mockups of the key pages. This will be in consultation with the client to ensure that you are happy with how the website/e-commerce solution will look.

The next 3 tasks are only applicable if your project involves an integrated database.

We will turn the data model into a real test database, which we will populate with the maximum amount of data that the system is expected to hold. This is usually twice the client's expectation, as experience dictates that databases always grow.

We will construct some database queries to emulate database activities that the user of the website would typically do. For example, "How many items of a specific make do you have in stock?" We will then carry out performance testing to ensure that this is within client expectations. If not then we will re-design and re-test.

Finally we work with your existing data sources (e.g. stock system) to build data synchronization routines. We will also work with you to find the best way for you to keep the content of the website/e-commerce solution updated.

First Code Build
Here we build the website, develop any necessary administration and web user interfaces (such as web pages to control data upload), author static sample content and build the backend business logic.

Depending on the size of the development we may split the development phase down into a number of separate sub-phases. This helps to maintain better control of the project.

Any changes requested accepted by KlyNET and the client (including cost implications), via the Change Management Plan, for the First Code Build are also implemented.

Testing.
Testing is formally carried out in-house and/or at the client site, whatever is appropriate. This will be in accordance with the Test Plan.

During this phase minor bugs are fixed. Major bugs, or functional inadequacies, are planned into the Second Code Build.

Second Code Build
This usually spans 20-40% of the effort of the first code build, and involves the following tasks.

Functional inadequacies are redesigned and built.

Each web page is populated with the final page content.

Data source synchronization routines are implemented, if applicable.

Project databases are now populated with client data, if applicable.

Any changes requests accepted by KlyNET and the client (including cost implications), via the Change Management Plan, for the Second Code Build are now implemented. These may be functional additions or changes to existing functionality.

Release Testing
Testing is formally carried out in-house and/or at the client site, whatever is appropriate. This will be in accordance with the Test Plan.

All bugs, or functional inadequacies, are fixed.

Implementation
This phase is only relevant with websites/e-commerce solutions that have been developed exclusively on development servers, i.e. not 'live' on the Internet. This will usually be the case for website re-developments.

The website files are transferred onto the Internet, formally tested again (according to the Test Plan), and made 'live'.