To fulfill our goal of self-evident quality, we constantly improve our deliverables to match the increasing
expectations of our customers.
KIPL follows the quality standards established by the Capability Maturity Model created at the Software
Engineering Institute of Carnegie Mellon University and by the International Standards Organization (ISO).
KIPL has already taken initiative towards achieving SEI - CMM certification.
Our aim is to provide quantifiable and consistent results through automated processes that have been
tested over time.
| Testing Tools We Are Using: |
Team Foundation integrated Testing Tools, Win Runner & Load Runner, Rational Robot & Rational Purify,
Web Load, and QTP.
Objective |
Indicator |
Foster a team approach to
defect prevention and problem
solving, to develop and achieve
Quality Improvement Goals. |
We implement the Software Quality Assurance (SQA) that addresses
the quality assurance needs at every phase of the development cycle
that includes the following elements:
Test Plan and Test Cases - We develop a complete testing plan based
on the requirements. The test plan includes unit, integration and
system testing. The test plan includes all the test cases that typically
cover functionality, error handling, performance, scalability, and fail
over, among other required tests. The test plan and test cases are
validated with the client during the early stages of a project, and are
refined and enhanced during the downstream activities (detailed
design and coding).
Traceability Matrix - During the software lifecycle we trace the
requirements to the design components, to the code modules, and to
the test cases. This enables us to track changes to the requirements
and to validate the test plan covers all requirements and all design
elements.
Peer reviews of designs and code - Depending on the size and duration
of a project, we conduct design and code reviews with architects and
engineers from outside the project. These reviews provide an
opportunity for valuable feedback and independent perspective.
Acceptance Plan - At the beginning of each iteration of a project, we
develop a detailed acceptance plan that describes all the expected
deliverables during or at the end of the iteration. |
Lay emphasis on proper
understanding of the
requirements. |
Every SRS Document would be approved by customer before
proceeding with the next stage of SDLC |
Ensure conformance of our
products and services to their
specifications and our
standards. |
We would obtain a sign-off from the customer after implementation of
the project. |
Provide defect-free software
products to satisfy client
requirements |
KIPL uses the latest testing tools to make sure that the quality of your
delivery is not compromised other than focusing only on the short
completion time. Our software testing tools are tailor made to maintain
top quality software that is high on performance, user friendliness and
stability. |
Strive for complete
understanding of our
customers' application
requirements. |
We typically involve a lead quality engineer in the early phases of a
project to participate in requirements elicitation and analysis, to ensure
that our quality assurance team understands the business objectives
and the detailed requirements. |
Continuously improve our
processes to increase efficiency
and client satisfaction. |
The KIPL QA team constantly keeps track of the latest coding
standards, best coding practice, documentation standards and quality
assurance to give you quality software for your business requirements
without failing to meet deadlines |
Review and renew this Quality
Policy on a regular basis. |
As a company, we are committed to continuous improvement in the
quality of all of our Products, Services, and Operations. |
|
