Software Requirement Specification (GB856T--88)

Notes on writing software requirement specification

1 Introduction 1.1 Writing Purpose

Describe the purpose of writing this software requirement specification and point out the intended readers.

1.2 Background

Note:

A. Name of the software system to be developed;

B. the submitter, developer, user, and computing center or computer network that implements the software;

C. Basic relationships between the software system and other systems or institutions.

1.3 Definition

Lists the definitions of specialized terms used in this document and the original phrases of the foreign acronyms.

1.4 references

List useful references, such:

A. approved plans and tasks or contracts and approvals from higher authorities for this project;

B. Other published documents of the project;

C. Documents and materials referenced everywhere in this document, including the software development standards to be used. Lists the titles, document numbers, publication dates, and publishing units of these documents, indicating the source of these documents.

2. Task overview 2.1 goals

Describe the intent, purpose, scope of application of the software development, and other background materials related to the software development to the reader. Explains the relationship between the developed software and other related software. If this software product is an independent software and all content is self-contained, this is described. If the defined product is an integral part of a larger system, the relationship between the product and other components of the system should be described, to this end, you can use a block diagram to describe the composition of the system and the contact and interface between the product and other parts. |

2.2 user features

Describe the features of end users of the software, fully describe the educational level and technical expertise of operators and maintenance personnel, and the expected frequency of rejection of the software. These are important constraints of software design.

2.3 assumptions and constraints

List the assumptions and constraints for the software development work, such as funding restrictions and development periods.

3 Requirements 3.1 functional requirements

Use a list (for example, an IPO table in the form of an input, processing, or output table) to describe the functional requirements of the software in a quantitative and qualitative manner one by one, describe the inputs, processes, and outputs. Describe the number of terminals to be supported by the software and the number of concurrent operations to be supported.

3.2 performance requirements 3.2.1 Accuracy

The requirements on the input and output data accuracy of the software may include the precision during transmission.

3.2.2 time characteristics requirements

Specifies the time requirements for the software, such:

A. response time;

B. Update the processing time;

C. Data Conversion and transfer time;

D. Problem Solving time; and other requirements.

3.2.3 flexibility

Describes the flexibility required for the software, that is, the ability of the software to adapt to these changes when the demand changes, such:

A. Changes in operation methods;

B. Changes in the runtime environment;

C. Changes in interfaces with other software;

D. Changes in accuracy and validity period;

E. Planned changes or improvements.

Specific designs for the purpose of providing such flexibility should be noted.

3.3 output requirements

Describe the input and output data types, and describe the media, format, value range, and accuracy one by one. The data output of the software and the control output that must be indicated are explained and used as an example, including the hard copy report (normal result output, status output, and abnormal output) and the description of the graphic or display report.

3.4 Data management capability requirements

Describe the number of volumes and records to be managed, the size and size of tables and volumes, and estimate the storage requirements of data and its components based on foreseeable growth.

3.5 troubleshooting requirements

List possible software and hardware faults, as well as the consequences for various performance and fault handling requirements.

3.6 Other Special Requirements

For example, user organizations require security and confidentiality, convenient use, and special requirements for maintainability, complementarity, accessibility, reliability, and conversion of the operating environment.

4 Operating Environment Regulations 4.1 Devices

List the hard devices required to run the software. Describes the new devices and their special functions, including:

A. Processor Model and memory capacity;

B. External storage capacity, online or offline, media and its storage format, device model and quantity;

C. Model and quantity of input and output devices, online or offline;

D. Model and quantity of data communication equipment;

E. function keys and other dedicated hardware

4.2 support software

List the supported software, including the operating system to be used, compiled (or compiled) programs, and test support software.

4.3 Interface

Describes the interfaces and data communication protocols between the software and other software.

4.4 Control

Describes how to control the running of the software and the control signals, and describes the sources of these control signals.