本标准提供了系统软件评审的最低可接受要求，其中？系统学？包括以下属性: --团队参与 --审查的记录结果 --进行审查的书面程序 不符合本标准要求的审查被视为非系统性审查。本标准无意阻止或禁止使用非系统性审查。 本标准包括以下五种审查的定义、要求和程序: a） 管理评审 b） 技术审查 c） 检查 d） 穿行 e） 审计 本标准未规定进行具体审查的必要性；这种需求由其他软件工程标准或本地程序定义。本标准提供了适用于整个软件生命周期内软件开发产品评审的定义、要求和程序。本标准的使用者应详细说明本标准适用的时间和地点，以及与本标准的任何预期偏差。 本标准可与其他软件工程标准一起使用，这些标准可确定要评审的产品、评审的时间和评审的必要性。 本标准与IEEE Std 1012-2004[B6]密切一致，但也可与IEEE Std 1074-2006[B11]、IEEE Std 730-2002[B2]、IEEE Std 12207-2008[B15]和其他标准一起使用。一个有用的模型是考虑IEEE STD 1023-2008作为一个子程序到其他标准。因此，如果使用IEEE Std 1012-2004[B6]来执行验证和确认过程，则可以遵循IEEE Std 1012-2004[B6]中的程序，直到遇到执行特定审查的指示为止。到那时，IEEE Std 1028-2008将是一个？卡莱达？使用本文所述的特定审查类型进行审查。 一旦审查完成，IEEE Std 1012-2004[B6]将成为？回到托亚？用于处置审查结果和IEEE Std 1012-2004[B6]要求的任何额外行动。 本标准也可用作软件评审和审核程序的独立定义。在这种情况下，本地管理层必须确定实际软件评审和审核之前和之后的事件。 在这个模型中，软件产品的需求和质量属性是？参数输入？是由a强加的吗？呼叫者 A.评审结束后，评审输出为？凯莉达？去a？卡莱拉？行动起来。评审输出通常包括异常列表和行动项目列表；异常和行动项目的解决由a负责？呼叫者A.

This standard provides minimum acceptable requirements for systematic software reviews, where "systematic" includes the following attributes: -- Team participation -- Documented results of the review -- Documented procedures for conducting the review Reviews that do not meet the requirements of this standard are considered to be non-systematic reviews. The standard is not intended to discourage or prohibit the use of non-systematic reviews. The definitions, requirements, and procedures for the following five types of reviews are included within this standard: a) Management reviews b) Technical reviews c) Inspections d) Walk-throughs e) Audits This standard does not establish the need to conduct specific reviews; that need is defined by other software engineering standards or by local procedures. This standard provides definitions, requirements, and procedures that are applicable to the reviews of software development products throughout the software life cycle. Users of this standard shall specify where and when this standard applies and any intended deviations from this standard. This standard may be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity of reviews. This standard is closely aligned with IEEE Std 1012-2004 [B6], but it can also be used with IEEE Std 1074-2006 [B11], IEEE Std 730-2002 [B2], IEEE Std 12207-2008 [B15], and other standards. A useful model is to consider IEEE Std 1028-2008 as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 [B6] were used to carry out the verification and validation process, the procedure in IEEE Std 1012-2004 [B6] could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-2008 would be "called" to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-2004 [B6] would be "returned to" for disposition of the results of the review and any additional action required by IEEE Std 1012-2004 [B6]. This standard may also be used as a stand-alone definition of software review and audit procedures. In this case, local management must determine the events that precede and follow the actual software reviews and audits. In this model, requirements and quality attributes for the software product are "parameter inputs" to the review and are imposed by the "caller." When the review is finished, the review outputs are "returned" to the "caller" for action. Review outputs typically include anomaly lists and action item lists; the resolution of the anomalies and action items are the responsibility of the "caller."