|
|
QA Methodology
-
TimelessMIND Quality Assurance Methodology
Quality Assurance Testing is just as important as the development of the code itself. Reviews, walkthrough and testing are done at each stage of the development cycle to ensure the solution is being developed to the superior standards set by TimelessMIND. We execute our testing, using proven methodologies, systematically and strategically to ensure highest quality results. The information below walks you through the methodologies TimelessMIND uses when applying Quality Assurance Practices.
The Methodology used to by TimelessMIND when applying Quality Assurance Practices and testing are as follows:
Determine test Strategy
Obtain Test Resources
Knowledge Transfer
Prepare Basic Understanding Documents
Develop Test Plans
Develop Test Cases & Procedures
Test Cases Review
Execute Tests
Report Defects and return to step 8 as required
Proposal Stage
TimelessMIND works closely with the customer in this stage to define a clear scope of the project that outlines every detail of the work to be done, which testing stages are covered, how many rounds of testing are required, what type of response time will be given by a customer when re-testing is requires. The estimated effort of the project is then calculated by classifying the work units in 3 categories viz. Simple, Medium and Complex. After the classification is done, the efforts are assigned to these units, and other composite activities depending on the understanding of the project.
The responsibly of the Vendor and the Customer will now be defined.
o Information and Material Exchange
o Reviews and Approvals
Post Implementation Support is now decided upon
o Scope of work covered in support
o Response time by us to address any issue
o Cost implication for the support
Contract Stage
Client and Vendor come to terms on Acceptance criteria and procedures
A change control process is defined to handle all change request that present themselves during he project. The process considers
o Impact of change request on current schedule
o Cost implication
o Consideration of how urgently the change is required
Issue Management and Escalation procedures are established to define how any unresolved issues will be handles by either side.
Planning Stage
A detailed schedule is designed. The Schedule consist of all significant milestones to help the customer in keeping track of the project progress. We ensure that several early milestones are defined, and other milestones are evenly distributed throughout the project schedule.
The schedule also identifies resource or information requirements from customer, and also indentifies milestones dependent on such input.
We also identify potential risks and their mitigation plan.
We identify a project Manger / Account Manager as a single point of contact for customer, and also expect a similar identification from the customer.
We define a method to share the progress status of the project , clearly defining who will send the status information, the contents of status information and recipients of the information.
Execution Stage
We understand customers requirements clearly. In addition to the business requirements, the requirements like response time, multi-lingual ability, user interface, fault tolerance, etc. are also captured.
Customer representative is involved in review of requirements to ensure that the requirements are understood by us correctly and completely.
After the requirements are understood, we design the Acceptance Test Plan and System Test Plan. If the glass box testing is to be done then we expect the design documents to be provided to us, and accordingly we make Unit Test and Integration Test Plans.
The Test Plans are reviewed by the competent team selected from within the organization. The customer can also participate in this review if desired.
Usually we expect customer to provide us the real life data for doing the effective testing. However, if such data is not available we create out own test data corresponding to all Test Plans.
The Test Log is created for all the Testing activity. All the errors are compiled and communicated to the customer as a result of the activity.
A regression testing is done, if software needs to be re-tested after the errors are fixed.
We keep customer posted on the progress status with respect to the schedule on regular basis.
All the identified risks and their status is reviewed regularly. Any new risks are identified along with mitigation plan.
The project may get delayed due to various reasons. We keep the customer informed and do a realistic re-planning for further tracking.
-
|
