Test assessment and risk analysis
- What is the assessment
In the outcome of the formal meeting on software projects (including all stages of documentation, code), etc., presented to the user, customer or staff of the departments of software products for review and approval.
- Purpose of the review
Make the appropriate checks at all stages of software development and testing, in favor of quality software product and process improvement
- The objective of the review
- Requirements Review [software requirements, testing requirements]
- Design Review [outline design, detailed design]
- [Specification] Code code review
- [Test review test plans, test case specification, bug report specification]
- Process review
- Peer Review: the work carried out by the software product as well as peer review, identify defects and correct shortcomings
- Management review: project managers to evaluate, identify process defects, to improve management activities
- Single Review: single assessor to evaluate simple task
- The code checks: Check writing good code, found not complying with coding standards, design issues can not achieve the design requirements, improve code quality
- Review of the general steps
- Develop evaluation plans
- Accreditation Preparation
- Review meeting
- To take action on the assessment results
- Assessment results are tracked to completion
- Submission and archiving
- Mistakes review
- Participants do not understand the review
- Review has not been scheduled into the project plan
- Review meeting becomes a problem Solutions Seminar
- Reviewers focused on non-substantive issues
- Ignore the organizational details
- Meeting time is too long
- Risk analysis process
