Differences between business and System Use Cases

Ask the following question:
Now I am working on a project, which divides all the businesses involved into small use cases such as add, delete, and browse. This should be all business use cases, what are my system use cases? What should I do? Or is it necessary to write? (You can take an e-commerce system as an example. Thank you !)

The examples you listed are actually system cases. How can you further segment them? Business Use Cases refer to business goals. For example, maintenance personnel files are a complete business goal and a business use case. As for the maintenance methods, there are manual and automatic methods, some can only be added and deleted, some can only be modified, and some can only look at... these are the methods to achieve business goals. These methods are system use cases that are intended to be included in the scope of software development.

Thank you for your advice.
Can I understand it in this way? If we divide business use cases into several small use cases, are these small use cases system use cases?
It is like maintenance personnel files. If they are divided into multiple parts, they can be used to add, modify, delete, and view files...
If your answer is yes, can I continue to understand it as follows: Generally, business use cases are actually looking at the business logic at a relatively high level, it is closer to the user's direct needs, while the system use case is the detailed division of the business logic, closerProgram?
Thank you for your advice !!!!!

not quite right. The difference between system use cases and business use cases is not a subdivision.
Note: Business Use Cases are used to capture functional requirements, which are reflected by the actor's business objectives. That is, for actor, the business it is responsible for must be composed of a series of business goals. For example, an archive Administrator's Business goal is to maintain the archive. For example, the Forum Administrator's business goals include maintaining users and maintaining posts. These business goals constitute all responsibilities of actor. Business Use Cases reflect requirements.
requirements can be implemented in multiple ways. How to implement it is embodied by system use cases. They are not a simple subdivision relationship, although it looks like. Let's talk about file maintenance. Such a business goal involves a variety of use case scenarios to accomplish it. These scenarios include how to add files, how to modify files, and how to delete files .... for system use cases, we analyze these scenarios to determine which parts of the scenarios should be included in the system construction scope. For example, in an archive maintenance business case, if it is difficult to modify the archive for a specific reason, you can only delete the archive first and then recreate it all. Then, the archive will be added and deleted in the system case, the file is not modified.
business and system use cases are planned from the customer's business perspective and system construction perspective respectively. Business Use Cases are not close, but completely direct requirements. system use cases are not detailed division of business logic, but the implementation method of the system's requirements, but are not unrelated to program design. It just says, the functional requirements of the system to be built are composed of these system use cases.
therefore, both business and system use cases are in the scope of requirements. They represent the business scope and system scope respectively.