1 Introduction
1.1 Purpose: to clarify the purpose of writing a requirement manual and specify the target audience.
1.2 Project Background: it should include
● The entrusting unit, happy unit and competent department of the project;
● Relationship between the software system and other systems.
1.3 definition: lists the definitions of specialized terms used in the document and the acronyms.
1.4 references: may include
● Approved plans and tasks, contracts or approvals from higher authorities
● Documents Reference Materials and specifications
● List the author, title, number, publication date, publisher or source of the materials
2 task Overview
2.1 goals
2.2 Runtime Environment
2.3 conditions and restrictions
3. Data Description
3.1 Statement data
3.2 dynamic data: Includes input data and output data.
3.3 database Description: name and type of the database to be used.
3.4 Data Dictionary
3.5 data collection
4. Functional Requirements
4.1 function division
4.2 Function Description
5. Performance Requirements
5.1 data accuracy
5.2 time features: such as response time, update processing time, data conversion and transmission time, and running time.
5.3 Adaptability: the ability to adapt to changes in operation modes, runtime environments, interfaces with other software, and development plans.
6. operation requirements
6.1 User Interface: such as screen format, report format, menu format, input and output time.
6.2 hardware interface
6.3 Software Interface
6.4 troubleshooting
7. Other requirements
Such as usability, security and confidentiality, maintainability, and portability.
