IEEE 1028-2008 pdf download IEEE Standard for Software Reviews and Audits
This standard does not establish the need to conduct specific reviews; that need is defined by other softwareengineering standards or by local procedures. This standard provides definitions, requirements,andprocedures that are applicable to the reviews of software development products throughout the software lifecycle. Users of this standard shall specify where and when this standard applies and any intendeddeviations from this standard.
This standard may be used with other software engineeringstandards that determine the products to bereviewed, the timing of reviews, and the necessity of reviews, This standard is closely aligned with1EEE Std 1012M-2004 B6 , but it can also be used with IEEE Std 10747-2006 B111, IEEE Std 730M-2002(B2], IEEE Std 12207.2008 [B15], and other standards. A useful model is to consider EEE Std 1028-2008as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 (B6] were used to carry out theverificaton and validation process, the procedure in 1EEE Std 1012-2004 B6 could be followed until suchtime as instructions to cary out a specific review are encountered. At that point, IEEE Std 1028-2008 wouldbe “called” to carry out the review, using the specific review type described herein. Once the review has beencompleted, IEEE Std 1012-2004 (B6] would be “returned to” for disposition of the results of the review andany additional action required by IEEE Std 012-2004 B6.
This standard may also be used as a stand-alone definition of software review and audit procedures. In thiscase, local management must determine the events that precede and follow the actual software reviews andaudits.
In this model, requirements and quality attributes for the software product are “parameter inputs” to thereview and are imposed by the “caller.When the review is finished, the review outputs are “returned” tothe “caller”for action. Review outputs typically include anomaly lists and action item lists; the resolutionof the anomalies and action items are the responsibility of the “”caller.”
1.2 Purpose
The purpose of this standard is to define systematic reviews and audits applicable to software acquisition.supply, developiment, operation, and maintenance. This standard describes how to carry out a review. Otherstandards or local management define the context within which a review is performed, and the use made ofthe results of the review. Software reviews can be used in support of the objectives of project management,system engineering (for example, functional allocation between hardware and software), verilication andvalidation, configuration management, quality assurance, and auditing. Diferent types of reviews reflectdifferences in the goals of each review type. Systematic reviews are described by their defined procedures.scope, and objectives.
1.3 Relationship with IEEE Std 12207-2008
This standard may be used to achieve the outcomes of 7.2.6 (Software Review Process) and 7.2.7 (SoftwareAudit Process) ofIEEE Std 12207-2008 [B15]
1.4 Conformance
Conformance to this standard for a specific review type can be claimed when all mandatory actions (indicatecby “shall”) are carried out as defined in this standard for the review type used. Claims for conformanceshould be phrased to indicate the review types used, for example, “conforming to IEEE Std 1028-2008 forinspections.” The word “shall” is used to express a requirement, “should” to express a recommendation.and “may,” to express alternative or optional methods of satisfying a requirement.
IEEE 1028-2008 pdf download
PS:Thank you for your support!
