How a program writes requirements documents

In the previous article "needs writing feelings-facing the document should have what mentality" in the simple to write how to face the document, with what mentality to write documents. Here we continue to discuss how to write the requirements of the document more in place, I said here is not in place to say that all in place, but on the description of the requirements, as the overall document in place will be in the future documentation and some discussion.
First of all to understand the needs, then how to understand the needs, more important joints than communication, many of the writing documents are mostly from the programmer to document production, more prone to err is: to a demand immediately can reflect the specific situation in the brain, or subconsciously think about how to achieve and so on, this is not very desirable. Demand is to know what customers need to meet the requirements, then how to know what the customer needs. Then ask, specifically how to ask, we discuss in other articles, through the question, we will know what the customer needs, or what the customer means, we help them through professional knowledge to organize, can be the customer's perspective to guide but do not add their own perspective thinking, Otherwise, it may mislead or unintentionally increase unnecessary project costs.
By asking what the customer needs to do, you need to consider how to implement the document. Everyone has their own document framework ideas, in the right mindset can be the information you know all in, initially do not need to consider the format and other display details. After the information in the brain is revealed, there are some rules or omissions, or even the contradictory details of their own, there are two sources of these problems: one is the customer himself to do something unclear, only know what they want, but not clear the details of their own , another is that they are wrong to understand the information given to the customer. Based on the above two problem solving methods can be done in such a way: first complete consideration of the whole, in the consideration of redundant text, and then look at the contradictions where the reason. After these work, you can see if you can sort out a text message that fits the normal logic. If you can communicate with the customer again to confirm, if there is still a problem then in and customer communication on a targeted problem solving.
Through this sort of thinking, to do the preparation of communication, on the one hand the customer is not so much time and you saw, and then some problems through their own thinking can be solved, this will make customers more happy, otherwise he will think you do not have a good to think about their needs, and your strength or attitude greatly discounted, The whole process must remember "you are not a programmer", only so that your needs can be more accurate, your understanding can basically meet the needs of customers.
These are some of the recent work experience if there is any inappropriate or wrong place want everyone to come up together to learn progress, thank you.