The software Requirements specification is designed to enable both users and software developers to have a common understanding of the initial requirements of the software, making it the basis for the entire development effort. The requirements for compiling the software Requirements specification are as follows:
1 Introduction
1. 1 Writing Purpose
Explain the purpose of writing this software requirement specification and point out the intended reader.
1. 2 background
Description
A The name of the software system to be developed;
b The task of the project, developers, users and the computing center or computer network to implement the software;
C The basic interrelationship between the software system and other systems or other institutions.
1. 3 definition
List the definitions of the special terms used in this document and the original phrases of the words in the first letter of the foreign language.
1. 4 reference materials
List resources that are useful, such as:
A The approved Plan task book or contract of the project and the approval of the higher authority;
b Other published documents belonging to this item;
C Documents, materials, and software development standards that are referenced throughout this document. The title, document number, date of publication and publishing unit of these documents are listed, indicating the source of the information available to these documents.
2 Tasks Overview
2. 1 goals
Describe the intention of the software development, application objectives, scope of action, and other background material on the software development that should be explained to the reader. Explain the relationship between the developed software and other related software. This is true if the SOFTWARE PRODUCT is a stand-alone software, and the entire content is self-contained. If the defined product is an integral part of a larger system, it should indicate the relationship between the product and the other components of the system, for which purpose a block diagram can be used to illustrate the composition of the system and the links and interfaces of the product with other parts.
2. 2 Characteristics of the user
The characteristics of the end-user of the software are listed, and the educational level and technical expertise of the operator and maintenance personnel are fully explained, and the expected frequency of the software is also given. These are the important constraints of software design work
2. 3 Assumptions and constraints
Lists assumptions and constraints for the development of the software, such as funding constraints, development deadlines, and so on.
3 Demand Regulation
3. 1 The provisions of the function
In the form of a list (for example, the IPO table is input, processing, the form of output table, a quantitative and qualitative description of the software requirements of the function, the input of what amount, how the processing, what output, indicating the software should support the number of terminals and the number of concurrent operations should be supported.
3. 2 Performance requirements
3. 2. 1 precision
The requirements for the input and output data accuracy of the software may include the accuracy of the transmission process.
3. 2. 2 Time characteristic requirements
Describes the time characteristic requirements for the software, such as:
A Response time;
b Update processing time;
C Conversion and transmission time of data;
D The time for solving problems;
3. 2. 3 flexibility
Describes the requirement for flexibility in the software, i.e., the ability of the software to adapt to these changes when a requirement has changed, such as:
A Changes in the mode of operation;
b Changes in the operating environment;
C Changes to interfaces with other software;
D Changes in precision and effective time limits;
E The change or improvement of the plan.
The part of the specialized design to provide these flexibilities should be marked.
3. 3 The output requirement of the lost person
Explain each input and output data type, and explain its media, format, numerical range, precision and so on. Explain and illustrate the data output of the software and the control output that must be indicated, including a description of the hard copy report (normal result output, state output and abnormal output) and graphic or display report.
3. 4 Data management capability requirements
Describes the number of volumes and records that need to be managed, the size of the tables and volumes, and estimates the storage requirements for the data and their components as predictable growth.
3. 5 Fault Handling requirements
Lists possible software, hardware failures, and the consequences for performance and the requirements for fault handling.
3. 6 Other specialized requirements
If the user unit to the security of the requirements, the use of convenient requirements for maintainability, complementarity, readability, reliability, operating environment and the conversion of the special requirements.
4 Operating Environment Regulations
4. 1 equipment
Lists the hard devices that are required to run the software. Describe the new equipment and its specialized functions, including:
A Processor model and memory capacity;
b External memory capacity, online or offline, media and its storage format, the type and number of equipment;
C Type and quantity of input and output devices, online or offline;
D Type and number of data communication equipment;
E function keys and other special hardware
4. 2 Support Software
Lists the supporting software, including the operating system to be used, compilation (or assembly) programs, test support software, and so on.
4. 3 interface
The interface between the software and other software and the data communication protocol are described.
4. 4 control
Describes the methods and control signals that control the operation of the software, and describes the source of these control signals.