Quality Management System

Quality Management System

The QMS necessary to meet the requirements of ISO 9001 is documented in the company’s Quality Manual. The organization of the QMS is in two separate volumes. Volume 1 covers Level One, whereas volume 2 covers levels Two and Three. Any changes in the Volume 1 will result in the release of a new version of the Quality Manual, whereas changes or revisions in the Volume 2 will be reflected in the revision history maintained for each section in the Procedures manual.

Structure of Quality System Documentation is as given under:

Customer Requirement Specification

As a part of the software development documentation, the customers’ requirement specifications are subject to Document control and Configuration Management. Customers’ requirements stated in the contracts by the marketing department are documented and reviewed for completeness and clarity. Head (Business Development) is responsible for ensuring that customers’ requirements are complete before they are passed on Head Quality & Operations for execution. The marketing department works in close liaison with the Technical/Quality departments and the customer for preparing the customers’ requirement specifications.

In the process of documenting customers’ requirement, Ramsoft pays special attention to the assignments of persons (on both sides) responsible for:

  • Establishing the customers’ requirements specifications
  • Methods for agreeing on requirements and approving changes
  • Efforts to prevent misunderstandings such as definition of terms, inclusions, exclusions, background explanations, etc.
  • Recording and reviewing discussions on both sides

Company, Customer Co-operation

Ramsoft will make every effort in encouraging the customer to interact with the company through the establishment of a customer representative who is responsible for dealing with the customer on all contractual matters. Likewise Ramsoft expects all its customers to cooperate with the company in providing all necessary information in a timely manner and in resolving pending issues with respect to software development and service activities of the customer.

Joint Reviews

Regular joint reviews involving Ramsoft software developers and customers’ representatives will cover the following areas :

  • Conformance of software to customer requirements and specifications.
  • Verification results.
  • Acceptance test results. All reviews are documented and retained for the duration of the project. Archives are available for a specified duration of time.

Conduct of Reviews

If applicable and called for in the proposal/contract, joint reviews are conducted either at the customer’s site or at the premises of Ramsoft, the communication of which is done through an appropriate media. Minutes of such meetings are documented and retained for the duration of the project.

Quality Planning

Ramsoft has proactive approach to quality and has made quality as an inseparable part of design and development. The process is imbibed into the SDLC chosen so that it is a part of the deliverables at the end of each phase of a project. The quality planning includes the following :

a)Quantification of quality objectives in measurable terms (whenever possible)

b) Identification and planning of tests, verification and validation activities to be carried out including schedules, resources and approval authorities

c)Laying down specific responsibilities for quality audits such as: · Conduct of tests · Configuration management and change control · Defect control and corrective action

d) Software status report

e) Incorporation of correction

f) Quality system documentation

g) Identification of proper skills and requirements of training, if any

h) Identification of applicable standards Quality plan document compliments the adequacy of all items of development plan document.

Validation In order to ensure that the software has been developed as specified in the contract, the software is validated as a complete product before delivery. Validation results are reviewed and recorded.

Field Testing

If field-testing is specified in the contract, such testing of the developed software is carried out with data provided by the customer.

Support Organization

Whenever necessary, an organization where the maintenance activities can be carried out, is identified with the help of representatives of Ramsoft and its customers. All requisite facilities and resources for maintenance activities are identified and their availability ensured before the start of maintenance through the support organization.

Software Change Under Maintenance

All changes to software carried out during maintenance are made according to a plan. These plans follow guidelines identical to those of the original software. Any changes in specifications during maintenance are documented in accordance with the procedures for document control and configuration management.

Configuration Management

Ramsoft’s Configuration Management plan pertains to changes in software being developed, and has the following objectives :

a) Control issue of all successive development stages of software components, from the time they are initially approved for registration on the configuration baseline.

b)Provide traceability of changes and enable reversibility of all changes that are performed on the baseline components from initial specifications to the delivered item.

c) Provide status information for management, ensure reliable storage, handling and supply of project deliverables.

Tools and Techniques

Ramsoft will identify, monitor, evaluate and improve tools and techniques and methodologies that may be applicable for building a software development environment of the company and include it in the project planning.

Ramsoft will appraise its customer about any improvement in tools that that may be found necessary for fulfilling contractual requirements or due to the complexity of the product specifications. The techniques adopted for using tools are periodically reviewed and whenever any improvement is envisaged, the same is communicated to the customer for their benefit, before their use in development. All Tools are thoroughly evaluated for its suitability and reliability, before being included in the project plan.