[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243104-105":53,"doc-detail-243104-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","ieee-std-830-1998-software-requirements-specifications-recommended-practice","IEEE Std 830-1998 - Software Requirements Specifications Recommended Practice","","The document describes the content and key qualities of a strong software requirements specification (SRS) and provides several example SRS outlines. It serves as a recommended practice for specifying requirements for software to be developed and also supports selection of internal or commercial software products. Guidance is included for compliance with IEEE/EIA 12207.1-1997.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":46,"@type":70,"position":76},"https://docshare.wps.com/template/paper-templates/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/ieee-std-830-1998-software-requirements-specifications-recommended-practice/243104/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/ieee-std-830-1998-software-requirements-specifications-recommended-practice/243104.png","ImageObject",442,249,{"name":88,"@type":89},"\tJames","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-18","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":8},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of IEEE Std 830-1998?","Question",{"text":108,"@type":109},"It recommends practices for specifying software requirements via a well-structured software requirements specification (SRS), and it can also help in selecting software products.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What does the document provide besides general guidance?",{"text":113,"@type":109},"It describes qualities of a good SRS and presents several sample SRS outlines.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the document relate to IEEE/EIA 12207.1-1997?",{"text":117,"@type":109},"It includes guidelines intended to support compliance with IEEE/EIA 12207.1-1997.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},243104,1790041342,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":45,"category_name":46,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":8,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":20},2336474466412,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","IEEE Std 830-1998 (Revision of  \nIEEE Std 830-1993) IEEE Std 830-1998  \nIEEE Recommended Practice for Software Requirements Specifications  \nIEEE Computer Society  \nSponsored by the  \nSoftware Engineering Standards Committee  \n20 October 1998 SH94654  \nAuthorized licensed use limited to: ULAKBIM UASL-Cankaya University. Downloaded on March 23,2012 at 10:22:52 UTC from IEEE Xplore. Restrictions apply.  \nIEEE Std 830™-1998(R2009)  \n(Revision of IEEE Std 830-1993)  \nIEEE Recommended Practice for Software Requirements Specifications  \nSponsor  \nSoftware Engineering Standards Committee  \nof the  \nIEEE Computer Society  \nReaffirmed 9 December 2009 Approved 25 June 1998  \nIEEE-SA Standards Board  \nAbstract: The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are 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.  \nKeywords: contract, customer, prototyping, software requirements specification, supplier, system requirements specifications  \nThe Institute of Electrical and Electronics Engineers, Inc.  \n345 East 47th Street, New York, NY 10017-2394, USA  \nCopyright © 1998 by the Institute of Electrical and Electronics Engineers, Inc.  \nAll rights reserved. Published 1998. Printed in the United States of America.  \nISBN 0-7381-0332-2  \nNo 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.  \nAuthorized licensed use limited to: ULAKBIM UASL-Cankaya University. Downloaded on March 23,2012 at 10:22:52 UTC from IEEE Xplore. Restrictions apply.  \nIEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards.  \nUse of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document.  \nThe IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.”  \nThe 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. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state","cbCaihLV8RahWKnA","https://ap.wps.com/l/cbCaihLV8RahWKnA","pdf",432852,39,"English","# Abstract\n# Keywords\n# Scope and Purpose\n## Software Requirements Specification (SRS)\n## Applicability to Product Selection\n## Compliance Guidance (IEEE/EIA 12207.1-1997)\n# Legal Notices and Disclaimers","[{\"question\":\"What is the purpose of IEEE Std 830-1998?\",\"answer\":\"It recommends practices for specifying software requirements via a well-structured software requirements specification (SRS), and it can also help in selecting software products.\"},{\"question\":\"What does the document provide besides general guidance?\",\"answer\":\"It describes qualities of a good SRS and presents several sample SRS outlines.\"},{\"question\":\"How does the document relate to IEEE/EIA 12207.1-1997?\",\"answer\":\"It includes guidelines intended to support compliance with IEEE/EIA 12207.1-1997.\"}]","IEEE Std 830-1998 - Software Requirements Specifications Recommended Practice | PDF",1789200026]