1. WADM - Initiation

Project Initiation is about defining and refining a project at a high level in order to obtain approval for execution of the project. From the systems development and IT project management perspective this phase is about providing potential technical solutions and costs at a level of detail and accuracy commensurate with the level of detail provided by Customers as they define and refine the scope of the project.

Purpose

To produce high level IT design and costings to support the quote that is prepared for the Customer.

Objectives

• To provide an effort estimate that reflect the project scope and level of detail available at the time.
• To provide sufficient information to support the decision making process to progress a project to the next stage/phase.
• To identify key stakeholders within the Customer’s organisation and within WebArtisan,

2. WADM - Analysis & Design

The Analysis & design phase is where the functional design of the proposed solution occurs. Using key deliverables such as the Scope Statement, design activity occurs to define and document the solution in architectural and functional terms. Review activity occurs with the Customer within the phase in order to ensure that the proposed designs meet business needs and that they can also support design activities within the 3 Build phase.

This phase also generates the final level of costing that can result in alterations to the previously agreed Scope Statement.

Purpose

To detail the systems design at a functional level. From a systems development standpoint this involves developing detailed functional and applications architecture specifications.

Objectives

• To define and produce the Application architecture for the preferred solution.
• To arrive at the final level of costings for the project and document them in the Scope Statement
• To produce one or more detailed functional specification documents to support and guide design activities in the 3 Build phase.
• To obtain sign-off of the above deliverables from the customer.

3. WADM - Build

The build phase is where the development of the system takes place. The system components are identified, designed, built and cross referenced from the Functional Design. This results in the production of the required programs, modules, components and/or interfaces for the application being built.

The build phase includes establishing the environments to support the development and testing (excludes enterprise testing) of the system. A detailed technical design takes place in order to design the technical components of the system at a detailed level. Once designed, the system is built in accordance with WebArtisan's current IT standards and policies. Technical reviews are performed throughout the build phase to ensure quality and adherence to standards. Unit and assembly testing (often this combination is referred to as unit testing only) is carried out during the build phase to validate and verify the system. Once successfully unit and assembly tested, the system is packaged and deployed to function testing.

Purpose

To complete the tasks necessary to successfully build a new or update a system.

Objectives

• To ensure developers can build quality components or integrate components in a structured and timely fashion.

4. WADM - Test

The Testing Activity is a key element in the WASD. It is designed to provide the customer with a level of confidence that an application is fit for purpose.

Testing within WebArtisan is broken up into the following test phases which occur at a number of points during the lifecycle. For example:

• unit testing - undertaken in the build phase
• function testing - planning commences early in the build phase with execution undertaken early - mid test phase
• system testing - planning commences in the build phase with execution undertaken mid - late test phase
• user acceptance testing - undertaken late test phase
• performance testing (if required) - involved in design, build and test phases

Generally speaking, each test phase will entail the following activities:

• the setting of test scope and criteria
• preparation of test plans and scripting
• data identification and setup
• execution of tests
• reporting of results and test outcomes

Purpose

To demonstrate that the application/system under test:

• meets business requirements
• adheres to standards, and
• can function in a production-like environment

Objectives

The objectives of testing in WebArtisan are:

• to demonstrate that the developed or purchased system matches customer and user expectations, and
• to identify problems as early as possible

5. WADM - Deployment

This phase represents the time period after the completion of system testing through to the release to production of the working system. It is mainly concerned with the migration of data, the establishment of the production environment, managing the actual system deployment, and the development of production control processes and procedures.

During this phase the following activities are completed:

• migration of existing data
• deployment of a new or updated system
• decommissioning of existing system (if required)
• establishing the future production support environment, and
• planning, producing and distributing system documentation.

At the end of the deployment phase, the system is released to users.

Purpose

To complete the activities necessary to successfully implement a new or updated system.

Objectives

To ensure that the system deployed into the production environment:

• is deployed correctly, and
• provides the business functions as expected in that environment.

6. WADM - Implementation

The production phase relates to the period after a system is implemented into the managed production environment until the end of the warranty period.  The warranty period begins immediately after the system is implemented and may last for several weeks (as defined in the contract) depending on the size and complexity of the project.

Purpose

To support and maintain a system following its release into a managed production environment.

Objectives

To ensure that:

• appropriate support procedures are in place for the duration of the warranty period,
• support staff are trained and capable of maintaining the system,
• the health of the system is in a stable state with no critical defects prior to handover, and
• the appropriate procedures are in place to close-out the project.