Report = chicken ribs?

I have been making reports for nearly a month. It's boring and boring. Not because of the report itself, but the entire company. Neither the consultant nor the final coder paid enough attention to the report, or even regarded it as the final action of the project.

The current project has reached this point, and the efficiency of the business operation interface is unfriendly. On the one hand, the report mess is indeed the root cause. If you want to close the project, the report cannot be escaped. At the beginning, the customer said that what we wanted was a report, and we could not just read a flow account.

Obviously, the customer regards the report requirements as the most important part, and it is inevitable that we only treat those reports as a chicken ribs.

Report is one of the most important modules in the system, and development is the most difficult. developers need to have a clear understanding of the entire business process and have a thorough understanding of the database physical table structure.

So far, I have written dozens of reports, but I have really figured out the entire business and dared to say: "I know the logic of this report, what I wrote is correct and there is no problem!" Just a few.

Let's see how I made the report!

There is a database design document, holding the mouse in the E-R studio desperately from an arrow to another arrow, looking for seemingly usable fields. Tired and sweaty, then said, "Oh, my God, Consultant, we didn't find the field you said! You told the customer that this report cannot be done .". Dizzy. Why did you go!

It's not that I am willing to fall, but that the company knows so much about the report. A report is sent to three days and says, "This is a long time !". I don't know how long it takes to get familiar with a business module or the entire business process.

The boss of the company wants to see the system. The following dialog occurs:
"Can you tell me how to use the system ?", The boss of the company asked with great interest.
"Click" Add button "to go to another page. Enter the required fields. Our required fields are marked in blue !" You can click the table and demonstrate it with pride.
"Click" save "and a message is displayed, indicating that the file is successfully saved. If the file is added, the file is displayed on the add page. Repeat the preceding operation. If the file is added, click" return "to return to the query page ."
You continue your brilliant speech and are about to click the modify button. Then, if you do not select a record, the system will provide a powerful smart prompt function, "select a record, instead of the Yellow Pages.

The boss really couldn't listen: "Do you know that I am a local King ??! How much is a waste of money if you delay me one minute ?!!",
"I want to know the sales performance of our company this year. Could you show me !"
"Sorry, this report cannot be made because some fields are not designed in the database ." Your face is a bit shy, and your eyes have tears left.

Some people say that we are working on a sales system, not a report system. Reports can be made by Bi. It is simply a bandit logic. I made more than 100 orders a day. Would you like to see how many refrigerators and how many color TVs are there for a single set of one hundred orders? Is this too demanding? Not much! If someone else wants to read such a simple data, you will say, "Please pay another 10 million RMB, purchase our company's Bi system, and view the summary of orders !". Good "professional" sales. Bi is required to do such a simple task. What is your sales system required ??!!

Let's take a look at the speed of up to 3000. Someone else has a special report part and also disperses the report to each module, so you don't have to jump to the menu. I make an order, so good, I only need to enter the Sales Section, there is order management, under the Order Management is the Order Statistics Report. Even if our reports are well written, it is inconvenient for users to use them. I made an order and ran to the report to view their summary information.

I think in the demand analysis phase, a system should take into account what the customer wants to see and what kind of reports it needs, and design the system based on this. Instead of running the flow account interface, you can view the report. A report can establish a complete business logic. The data required by the report is the data that should be collected when the flow account is collected normally.

if you don't want to talk about it, drag the arrow of Er-studio to write the report. Oh, forget that there is no design document for the table used in the current report, and I don't even know what each field represents. What should I do! I guess, I guess! Genius Go go !!!