GB/T 9385-2008Norm of computer software requirements specification (English PDF)

Foreword

This standard is GB/T 9385 "computer software requirements specification guidelines for the preparation," the first amendment. This standard and GB/T 9385-1988 The main difference is as follows.

a) according to GB/T 1.1 the provisions of the original GB/T 9385-1988 edition Chapter 1, the introductory part of the content on the new version of Introduction section;

b) the scope of the new standard part readjust rewritten;

c) Section 2 normative references omitted the GB/T 8567;

d) under the provisions of GB/T 8566 and GB/T 11457, the term "developer" to "supply-side";

e) the original GB/T 9385-1988 edition of Chapters 4 and 5 is adjusted to the new version of Chapter 4, and the name for the preparation of Principles "SRS" is.

Chapter 4 adjusted more clear, perfect. And deleting the contents Older Chapter 5 about the model;

f) version of the standard of Chapter 6 of the main content is adjusted to the new standard in Chapter 5, while the outline part of the adjustment to the new Normative A, and appendix A of the expanded part. Appendix A of this standard is the data appendix.

The date of implementation of this standard in place since been repealed GB/T 9385-1988.

The standard proposed by the People's Republic of China Ministry of Information Industry.

Introduction

This standard describes the method of the software requirements specification. It is based on the assumption that the software requirements specification determination process The result is a clear and complete specification document. This standard will help to.

--- Software customers to accurately describe what they wish;

--- Supplier of software to correctly understand what customers want;

--- For the following goals of the relevant units and personnel.

- organization of its location to develop a standard software requirements specification (SRS) outline;

- define the format and content of their specific software requirements specification;

- preparation of other local support materials, such as, SRS quality checklist, or SRS manual writers.

For customers, suppliers and other relevant personnel, a good SRS may bring some specific benefits, such as.

--- To provide any software products, establish a basis for agreement between customer and supplier. Complete description in the SRS software functions We will assist potential users in order to determine whether the software to meet their specific needs, in order to meet their needs or how to modify the software;

--- Reduce development effort. Document preparation SRS forcing the customer organization or person interested parties before considering all the strict design Demand and reduce future re-design and re-coding and re-testing. SRS in the demand for careful review, the In early in the development cycle reveals some omissions, misunderstandings and inconsistencies, when these problems are easier to fix;

--- Provide the basis for the estimated cost and schedule. SRS given in the description of the product to be developed is the estimated project cost basis in reality, It can be used to obtain approval or bid prices derived estimates;

--- Provide a baseline for the verification and validation. The adoption of a good SRS documentation, organizations can submit their more effective verification and validation count Draw. As part of the development contract, SRS can provide a baseline for measuring compliance;

--- Facilitate the transfer of software products. SRS document makes a software product is transferred to a new user or machine easier. Customers therefore find soft Products more easily transferred to other parts of the organization, the supplier discovery software products more easily transferred to new customers;

--- As a further enhancement of the foundation. Because SRS discussion document is the product, rather than developing its projects, therefore, SRS is already Enhanced follow-up product development foundation. Although SRS documents may need to be modified, but it does provide for the following product evaluation basis. Computer software requirements specification specification

1 Scope

This standard gives the software requirements specification (SRS) preparation requirements, describes the content and quality of a good SRS, and in the attached Appendix A gives examples of some of the SRS outline.

This standard applies to the preparation of SRS.

This standard does not define any particular method for the preparation of SRS, naming conventions and tools.

2 Normative references

The following documents contain provisions which, through reference in this standard and become the standard terms. For dated references, subsequent Amendments (not including errata content) or revisions do not apply to this standard, however, encourage the parties to the agreement are based on research Whether the latest versions of these documents. For undated reference documents, the latest versions apply to this standard.

GB/T 8566 Information technology - Software life cycle processes (GB/T 8566-2007, ISO /IEC 12207:1995, MOD)

GB/T 11457 IT software engineering terminology

3 Terms and Definitions

GB/T 11457 and established in the following terms and definitions apply to this standard.

3.4 Run directly interact with the product or products to individuals or groups. Users and customers are usually not the same person or group. Establishment of the principle of 4 SRS