Verification:
It is the process of confirming that software meets its specifications.It is used to identify the defects in the product early in the life cycle.
Classification:
1. Based on time
2.Based on classes.
1. Based on Time:
• In process review
* During the specific period of the development cycle. Ex : Design phase
* Used to find the defects in the work product and the work process.
* Catches defects early where they are less costly to correct.
* It may occur at any time.
• Phase end/ decision making review/ milestone review
* Review of product or process near the completion of each phase of development.
* Decisions for proceeding with development or based on the cost, schedule, risk, progress, readiness for the next phase.
* Also referred to a milestone review
• Post implementation/ post Morten review
* Review or evaluation of the product that includes planned Vs actual development results and compliance with requirements.
* Used for process improvement of software development.
* Can be held up to 3 to 6 months after implementation.
2. Based on classes:
• Informal (peer reviews)
* Generally one to one meeting.
* No agenda
* Results are not formally reported
* Occur as needed throughout each phase.
• Semi formal
* Facilitated by author(tester).
* Reports are distributed to the participants.
* Possible solutions for defects not discussed.
* Occurs one or more times during a phase.
• Formal
* Facilitated by moderator
* Assisted by recorder
* Meeting are planned in advance.
* Directly dependent on the preparation of participants.
* Held at any time.
Validation:
Its is the process confirming that it meets the users requirement.
It is the process of confirming that software meets its specifications.It is used to identify the defects in the product early in the life cycle.
Classification:
1. Based on time
2.Based on classes.
1. Based on Time:
• In process review
* During the specific period of the development cycle. Ex : Design phase
* Used to find the defects in the work product and the work process.
* Catches defects early where they are less costly to correct.
* It may occur at any time.
• Phase end/ decision making review/ milestone review
* Review of product or process near the completion of each phase of development.
* Decisions for proceeding with development or based on the cost, schedule, risk, progress, readiness for the next phase.
* Also referred to a milestone review
• Post implementation/ post Morten review
* Review or evaluation of the product that includes planned Vs actual development results and compliance with requirements.
* Used for process improvement of software development.
* Can be held up to 3 to 6 months after implementation.
2. Based on classes:
• Informal (peer reviews)
* Generally one to one meeting.
* No agenda
* Results are not formally reported
* Occur as needed throughout each phase.
• Semi formal
* Facilitated by author(tester).
* Reports are distributed to the participants.
* Possible solutions for defects not discussed.
* Occurs one or more times during a phase.
• Formal
* Facilitated by moderator
* Assisted by recorder
* Meeting are planned in advance.
* Directly dependent on the preparation of participants.
* Held at any time.
Validation:
Its is the process confirming that it meets the users requirement.
Post a Comment