How can technicians determine the requirements of Web products?

The Web requirement definition involves two parts: Presentation and interaction. display is the page effect displayed when a page is opened, and interaction is performed by the user through the mouse, keyboard, the system returns a response after a touch or other peripheral operation.

The requirements for page display should be confirmed from the following perspectives.

1. Interface display. Check the display logic.

1) The display logic usually needs to consider whether the display of different roles is consistent when entering the page. If they are inconsistent, it is necessary to clarify the similarities and differences of the content displayed after different roles come in.
2) For controls with hidden content, you must confirm the hidden content, such as menus and tabs.
3) For each display unit, you need to confirm the logic of displaying data, for example, "the most popularArticle", You must confirm how the most popular article is defined, whether it is by clicking, by posting, or other logic, and also pay attention to whether the most popular has an implicit time range.
4) for the confirmation of the critical conditions in the display area, you must confirm how to display the critical conditions in case of insufficient data and how to display the critical conditions when the data field is too long.

2. Confirmation of interaction requirements

What is interaction? The page is displayed. After the user uses the mouse, keyboard, touch, or other peripheral operations, the system responds to the interaction process.

The most common web interaction is to fill in forms and mouse clicks.

We can first consider the confirmation of form requirements. The confirmation of form requirement can be divided into three stages. 1) Fill in the form; 2) submit the form; 3) respond after the form is submitted.

First, let's take a look at the requirements for confirmation in form filling:

1. For the input control, check whether the input box is required, whether format verification is required for the input box, whether there is a maximum length limit, and whether there is equality verification.
2. For the selective control, you must also determine whether there are a maximum selection quantity, a minimum selection quantity, and whether the boundary conditions such as can be left blank.
3. Pay attention to the need for convenient keyboard operations, such as press ENTER or press Ctrl + press enter to submit, press tab to go to the next form Element
4. Do you need to automatically focus on a control when entering the interface?
5. Whether to perform interactive judgment when the user moves the focus to the next control (the most typical is that the registered user automatically verifies whether the user name exists after entering the user name)

The first two points above are the confirmation of the boundary condition, the third point is the confirmation of the convenience requirement, and the third point is the user-friendly confirmation.

After the form is filled out, the user can submit the form. There are two ways to submit the form: asynchronous and synchronous. It is best to confirm the submission method to the product manager, and also evaluate whether the form submission involves time-consuming operations, if the operation is time-consuming, the product manager should be asked to provide a solution to cope with user waiting anxiety.

Finally, you need to clarify the business logic of backend processing after the form is submitted, and the prompt or page jump after the processing is successful or failed.

In addition to forms, the most common interaction is mouse clicks, such as clicking Delete link to delete a record. At this time, you need to confirm how the client responds before clicking, and how to display the result after the server receives a successful response, how to display the failure.

For a system, adding or modifying a function will often affect other function points. When you confirm the requirements, you must specify the locations where the current operation will affect and what the impact will look like, if the cache is used for performance reasons, you must specify the cache time for the product colleagues.

Summary:

The technical staff should consider the interface effect, the display logic, the background business logic, and the impact of the operation logic of the current requirement on other places.

The boundary conditions displayed on the interface, the validation conditions entered by the user, the display logic of user interaction, and the handling of errors must be fully taken into account in the validation requirement phase.

In business logic, you must consider whether the current user is assigned a role, who the operation object is, whether the requirement has a time range, whether the operation has other prerequisites, and whether the operation affects other places.