Aliment Software Technologies has a well-established Quality Management System specifications and requirements. By default, this QMS is followed for any project. However, if the client wishes to have its own quality processes to be followed, then the same can be implemented; the client normally provides the required training.

A brief outline of the processes being followed is given below:

Requirements Definition and Task Planning phase

Design and Implementation Planning phase

Coding and Unit Testing

Integration Test

Function Test

System Test

AcceptanceTest

During the course of the project, the Aliment Software Technologies Project Manager reports to the Client Representative on a weekly basis. This report consists of:

Tasks completed during the week

Tasks scheduled to be taken up for the following week

Any deviation from the planned activities

Any critical constraints that need to be considered immediately, along with suggested alternatives

Deliverables made during the week or being planned for the following fortnight

We propose the client to call a teleconference every week to review the status of the project

Aliment Software Technologies's quality processes lay a lot of emphasis on reviews. This is in conjunction with the philosophy that catching defects during reviews is much more economical and much more effective than during testing. We conduct sever al reviews during the course of the project, for its effective management. These include both internal and external reviews. The client's representative can get involved in the reviews, if required.

To reduce the problems associated with changes, Aliment Software Technologies follows a strict Configuration Management procedure. The procedure identifies the configurable items and the methodology to control changes whenever they occur. Every change desired after freezing of a stage, must be well documented by the initiating party and the approval for change must be obtained from both sides.

Change control is exercised through a Change Request document - which has to be adequatelyreviewed by both the Aliment Software Technologies project manager and by the client - before it is implemented.

A hierarchy of reporting is agreed before a project commences, to handle escalation, in the rare instances that may occur during the lifetime of a project. The Project Manager is responsible for appraising the client's representative on the effects of changes proposed, with information pertaining to the following:

Details of the change

Parts that would be affected by the change

Estimated man-months of effort for incorporating the change

Impact of the change on the project time schedule

Implementation, unit testing, integration testing, etc.