In the case of a health care software system, review the project could be a good start to improve the software development process. Reviews can increase the quality of the software product, reduce rework and blind efforts, it exams the produced product for defects by individuals who are not involved with developing of the product itself, and it increases the reliability of the product, improves the schedule performance. The main objective of reviewing software is to discover all defects , ensure the work product has meet the requirements and improve the software development process.
There are few type of reviews such as formal technical reviews, walkthroughs and inspections etc. To begin with, software inspections are a formal engineering process for finding and correcting defects in the software. There are several defined role that involved in the inspection:
Moderator : Who is responsible for making sure that all the processes are performed correctly and completely. The responsibilities include :
Inspector : Who is a trained and experienced individual, and responsible for analysing and identifying defect from the work product.
Author : The person who developed the work product, the creator of the product and responsible for updating work product after inspection .
Reader : Who is responsible to ensure the meeting is running on track by reading out the logical unit.
Formal process, checklist and measurements are typical attributes in inspection method. A inspection is a visual examination of a software product to detect and identify software anomalies, including errors and deviations from standards and specifications. Inspections are often used to establish additional properties such as portability and adherence to standards. A reviewer may be supplied with a checklist of items, or he or she may only be informed of the desired property. Inspections are also used to check for particular errors that have been prevalent in the past. [3]
A formal inspection consists of several activities:
References:
[3] ONLINEMCA, Formal Technical review http://onlinemca.com/mca_course/kurukshetra_university/semester5/testing/ftr.php (Accesse on 15/03/2015)
[4] Karl, E, Wiegers, Improving quality through software inspection http://www.processimpact.com/articles/inspects.html (Accesse on 15/03/2015)
There are few type of reviews such as formal technical reviews, walkthroughs and inspections etc. To begin with, software inspections are a formal engineering process for finding and correcting defects in the software. There are several defined role that involved in the inspection:
Moderator : Who is responsible for making sure that all the processes are performed correctly and completely. The responsibilities include :
- Schedule meetings, ensure participants are provided with enough materials
- Verify if the entry criteria are met.
- Keep the meeting on track
- Assemble an effective inspection team
- Verify the work products readiness for inspection
Inspector : Who is a trained and experienced individual, and responsible for analysing and identifying defect from the work product.
Author : The person who developed the work product, the creator of the product and responsible for updating work product after inspection .
Reader : Who is responsible to ensure the meeting is running on track by reading out the logical unit.
Formal process, checklist and measurements are typical attributes in inspection method. A inspection is a visual examination of a software product to detect and identify software anomalies, including errors and deviations from standards and specifications. Inspections are often used to establish additional properties such as portability and adherence to standards. A reviewer may be supplied with a checklist of items, or he or she may only be informed of the desired property. Inspections are also used to check for particular errors that have been prevalent in the past. [3]
A formal inspection consists of several activities:
- Planning - The moderator selects the inspection team, obtains materials to be inspected from the author, and distributes them and any other relevant documents to the inspection team in advance.
- Overview meeting - The author describes the background of the work product. It can be skipped if this information is already known to the other participants.
- Preparation - Participants are responsible for examining the work product prior to the actual inspection meeting, identify any defects or issues to be raised. The work product should also be compared with any specification documents to ensure the correctness.
- Inspection meeting - During this session, the reader is responsible to read out the work product, and the inspector should point out every defect during the process.
- Rework - The author is responsible for resolving all issues raised during the inspection. This does not necessarily mean making every change that was suggested, but an explicit decision must be made about how each issue or defect will be dealt with.
- Follow-up - To verify that the necessary rework has been performed properly, the moderator is responsible for following up with the author. If a significant fraction (10 percent, for instance ) of the work product was modified, an additional inspection may be required. This is the final gate through which the product must pass in order for the inspection to be completed. You may wish to define explicit exit criteria for completing an inspection. These criteria might require that all defects are corrected and issues resolved, or that uncorrected defects are properly documented in a defect tracking system.[4]
References:
[3] ONLINEMCA, Formal Technical review http://onlinemca.com/mca_course/kurukshetra_university/semester5/testing/ftr.php (Accesse on 15/03/2015)
[4] Karl, E, Wiegers, Improving quality through software inspection http://www.processimpact.com/articles/inspects.html (Accesse on 15/03/2015)