Use case design based on technical solution

The previous article introduced the use case design based on the requirement document, mainly using the case design method of black box test. Previously mentioned use cases in the entire project process is dynamic update, gradually improved, after the requirements review of the use case preparation, the project will be technical program review, after the review, the need for a technical solution to complement the use case.

I still use the login as an example, because each development design of the different scenarios, in this column a general common scenario, based on the scheme to do use case design, the essence will be, other mastery.

The sequence diagram of the successful login is as follows:

The timing diagram for login failures is as follows:

Analyze the sequence diagram, the steps are clear, the client's main work is divided into several parts:

1. Draw the Login interface (UILabel, UIButton, Uitextfield)

2, receive user input user name, password, send login request to server

3, the server returns successfully, processing the login successful callback

4, the server returned failure (user name or password error), draw the verification code interface, receive user input verification code, send to the server

5, the server returns a failure (not a user name or password error), the execution of the login failed callback

Once the steps are clear, you need to refine the use case for each step.

1, Draw the login interface (UILabel, UIButton, Uitextfield)------------This step the client mainly completes the UI drawing work, need to pay special attention to several properties of Uitextfild: Clearbuttonmode ( Input box Clear button mode), Keyboardtype (keyboard type), Securetextentry (is safe mode, password input box to be set to Yes), the use case is as follows:

2, receiving user input user name, password, send login request to the server------------This step is mainly to accept the user name, password verification, and then assemble the request, it is necessary to pay attention to the input of the empty processing.

3, the server returns successfully, processing the login successful callback------------because each module is not the same, you can do different checks according to different modules.

4, the server returns failure (user name or password error), draw the verification code interface, receive user input verification code, send to the service side------------draw the verification code (Uiimageview, Uitextfield), Verify the properties of the Uitextfield corresponding to the verification code here, no special check points for assembly requests

5, the server returns failure (not a user name or password error), the execution of the logon failure callback------------primarily the form of a popup toast.

At this point, the design of the use case based on the technical solution is almost complete, some from the point of view of the white box code, some from the point of view of function, but the core points are based on the development of the listed implementation of the decomposition into a module, each module complements the use case.

Use case design based on technical solution