Answer Posted / sa
The QA life cycle starts from project initiation to project
windup if its a development project otherwise QA life cycle
for maintenance will have to take care of every change
requests.For the new change same procedure like
estimation,resourcea,efforts etc are to be taken care of.
the phases of life cycle of Software as per qa activities
are:
1. project Initiation -It includes following:
-Statement of work(SOW)or contract
-Kick-off Minutes of meeting
-Project initiation note
-Resorce tracking sheet
-Estimation
2. Project Planning
-Project Management Plan
-MPP (project plan )
-Risk logs and Issue logs
3. Project Monitoring and control
-Check for Requirement Traceability matrix preperation and
updations
-Reviews of the following-
Requirement documents (SRS)
Design documents
Testplan,test cases
Code
-Baselining of the documnents
-Collection of all Documents in a repository
-Time lines constraint and schedule tracking
-Deliveries and Releases time constraints
4. Configuration Management
-Tracking tool for CM
-Tracking and managing the change requests
-Impact analysis
-logs of change requests
5 Risk Management
-Tracking of Risk logs and issue logs
-Root cause analysis
-alternative solutions
-Mitigation and Contingency plans
6.Project windup
-Prepare windup plan
-Lesson learnt in central repository
-windup report
| Is This Answer Correct ? | 14 Yes | 6 No |
Post New Answer View All Answers
What does the software qa document should include?
What are the key challenges of software testing?
Explain cmm?
Why regression testing is important?
Which institute in hyderabad is good for ETL testing? Please suggest
Explain what is traceability matrix?
How will you manage a team member who is more experienced than yours and what challenges will you face? ( that guy might be technically sound).
Tell me about any quality efforts you have overseen or implemented.
What is difference between ach credit and the normal credit?
What is breadth testing?
What are the common problems with software automation?
Explain the steps for bug cycle?
We have one home page for a web application.It has so many components which are being tested by different teams. If one component testing get delayed but all other components testing is done, can we sign off testing for that home page? If no, what should be done?
How do you define a format of writing a good test case?
What is a ‘use’ case and what does it include?