From the user to the completion of the demand manual Wang Hui (DDXXKK@21cn.com) Technical Experts and PM 2002 IBM: DeveloperWorks Chinese Website Foreword For Demand Analysis, there are many corresponding books, but there is no specific process description, this article tells A actual needs confirmation process. Prerequisites Under the premise of signing the development agreement with the company, the company completed the company's sales staff as the key to the company's system development department, the first step --- Demand analysis. For the user, it is a selection of a number of developers. Finally, a developer is finally signed, and the process of providing a specific demand for clear demand after the development agreement - clearly telling the developer to develop a software product with what functional software . The agreed user has probably knows and has been recognized. For example, all the hardware is a PC, the client software is Windows98 / ME / 2000, and the server software is Windows 2000, the database software is SQL 20000. Alternatively or for business functions, users can recognize the regular configuration for server, clients, databases, and hardware platforms. The technical system used is generally known before performing demand analysis, or system analysts are required to understand all technical systems. Otherwise, the technical system and users understand the technical system and the user know the same, and it is difficult to analyze some think that it is easy to achieve and actually realize it if the luck is not good. For example: Restore DB2's database completely back up to Sybase. In the case where the technical system used is clear, the appropriate system analyst is selected. System analysts require a certain understanding of the corresponding technical system to be based on the corresponding analysis. Different technical systems have certain limitations, and some needs have certain difficulties in certain technical systems. If WAP (mobile Internet access) is unlikely to implement print. Although there is no unacceptable user business needs, it is generally clear that the system function has determined what extent. The extent of the use of other corresponding tools. If multi-person conducts the clear analysis, division of labor and responsibilities, and the stability of the team. Whether the corresponding planning schedule is reasonable, etc. is also a factor affecting the quality of demand. The preparation organization team before the user has established a demand research team team according to the actual workload and other situations, providing the equipment, clear responsibility, and launching the task. The system analysts prepare the corresponding document developer-based system analysts are officially contacted before the user's demand provides personnel, completes an inquiry table and demand analysis plan. Under normal circumstances, only one overall detail questionnaire, general inquiry users to clear the documentation that has been completed (if you can get and understand the best in the formal contact), the purpose of the business, the current goal, Long-term goals, current preparation, completed business function list, future system operator's business and computer technology understand the situation, ultimately operate user, current and future hardware, software and network environment. The analyst of the developer system is appropriately written in accordance with the degree of understanding of the business. However, the use of the business function details is the use of the user demonstrate its demand during the business needs research, and then inquiries according to the problem. However, sometimes the business function details ask the business function detail table inquiry due to the user's needs and the original plan. Other business related policies and regulations, technical documents, technical support personnel, etc. also have to prepare. Contact and understand the user's personnel to contact and obtain the list of personnel, division of labor, weight, work plan, working hours, holiday arrangements (especially the additional provisions within the user company), if possible, requires also available IT Personnel participate in the demand process, the actual needs If there is no IT personnel to participate, the rear changes are generally proposed by IT staff. The demand for users IT personnel should be investigated as part of business research during the demand process.
Writing plan According to the current situation, writing a demand analysis plan, clearly formal start date, intermediate stage date (more time long, no more than 3 days can be not more than 3 days), end time, person list, division of labor, required users Help, etc. The plan is sent to the user to confirm, and the plan is coordinated with the plan to work together to work together. If the plan can be written and controlled to a daily bas, it can achieve truly control to the day, then look at your ability. If it is controlled for an intermediate stage every 3 days, the delay time can make up for overtime. The plan is best to work 8 hours a day. If the plan is working 10 hours, perhaps the first delay can make up for 8 hours (24 hours a day), but then you will find that your staff is not working hard. If you want to go to the user, you have to prepare the corresponding office tools, a man-handed laptop (power socket and network interconnection should be considered) is a better resource configuration. The first day of the first day of the demand research is the first day of the developer system developer to the user's official demand research process. If it is an off-site research, the developer system developer should reach the user's location on the first day, to understand the accommodation of accommodation. It is best to rest early, ready to prepare for the first day. Generally, the first day of the morning is the overall introduction of developer system analysts and user business needs, understand the office environment, and establish a demand research process office environment. If the small project involves not many people (there are not more than 3 people in the two sources), in the morning, you can conduct 1 to 2 hours in the morning, or in the afternoon can formally began to work (the first day of the schedule is generally only half a day. operating hours). The process of researching process research recommended developer system developers have a special person's meeting record, and after the end of the daily meeting, the results of this meeting were announced and signed by participating personnel. The second day is cop or sends an electronic file to participate in the conference staff and related personnel. In order to be able to check, clear the process. Developer system developers provide users with a weekly report on users a week, telling users that there is a problem, whether there is a problem, whether user assistance, etc., this is a good way to strengthen both parties. Method. Note: The changes in the system developers in the survey process will have a major impact on the plan, and do not simply consider the problem of personnel replacement. Because understanding the business during the survey, it can be achieved by seeing the document. Three days, through discussion, 9 days to learn from the declaration, the learning of documents is not necessarily achieved. Overall research on the overall research in the process of research, must participate in the user's executive and user all personnel (including user IT staff), the first purpose is to understand the details of the user's overall demand, the second destination user staff from respective The angle also learned what kind of system is the user. If a demand provider is a person, he knows what kind of system you want. But if it is a number of people, before the developer system analyst conducts investigation, each person is just a planned need, even if it is sometimes communicated, it is generally discussed rather than the conclusion. Make business needs are not very clear. One of the best in the overall research is to make the multiplayer demand of users, and the overall research process is also a process of communicating and integrating the needs of users. If many users have confirmed that the business is quite normal before the developer needs confirmation, and the developer system analyst must reach agree in the demand research process.
Under normal circumstances, the following issues are required: the current overall business needs of the current overall business requirement requires the demand function lists that have defined the requirements rules to develop in the future development of the server, the client's soft, hardware, and performance requirements (capacity, speed, operability, etc. The user's current technician and business personnel will require users 'system and user's interface for users to require users' other requirements for users. The needs of users are fully clear and clear. The survey of each specific business requirement, if the specific demand investigation, if it is the existing document provided by the user, the developer's system analyst is only aware of the business to understand the needs of the system analyst and the business personnel can understand. Then this process is easier. As long as the system analysts understand the business documentation, and for some unexpected business descriptions are easy to understand (some business nouns have some professionalism to make additional instructions), clear the documents (data items) can. Of course, the specific details of the description instructions can see other books and file templates. The demand is not fully clear. If the user is not fully clear for his own needs, it is more troublesome to be guided and refined, then this process is more troublesome. For the user's own demand, the business should be detained from the basic business, which is carried out later for unknown service or uncertain service. For entering and export documents, the user does not have a present document in this case, this process only needs to clarify the data source that the document must be imported, if detail, the user determines the document during the demand research period, is not too Possible ---- just the style of design documents, the style is not a short period of time. For reports, the basic report requirements and data items can be explicit. Generally, this situation uses the prototype method, first make a simple one, and improve it on the simple top. For the investigation of the user's own demand, it is necessary to do every day (or 2 to 3 days, up to 3 days to interval), and sign the two sides, because the research process will add a new new After the business is analyzed, it cannot be added due to some reasons. The result of this process is 0, but for proven 0 this result may take a long time. To record this process, explain what is done during the research process, sometimes some people may say this for so long, when it comes to explain the reason. Regarding the selection of development models Sometimes the selection of models is not easy to judge, this is sometimes not available to demand and development, and the development of the developer has the development cycle, the development costs, and the user also has internal plan, company development plan and other factors Influence. Generally speaking, for application development --- to develop software, customers will actually start using the software after development and testing, then the waterfall model is used. Of course, it is natural to use the waterfall model to use the waterfall model to be independent development and customer demand in the case of clear demand. The evolution model can be used. The helical model is suitable for large software development, absorbing the concept of "evolution", but sometimes it is also used for unclear demand for users. Of course, there are other development models, not discussed herein. Noun definition: Waterfall model: Provides various software engineering activities. Including: Developing a development plan, performing demand analysis and instructions, software design, program coding, testing and maintenance. Features: Self-up, mutually connected fixed order, such as waterfall flow, grade floor. Evolution model: The first time just test development, its goal is only to explore feasibility, understand software requirements; second, based on this, a more satisfactory software product, usually given an experimental product to be "prototype" . Features: Reduce the risk of developing due to unclear software demand. Spiral model: combine the waterfall model and evolutionary helical model, and the risk analysis that is neglected by the two models, which makes up for the shortcomings of the two.
