Active Oldest Votes 23 Short answer: is not a standard, it is a recommended best practice on how to write SRS in the style of On how it is actually done in the industry today: Truth to be told, formal project documentation, especially requirements documentation was killed off mostly in the age of Agile, as the Agile Manifesto discourages formal documentation. There is no one, single, large formal specification, but instead, there are so called user stories, product backlogs and such. This is because of iterative development, only a handful of features are specified informally for each cycle of weeks. A renowned book is User Stories Applied. There are so-called "executable" specifications, which are formal, since they are essentially domain-specific languages DSLs for testing.
|Published (Last):||2 September 2012|
|PDF File Size:||10.6 Mb|
|ePub File Size:||10.14 Mb|
|Price:||Free* [*Free Regsitration Required]|
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. Keywords: contract, customer, prototyping, software requirements specification, supplier, system requirements specifications The Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published Printed in the United States of America. ISBN 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.
Members of the committees serve voluntarily 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. The existence of an 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 the standard.
When a document is more than? Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership af? 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? 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 and Standards 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. Box Piscataway, NJ USA Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights.
By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention.
Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. This recommended practice describes recommended approaches for the speci?
It is based on a model in which the result of the software requirements speci? It should help a b c Software customers to accurately describe what they wish to obtain; Software suppliers to understand exactly what the customer wants; Individuals to accomplish the following goals: 1 Develop a standard software requirements speci? To the customers, suppliers, and other individuals, a good SRS should provide several speci? Establish the basis for agreement between the customers and the suppliers on what the software product is to do.
The complete description of the functions to be performed by the software speci? Reduce the development effort. The preparation of the SRS forces the various concerned groups in the customer? Careful review of the requirements in the SRS can reveal omissions, misunderstandings, and inconsistencies early in the development cycle when these problems are easier to correct. Provide a basis for estimating costs and schedules. The description of the product to be developed as given in the SRS is a realistic basis for estimating project costs and can be used to obtain approval for bids or price estimates.
Provide a baseline for validation and veri? Organizations can develop their validation and veri? As a part of the development contract, the SRS provides a baseline against which compliance can be measured. Facilitate transfer. The SRS makes it easier to transfer the software product to new users or new machines. Customers thus? Serve as a basis for enhancement. Because the SRS discusses the product but not the project that developed it, the SRS serves as a basis for later enhancement of the?
The SRS may need to be altered, but it does provide a foundation for continued production evaluation. Software life cycle processes? Life cycle data. At the time this recommended practice was approved, the working group consisted of the following members: Leonard L. Atchinson Mikhail Auguston Robert E. Barry Leo Beltracchi H.
Ronald Berlack Richard E. Biehl Michael A. Briggs M. Cardow Enrico A. Geoff Cozens Paul R. Croll Gregory T. Derganc Perry R. Fairley John W. Fries Roger U. Fujii Adel N. Gunther David A. Gustafson Jon D. Hagar John Harauz Robert T. Harley Herbert Hecht William He? Horch Jerry Huller Peter L. Hung George Jackelen Frank V. Jorgensen William S. Junk George X. Kambic Richard Karcich Ron S. Kenett Judith S.
Kerner Robert J. Kierzyk Dwayne L. Knirk Shaye Koenig Thomas M. Kurihara John B. Lane J. Lively James J. Modell James W. Moore Pavol Navrat Myrna L. Olson Indradeb P. Pal Alex Polack Peter T. Poon Lawrence S. Przybylski Kenneth R. Ptack Annette D.
Reilly Dennis Rilling Andrew P. Sage Helmut Sandmayr Stephen R. Schultz Lisa A. Selmon Robert W. Shillato David M. Siefert Carl A. Singer James M. Sivak Richard S. Sky Nancy M. Smith Melford E. Smyre Harry M. Sneed Alfred R. Sorkowitz Donald W. Urbanowicz Glenn D. Venables Udo Voges David D. Walden Dolores Wallace William M.
Walsh John W. Whitmire P.
Norma IEEE-STD-830-1998 - Português
Subscribe to RSS