Using Axure RP Prototype design practice 07, registration judgment

This article implements some features of the registration page. This item is registered by username and email.

In this article, the registration page has been basically processed in the prototype "using Axure RP Prototype design Practice 03 to create a login interface."

Open the registration page and place the prompt dynamic panel of the login page directly below the current registration page prompt and align.

Prompt, some hints only one line, such as the user name is not filled, some tips have 2 lines, such as user name and mailbox are not filled. You can put 2 states in the same dynamic panel, name the different states, and let the names of the parts in the panel not repeat.

Let the dynamic panel hide, and then display when you click Register.

Write a use case for the OnClick event of the Register button.

How do I make a click on the Register button to use a state in the dynamic panel first?

Modify the use case for the Register button onclick event.

Above, try to display the dynamic panel and display a status in the dynamic panel. The next step is to tidy up the idea of registration.

Above, a hint of 7, two hints of 8, followed by the mind map based on the targeted writing event use cases.

1, the user name and mailbox are empty
--Error: Please fill in the user name
--Error: Please fill in the email address

To add a use case, set the following:

2, the user name is empty, mail input
--Mail is registered (1 means mail is registered)
--Error: Please fill in the user name
--Error: Email has been registered please change one

To add a use case, set the following:

3, the user name is empty, mail input
--Invalid message (with 2 indicating invalid message)
--Error: Please fill in the user name
--Error: E-mail address is incorrect

4, the user name is empty, mail input
--Mail not registered
--Error: Please fill in the user name

Now to think of a problem: in our mind map, there are 15 cases, now only 4 cases, the code is more.

Is there a better way to do it?

Through the mind map, we find that there are only a few cases of error, can we use this as a starting point?

Copy out a current registration page, delete all the login buttons for the onclick event use case, and rewrite the following:

Above, a username of 2 indicates a malformed user name, and 1 indicates that the user name has been registered. An email of 1 indicates that the message has been registered and 2 indicates a malformed message.

Summarize:

When the situation is more, consider using mind mapping to help design
When there are repeated parts of the action, it is possible to consider extracting the duplicated parts and abstracting them again.

Reference: http://www.iaxure.com/

Using Axure RP Prototype design practice 07, registration judgment