Software Requirements Best Practices read Note two

Demand capture is the first activity in demand development, and each team must improve the effectiveness of demand capture, with a focus on planning and science.

The process of demand capture is the process of dealing with people, need to capture needs analysts actively to obtain demand, is scattered nets fishing, rather than recreational fishing; When asking questions to the user, be good at focusing on the topic of the interview; The user needs is an iceberg, there are many potential needs we are not easy to realize, Understanding business scenarios can help demand analysts understand the needs of users in a deeper sense. There are many ways to capture demand, (1) User interviews: The most common, most basic requirements capture technology, direct and effective, flexible form, but to avoid time-consuming and user information of the one-sidedness, the most common interviewees include senior management, middle management, Operation Layer and technical team four categories. Before the interview to have a detailed user interview plan, the interview should be good at arranging the problem sequence, can be used according to the situation pyramid structure, funnel structure and diamond structure organization problems; (2) User survey: Wide range of survey, can get more people's feedback, but not enough depth, easy metaphysics, It can effectively overcome the one-sidedness in user interviews, first interview and then investigate the most reasonable. (3) Documentation archaeology: detailed and intuitive understanding and analysis of data flow details, but easily misleading. In addition, there are storyboards, on-site observation and joint development, make full use of these methods can be a good analysis of requirements.

The demand capture process generates a lot of information that needs to be methodically documented with some useful tools. The task card is a kind of recording tool which is very suitable for the information collection and collation of business activity level, and the scene description can make the requirement staff abstract and organize the task according to the information, and also the user story, Volere White card is also the record tool.

Demand analysis is the core work in demand engineering, and demand modeling is the main means of demand analysis. Demand analysis is actually business analysis, first decomposition, re-refining, in the process of eliminating contradictions. Behavioral requirements + Structural requirements form the core of the overall requirements. The requirements modeling process is more important than the modeling results, and modeling can help us visualize the system according to the actual situation or the style we need, providing a non-root hair that details the structure or behavior of the system, and a template for guiding the system's construction. The requirements analysis phase is divided into two periods, the task of the first cycle is to clarify the requirements of the structural framework (class domain diagram) and the behavior of the context (flowchart and use case diagram), the second cycle of the task is to the use case model, the domain model identifies the use case, the domain class details to fill. To choose the right modeling tools based on the tasks you want to accomplish, UML is a unified, standardized modeling language that is widely used. Each business event is triggered by a business process, where business process analysis is performed on each business event, the analysis and identification of existing business activities, and the identification of relationships between business activities. Data flow diagram is also a modeling method, there are 5 kinds of basic elements, in order to express the processing information processing process, need to have a hierarchical structure of data flowchart.

Requirement description is the process of documenting the results of demand capture and analysis. In describing the requirements, the most common description style can be divided into natural language, graphical model and formal specifications three, according to different projects, software development team to choose different style combinations. There are several typical requirements specification template, explaining the "Communication decision content, Content decision format", to create a template in line with their own project characteristics, team characteristics.

Demand verification is the last step of demand development, the goal is to find as many errors as possible, reduce the amount of waste due to the error of the demand, the main means of demand verification is review (review, review), there is a different degree of formality review, review has a complete process, including planning, convening a general meeting, Prepare, convene review meetings, counter-attack, track 6 stages. To do well in demand verification, it is necessary to do the corresponding work in 5 points of thought, method, language, personnel and content, otherwise it will have many negative effects.

In recent lessons, teachers are also capturing the requirements of the content, this part is very important, through a number of cases give us to analyze the needs of the capture process should pay attention to the problem, capture the method, and also do the practice of using user interviews to capture demand, through a specific person to a project interview, more effective, Get full access to requirements and help us understand demand capture. In the course of time may be based on a few scenarios can not be very good understanding of the case, under the class through reading, do practice can consolidate the content of the class learning, there is a deeper understanding.

Software Requirements Best Practices read Note two