Ieee does not warrant or represent the accuracy or content of the material contained in its standards, and expressly disclaims all warranties express, implied and statutory not included in this or any. The resulting software requirements specification documents produced from within this environment conformed to standard 830 1998 promulgated by the institute of electrical and electronics engineers ieee. Ieee 730 standard for software quality assurance plans equipo 7. Reengineering requirements specification based on ieee 830. The content and qualities of a good software requirements specification srs are described and several sample srs outlines are presented. Ansiieee std 811983 revision of ieee std 811962 an. It describes the content and qualities of a good software requirements specification srs and presents several sample srs outlines. Ieee recommended practice for software requirements. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of inhouse and commercial.
This standard replaces ieee 830 1998, ieee 12331998, ieee 621998. Ieee standard 7302014 software quality assurance processes. The proposed model of srs uses a semistructured data approach aiming at transforming the srs into a hypermedia and is based on. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of inhouse and commercial software products. This recommended practice describes recommended approaches for the speci. Ieee recommended practice for software requirements speci. Advances in intelligent systems and computing, vol. Ieee recommended practice for software design descriptions. Guidance for creating software quality assurance plans the aim of prior ieee 730 versions, which this version includes d.
Software quality assurance ieee 730 standard for plans. Ieee standard for software quality assurance plans ieee. Ieee recommended practice for software requirements specifications iee e std 830 1993 author. The aim of an srs document is to capture requirements in an unambiguous manner in order to facilitate communication between stakeholders. This standard assists in the preparation and content of software quality assurance plans and provides a standard against which such plans can be prepared and assessed.
It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative. This is a recommended practice for writing software requirements specifications. Developing software requirements specification ieee std. Isbn 0738114561 ss94688 no part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.
232 812 296 1410 911 337 218 1518 4 706 118 1239 1110 862 809 487 856 1009 890 1085 481 485 749 1078 370 1131 472 853 13 1417 275 1171 121 271 474 1463 683 370 849 241 1479 62 189 76 894 1356 656 151 1456 550 264