Step needs analysis
Since undertake needs analysis, whether it is his own participation or totally by itself needs a man of research, and there have been large and small project needs research experience. This week went to Shenzhen, a brokerage survey conducted a week-long demand after demand for research is complete, in fact, conclude some routine can be used.
If IT likened to an arena, no matter what the company is what business needs, learn well the martial arts miscellaneous "four five clear five-step method", you can understand the needs of users from the macro and the micro part. The reason why is microscopic part, because of specific needs, have specific analysis, but this needed to train martial arts miscellaneous, demand analysis at the macro it can be said that there is no problem.
For the analyst needs to do from the macro research, the need to figure out the four levels (for the average person needs analysis to figure out the first two levels are possible).
Four:
The first layer functional layers: carded functions of various departments.
If a system involves many departments, then sort out the functions of the various departments can help us to understand why they made the demand, even by understanding the functions of various departments of the anti so far as to question the needs of other departments.
Take a very simple example, a brokerage risk control led by the Ministry to build a credit risk management system for the realization of supervision "of the same customers, the same service, unified management," risk control unit Other business units are also incorporated into the system in the past, the demand for research phase, a business unit presented in the realization of a report query to the time required permissions departmental isolation, namely solid position data look solid income part of the closing part of other departments can not see solid look with a report when position data receiving portion.
Ye one needs to mention this is very reasonable, but the functions of risk control unit is to control the risk from the company as a whole and prevent risks, risk control unit can look at the data in all business units.
When the user needs only to mention for their own reasons, he did not think other departments, so when demand involving multiple departments, the analyst at the research phase needs to clarify the functions of various departments.
Service layer 2. The second layer: carding business.
No one reason to buy a system, for businesses that want to buy the system on the company's business systems to do it. Different types of companies or different departments, business is not the same, the complexity of the business determines the complexity of the system, if a complex business logic can be clearly combing clarity, the system will not be very complicated, but only if you really understand really understand business.
When a white business how to quickly understand the business, you can collect business-related Glossary, make sense of these terms be considered to understand the business quarter. Each business will have its own specific terminology, such as in the logistics industry, you need to know what is the freight forwarding, postal routes, head Cheng, forecasting, etc., in the financial industry, you need to know what is the pledge of shares, bonds and investment, margin trading , and information management plan, apart from not enough, you need to thoroughly understand the difference between every business and business to business, such as stock collateral and margin difference in what?
Data layer 3. The third layer: carding information.
This requires the analyst to understand some of the techniques to distinguish clearly, the demand for analysts demanding the next level. For the underlying data systems, the logic flow of data and need to sort the data, the data and the data, which are clearly sort out later, for now or later developed iterations can play a significant role.
4. Fourth layer: carded supporting environment.
After the business needs and data are clear, also we need to consider non-functional requirements, such as what hardware and software environment of the system is to use Google Chrome or IE browsers.
These are the four four five-step method of how to achieve the above four, do the following "five steps":
- According to functional organizational structure combing domain functions, such as agency / department, each job duties
- The functions of the carding business domain elements, including business terms, and the like Glossary
- Carding element according to the service business activities, such as business processes, business sectors, state information, etc.
- According to business activities such as combing operations inside and outside contact, such as business collaboration, information flow
- Depicting business architecture, information architecture, such as the user classification, traffic classification, information classification
After four and five steps to do, ask yourself a few questions to see if it really needs to understand:
- Business Objects is not clear? Users, and users of the system functional modules is whether anyone clear.
- Business process clear? People of all aspects of processing and treatment action is clear.
- Business scene clear? Each needs of business scenarios to figure out whether, if all the needs of business scenarios can be connected together to form a complete story in mind.
- The number of operational matters clear? There are a number of requirements, there are a number of kinds of roles, a total of how many reports, a number of pre-conditions for a total of ......
- Cross-sectoral business relationship is not clear? The relationship between the department and the department of business generated and what is clear.
After four five clear five-step method are done, you can outline a story needs an audience, plus details of the needs analysis (see previous article please write how to analyze different types of requirements), the details filling in the outline of the story demands it, a complete story came out.
The analyst can demand a story from scratch every night to speak clearly in demand on the control generally can not go wrong, you know, if the demand is wrong, the consequences are very serious.
Author: Vi-Vi-Fu, microblogging @ wind to the letter, a financial software company Hangzhou requirements analyst, responsible for credit risk management of securities companies demand analysis of the project.
Original article published on everyone is a product manager of @ Vi-Vi-Fu. Without permission prohibited reproduced.
Title figure from PEXELS, based on the agreement CC0