1. What is the demand
In general sense, the definition of the software industry demand may be caused by the "demand side" in words, oral, or diagram of the expression "feature on how to do" other avenues proposed.
2, the demand for what is the problem
Software development industry often caught in a dilemma, obviously a demand made in accordance with the demand side, one by one to achieve, and why the demand side is often not satisfied, done and immediately made a bunch of changes, both sides made a belly opinions
3, what the real needs are, how should analyze
Should grasp the real needs of these key points, "aim", "manner", "test", "result"
One by one to explain,
Objective: the nature of demand, this is what needs to be done, a lot of this in the analysis of the demand in both made it very clear that the analysis of user requirements to mention the motivation, what is to be achieved. Examples of carriage and take a classic car, is to demand a faster horse, but in fact if given car program more in line with demand. Software development process such examples are common, such as customers want to add a form in a position to achieve at the same time to browse this page, by the way can submit a what, in fact, if given a new demand for this feature module, a separate entrance on the home page, or a special page, so from the promotion or from the appearance of the page is more reasonable.
It boils down to this: the purpose of analysis, which lead to a variety of implementations, merit-based. (Often mentioned as equivalent itself needs certain one implementation, need to be traced back to the original node, and a variety of paths found)
Way: and purpose of a chain, the purpose of export, rather the way determines the outcome of the latter meets the purpose.
Testing: Why is there a test? Here is the validation test requirements analysis. To confirm the demand side of things past are documents, pile design. But the details are not reflected, the customer is in accordance with their own imagination to fill these portions of the brain, resulting in what is the result? It produced two needs! ! Do you think is a document + UI + complete demand that would not directly reflected in the details, a customer thought the document + UI + brain needs its own complement of detail. Needless to say it back.
So how should you do it? Another term to understand, and performance. The system is in a way true to what to customers, allow customers to maximize the understanding of the software you're about to do, the effect is like.
Business high-fidelity prototype + detailed presentation. Follow Anmo than would send some specific cases, this is actually a sandbox exercise process software, and customers to scrutiny.
Results: The result is a final node 3 or more portions. What is the result depends entirely on the front part is how to do.