Demand specifications Sample (Pick) 1 purpose
Standardize the preparation of the "Demand Manual" in the process of software development, making it the basis for the entire development work.
2 applicable range
This specification applies to the "Software)" Demand Manual "of the Group Development Project.
3 Written content tips
1 Introduction 3.1.1 Background Description
Note The name, task maker, user, and computer network implementation of the software.
3.1.2 References
List the relevant information (name, date, publishing unit, author, etc.).
3.1.3 Terms and Abnormal Words
List the definitions of specialized terms used in this document, and terminology abbreviations.
3.2 Overall Software Overall
3.2.1 Target
The intent of software development, application goals, scope, and description of background materials.
3.2.2 System Model
The illustration shows all the functions of the software and its interrelationships and data delivery.
3.2.3 Assumption and Constraint
Explain certain assumptions and constraints that affect software development, operating environment, and system capabilities (such as the ability to make an error). 3.3 Detailed requirements
The functional requirements and performance requirements of this software system are described in detail.
3.3.1 Functional requirements
For each function in the system, you will be described in detail (icon or text).
Overview Description Function Name, Goals and Rices. Enter the information to enter this feature. Processing This function does, how to process the input information and convert to an output information. The output lists the files generated inside. 3.3.2 Performance requirements
Quantitatively describes the specific performance requirements of this software system to meet. The following:
3.3.2.1 Accuracy
Explain the accuracy requirements of the system, such as:
The accuracy requirements of the data. The accuracy requirements of digital computing. Data transfer error rate requirements. 3.3.2.2 Time Features
Describe the time characteristics of the system, such as:
Solution time. Ask and update the response time of the data file. The order relationship between the function of the system. 3.3.2.3 Flexibility
Note When a system is adapted when a variation occurs, the software ingredients and processes needed to be designed to accommodate these changes.
3.3.2.4 System capacity
Includes the design capacity and theory of the system (calculated) capacity.
3.3.3 Input and output
Explain the type of input and output data, and describe a media, format, numerical range, etc. Interpretation of the data output of the software and the required control output, including a description of the hard copy report (normal result output, status output, and exception output) and graphics or display reports.
3.3.4 Data management capabilities
Number of documents and records that need to be managed, the size of the table, and the size of the scrip are estimated to be estimated to save the storage requirements of the data and their components in accordance with the foreseeable growth.
3.3.5 Troubleshooting
List possible software, hardware failures, and consequences of performance, and requirements for troubleshooting.
3.4 Environment
Describe the environment you need to run the developed software.
3.4.1 Equipment Environment
Describe the equipment required to run the software system, such as:
The model and memory capacity of the processor. The number of storage media is stored. Communication networks (including network structures, line speeds, and communication protocols, etc.). 3.4.2 Support Software Environment
List the support software (including name, version number, and file information) to be developed, if necessary, should also list the test software, but also point out the programming language, compiler, operating system, and data management of the software. system.
3.4.3 interface
Describe the interfaces, data communication protocols between the software and other software, and the like.
3.4.4 Other
Description This software system is required in security and confidentiality requirements and users of easy accessibility, maintainability, replenishment, readability, reliability, and operational environment.
