At CCS, quality is our highest priority.
From our working environment, to our client's experience
with every project to the final software delivered, our
endeavor is to provide quality. The primary objective of
CCS's QA system is to embed quality into all our processes.
Our QA processes are proactive in nature - aimed at identifying
problems during software development, rather than identifying
them during the verification process and then having to
correct them.
We ensure at all points in the
process, that the client has visibility into where his
project stands - whether requirements have been tested
and satisfied, tests have been executed, or defects have
been found and resolved.
CCS QA methodology:
The QA methodology begins with the
requirements gathering phase . This process is carefully
managed by a Project Manager and also includes a Business
Analyst working closely with the client. Herein, our testing
team carefully and thoroughly documents all project requirements,
identifying potential risk areas and possible contingency
plans.
Once project requirements are finalized,
we perform systems analysis and create detailed specifications.
The QA team maps the requirements document to the specifications,
thereby ensuring that all functionality is addressed and
that the software we have specified is exactly what the
client desires.
This is followed by detailed test
plans - including use cases and user scenarios, they are
created and reviewed by our team as well as by the client.
Stringent quality checks are performed by preparing checklists
at various phases of the Development Life Cycle.
We provide detailed reports as
a result of our testing, ensuring all problems and issues
are corrected and verified immediately.
CCS QA Process Diagram

QA Tasks and Activities:
We conduct Walkthroughs, Inspections and Reviews as part
of CCS's QA tasks and activities.
Testing Approaches:
All testing is done from the point of view of the user.
It is aimed at finding and correcting bugs such as incorrect
functions, interface problems, and database errors. As
a standard practice, we use the black box testing approach.
QA TOOLS: The QA tools
used by CCS help developers in identifying errors and anomalies
during the different phases of the software design life.
They include: