The existence of this standard should not be construed to prohibit additional content in a Software Quality Assurance Plan. An assessment should be made for the specific software product item to assure adequacy of coverage. Where this standard is invoked for a project engaged in producing several software items, the applicability of the standard should be specified for each of the software product items encompassed by the project.
The standard also provides a standard against which such plans can be compared and assessed. It applies to the development and maintenance of critical software. For noncritical software, or for software already developed, a subset of the requirements of this standard may be applied. Tools and techniques that may be used to improve the control of software maintenance activities are discusses. Managing the maintenance process and maintenance specific definitions will be included in the standard.
In addition it will establish a correlation between the content of software maintenance plan as derfined in and the content of such plans as defined in IEEE Purpose: To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
In totality, the requirements constitute a minimal set of criteria that are necessary and sufficient conditions for conformance to this standard. Users of this standard may incorporate other items by reference or as text to meet their specific needs. The basic process model includes input, process, output, and control for software maintenance.
This standard does not presuppose the use of any particular development model e. Read more… Read less…. Prices subject to change without notice.
About Us. Contact Us. Sign In. Standards Store. Purchase History. Currency display settings. Manage society memberships. Featured Products. View All Publishers.
Quality Management.
0コメント