Discussion board where members can get started with QlikView.
I'm trying to find a resource (document, paper, book etc) which describes in some detail the stages involved in building a QlikView application. Say, from Proof of Concept through Design and Development to Implementation.
I have a copy of QlikView 11 For Developers, which is excellent but it only really covers the design and development aspects of the life cycle. It would be useful to read up on requirements gathering, KPIs, testing, implantation.
Visit community for this and refer the sample application which will help you for the design and development concept or for proof of concept work on data modelling ,UI design and KPI finding will help you.
Hope this helps
Thanks & Regards
It depends on the level of detail you are looking for. In the attached document you find a summary of an enterprise environment. This document also describes the QPM (QlikView project methodology). This is based on Prince2 and Agile project methodologies.
For KPI requirements you can use different methods. One is described by Kimball: Design Tip #160 Think Dimensionally (Beyond Data Modeling) - Kimball Group
More information and tips can be found on this site. Also check the BUS-Matrix methodology of Kimball in which you can make an inventory of the dimension and facts.
Pick a model - Waterfall / Prototpye / Incremental / RAD etc.;
Pick a methodology - RAD / JAD / Agile / XP / CMMI etc.;
Plot your business / data model - user stories / test driven / UML etc.;
THEN you can start working out the (generic) lifecycle of a project, until you hit the real world...
Well you obviously know what you're talking about. Sadly, I don't. Which is why I asked the question in the first place. An introductory resource of some kind would be a good starting point.
In this case talk with your account manager to provide you documentation on SAFE or QPM methodology that Qlik Follows.
I think James illustrates the issue quite well. There are no rules regarding the design methodology and lifecycle for QlikView. Usually, it fits in with existing I.T. practices within your company.
That being said, assuming the data is readily available, it does lend itself to RAD (Rapid Application Design) or JFDI ( Just Do It - I'll leave you to guess what 'F' stands for !) which can be played back to the project sponsors on a regular basis.