包含编写软件需求规范的指南。该标准描述了良好的软件需求规范(SRS)的必要内容和质量,并提出了原型SRS大纲。本指南没有指定行业范围的 SRS 标准,也没有规定强制性的 SRS 要求。本指南的编写前提是当前的技术水平无法保证或支持这样的正式标准文件。本指南适用于内部和商
for Software Requirements SpeciÞcationsSponsorSoftware Engineering Standards Committeeof theIEEE Computer SocietyApproved 25 June 1998IEEE-SA Standards BoardAbstract: The content and qualities of a good software requirements specification (SRS) are de-scribed and several sample SRS outlines are presented...
IEEE830-1998软件需求规格编写规程
srs-template(IEEE-830-1998)-英文版SoftwareRequirementsSpecificationfor<Project><author><organization><datecreated>TableofContentsTableofContents iiRevisionHistory ii1. Introduction Purpose DocumentConventions IntendedAudiencean
Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem.> 1.2 <Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special ...
(SRS) are de- scribed 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 selec- tion of in-house and commercial software products. Guidelines for compliance with IEEE/...
IEEE-STD-830-1998
Requirements Specifications 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 de- scribed and several sample SRS outlines are presented....
The IEEE Std.830-1998 was created to standardize the software requirements specification document. The aim of an SRS document is to capture software requirements in an unambiguous manner in order to facilitate communication between stakeholders. The Use-case approach has become a de-facto standard ...
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 the requirements of software to be developed, but can also be applied to assist in the selection of in-house...