Syntrix Application Development Framework

www.syntrixconsulting.com
For Qlik Sense® Implementations

www.syntrixconsulting.com | 877.SYNTRIX (877.796.8749) 2
Syntrix Consulting Group specializes in
data reporting and business analytics
for healthcare organizations.
We provide tools, processes, and
expertise to accelerate the production
and adoption of analytic applications
in healthcare.
We are a Qlik Implementation Partner
with expertise in multiple EMR systems
including Epic.
877-SYNTRIX (796-8749)
BIAdvisors@syntrixconsulting.com

www.syntrixconsulting.com | 877.SYNTRIX (877.796.8749)
 Syntrix Application Development Framework
 Qlik Sense Development Pathway
 Roles and Responsibilities
 Layered Data Environment
 Metadata Management
 Design Best Practices
 Application Certification Process
3

Purpose
 To facilitate adoption of reusable and governed data
constructs for improved self-service capabilities, rapid
development cycles, and single-point maintenance
Goals
 To create a methodology to develop and deploy Qlik
Sense® applications
 To ensure that there is confidence in the data used in
the applications
 To provide a team structure to maintain a Qlik Sense®
environment
5

 Key Elements of Syntrix Application Development Framework
for Qlik Sense®
• Application Architecture – this is the structure of the data environment,
conformed datasets, pre-aggregated metrics, reusable components,
data models and the actual presentation layer applications
• Metadata Management – the management of the data about the data
is vital to understanding what is in your data environment
• Design Methodology and Best Practices – making sure consistent and
well thought out standards will enable you to maximize the reuse in
your environment
• Certification Reviews and Processes – this is the process to ensure
accuracy and acceptance of published applications
• Role and Responsibilities – understanding the roles and responsibilities
on the team will promote accountability
6

 Qlik Sense® applications go through the following
stages to production
• Extract – data is pulled from the source systems at scheduled
time points and a QVD repository is created
• Transform – concepts are conformed and manicured in this
environment and provides governed data concepts to be used
by your applications
• Design – design the applications on the Qlik Sense® hub using
best practices and reusable elements
• Deploy – publish to streams and provide access to the users
and groups
8

Extract Transform Design Deploy
• Define Sources
• Define Data
Requirements
• Create
Connection
Strings
• Create Extract
Data Layer
• Plan Reload
Schedule
• Create Apps per
source
• Determine Data
Security
Requirements
• Extract Data
• Create Repository
Directory
Activities
• Determine Reload
Schedule
• Define Metrics
• QVD Monitor
• QVD Status App
• Create Concept
Directory
• Create Reusable
Library
• Standardize Field
Names
• Create Reusable
QVDs
• Transform Data
• Define Reusable
Elements
• Develop
Reference Repo
• Update Library
• Define and
Document
Requirements
• Test and Validate
Application
• Define Data
Model Apps
• Define Streams
• Define Security
Access
• Communicate to
user base
• Create Release
Notes
• Update Version
Control Library
• Validate
Application
• Update Code
Library
• Publish Apps

 Extract Pathway Outputs
• This is a directory on a server that can be accessed by the QMC
• Source level QVDs are housed in this repository
• This will enable you to extract metadata about the QVDs
• Mapping files for raw level data will be centralized in this area
• Reusable scripts and expressions will reside in this structure
 Transform Pathway Outputs
• Concept level QVDs will be located in this repository
• This is a directory on a server that can be accessed by the QMC
• Mapping files for concept data are centralized in this area
• Governed metric library and data sets are curated in this repository
• Robust metadata from QVDs associated with business definitions can
be created in this environment
• Reusable scripts and expressions will reside in this structure
10

 Design Pathway Outputs
• Qlik Sense design is done in the Qlik Sense Hub from a
web browser
• All applications in the development phase reside in the
developer’s Work stream.
11
• Applications reside in the centralized repository, but can be exported
and reviewed on Qlik Sense desktop
• Images and other content that will be used by the applications will be
upload here
• Applications can be tested at this point before being published
 Deploy Pathway Outputs
• Deployments of applications are done to the Streams in the QMC
• Update application versions during this activity
• Communicate changes to the community
• Administer security and permissions through the QMC

