Como diligenciar formato ieee 830 espc. de req. de software

IEEE Std 830-1998
(Revision of
IEEE Std 830-1993)

IEEE Recommended Practice for
Software Requirements
SpeciÞcations

Sponsor

Software Engineering Standards Committee
of the
IEEE Computer Society
Approved 25 June 1998

IEEE-SA Standards Board

Abstract: The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlinesare presented. This recommended practice is aimed at
specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/EIA
12207.1-1997 are also provided.
Keywords: contract, customer, prototyping, software requirements specification, supplier, system
requirementsspecifications

The Institute of Electrical and Electronics Engineers, Inc.
345 East 47th Street, New York, NY 10017-2394, USA
Copyright © 1998 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 1998. Printed in the United States of America.
ISBN 0-7381-0332-2
No part of this publication may be reproduced in any form, in an electronic retrieval system orotherwise, without the prior
written permission of the publisher.

Authorized licensed use limited to: IEEE Xplore. Downloaded on November 5, 2008 at 11:17 from IEEE Xplore. Restrictions apply.

IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the
committees servevoluntarily and without compensation. They are not necessarily members of the
Institute. The standards developed within IEEE represent a consensus of the broad expertise on the
subject within the Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard.
Use of an IEEE Standard is wholly voluntary. The existence ofan IEEE Standard does not imply
that there are no other ways to produce, test, measure, purchase, market, or provide other goods and
services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the
time a standard is approved and issued is subject to change brought about through developments in
the state of the art and comments received from users of thestandard. Every IEEE Standard is subjected to review at least every Þve years for revision or reafÞrmation. When a document is more
than Þve years old and has not been reafÞrmed, it is reasonable to conclude that its contents,
although still of some value, do not wholly reßect the present state of the art. Users are cautioned to
check to determine that they have the latest edition of any IEEEStandard.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of
membership afÞliation with IEEE. Suggestions for changes in documents should be in the form of a
proposed change of text, together with appropriate supporting comments.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as
they relate to speciÞcapplications. When the need for interpretations is brought to the attention of
IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of all concerned interests, it is important to ensure that any interpretation has
also received the concurrence of a balance of interests. For this reason, IEEE and the members of its
societies andStandards Coordinating Committees are not able to provide an instant response to
interpretation requests except in those cases where the matter has previously received formal
consideration.
Comments on standards and requests for interpretations should be addressed to:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855-1331
USA

Note: Attention is called to the...