Use case description for continued demands of household financial software written by cainiao

I have never written a case before. I wrote it for the first time, so there must be a lot of errors. Please do not be misled. I just want to hear the old bird's opinions here. Otherwise, I don't know either of them.

Some requirements http://www.cnblogs.com/sss/archive/2009/05/25/1488573.html of the family financial software written by cainiao

By streamlining the description (starting from the agile point of view, we will focus on it first), and draw the following use case diagram, which seems useless.

The following is a description of the three use cases.

User Authentication)

Brief description:Enter or select a user name, enter the password, and then the system authenticates the user identity.

Main participants:User

Prerequisites:None

Post condition:The system correctly identifies the user

Main success scenarios:

1. Enter or select a user name and password.

2. The system successfully authenticates the user identity

3. Record User Logon Information

Extension:

2a. system verification failed

1. Return to Step 1

Account Management)

Brief description:Create, modify, and delete accounts

Main participants:User

Prerequisites:User identity authenticated

Post condition:Account created, modified, or deleted

Main success scenarios:

1. Select Account Management

2. List accounts in the system

3. Create an account, enter the account name, initial amount, and account description.

4. user input verified by the System

5. The system creates a user account and refresh the account list.

Extension:

3A. The user selects to modify the account

1. The system displays the user-selected account information and edits it.

2. Edit an account

3. system update account

3B. user-selected account Deletion

1. The system determines whether the account has a sequential account. If yes, the system prompts that the account cannot be deleted.

Problem to be resolved:

1. account cancellation

2. Account visibility between users

Running Account)

Brief description:User input stream account content

Main participants:User

Prerequisites:The user has been authenticated and has an account

Post condition:Store sequential account information and update account amount

Main success scenarios:

1. Select an account

2. The system lists the flow accounts of this account.

3. Select to add a flow account

4. Enter the consumption product information (generally the bar code or name)

5. the system automatically completes product consumption information based on user input.

6. The system records the flow account information and updates the account amount.

7. Refresh the flow account list

Extension:

5a. The system does not find the product information entered by the user.

1. The system prompts the user that the product information has not been found and provides the user with the information to enter the product information.

2. Enter the product's barcode, name, and price, and select the consumption location.

3. If the location is not in the selection list, the user is prompted to add a consumption location.

4. The system is switched to 5B.

5b. The system does not find the location information entered by the user.

1. The system prompts the user that the location information is not found, and provides the user's entry of the Location Information

2. user entry Location Information

Problem to be resolved:

1. Modification of the journal account