Specification samples of Software Requirement Specification

From: www.csdn.net

 

Specification samples of Software Requirement Specification

Author: hyenachenyao (BlueHyena)

I. Writing Purpose
The software requirement specification is prepared to enable both the user and the software developer to operate the environment and function of the software.
It has a common understanding with the initial performance requirements, making it the basis of the entire development work.
The summary design provides a description of the requirements.

Ii. Main Content and writing requirements
1. Introduction
1.1 Purpose
A. Describe the purpose of developing the software;
B. Describe the purpose of writing this software specification;
C. Describe the intended readers of the software requirements.
1.2 Background
A. Identify the software product to be developed (name, Code );
B. List the task initiators, project owners, system analysts, system designers, and program designers of the project.
Reporters, programmers, data reporters, and people and users directly related to the project's work;
C. describe the relationship between the software product and other related software products.
1.3 references
A. List the approved task books or contracts of the project and approvals of higher authorities;
B. List documents, materials, technical standards and their authors,
Title, number, release date, and publishing organization.
1.4 terms
Lists the definition of technical terms in this software requirement specification and the original phrases of English acronyms.

2. Project Overview
2.1 General description of the software being developed
Describes the main components, links, and external interfaces of the developed software, and the hierarchical structure of the system flow chart.
Description, 1:
Figure 1 hierarchy chart example

2.2 functions of the developed software
Briefly describe the functions of the developed software and the hierarchical structure of the system flowchart.
Design tools, such as PowerDesigner, must be used.

2.3 Implementation Language
Lists the programming languages used.
2.4 user features
Describes the educational level, work experience, and technical expertise of end users.
2.5 General constraints
Provide the constraints that affect the design of the software by the contractor and the changes to the software when the demand changes.
The ability to adapt is the demand for flexibility.
3. Specific Requirements
3.1 functional requirements
Describe in detail the input, processing, output and
The basic operation that occurs in the process. For each category of functions, see the following four sections.
(A design tool, for example, PowerDesigner, must be used. The report does not conform to the following format ).


3.1.1 Introduction
A. describes the functions and usage of the software;
B. List background information related to the function.
3.1.2 input requirements
A. Description of the input data, including the input source, quantity, measurement unit, and accuracy;
B. Operator specific operation control requirements (such as input format, data type, accuracy, automatic range inspection, etc.
);
C. Specify the referenced input device interface information (including the device model and quantity ).
3.1.3 handling requirements
Describes the operations performed on the input data and intermediate parameters to obtain the expected output, including:
A. Check the input data validity;
B. Operation Sequence and handling process;
C. abnormal response. Such as overflow, communication faults, and error handling;
D. Check the output data validity.
3.1.4 output requirements
A. Description of the output data, including the destination (storage media and usage), quantity, measurement unit, and accuracy;

B. Illegal data processing;
C. Specify the referenced output device interface information (including the device model and quantity ).
3.2 external interface requirements
3.2.1 user interface
A. Point out the interface requirements when users use software products. If you operate through the display terminal, you must specify
Requirements:
Screen format requirements;
The format and content displayed on the page of the explain report or menu;
The format of your command.
B. List the formats of output error messages.

C. Use development tools as much as possible to construct the interface, so that the requirement definition and design and coding are connected, and the interface should comply with
Design specifications.

3.2.2 hardware interface
A. Logical Features of each interface between software products and system hardware;
B. devices supported by hardware interfaces;
C. Agreements between software and hardware interfaces and between hardware interfaces and supporting devices.
3.2.3 Software Interface
Describes the interface relationship between the software product and other related software, and points out the software name, mnemonic and
Version number.
3.2.4 Communication Interface
Describes various communication interfaces and protocols.
3.3 Performance Requirements
A. Total amount of data to be processed under normal conditions and peak working conditions within a certain period of time;
B. response time;
C. output result accuracy.
3.4 software property requirements
A. correctness requirements;
B. robustness requirements;
C. Security and confidentiality requirements;
D. Usability requirements;
E. Understandable requirements;
F. maintainability requirements;
G. testability requirements;
H. portability requirements (different operating systems, database systems, Network , System software)
3.5 data requirements
, This part of content is done together with the functional description of the software. Design tools are required, such as PowerDesigne.
R ).
3.5.1 Data Description
A. List static data elements used for control and reference;
B. list dynamic input data elements;
C. List dynamic output data elements;
D. List the data elements generated inside the software.
3.5.2 Data Acquisition
A. List the organizations that provide input data;
B. List data input media and devices;
C. List the data generation media and devices.

3.6 product requirements
A. Installation program requirements;
B. Learning software requirements;
D. versatility of software functions.
E. Software encryption requirements
F. General requirements for software runtime environments (different operating systems, database systems, networks, and system software)