检查和演练之间的区别

1.演练：
演练是一种进行非正式小组/个人审查的方法。在演练中，作者在非正式会议上向同事或主管描述和解释工作产品，以获取反馈。在此，检查所提出的针对工作产品的解决方案的有效性。

当设计在纸上而不是转换时，进行更改的成本较低。演练是一种静态的质量保证方法。演练是非正式会议，但有目的。

2.检验：
检查被定义为正式，严格，深入的小组审查，旨在识别出尽可能靠近问题源头的问题。检查可以提高软件产品的可靠性，可用性和可维护性。

可以检查在软件开发过程中产生的任何可读内容。检查可以与结构化的系统测试结合使用，以提供强大的工具来创建无缺陷程序。

检查活动遵循指定的流程，参与者扮演着明确定义的角色。
一个检查小组由三到八名成员组成，他们分别担任主持人，作者，读者，记录员和检查员的角色。

例如，设计人员可以在代码检查期间充当检查员，而质量保证代表可以充当标准执行者。

检验过程中的阶段：

• 计划：检查由主持人计划。
• 概述会议：作者描述工作产品的背景。
• 准备：每个检查员检查工作产品以识别可能的缺陷。
• 检验会议：在这次会议中，读者逐部分阅读工作产品，检验员指出每个部分的缺陷。
• 返工：作者根据检查会议的行动计划对工作产品进行更改。
• 后续行动：检查作者所做的更改，以确保所有内容均正确无误。

检查和演练之间的区别：

S.No.	Inspection	Walkthrough
1.	It is formal.	It is informal.
2.	Initiated by project team.	Initiated by author.
3.	A group of relevant persons from different departments participate in the inspection.	Usually team members of the same project take participation in the walkthrough. Author himself acts walkthrough leader.
4.	Checklist is used to find faults.	No checklist is used in the walkthrough.
5.	Inspection processes includes overview, preparation, inspection, and rework and follow up.	Walkthrough process includes overview, little or no preparation, little or no preparation examination (actual walkthrough meeting), and rework and follow up.
6.	Formalized procedure in each step.	No formalized procedure in the steps.
7.	Inspection takes longer time as list of items in checklist is tracked to completion.	Shorter time is spent on walkthrough as there is no formal checklist used to evaluate program.
8.	Planned meeting with the fixed roles assigned to all the members involved.	Unplanned
9.	Reader reads product code. Everyone inspects it and comes up with detects.	Author reads product code and his teammate comes up with the defects or suggestions.
10.	Recorder records the defects.	Author make a note of defects and suggestions offered by teammate.
11.	Moderator has a role that moderator making sure that the discussions proceed on the productive lines.	Informal, so there is no moderator.