Now that we've gone
through the theoretical part of QlikView use cases and user types, it's time to get practical again. To continue, open the Airline Operations.qvw
file we've been working on. We will build our exercises upon the previously created data model and frontend.
If you've not followed each exercise in previous chapters and don't have an up-to-date document, don't worry. Take the file named Solution_Chapter 6_Airline Operations.qvw
, which is located inside the Airline OperationsApps
folder; create a copy for back up, and rename it to Airline Operations.qvw
.
When we look at the document we have built so far, we will notice that this does not yet cover the Dashboard, Analysis, and Report use cases. That's why, in this section, we will expand on the various charts that are available in QlikView, while also applying the DAR principles.
First, though, we need to take a better look at the business requirements set by HighCloud Airlines.
After requirement workshops and interviews with the HighCloud Airlines' executive team, Sara has distilled the following KPIs:
Besides these requirements, there is a need to further analyze the data. While the workshop and interviews weren't conclusive about the exact analytics requirements (they rarely are), there was consensus that at least the following areas should be investigated:
In addition, the current metrics currently shown on the Dashboard sheet should be moved to the new analysis section.
It was also decided that the following two reports should be available: