Various steps will be taken to ensure that the designed application works as per the accepted requirements/specifications. Once the requirements have been finalized, they will be documented and signed off by CLIENT authorized scope changes will be formalized through the change control process.
The testing team will test independently all built code. The testing process will involve the active participation of CLIENT team. We invite CLIENT project team members to scrutinize the development process at any point within our methodology.
Organization for Quality Assurance
The Quality Assurance team within the production support organisation will consist of a Quality Assurance Lead and a team of Reviewers. The size of the Quality Assurance team will be approximately 20-30% of the size of the production support team.The standard ANVIN’s Checklists, Review templates will be used in QA.
The work products that would be subjected to quality assurance process are:
Statement of Work
Software Project management Plan
Work Product Standards
Source Code including include files, text files, scripts, etc.
Test Plan, Test Data and Test Results
All manuals and Guides
The activities that would be performed by the Quality Assurance Team are:
Review of Standards and Guidelines
Review of procedures
Review of Source Code and Technical Documentation
Preparation and review of test plan, test data and test results
Publish Productivity (LOC/Person hour)
Publish defect detection rate (bugs/KL)
The purpose of ANVIN Software Configuration Management (SCM) is to establish and maintain the integrity of the work products throughout the life cycle of the project. The SCM activities will be planned and executed at a very early stage of the Software Project.
Software Configuration Management involves identifying the configuration of the software (i.e., selected software work products and their descriptions) at given points in time, systematically controlling changes to the configuration, and maintaining the integrity and traceability of the configuration throughout the software life cycle. The work products placed under software configuration management include the software that will be delivered to CLIENT (e.g. unit test plans, system integration test plans, unit tested code, Deployment descriptors if any)
Our offshore development environment can be suitably configured to manage the development of code during development and to ensure proper delivery of code to CLIENT on-site development environment.
Risk Management describes the processes concerned with identifying, analyzing, and responding to project risk. Risk management is a formalized way to identify, analyze, address, and potentially eliminate problems within a project before they affect the outcome of the project, or before the risk becomes unmanageable.
ANVIN will use the Continuous Risk Management model developed by Software Engineering Institute.
This will allow us to:
Assess continuously what could go wrong (risks)
Determine what risks are important to deal with
Implement strategies to deal with those risks
The objective is to control the risks associated with those cost, schedule, functional, and technical aspects of the project
The following table describes the various activities in the ANVIN risk management approach
Search for and locate risks before they become problems
Transform risk data into decision-making information. Evaluate impact, probability and timeframe, classify and prioritize risks
Translate risk information into decisions and mitigating actions (both present and future) and implement those actions
Monitor risk indicators and mitigation plans
Correct for deviation from risk mitigation plans
Provide information and feedback internal and external to the project on the risk activities, current risks, and emerging risks
Note:Communication happens throughout all the functions of risk management