Software Reviews (Formal Technical Reviews)
Software Reviews is the important topic of the Software Engineering. It is the Important subject of the Computer Science & Technological field.
A formal technical review (FTR) is a software quality control activity performed by software engineers (and others).
The objectives of an FTR are:
- To uncover errors in function, logic, or implementation for any representation of the software.
- Moreover, To verify that the software under review meets its requirements.
- To ensure that the software has represented according to predefined standards.
- Also, To achieve software that developed in a uniform manner.
- To make projects more manageable.
Review Reporting and Record Keeping
- During the FTR, a reviewer (the recorder) actively records all issues that have raised.
- These are summarized at the end of the review meeting, and a review issues list produced. In addition, a formal technical review summary report completed.
- Guidelines for conducting formal technical reviews must establish in advance, distributed to all reviewers, agreed upon, and then followed.
- A review that un-controlled can often be worse than no review at all.
- Review the product, not the producer.
- Set an agenda and maintain it.
- Limit debate and denial:
- Moreover, Speak problem areas, but don’t attempt to solve every problem noted.
- Take written notes.
- Limit the number of participants and insist upon advance preparation.
- Develop a checklist for each product that likely to review
- Moreover, Allocate resources and schedule time for FTRs
- Conduct meaningful training for all reviewers.
- Review your early reviews.
- In an ideal setting, every software engineering work product would undergo a formal technical review.
- moreover, In the real world of software projects, resources limited and time is short.
- As a consequence, reviews often skipped, even though their value as a quality control mechanism recognized.