1. 1 writing purpose 2

1.2 background 2

1.3 Definition 2

1.4 Reference 2

2 Task overview 2

2. 1 objective 2

2.2 User characteristics 3

2.3 Assumptions and Constraints 3

3 demand adjustment 3

3. 1 Function Specification 3

3.2 Provisions on Performance

3.2. 1 accuracy 3

Time characteristic requirement 3

Flexibility 4

3.3 Input and Output Requirements 4

3.4 Data management capability requirements 4

3.5 Troubleshooting Requirements 4

3.6 Other Special Requirements 5

4 Operating environment regulations 5

4. 1 equipment 5

4.2 Supporting software 5

4.3 Interface 5

4.4 control 5

Skills of Writing Software Requirements Specification

1 Introduction

The use of 1. 1

Explain the purpose of writing this software requirement specification and point out the expected readers.

1.2 background

Description:

A. the name of the software system to be developed;

B. The task proposer, developer and user of the project, and the computing center or computer network to realize the software;

C. Basic interaction between software systems and other systems or institutions.

1.3 definition

List the definitions of technical terms used in this document and the original phrases of foreign initial words.

1.4 reference

List useful reference materials, such as:

A. Approved project plan or contract and approval from higher authorities;

B. Other published documents belonging to this project;

C documents and materials cited in this document, including the software development standards to be used. List the titles, document numbers, publication dates and publishing units of these documents, and explain the sources where these documents can be obtained.

2 task overview

2. 1 target

Describe the intention, application goal, application scope of software development and other background materials related to software development that need to be explained to readers. Explain the relationship between the developed software and other related software. If this software product is an independent software and all the contents are independent, then this is a statement. If the defined product is part of a larger system, the relationship between the product and other parts of the system should be explained. For this reason, the block diagram can be used to explain the composition of the system and the connection and interface between the product and other parts. |

2.2 User characteristics

List the characteristics of the end users of this software, fully explain the education level and technical expertise of operators and maintenance personnel, and the expected frequency of use of this software. These are important constraints of software design.

2.3 Assumptions and constraints

List the assumptions and constraints of this software development, such as funding constraints, development cycle and so on.

3 demand adjustment

3. 1 Provisions on functions

In the form of list (such as IPO table, that is, the form of input, processing and output table), the functional requirements of the software are described quantitatively and qualitatively item by item, indicating how much to input, how to process and what output to get, as well as the number of terminals that the software should support and the number of users that should support parallel operation.

3.2 Performance clause

3.2. 1 accuracy

Explain the requirements for the accuracy of software input and output data, which may include the accuracy during transmission.

3.2.2 Time characteristic requirements

Explain the time characteristic requirements of the software, such as:

A. response time;

B. update processing time;

C. data conversion and transmission time;

D. time to solve the problem; Requirements, etc.

flexibility

Explain the requirements for software flexibility, that is, the adaptability of software to certain changes in requirements, such as:

A. changes in business methods;

B. changes in the business environment;

C. changes in interfaces with other software;

D. changes in accuracy and effective time limit;

E. plan changes or improvements.

Parts specially designed to provide these flexibility should be marked.

3.3 Input and output requirements

Explain the types of input and output data, and explain their media, format, numerical range, accuracy, etc. One by one. Examples are given to illustrate the data output of the software and the control output that must be marked, including the description of hard copy report (normal result output, status output and abnormal output) and graphic or display report.

3.4 Data management capability requirements

Explain the number of files and records to be managed, the size of tables and files, and estimate the storage requirements of data and its components according to the foreseeable growth.

3.5 Fault handling requirements

List possible software and hardware faults, consequences of various performances and requirements for fault handling.

3.6 Other special requirements

Such as the user's requirements for security and convenience, and the special requirements for maintainability, complementarity, readability, reliability and convertibility of the operating environment.

4 Operating environment regulations

4. 1 equipment

List the hardware devices needed to run the software. Explain the new equipment and its special functions, including:

A. processor model and memory capacity;

B external storage capacity, online or offline, media and its storage format, equipment model and quantity;

C models and quantities of online or offline input and output devices;

D. Model and quantity of data communication equipment;

E. Function keys and other special hardware

4.2 Support software

List the supporting software, including the operating system to be used, compiled (or assembled) programs, test supporting software, etc.

4.3 interface

Explain the interface and data communication protocol between this software and other software.

4.4 control

Explain the methods and control signals for controlling software operation, and explain the sources of these control signals.