Functional use case design based on requirement document (PRD)

I told you that in the process of running a project, the use case needs to be updated dynamically. Next I'll use the examples (mobile app) to explain how to design use cases at different stages.

The requirements document (PRD) focuses on what the functionality of a module of the app is, the page presentation of each feature, what the page is doing, and what the relationship is between the different operations. The use case design based on PRD is using black box test method, and I usually use the Equivalence class division, boundary value analysis, state transition test, scene test, the operation practice is preferred to divide the module into page display, page operation, interface, abnormal flow, in each of the sub-items using black box test method to design.

Take the mobile app login as an example, the general requirements such as:

First, verify that the login pop-up scene, is definitely the user click on the need to log in to view the function, will pop up the login box. The design use cases are as follows:

1, click on the login information function when the login box (such as shopping cart, favorites), according to the equivalence class division method , the effective equivalence class is to click the login information required to log in the box, invalid equivalence class is to click No login information without playing the login box

Second, the verification page display, login mainly on a page, according to block division, as follows:

Third, the operation of the page, according to the existence of each block operations, as follows:

Four, the interface of the check, due to different applications call different interface, so do not say details, interface business logic check the best to write a separate interface test engineering verification, here the interface check mainly to do the client into the compared with his inspection, return processing check.

V. Abnormal flow

The exception flow mainly considers the client input is empty, the interface call returns the exception when the client's presentation and prompt, the display of the page without the network, the display of the page when the weak network

For example, when the password is empty, the prompt password cannot be empty

Finish the above, and then read through the PRD, the use case has covered most of the functionality, but found that some of the missing. For example, when entering a password, the password does not show the specific content, in order to replace, the login box can be point and color transformation, these points can be covered by the state transition method and exploratory test method.

Vi. State Transitions

1, the input box content from the non-change, there is no change, the application example: the Account input box from no input to have input, the right side of the Clear button appears; the right clear button disappears when the account input box changes from input to no input. Password input box from no input to have input, the right clear button appears, the password content is an asterisk, the password input box from the input to no input, the right clear button disappears.

2, the Login box color and the available state changes, the application example: the account number, password are entered, the login box from gray to orange, and can be clicked; account number, password from the input into a part of no input, the login box from Orange to Gray, from the point to become not point.

At this point, the need-based use case design is basically completed, mainly using the Equivalence class division, boundary value, state transformation, scene design method, in the concrete practice, can be combined with specific circumstances to adjust.

The overall requirements-based use case is completed as follows:

Functional use case design based on requirement document (PRD)