Humans are visual learners—well, at least the majority of us are―65% according to the Social Science Research Center.
With this in mind, it’s no surprise that data visualization is as hot as it is. Communicating data effectively continues to be one of the most important and difficult dimensions of BI & Analytics―leading to an explosion of Javascript charting libraries targeted at modern web developers. With so many options, it’s difficult to know where to begin.
Explain how application developers can get the best of both worlds by using a BI & Analytics platform that can extend visualization options to include those sourced from charting libraries?
Time to market should be emphasized*
Time to market should be emphasized*
Example of an engineering diagram.
This is a well bore diagram showing the final production hole.
It shows the layers of rocks the well was drilled through
How the casings were cemented,
Where the plugs are set along the well bore
Where the perforations are to allow the communication of condensate to flow into the production line
Emphasize the importance of embedding here
Why IDS chose Jaspersoft?
Quick Development Time
Tools to explore data
Embeddable
Extensible
Scalable
Time to market should be emphasized*
Shane to cover: Intro, Definitions & Comparison,
Key Takeaways.
There is a laundry list of items we could have put here but
We wanted to draw your attention to 3 things to think about when you leave today.
The first is know your audience. Who are you developing this visualization for? Is it for a fellow data analyst or someone fluent with interpreting data? Is it a business executive? Is it an LOB worker that will be viewing this in an operational application? Start with the audience, understand their goals and what you want them to get out the visualization, and then work your way back to selecting the visualization.
Takeaway #2. Be deliberate in picking visualizations. We just mentioned that one of the big factors influencing this is your audience. But there are also inherent psychological biases in how we perceive visual stimuli. Charting libraries are great because they give us the flexibility to create almost any visualization to capitalize on this. But just remember that you should have justification for selecting the visualization that you do. A visualization may look cool but if it’s not the most effective way of communicating that data, then use the better option. On the last slide, we’ll point you to an awesome book that can help you with this subject.
The final takeaway is consider the importance of time to market. Using a charting library gives you ultimate development flexibility. For ad hoc projects or projects with smaller groups of users this is likely a great option. But if you are deploying this to a broad audience or if it’s being embedded into an application, make sure you think about requirements around security, how you’re going to deliver those visualizations securely down to the user level, whether or not you want to give users self-service capabilities. There tends to be a lot more than meets the eye when embarking on data visualization project. Properly scoping out the requirements at the beginning can save you from having to audible and make changes mid-way through.