软件检查和技术审查之间的区别

1.技术审查：
在审查中，即也称为技术审查，工作产品由除实际生产者以外的几个人特别检查是否存在缺陷。在此，工作产品被定义为在软件开发的需求、设计、编码或测试阶段创建的必不可少的重要可交付成果。

2. 软件检查：
这些被认为是最正式的审查类型。这些通常在工件满足预定义的退出标准(如实现特定要求)后进行。

软件检查和技术审查之间的区别：

Issue	Technical Review	Software Inspection
Objective	It usually determines the suitability i.e. the quality of being right of a work product for its intended use.	It usually determines the suitability i.e. the quality of being right of a work product for its intended use. But beyond that, it also searches for anomalies i.e. unexpected results by examination through educated inspectors.
Roles	In technical review, minimum of two persons are required for work. Each of them can perform different roles. Since the scope is different additional persons like customer representatives or management representatives can participate, but this is never regarded as a role in the process.	In inspection, additional roles that are required are the Author and the Reader. The roles are separated explicitly and can not be assumed by one person.
Input	The inputs are mostly similar to that of the inspection. It is needed to be observed that checklists are not mentioned i.e. not required.	Inspection reporting forms, Hardware performance data, Inspection checklists, all of these are additional inputs and some of these inputs are optional also. The reporting form and inspection checklist are mandatory but hardware product specification is optional. The wording of the standard usually suggests that checklists are not mandatory, but a table in the appendix of standard makes them mandatory.
Output	Action Item List and a record of the technical review are the only output.	Formal inspection report, formal defect summary, and a defect list along with classified defects are the outputs. The main emphasis is only on providing a standard output of errors that are found which also might allow statistical evaluations.
Entry Criteria for the Meeting	In this, no special criteria are mentioned.	In this, it is explicitly stated that the meeting usually needed to be re-scheduled if the inspection leader somehow finds out that the participants are not really prepared well.
Meeting	Described rules of a review meeting are usually kept.	Defined roles need to be kept explicitly. The material will be presented by the reader and not the author. The other roles are also needed to kept formally.
Outcome of the Meeting	Defined review report is being generated as the outcome of the meeting.	The decision is needed to be made simply to accept the work product, close the inspection, but usually require a rework, reject the work product, and require a re-inspection after the rework is done at the end of the inspection.