Understand customer business and customer needs

First, how to understand customer business and customer needs?
　　
Principle 1: From coarse to fine, from macroscopic to microscopic.
　　
We must first understand the full picture of the customer's business from the macro level, and then step into detail. Because for the customer's business, we are laymen, if from the business details, it is easy to lose direction, lose the core of the business grasp. At the same time realize that for a layman, our depth of detail is bound to be limited, do not expect to be able to endlessly thoroughly understand each of the details. It is impossible to have unlimited time for you to understand, two is not necessary. Because the future system will not be able to fully deal with all the details of the business, there are many things to rely on the customer's enterprise in the professional skills of the people to do.
　　
Principle 2: Collect different levels of demand from different levels of customer representatives
　　
For the high-level decision-makers, he will give you a description of a system of large functional blueprint, such as the enterprise has the overall ability to quote, can better serve the high-end customers, can support the enterprise's major business decisions, etc. for the enterprise managers at all levels, he will tell you about his management needs of this layer, such as better to carry out departmental Generate monthly reports, better business settlement, etc. for business operators at all levels, he may give you a lot of business details and operational details ...
　　
In the top-down step-by-step interviews, the description of the future system from a large black box into a number of small black boxes, and then into a transparent, clear, detailed system definition process.
　　
Customer Business Research and demand analysis is destined to be a continuous refinement of the process, do not expect an interview/research can be exhausted, and do not expect a development process can be fully meet the expectations of the customer's dream system. Because in fact a lot of demand is hidden, even users are not aware of their own needs. Only after several cycles of refinement can be more hidden in the continuous excavation, exposure.
　　
Second, how to carry out the demand research work concretely?
　　
The purpose of defining the requirements workflow in Rup is as follows:
1. Customers and other stakeholders * achieve and maintain consistency in the work content of the system;
2. Enable system developers to better understand system requirements;
3. Define the system boundaries (limit);
4. Provide a basis for the technical content of the planned iteration;
5. Provide the basis for estimating the cost and time required to develop the system;
6. Define the user interface of the system, focusing on the user's needs and goals.
　　
[Stakeholder]: The translation of English stakeholder in Rup, which is often translated as "stakeholder" in project management monographs, refers to all individuals or groups who have a direct and indirect interest in the success or failure of the project. In software projects, it often includes corporate investors, managers at all levels, system users, corporate customers, and even corporate partners and competitors.
　　
First of all, do business research. Familiarize yourself with the business data you have collected as early as possible and refine the list of questions on an understanding basis to make a questionnaire. The requirements of business research is to sink, in-depth and detailed understanding of the customer's business processes, rather than rush to complete their own requirements of the workpiece design and business model building. In understanding each business process, together with customers in-depth analysis of the implementation of the logic of the business, and record the relevant implementation of case information, collect good, tidy up, analysis of relevant reference materials.
　　
The idea of iteration should be carried out from business research, demand analysis and even project implementation. The so-called iteration, is that we honestly admit that we do not have the ability to make things perfect at once. So we first put a large part of the grasp of the place to do, and then on the basis of success in the previous to do the rest of the part, and ultimately can be infinitely close to success. This is true of the design coding process, as is the case with business research and demand analysis.
　　
Enterprise system design and development and software product design and development has one of the biggest difference, is the enterprise's demand will certainly change, the past in the change, the time of investigation will change, the system will change after implementation. And all we have to do is adapt to this change. In fact, it is precisely because we are using an object-oriented approach that we can do that. Because the object-oriented approach argues that the basic properties of an object are objective and do not change frequently, the relationships between objects are likely to be constantly changing. So we have to recognize this in business research and demand analysis, and keep the constant precipitation, leaving the variable flexibility and the autonomy of change to the customer.
　　
Everyone is to do the technology, in the business research and demand analysis will inevitably be involuntarily to consider some of the technical implementation of the problem. It is worth emphasizing that the requirements are not technology-related. Keep a faithful record of your business research and do not modify or cut the user's needs (prematurely) because of your personal doubts about the implementation.
　　
Be good at the support of clients at all levels (all stakeholders, referred to as stakeholders in RUP). Only with the full participation of the users of the future system will the project be able to ultimately succeed. A system that lacks user involvement is destined to be used even when it is finally made.
　　
One is to use the relationship between the customer's enterprise, to obtain the support of the upper level, from the top to the next research and cooperation; The second is to be in the research process for the target users to establish a targeted vision, let him identify with the vision of the initiative, actively support your research process.
　　
......
　　
(The following content withheld)

Understand customer business and customer needs