Qlik Community

Ask a Question

QlikView Documents

QlikView documentation and resources.

Announcements
Welcome to our newly redesigned Qlik Community! Read our blog to learn about all the new updates: READ BLOG and REPORTED ISSUES

SDLC of Qlikview

Creator II
Creator II

SDLC of Qlikview

I have gone through number of documents and articles for Qlikview Development Cycle. It was one of the things, which is the base of any development in IT industry. If we have proper process for any development, there are very less chances of more numbers of bugs coming in future.

So, here I have merged all the data related to Qlikview Development Process from different resources like, my own experience, blogs, article, Community etc.

Qlikview Development Life Cycle

  • (Analyse) Requirement Analysis
    • Interacting with Business Analysts and Business users to understand the dashboard, reporting and BI requirements
    • POC Application
      • § Developer working with the users will create a mock-up of the dashboard to show the users how the data will be presented on the screen.  Also discussions should take place on the type of device(Laptop,Desktop,Ipad etc.) and screen resolution where this dashboard will be displayed
  • (Design) Data Analysis
    • Data elements required to full fill user’s requirements.
  • (Develop) Development
    • Create a data model and visualizations using QlikView Desktop.
    • Create n-tier QVD architecture
    • Any object which does not provide insights into data should not be present in the dashboard
    • Any changes or expectations from client
  • (Testing) Review
    • Best Practices
    • Peer Review
    • Debugging
    • Unit Testing
    • Fine-Tuning
  • (Finalize)
    • Deployment on Access Point

This is just the basics of Development Cycle. It will be helpful for me and to others if you provide your valuable comments on this. Please fill free to add any step or any point if I have missed it in the above Cycle.

Comments
Creator II
Creator II

Hi,  I would add more to the deployment, such as scheduling, publisher setup, etc.

Also, in our area we always look to understand the bigger picture in terms of overlapping projects/business requirements and how our suite of apps align with each other.  There is a lot of overlap in the company I work in, so this may not apply to everyone.

Mike.

0 Likes
Not applicable

Hi,

I usually start the requirements phase by asking users to list all of the questions they need their data to answer. If you can get a representative sample of users from various layers of your target audience so much the better (i.e. Managers, Directors, front line staff etc). This should give you a good range of questions to be answered. This information then helps to identify the type of data required, the granularity, the kinds of charts / graphs required and can ever be used during UAT & End User Training (for example - "You asked How many widgets did manufacturing produce this month? - Well this is how you answer that question using the app that we have given you..."). We find that the list of questions can actually drive the entire process.

Also we work closely with our end users in fortnightly iterations where we review the work done in the previous iteration and plan / agree what we will deliver in the next.

Hope this helps

Robin H.

0 Likes
Master
Master

Hi Meetmrudul,

Great helpful post.

It really helps freshers in BI ,how to go about development in qlikview,

as it is iterative process and need to interact with Business users regularly to make sure

the dashboard is as per requirements and is it useful to make strategic decisions.

Regards

Neetha

Version history
Revision #:
1 of 1
Last update:
‎2015-05-22 08:37 AM
Updated by: