Quality Policy

We at RCS strive to deliver simple solutions through innovation that exceed customer expectations, through an organizational culture that encourages continuous improvement of the Quality management system and individual commitment to quality.

Quality Objectives

• Delighting the Customers in terms of quality and performance of solutions
• Continuous improvement of our processes and systems
• Timely deliveries to meet customer requirements
• Constantly upgrade the skills of our employees to serve our customers better

Quality Standards

RCS has highly reputed Customer base which are the leaders in the respective Industry. To meet Quality statndars of these customers, we follows well defined   standard process.  The processes RCS follows for requirements study, design, coding, testing and support are in accordance with the global Industry Standards. The Software Quality Assurance (SQA) group is responsible for monitoring and improving quality processes and systems. The SQA monitors the quality processes followed by various project teams at RCS.

Testing Methodology

The quality process starts from the project initiation stage. The project plan is prepared by the Project Manager and is reviewed by the Quality Assurance team, to ensure that the plan follows RCS' standard process. The test engineer designs a test plan for the project. This contains the testing objectives for the project, the testing approach adopted, success/failure criteria for tests, test deliverables, pre-requisites for testing and the testing schedule, which is dependent on project milestones. The developers prepare unit test cases before the start of application development.

On completion of coding, peer-to-peer code review is done. After correction of faults observed in the peer-to-peer code review, the application is tested against the unit test cases. Subsequent to successful unit testing, the application is submitted to the testing team for system level testing. The testing team designs test cases and prepares test case documents for module level, integration and acceptance testing. This occurs in parallel with the development team's coding work.