Duration: 7 hours |  List Price: USD 120 |  Delivery Mode: eLearning

Software products are built using a software process, and errors get introduced during the process for various reasons. The errors that are not detected and fixed during the software process reach customers and are called ‘defects’. Defects are often costlier to fix than errors and also damage the developer’s reputation. Therefore, it is necessary to reduce the errors in the end products.

In order to deliver products of good quality, we need ‘quality filters’ that can be used to detect errors. Formal technical reviews (FTRs) are powerful quality filters.

Formal Technical Reviews course includes:

• Formal Technical Reviews as a Quality Filter
• FTR Types along a Formality Spectrum
• Steps in a Generic FTR
• Roles in a Generic FTR
• Conducting Effective FTRs

This course has been co-authored by the internationally recognized consultant and authority on software engineering—Dr. Roger S. Pressman.

Course Benefits

This course will enable you to:

• Explain the importance of reviews as a quality filter.
• Discuss the types of reviews along a formality spectrum.
• Describe the steps of a review process.
• Discuss the roles of the people involved in a review process.
• Explain how to conduct effective FTRs.

You receive a certificate of completion after successfully completing this course.

Content Brief

In order to deliver products of good quality, we need ‘quality filters’ that can be used to detect errors. Formal technical reviews (FTRs) are powerful quality filters. They use a structured meeting, known as the review meeting, in which a review team assesses a work product technically. Unlike testing, which can only be done once the source code is ready, FTRs can be conducted for any type of work product during any phase of the software process.

There are many review types under the broad category of FTRs. These vary in the degree of formality - walkthroughs and inspections being the most formal and casual meetings being the least formal. The more formal the review type, the more effective it is in finding errors.

While various review types differ in their ‘exact’ activities and roles defined, there are some common steps and roles in a generic FTR. The common steps are:

Step 1: Pre-review meeting
Step 2: Review meeting
Step 3: Post review meeting

The generic roles are the roles of the review leader, the producer, the recorder, and the reviewers.

Some guidelines that can help us derive the best out of FTRs include:

• Planning for project reviews
• Training reviewers on how to participate in reviews
• Ensuring that the review meeting is effective
• Using review data to see how the review process can be further refined

Target Audience: Developers, Testers, System Analyst, Team Leaders, Project Manager, Business Analyst, EPG Members

Prerequisites:   SE301: Basic Concepts of Software Quality   SE302: Formal Technical Reviews