Extract
Developer
Data Modeler
Application
Developer
QA Analyst
Business
Analyst
System
Administrator
• Create and
Manage Qlik
Extract
Application
• Maintain
Functional
Extract Specs
• Schedule
Reload Tasks
• Monitor
Repository
• Create and
Manage
Concept
QVDs
• Maintain
Functional
Specs
• Maintain QVD
Dictionary
• Ensure Reuse
Assets are
Utilized
• Maintain
Design
Requirements
• Create Qlik
Sense Apps
• Meet User UI
Requirements
• Update and
Maintain
Catalogs
• Validate Data
Concepts
• Validate
Applications
• Develop Test
Plans
• Validate
Coding
Standards
• Document
User
Requirements
• Conduct User
Acceptance
Testing
• Manage User
Expectations
• Update End
User
Documents
• Publish Apps
• Create and
Maintain
Streams
• Provision
License and
Security
• Maintain QMC
Maintenance
Plans
Individuals on the Business Intelligence team can fulfill multiple roles.

Business
Analyst
Subject
Matter Expert
Requirements
Data
Modeler
Extract
Developer
Conformed
QVDs
Application
Developer
Applications QA Analyst Business
Analyst
Test Cases
System
Administrator
Publish
Apps
Fail
Pass

Benefits
 Data can be staged and cleansed
 Create governed datasets
 Implement reusable elements
 Allows for robust and flexible security
 Ability to create metric libraries
 Create denormalized dataset for ease of reporting
 Update and maintain one source of truth
 Automate the creation of data dictionaries
16

Data Environment
• Repository Layer
 Load source data into this environment
 Create incremental loads
 Source Mapping Documents
• Concept Layer
 Sourced from the Repository layer
 Remove any unnecessary data
 Conceptualize multiple data sources into
single concept
 Create a reusable measure library
 Conform field names for business use
17

 Qlik Sense® data connection and security is set up in the QMC
 Minimal Security – Open Access
• Create connections to the top levels QVD directories (i.e. Repository,
Transform, Concepts)
• Provide access to the developers who will be working on the QVD
environment
• This is good for developers who should have access to all data
 Granular Security – Strict Access
• Create connections to the specific QVD folders
• Provide access to each QVD folder individually
• This is effective when your developers should only have access to
specific QVD datasets
18
NOTE: If you are using an LDAP account, it will add your username to the account name. It is
recommended to remove that before utilizing that connection. To do that go to the QMC and
Edit the data connection name and remove the username information.

 Develop metadata management tools
• Create tools to monitor the QVD directories
• Associate data to QVD metadata to create data dictionaries
20
Repository Concepts
Monitor QVDs Data Dictionary

 Create QVD Profile apps
 Add business definitions to your fields to create data dictionary
applications
 Use the XML in the QVDs to get linage and other useful metadata about
the QVD environment
21
Business descriptions
provide great value to
the developer

 Rename fields during the transform phase
• Make fields business friendly (no underscores or slashes)
 Add notes to code changes and if you have a tracking
number add that too
 Break script up into logical tabs
 Utilize optimized QVDs properly
• Use preceding load statements
 Use Qualify selectively and remove fields that are not
needed
 Develop coding standards and naming conventions
and follow them
 Use include files for signal point of maintenance
23

 Good interface design leads to high adoption rates
 Use clear and concise charts
24
This slide provides
excellent explanation
when to use different
chart types.

Snowflake
Schema
Star Schema Single Table
Response Time Slowest Medium Fastest
RAM
Consumption
Lowest Medium Highest
Script Runtime Medium Fastest Slowest
Flexibility Worst Best Best
Complexity Most Moderate Least

 Implement checks and balances for your development
process to achieve final signoff
 Review, test and signoff on the applications that are
published to production
 Develop checklists to ensure everything is reviewed for
each application
27
Review
Requirements
Review
Application
Determine
Readiness
Determine
Training
Evaluate
Feedback
Review
Rollout Plan
Certification Meeting

 Roles of the certification process
• Review leader (not the developer)
 Review the business and functional requirements
 Helps determine readiness of the application
• Developer
 Demonstrates the application to the team
 Explains architecture, design and functionality of the application
• Business Analyst
 Provides feedback
• Subject Matter Expert (customer)
 Determines if the application is ready for production
• Others (Jr developers and designers)
 Learn and provide feedback
28

 Review application and script, things to look for
• Naming Standards
• Data accuracy
• Reload Schedules
• Branding
• Consistency
 Color
 Navigation
 Layout
• Performance
• Maintenance Support Review
• Meeting requirements
• Review Master Library
• Properly Commented Code
29

To learn more, contact us at:
877-SYNTRIX (796-8749)
BIAdvisors@syntrixconsulting.com
30

Syntrix Application Development Framework

Recommended

Recommended

More Related Content

Recently uploaded

Recently uploaded (20)

Featured

Featured (20)

Syntrix Application Development Framework