Summary 1. How to effectively identify the needs with the customer?

Summary 1. How to effectively identify the needs with the customer?

The afternoon of September 2 received a notice to JCZB to work. The goal is to use the SSH framework to implement a completely new system. Because SSH just finished, have done project, so the heart is more nervous. But, after all, it was a very rare opportunity for me, so I accepted it willingly.

September 3 is the first day of official work. PM the manager arranges each person to do a small project.

I got the "enterprise Social Security Arrears Inquiry System", the need to receive documents. There is only one page of paper. Another corresponding prototype. So, I started to make full use of my imagination to understand the needs of customers. And on the basis of the original expansion.

Once done the project is the demand has been determined, just to do it can be.

This time is different, the demand is also need and customer to determine.

Communication is also a big challenge!

as was often heard: customers only understand the business, do not know how to achieve.

And as a program ape, we just know how to do it with code, not necessarily what the customer really wants. In fact, the customer does not know what they want, so after and customer ditch through the main business, only need to draw prototypes and determine the requirements of the document, to find the customer can be determined. Although. It's easy to say, but it's not as simple as it should be when it's really realized.

September 11, with the prototype and requirements of their own design documents, with the manager to determine the needs of customers. In the process of communication, more and more found themselves too taken for granted.

Just think about the problem according to your own way of thinking, and do not stand on the customer's point of view to understand the business.

On the contrary, customers in the process of telling the business, help me comb the needs.

It's also a good explanation: a paper file kills people! There are only static documents and prototypes. Easy makes people ambiguous. Of course, it is better to communicate with customers in person and clearly understand the needs.

But. Communication is inconvenient due to various reasons.

Because of the documentation, it has become a way for customers to communicate with us. This also explains the importance of writing documents! The documentation must be rich. what function does the user need? Order of operation successively? What are the limitations of each step? Be sure to be clear-minded.

The manager also realized that he had only been busy with his work before, and had not communicated with the client.

Originally thought very easy business, the result is our understanding has the deviation.

Cause this line to be fruitless. The most reluctant to let the manager see is: I am guided by the mentality of learning to do the project. Extend the functionality. And for the manager, the price has been discussed. Functionally, it is only simple to implement. Different positions, so ...

It's a surprise!

It should have been determined by PM after we were only responsible for developing the requirements.

As a result, PM said the project was communicated directly by me and the client. The results of the communication need to be collated into the required document feedback to PM.

It's good to exercise your communication skills with your customers.

for the next one weeks, the prototype interface was designed according to the customer's requirements, and the requirement specification was written in accordance with the template given by PM at the same time. Then feedback to the PM,PM revised document, through the text + Phone + video guide way, and I communicate. And pointed out some need and customer identified problems to me to do. Plus the manager's initial acceptance and guidance, the three people and my coupling degree is too close, finally led to the requirements of the document and the prototype interface revision of more than 15 version number. It's called a tangle.

No wonder design patterns always say: decoupling, decoupling. Such a high coupling, I am afraid that only the people in the deep experience it!

Here are some tips to share with you on the process of identifying requirements:

The general process is this:

1. What functions do you want to achieve by communicating with your customers first?

2. Collate a coarse-grained requirement document and design the prototype.

3. Find the customer to confirm the prototype and sign the made his mark on the requirement document.

4. Cycle the above steps

How to communicate with customers?

1. what function does the user need? What data does the user provide? Does this data enable the functionality that users need?

2. Listen to the customer's request. Use your own language to listen to the customer repeatedly.

Recommendation: Record and organize after saving.

3. How often the software is used, how long it is used, and how much data it is (for example, the maximum number of records uploaded per month) for later optimization.

And who uses this system? Involves the administration of permissions.

4. Terminology in the area of specialization must be understood. Type, whether unique. such as: "Code certificate Number" = = "Organization Code certificate Number"

How do I write a document? all the people can read. and correct understanding is a good document.

1. The most important requirements are: Document format, font, rating, indentation, font size ....

Required Basic skills: annotations, revisions.

The most important thing is: don't have typos!

2. Use popular language to describe the narrative, logic should be clear, concise, do not have ambiguity. As far as possible with the picture/prototype + text descriptive narrative form to show the customer.

3. It is important to highlight the focus . For example: Do you want to save historical data? Be sure to ask the customer for confirmation. Otherwise, you will encounter a situation where customers require extended functionality. But none of the original data exists.

1) another. "uploaded" file that is not "confirmed". "Delete" can be uploaded again. Files that have been "confirmed" cannot be deleted, please make sure the operation is correct. to upload.

2) Another: The system in the monthly upload of the latest documents, are not retained historical documents.

4. Clear control .

There are a lot of situations in describing a phenomenon. Can be used to extract the public parts, compared to the difference between the way to compare.

1) upload two times a month four insurance documents (for the first time in arrears, the second is a paid document)

2) upload two health insurance documents per month (for the first time in arrears, the second is still unpaid documents).

5. Example : It is very difficult to describe a narrative business. It is not to be explained clearly by examples.

6. Cue information template : use if necessary. The prompt information is given by the customer or manually entered by the customer.

such as: Set up the expense prompt information template, do not owe fee prompt information template.

7. Upload the file : If you upload Excel and so on, before uploading to pay attention to version number compatibility issues, what fields, data format requirements. The classification of upload errors needs to be enumerated and identified with the customer

8. Fault-tolerant processing .

All the things in the system can be changed manually, do not write dead.

9. Flowchart must keep the logic of thinking rigorous.

First there is a diagram, after the description.

how to draw a prototype? Axturerp is used here.

1. Style to unify:

Assuming that the subsystem (small module), must be modeled after the basic system style to deal with.

This system internal style, tonal also must unify, these are the most important.

2. Interaction between pages:

Not just to display static pages, but also to focus on the interaction between the interface.

Simulate real-world scenarios with fake data. Although. Just a prototype, but make sure the customer feels the same as the real operating system.

3. Friendship tips must not be less:

What can I do with this interface here? How does it work? What needs to be stressed?

some experience in the work is taken out and tidied up. Hope can help you to work efficiently. To do well in demand investigation is a strategic decision, its importance is self-evident.

Summary 1. How to effectively identify the needs with the customer?