Requirements document writing points

Requirements document writing points

An old one of mineArticleBy chance, I found it from the machine and shared it with everyone.

There are two forms of requirement writing: Object-oriented and process-oriented. Different modes are used for different audiences and applications.
Process-oriented form:
The main idea is the IPO principle, that is, "output-processing-output"
Document format,
I. First, a brief introduction to the overall system: purpose: to determine the object and body content described in the document
Ii. System context: describes the relationship between the system and other systems and how the boundaries are divided.
Iii. System Requirement decomposition: describes the requirements for a large framework to be decomposed for the overall system.
Iv. Specific Requirements
The specific requirements are simple, as follows:
1. Introduction
2. Input
3. Processing
4. Output
5. In addition to specific requirements, the requirements also include:
1. The interface requirement (interface with other systems, subsystems, modules, user interfaces, etc.) is actually the content of the interface requirement. Because the interface prototype is usually very important, you can take this part out and put it into specific requirements.
The interface prototype is not just a figure, but also contains the description, range, and error message of the interface elements.
2. Performance Requirements
3. Dependency: Dependent databases, third-party software, etc.
4. Demand priority sorting, used to measure development strategies
Vi. References

Object-oriented form. The overall document architecture is the same as described above. There are only two differences.
1. In the system requirement decomposition, it is very easy to describe using the package diagram of the use case. It is actually a graphical display described in the above text.
2. The main difference is the specific requirements, which are described in the form of use cases, including
1. Introduction
2. User (actor)
3. Prerequisites
4. Post Conditions
5. trigger conditions
6. event stream
7. Alternate event streams
For details about the writing method, refer to "Compiling valid use cases". This is the best reference book I have ever seen.