“Explain the formal technical reviews.” It is the question of SMU MBA assignment for Software Engineering (MI0024). It is for students of Sikkim Manipal University with Information System (IS) specialty MBA MI0024. I have already written some assignments of MBA MI0024 for students of SMU - Earned value is a measure of progress, COCOMOL model and Linear Sequential Model.
A formal technical review is a software quality assurance activity performed by software engineers (and others). The objectives of the FTR are (1) to uncover errors in function, logic, or implementation for any representation of the software; (2) to verify that the software under review meets its requirements; (3) to ensure that the software has been represented according to predefined standards; (4) to achieve software that is developed in a uniform manner; and (5) to make projects more manageable. In addition, the FTR serves as a training ground, enabling junior engineers to observe different approaches to software analysis, design, and implementation. The FTR also serves to promote backup and continuity because a number of people become familiar with parts of the software that they may not have otherwise seen.
(1) The review Meeting:
The review meeting is attended by the review leader, all reviewers, and the producer. One of the reviewers takes on the role of the recorder; that is, the individual who records (in writing) all important issues raised during the review. The FTR begins with an introduction of the agenda and a brief introduction by the producer.
(2) Review Reporting and Record Keeping:
The review summary report is a single page form (with possible attachments). It becomes part of the project historical record and may be distributed to the project leader and other interested parties.
(3) Review Guidelines:
Guidelines for the conduct of format technical reviews must be established in advance, distributed to all reviewers, agreed upon, and then followed. A Review that is uncontrolled can often be worse that no review at all.
A formal technical review is a software quality assurance activity performed by software engineers (and others). The objectives of the FTR are (1) to uncover errors in function, logic, or implementation for any representation of the software; (2) to verify that the software under review meets its requirements; (3) to ensure that the software has been represented according to predefined standards; (4) to achieve software that is developed in a uniform manner; and (5) to make projects more manageable. In addition, the FTR serves as a training ground, enabling junior engineers to observe different approaches to software analysis, design, and implementation. The FTR also serves to promote backup and continuity because a number of people become familiar with parts of the software that they may not have otherwise seen.
(1) The review Meeting:
The review meeting is attended by the review leader, all reviewers, and the producer. One of the reviewers takes on the role of the recorder; that is, the individual who records (in writing) all important issues raised during the review. The FTR begins with an introduction of the agenda and a brief introduction by the producer.
(2) Review Reporting and Record Keeping:
The review summary report is a single page form (with possible attachments). It becomes part of the project historical record and may be distributed to the project leader and other interested parties.
(3) Review Guidelines:
Guidelines for the conduct of format technical reviews must be established in advance, distributed to all reviewers, agreed upon, and then followed. A Review that is uncontrolled can often be worse that no review at all.
0 comments:
Post a Comment