Personal software process 4 Function Description and user experience design

Updating the daily line is a data import feature that we often encounter.

This is the description of this function:

When users use the system for the first time, they need to install all the historical data from the Shanghai and Shenzhen stock markets to the current year. These data can be obtained from a securities market software, is a binary file in a certain format. Afterwards, after the transactions in the two cities every day, the user must update the daily quotation of the day. Of course, the user may also update the daily quotation of the past few days in a single time. Only when users update the daily data lines can they build a complete and accurate data base. All our analysis work is based on these daily data.

In fact, you only need to make a simple description to find out the purpose and specific application scenarios of this function.

 

Inevitably, we need to design user experience, which is the prerequisite for converting functions into a series of development tasks. The so-called user experience design can be simply understood as part of the interface design. The interface design includes two aspects: 1. How to make it more beautiful; 2. Set the minimum functions to meet all user requirements. The latter can be simply understood as "user experience design ".

We can perform step-by-step deduction based on the functional description, followed by the entire thinking process. First, we need to list the operations that users may need and possible problems:

1. You need to select a quote file for each daily update and start the update.

2. The user may misoperate, and the selected file is not a real quote file.

3. When a user generates a quote file from the analysis software, it may only include data of one market, or data of other markets such as futures and Hong Kong stocks.

4. The user may not be able to remember whether the daily quotations for the last 10 days have been updated.

5. You need to view the update progress when updating the daily routine.

6. Users may not have any confidence in the data stored in the system. They are ready to re-install the historical data from the first day of the two cities.

7. The user may update a file twice, or some data has been installed, but another market file selected by the user contains the data.

 

In view of the above situation, we can simply design the interface elements. Of course, there is no need to consider the appearance of the problem here, just pay attention to: 1. Can all problems encountered by users be handled; 2. Is the interface the simplest and easiest to understand when it can handle all problems. After a simple thought, we can get the prototype of the interface. here we can use the VC 2010 dialog box designer to draw a simple sketch as follows:

 

 

 

In the first line, the "date" section, you will be able to see the start and end dates of the currently installed market data. After each installation, refresh the data in real time, in this way, users can always be aware of it. The following line is easy to understand. On the left side is the control of the selected file, and on the right side is the start Update button. The third line is the text information report area of the progress. When you first enter the interface, you should be prompted to select a file. The fourth line is the progress bar. After the update starts, the progress bar will report the update progress. The next two buttons are: the first is to delete the latest five-day line, and the second is to delete all the daily lines.

There is no need for too much analysis here. We know that this form of interface can cope with all the situations that the above users may encounter. CainiaoProgramPersonnel can easily ignore the two parts: the start and end dates and the progress period area in the reporting system.

 

Some senior project managers may not care about such things. Why? "You seem to have designed the interface too early. But to be honest, how can a Project Manager assign development tasks to the programmers of the team if he cannot show the form chart as quickly as possible? As a result, scholars often say that project management masters do not need to understand programming. In the software field, or even in any other field, this is a nonsense. In fact, a team does not need to be a designated person. Everyone needs to clearly and easily know what they are doing today, what they are doing tomorrow, and how they are doing right, that is, what standards are, how can a layman use his imagination to achieve this? A lame programmer can never be a competent project manager. Just like a person who has never touched a gun, how can he direct a thousand troops to fight? Of course, the company manager does not understand the technology at all. Why? Because he can encapsulate this piece, the Technical Director will be responsible for it, the company manager will not point to the technical team for every job.

 

After the user experience design is completed, it is very easy to determine the development task:

 

The above is the list of tasks for the first function. Of course, some TFs terms are very hard to translate. For example, the stack level is actually the development sequence. User scenarios are just functions. Ignore it, we simply assign these tasks to different members of the team, and the Project Manager can start to work as an invigilator easily.

For this function, I pay more attention to a simple repeated test, that is, to install a file cyclically, delete all the daily threads, and install the same file. This is repeated multiple times, to determine the stability of these two functions. Because of the need to display the progress, it is best to update the daily line operation in the background, so that the interface will not be frozen, so this out-of-order test is a test of this part of background operations.

now, we have fully explained the entire process from project startup to programmer writing Code . In fact, there is not much extra work, but the entire development process will be more standardized in this simple mode. If you still have time and interest later, you may have a complete description of the development process and record the process of learning VC ++ 2010.