Standard: IEEE 1028

SOFTWARE REVIEWS AND AUDITS

This standard is available for individual purchase.

or unlock this standard with a subscription to IHS Standards Expert

IHS Standards Expert subscription, simplifies and expedites the process for finding and managing standards by giving you access to standards from over 370 standards developing organizations (SDOs).

FEATURES & BENEFITS
  • Maximize product development and R&D with direct access to over 1.6 million standards
  • Discover new markets: Identify unmet needs and discover next-generation technologies
  • Improve quality by leveraging consistent standards to meet customer and market requirements
  • Minimize risk: Mitigate liability and better understand compliance regulations
  • Boost efficiency: Speed up research, capture and reuse expertise
For additional product information, visit the IHS Standards Expert page.

HOW TO SUBSCRIBE
For more information or a custom quote, visit the IHS Contact Us page for regional contact information.
Scope:

This standard provides minimum acceptable requirements for systematic software reviews, where “systematic” includes the following attributes:

a) Team participation

b) Documented results of the review

c) Documented procedures for conducting the review

Reviews that do not meet the requirements of this standard are considered to be nonsystematic reviews. This standard is not intended to discourage or prohibit the use of nonsystematic 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.

It is intended that this standard be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity for reviews. This standard is closely aligned with IEEE Std 1012-1986 [B5],1 but can also be used with IEEE Std 1074-1995 [B10], IEEE Std 730-1989 [B1], ISO/IEC 12207:1995 [B15], and other standards. Use with other standards is described in Annex A. A useful model is to consider IEEE Std 1028-1997 as a subroutine to the other standards. Thus, if IEEE Std 1012-1986 were used to carry out the verification and validation process, the procedure in IEEE Std 1012-1986 could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-1997 would be “called” to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-1986 would be returned to for disposition of the results of the review and any additional action required by IEEE Std 1012-1986.

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.”

1 The numbers in brackets correspond to those of the bibliography in Annex C.

NASA Notes:
  • This is an excellent description and approach to V&V. This standard should be selected for mission critical software. However, the following caveat applies. There are minor Discrepancies between the contents of the verification plan and validation plan defined in IEEE12207.1 and the Requirements of IEEE1012-1998. These are identified in the
    maping supplement of IEEE1012a-1998. The discrepancies are essentially in the generic content requirements of IEEE 12207.1. They are: 1) Date of issue
Organization: The Institute of Electrical and Electronics Engineers, Inc.
Document Number: ieee 1028
Publish Date: 2008-06-16
Page Count: 52
Change Type: COMPLETE REVISION
Available Languages: EN
DOD Adopted: NO
ANSI Approved: NO
Most Recent Revision: YES
Current Version: YES
Status: Active

Document History

Document # Change Type Update Date Revision Status
IEEE 1028 Change Type: REAF Update Date: 1997-12-09 Revision: 97 Status: INAC
IEEE 1028 Change Type: Update Date: 1997-12-09 Revision: 97 Status: INAC
IEEE 1028 Change Type: Revision: L Status: INAC
IEEE 1028 Change Type: Revision: 1 Status: INAC
IEEE 1028 Change Type: REAF Update Date: 1988-01-01 Revision: 88 Status: INAC
IEEE 1028 Change Type: Revision: 4 Status: INAC
view more
Advertisement
Advertisement
Advertisement
Advertisement