The third reading note on the writing of an effective use case

13th: Extending to multiple use cases
When dealing with a large number of use cases, two proven techniques can be used: a simple description of each use case, or a use case divided into multiple clusters.
There are four common and effective clustering techniques available:
Classification by performer, classification by summary use case, classification by development Group and version number, by Subject field

14th: crud and parameterized use cases
So far, there has been no consensus on how to organize the use cases of creating an entity, retrieving an entity, updating an entity, and deleting an entity. We refer to these small use cases based on database operations as crud use cases.
This is occasionally the case when extracting system use cases: some use cases are roughly the same. For these use cases, a common search mechanism may be established by only one development group and called by other people.
15th Chapter: Business Process Modeling
The contents of this book can be used in both software system design and business process design. For any system, including business systems that provide services to outside users while protecting the interests of other users, the force can be described.
The 16th chapter: missing demand
The purpose of writing performers is to use aliases to express only the details of the data that need to be passed. This is a good suggestion, as customer information is represented by name and address. For programmers, however, this does not provide the detailed information necessary for software development.
Use cases are simply the behavioral requirements of a requirement document and do not include system performance requirements, business rules, user interface design, data description, finite state machine behavior, priorities, and other relevant information.
Using the "precision" level to classify your data needs can also help you rationalize your efforts, often dividing your data requirements into three levels of accuracy: information aliases, domain lists or data descriptions, domain details, and domain validation
The 17th chapter: The role of use cases in the whole process
Use cases indicate to the manager the system functions that should be submitted to the user. The title of the use case indicates the needs of the main performer, and the system must support these requirements, while the use case description describes what the system needs and what services it will provide.
The 19th chapter: Error correction
When writing a use case, the most common mistake is to omit the subject of the sentence, assuming that the user's excuses and target writing are too detailed.

The third reading note on the writing of an effective use case