The statistical report has always been part of the system integrated software development, but the reason why the headache has to pay attention to it is that users have already made hundreds of reports and statistics, but the user does not buy, always ask for modification. Change to change the people. Not paying attention is because statistics and reports are part of the system relatively less important, users are not commonly used, and the research is not cost-effective.
We can make an analysis:
1. We have done hundreds of reports and statistics, basically cover all the combinations of all data, but the user does not buy, why? One is not the user's habits (some people have to greet each other's **); Second, the data needed by the user is very rare, essentially a combination of multiple data (here someone must crazy). Weird users are uneven, because you are not what he wants, give more giving more. What's more, some people make an universal querier, what kind of reports do you need, you can get it, and this thing is not used at all, and it's too lazy to use, 嘿! ~
2, do not pay attention, the original system integrated software attaches great importance to real-time monitoring, operation, and later joining the management factor, and then introducing the concept of workflow, and also has point OA / ERP. Can provide remote control to users, many collaborative management, not much, reports and statistical users do not have many uses, up to several reports to report jobs, so they don't study. In fact, the report and statistical analysis are very research value. It is useful to analyze historical data to predict the future development trend. This is very useful. If the user does not meet this, the system integrator should have an obligation to carry out this. Research and guidance, so that the social responsibility of the system integrator can be completed. At the same time, it is useful to record historical data. If the statistical analysis of historical data can predict the future development trend, it can really become the user. Decision assistance, truly realize user value.
How to design the statistics required by users?
1. Research users' business: need to do user interviews before starting the software, understand what work for one day to late, summarize, report, monthly, quarter, annual summary, report, each project is completed After the summary, what is needed. These are the information points for users concerned, and it is also a valid data finishing work for many years. Mastering this information is a learning process. This process will make people's eyes, and many users have a lot of soil. It is very simple but very effective. Sometimes there is extraordinary, and it is more than alert. Can see it.
2. Improve user service: Master these after analyzing, start from the perspective of the user, see how the user can easily completed the work or unreasonable work, it is not enough to finish these, it is not enough. For some government departments, use software to alleviate their workload, which is unpopular in the state of nothing, and it is necessary to refine and analyze these data, resulting in higher levels of latent in existing data. Information, such as development trends, interaction relationships, etc., make a root, have a reasonable report, this time, the user's work performance is obviously improved, and your work also has a meaning, why not?
