• About WordPress
    • WordPress.org
    • Documentation
    • Support
    • Feedback
  • Log In
  • Register
  • Home
  • Courses
  • Past Paper
  • FYP
  • Interview Questions
  • University Events
  • Contact
  • Quiz & Assignment
Cuitutorial
  • Home
  • Courses
  • Past Paper
  • FYP
  • Interview Questions
  • University Events
  • Contact
  • Quiz & Assignment

Software Engineering II

Home » Blog » Software Reviews

Software Reviews

  • Posted by saqib
  • Categories Software Engineering II
  • Date November 5, 2022
  • Comments 0 comment

What Are Reviews?

  • a meeting conducted by technical people for technical people
  • a technical assessment of a work product created during the software engineering process
  • a software quality assurance mechanism
  • Serves as a training ground for junior software engineers to observe different approaches to software analysis, design, and construction

Purpose of Reviews

  • Include the formal technical review (also called a walkthrough or inspection)

–Acts as the most effective SQA filter

–Conducted by software engineers for software engineers

–Effectively uncovers errors and improves software quality

–Has been shown to be up to 75% effective in uncovering design flaws

  • Require the software engineers to expend time and effort, and the organization to cover the costs

Formal Technical Review (FTR)

  • Objectives

–To uncover errors in function, logic, or implementation for any representation of the software

–To verify that the software under review meets its requirements

–To ensure that the software has been represented according to predefined standards

–To make projects more manageable

The Players

Conducting the Review

The FTR Meeting

  • Has the following constraints

–From 3-5 people should be involved

–

–Advance preparation (i.e., reading) should occur for each participant but should require no more than two hours a piece and involve only a small subset of components

–

–The duration of the meeting should be less than two hours

–

  • Focuses on a specific work product (a software requirements specification, a detailed design, a source code listing)
  • Activities before the meeting

–The producer informs the project manager that a work product is complete and ready for review

–

–The project manager contacts a review leader, who evaluates the product for readiness, generates copies of product materials, and distributes them to the reviewers for advance preparation

–

–Each reviewer spends one to two hours reviewing the product and making notes before the actual review meeting

–

–The review leader establishes an agenda for the review meeting and schedules the time and location

  • Activities during the meeting

–The meeting is attended by the review leader, all reviewers, and the producer

–

–One of the reviewers also serves as the recorder for all issues and decisions concerning the product

–

–After a brief introduction by the review leader, the producer proceeds to “walk through” the work product while reviewers ask questions and raise issues

–

–The recorder notes any valid problems or errors that are discovered; no time or effort is spent in this meeting to solve any of these problems or errors

–

The FTR Meeting

  • Activities at the conclusion of the meeting

–All attendees must decide whether to

  • Accept the product without further modification
  • Reject the product due to severe errors (After these errors are corrected, another review will then occur)
  • Accept the product provisionally (Minor errors need to be corrected but no additional review is required)

–All attendees then complete a sign-off in which they indicate that they took part in the review and that they concur with the findings

  • Activities following the meeting

–The recorder produces a list of review issues that

–

  • Identifies problem areas within the product
  • Serves as an action item checklist to guide the producer in making corrections

–The recorder includes the list in an FTR summary report

  • This one to two-page report describes what was reviewed, who reviewed it, and what were the findings and conclusions

–The review leader follows up on the findings to ensure that the producer makes the requested corrections

FTR Guidelines

  • Share:
author avatar
saqib

Previous post

Software Quality Assurance
November 5, 2022

Next post

Package Management in Linux
November 6, 2022

You may also like

Software Engineering II Topics
6 November, 2022

Software Engineering II Course Content component-level-design Component Based Software Engineering Software Design Patterns User Interface Design Software Quality Assurance Software Reviews

Software Quality Assurance
5 November, 2022

The need for comprehensive SQ Requirements “our new sales information system seems okay, the invoices are correct, the inventory records are correct, the discounts granted to our clients exactly follow our very complicated discount policy, but our new sales information …

User Interface Design
5 November, 2022

User Interface Design-Software egineering User Interface Design Interface Design Easy to learn ? Easy to use? Easy to understand? Typical Design Errors Lack of consistency Too much memorization No guidance / help No context sensitivity Poor response Unfriendly Golden Rules …

Leave A Reply Cancel reply

You must be logged in to post a comment.

admin@cuitutorial.com
Facebook-f Twitter Youtube Linkedin Instagram Stack-overflow Pinterest Github Quora Whatsapp
Courses
  • All Courses
  • Past Paper
  • Final year projects
  • Interview Questions
  • Contact
Important Pages
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
Links
  • University Events
  • Team
Education & learning platform for All Computer science subjects
Final year projects
Past Paper
Interview questions
Programming, C/C++, Asp.net/MVC. Android, MySql, Jquery, Ajax, javascript, Php, Html5, Bootstrap4.
NTS, GAT, PPSC, FPSC

Copyright © 2021 | Cuitutorial