Technical Review

August 23, 2016

---

What is Technical Review?

It is a form of static testing, which is used to evaluate a software system, using the white-box testing approach, i.e. the internal structure of an application, such as code, program, etc., is being examined, through studying and reviewing the technical documents. It is a defect detection activity. Instead of, testing the actual software system as a product, the technical review approach, involves the examination of various technical documented artifacts, used in the development of a software application, to evaluate the working of the product, as per the standards and specified requirements. These technical documents may include programming source code, software design document, use cases, etc.

The basic purpose of carrying out the technical review, is to verify and validate the requirements and specifications, implemented in the software application, against, what is specified in the software requirement specification (SRS). It is used to locate discrepancies or deviation or defects, prevailed in the design, requirements, specifications, use cases, test cases and other types of documentation work. Further, it may help in the detection of bugs and defects, at an early stage of the development lifecycle, thereby saving precious time and efforts, of an organization.

What is the necessity of a technical review, instead of testing activities?

Owing to benefits and solutions, delivered through technical review process, it has become an essential component of a software testing phase. Some of them are:

• Exhaustive testing of a whole product or the programming code is not possible, which is also an underlying principle of software testing. Therefore, technical review, may seems to be a best alternative, to exhaustive type of testing.
• Monitoring, reviewing and controlling the deliverables, at each point of the software testing lifecycle, including entry and exit criteria, may help in visualizing the progress status, and accordingly, managing and directing the software development process, in a particular or desired direction.
• Outcomes of technical review, includes variant types of feedback, opinion, solution, recommendation, alternatives, suggestion, issued that needs to addressed, and many such things, from each different participant, which may subsequently, provides numerous ways and approaches, to enhance the software product quality and its development process.
• It is also a type of testing, which may helps in saving time and efforts, during the actual test execution on a software product, by identifying bugs and defects, in a documentation work, at an early stage.
• Further, these reviews, acts as a guide or a knowledge source, for the participants, to have a better understanding of the developed software product, through its technical content.

Who participates in the technical review process?

Technical review is a less formal type of review. However, it may be carried out, in an informal or a very formal way. It, may involve the participation of technical professionals, and does not require the involvement of management personnel. However, management professional, may participate, in it, for the purpose of reviewing and understanding the issues, pertaining to the management team. These technical professionals/staffs may include software designer, programmer, database architects, etc.

In addition, a trained and expertise, technical personnel other than the Software Author, is deployed, to acts a moderator, to lead and manage the process of technical review. Apart from the moderator, it may also include:

• Decision Maker: for which technical review is conducted, so as to take appropriate decision.
• Recorder:Engaged, for the purpose of writing and documenting the outcomes of a technical review.

Further, a user or a customer or a client's representative, may also take part in the technical review of the process.

In view of the above, it may be stated that a technical review of a software product is a cost-effective and a time saving solution, which may accompany the actual testing activities, to carry out the process, in a best possible manner.