Qlik Sense

Business Glossary

Business Glossary defines main business terms and their intended use for all business operations.

Automation of Metadata Creation

Asset metadata can be created using rules.

Business Context

Allows customers to record metadata about tracked third parties which can provide useful business context, such as data types being shared with the third party.

APIs and Integration

Has inbuilt APIs allowing access to the database layer without having to go through JDBC/ODBC.

Metadata Design

Ability to define an organization-wide metadata schema, design its structure and constituent members (metadata tag values).

Business Rules and Event Management

Includes modeler-editable business rules engine, rule library, and reporting and optimization.

Data Monitoring and Administration

Includes data progress, data systematic review, and error monitoring.

Data Lineage

Metadata describing data source and consumption points, movements from the source to consumption, and any transformations happening during this journey.

Collaboration

Includes ability to view, share and direct work between co-workers in real or near real-time.

Hierarchy Management

Ability to manage taxonomies and organizational classifications.

Breadth of Features

Users prefer feature rich software that enables them to perform diverse series of tasks. This data expresses user satisfaction with the product's breadth of features.

Ease of IT Administration

This data indicates whether IT personnel will be able to resolve issues and perform configurations efficiently and effectively.

Business Value Created

Software needs to create value for employees, customers, partners, and, ultimately, shareholders. This data expresses user satisfaction - or lack thereof - with the product's business value.

Ease of Customization

Don't get bogged down in a difficult customization; use this data to make sure you can easily achieve the functionality you need for your particular situation.

Ease of Data Integration

Use this data to determine whether the product will cause headaches or make data integration easy.

Quality of Features

Feature quality is just as important as quantity. Use this data to determine if this product will do what you're purchasing it to do, easily, intuitively, reliably, and effectively.

Usability and Intuitiveness

End user learning curves cost the organization money. Pay attention to your end users' technical ability to determine how important UX is in your purchase.

Ease of Implementation

Successfully implementing new software is necessary to realize its full value and promote end user adoption. This data indicates whether or not the product is easy to implement.

Availability and Quality of Training

Effective and readily available training enables users to get the most out of the software you've chosen. Use this section to make sure your vendor's training programs and materials measure up.

Product Strategy and Rate of Improvement

Vendors who don't stay on top of emerging needs and trends won't enable you to meet your business goals. Use this data to separate innovators from imposters.

Vendor Support

The importance of vendor support will vary for each organization depending on internal capabilities, but there will always be issues that only the vendor can resolve.