"Mastering the demand process" read the note one

Demand must be ready before you begin to construct a thing. Much of what is described earlier in this book is how to know these requirements and ensure that they are correct.

The diagram in the book is very concise and tells us the relationship between demand analysis and system analysis in the development process. In the early stages of development, or in the preparation period, demand activities dominate, we need to make a lot of detailed analysis of the existing information, to find out what our products are to do, need to have the quality, there are no other restrictions and so on. In the middle and later period, after the demand was determined, the system work gradually occupied the main position. Many software failures, are wrong in the pre-demand analysis, so there is a correct demand, is very important.

Requirements are broadly divided into functional and non-functional requirements, as well as constraints. Functional requirements, as the name implies, is to provide users with functions, products must perform the action, is a product of the most basic hard indicators. Non-functional requirements are an upgrade of functional requirements, which has a higher demand for the quality of products, not only to achieve basic functions. The limiting condition is the global requirement, which applies to the whole product. The requirements Analysis document also has a lot of rules to follow.

"Mastering the demand process" read the note one