Thoughts on Requirements

Read 《CodeI have learned a lot from this chapter about requirements. In addition, through work experience and discussions with friends about what needs to calculate a good demand, we all feel a lot of doubt about the demand. To what extent do we need to meet our needs? Maybe we can find the answer in the requirement checklist in this book.

Functional requirements:

1. Have you defined in detail all the input of the system, including its source, precision, value range, and occurrence frequency?

2. Are all outputs of the system defined in detail, including, destination, precision, value range, occurrence frequency, and format?

3. Are all output formats (web pages, reports, and so on) defined in detail )?

4. Have you defined the external interfaces of all hardware and software in detail?

5. Have you defined all external communication interfaces in detail, including the handshake protocol, error correction protocol, and communication protocol?

6. Does the list all the things the user wants to do?

7. Are the data used by each task and the data obtained by each task defined in detail?

For non-functional requirements

1. Are all necessary operations described in detail from the user's perspective?

2. are other timing-related considerations described in detail, such as processing time, data transmission rate, and system leaf size?

3. Have you defined the security level in detail?

4. Have you defined reliability in detail, including the consequences of software failures, critical information to be protected when a fault occurs, and policies for error detection and recovery?

5. Have you defined in detail the minimum memory size and the remaining disk quota?

6. Have you defined in detail the maintainability of the system, including changes to adapt to specific functions, changes to the operating environment, and changes to interfaces with other software?

7. Does the definition of "successful" exist? What is the definition of "failure?

Requirement Quality

1. Is the requirement written in the user's language? Do users think so too?

2. Do each requirement not conflict with other requirements?

3. Have you defined in detail the trade-offs between competing features-for example, the trade-offs between robustness and correctness?

4. Do you want to avoid specifying the design (solution) As required )?

5. Is the requirement level quite consistent in detail? Should I describe some requirements in more detail? Should some requirements be described more roughly?

6. Is the city requirement clear enough that they can understand it even if it is co-transferred to an independent group for construction? Do developers think so too?

7. are each clause related to the issues to be resolved and their solutions? Can each clause be traced back to the corresponding overview sources in the problem domain?

8. Is each requirement testable? Is it possible to carry out independent tests to test whether all requirements are met?

9. Have you described in detail all possible changes to the requirement, including the possibility of each change?

Completeness of requirements

1. Do I describe in detail the information that cannot be obtained between the start of development?

2. Is it acceptable that the product meets all requirements?

3. Are you comfortable with all your needs? Have you removed the impossible demands-those just to appease customers and bosses?