First, the importance of demand acquisition 1. Requirement Elicitation is the main body of the demand engineering. 2. For the proposed software product, the acquisition requirement is a process of determining and understanding the needs and restrictions of different user classes. 3. Get the user needs in the middle of the three-layer structure of the software demand. It describes the tasks that users need to be completed by the user. From these tasks, analysts can obtain specific software feature requirements for system activity, which help users perform their tasks. (Service Demand from Project View and Range Document determines user needs,) 4, demand acquisition is the first step in the bridge between the problem and its final solution. 5. Get demand to get a concentrated in user tasks - rather than concentrating on user interfaces - help prevent development groups from damage due to problem processing problems. 6, demand acquisition, analysis, writing demand specifications and verification (4 processes developed) do not follow linear order, which are separated, increment, and repeated. When you work with our customers, you will ask some questions and get the information they provide (demand acquisition). At the same time, you will handle this information to understand them and divide them into different categories, but also link customer needs as possible software requirements (analysis). You can then make the customer information structure and write a documentation and schematic (description). Next, you can let the customer represent the evaluation document and correct the existing errors (verification). These four processes run through the entire stage of demand development. Second, the guidelines for demand acquisition 1, try to explain the assumptions held by our customers, especially those that have conflicts. 2. Try to use all the demand information available to use. Source 3, after each discussion discussion, will note the items discussed (I T E M) and participate in the discussion user comments and corrected. 4. Try to understand the user's thinking process used to describe their needs. Fully understand the process of making a decision while performing a task. 5 to avoid the influence of immature details. To ensure that the demand discussion is concentrated in a suitable abstract level. 6. During a gradually detailed process, repeat the user's needs to determine the user's objectives and tasks, and form usecase. Furthermore, the task is described as a functional demand and non-functional demand.
