Module 4 Data Science
Module 4 Data Science
Lecture Notes
on
Module 4
VISUALIZATION TOOLS
(21CS754)
2021 Scheme
Prepared By,
Mrs. Prathibha S ,
Assistant Professor,
Department of CSE,PESITM
Module 4- Visualization Tools (21CS754)
MODULE -3
The data scientists must deliver their new insights to the end user. The resultscan be
communicated in several ways:
■ A one-time presentation—Research questions are one-shot deals because the
business decision derived from them will bind the organization to a certainThis chapter
covers considering options for data visualization for your end users course for many
years to come. Take, for example, company investment decisions:Do we distribute our
goods from two distribution centers or only one? Where do they need to be located for
optimal efficiency? When the decision is made, the exercise may not be repeated until
you’ve retired. In this case, the results are delivered as a report with a presentation as
the icing on the cake.
■ A new viewport on your data—The most obvious example here is customer
segmentation. Sure, the segments themselves will be communicated via reports and
presentations, but in essence they form tools, not the end result itself. When a clear and
relevant customer segmentation is discovered, it can be fed back to the database as a
new dimension on the data from which it was derived. From then on, people can make
their own reports, such as how many products were sold to each segment of customers.
■ A real-time dashboard—Sometimes your task as a data scientist doesn’t end when
you’ve discovered the new information you were looking for. You can send your
information back to the database and be done with it. But when other people start
making reports on this newly discovered gold nugget, they might interpret it incorrectly
and make reports that don’t make sense. As the data scientist who discovered this new
information, you must set the example: make the first refreshable report so others,
mainly reporters and IT, can understand it and follow in your footsteps. Making the first
dashboard is also a way to shorten the delivery time of your insights to the end user
who wants to use it on an everyday basis. This way, at least they already have something
to work with until the reporting department finds the time to create a permanent report
on the company’s reporting software.
You don’t want to send enormous loads of data over the internet or even your internal
network though, for these reasons:
■ Sending a bulk of data will tax the network to the point where it will bother
other users.
■ The browser is on the receiving end, and while loading in the data it will temporarily
freeze. For small amounts of data this is unnoticeable, but when you
start looking at 100,000 lines, it can become a visible lag.
Multiple reasons why you’d create your own custom reports instead
of opting for the (often more expensive) company tools out there:
■No budget—When you work in a startup or other small company, the licensing
costs accompanying this kind of software can be high.
■ High accessibility—The data science application is meant to release results to any
kind of user, especially people who might only have a browser at their disposal—
your own customers, for instance. Data visualization in HTML5 runs fluently
on mobile.
■ Big pools of talent out there—Although there aren’t that many Tableau developers,
scads of people have web-development skills. When planning a project, it’s
important to take into account whether you can staff it.
■ Quick release—Going through the entire IT cycle might take too long at your
company, and you want people to enjoy your analysis quickly. Once your interface
is available and being used, IT can take all the time they want to industrialize
the product.
■ Prototyping —The better you can show IT its purpose and what it should be capable
of, the easier it is for them to build or buy a sustainable application that
does what you want it to do.