powerpoint presentation · title: powerpoint presentation author: paul turley created date:...
TRANSCRIPT
Transforming Reporting Requirements Into a Visual
Masterpiece
Paul TurleySqlServerBiBlog.com
Abstract and Objectives
Starting with an understanding of user objectives and business needs, we’ll talk about choosing the right visual theme for a report or dashboard; choosing the right tool and then explore techniques to deliver a functional reporting experience.
We’ll talk about reporting on different data sources such as a SQL Server data mart, SSAS multidimensional & SSAS Tabular model. We’ll also consider a choice of visualization tools like SSRS, Power View and Excel Services.
The Secret to Achieving Success in Reporting Projects:
• Find a single stakeholder to articulate all the business requirements
• Establish all requirements before beginning work
• Document requirements thoroughly and get sign-off
• Give the users exactly what they want; nothing more, nothing less
…blah blah blah(it’s not that easy)
Facts to Consider…
Reporting and BI Projects are Chaotic by Nature
You Must Exercise Discipline
Sometimes There Are No Rules
Only Guidelines
Balance Planning with Iterating
Design
PrototypeValidate
Plan
Know Your Audience
“Help me do my job”
“Show me the numbers”
“What’s most important?”
User Perception and Visualization
Report styles may depend on factors such as:• Left and right brain thinkers• Operational & analytical applications• Business culture
SharedDesktop
Reporting Tools & Platforms
On Premises Report Server
Office 365 or Power BI
(in the cloud)
On Premises SharePoint
• Excel PivotTables & Charts
• Power Query• Power Pivot• Power View• Power Map• Access
Reporting Services
Excel Services
Power BI Q&A
Mobile Dashboards
Power View
How this statement make you FEEL?
“Microsoft gives me
a lot of tool choices”
Power Pivot models
Report Data Sources
What about: Hadoop, OData, XML, Text, JSON, MongoDB, DocumentDB, etc?
Tabular modelsRelational DBMS Multidimensional
models(cubes)
Conceptual, provides structure
Simple, non-comprehensive
Requirement Documentation
Non-Functional Mockups
Formal Requirement Template
Converting Requirements to Visuals
Segmentation
Geographic Analysis
Time-series
Deviations & Outliers
Measure to Target
Contribution to Whole
Dashboard Design Essentials
Poor design is painfully obvious…
…only after it’s finished
Examples: Stephen Few, PercetualEdge.com
A great dashboard is a product of planning, interactive design and simplification
Demonstrations
Transforming Reporting Requirements Into a Visual
Masterpiece
Paul TurleySqlServerBiBlog.com