IMPROVEKIT

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

"There is the desire of a consumer society to have no learning curves. This tends to result in very dumbed-down products that are easy to get started on, but are generally worthless and/or debilitating" -- Alan Kay

Datasources

Zeppelin application works from a data source for the predefined KPIs. This can be fed from local data files or through a connection to Jira.

As for the data files, an unlimited number of them can be used. Each desktop can have its own source/repository. Select which one to use via the Connection | Connector | DatasourceInterface -> file name

The content of the data file must be delimited by TABS (and have the extension *.tsv).

The application provides three examples (FULL) with real data that can be used to create your own data source (for example via a spreadsheet). Certain fields are required (see Data Sources), and custom fields are allowed.

In the case of the Jira server plugin version, you do not need to configure the connection (it runs within the web browser session), but in the case of the Jira Cloud version it is necessary to indicate in the Preferences | link:

  • Jira server address: method (http/https), server name[:port][/path]

  • Jira user to establish the connection to the Jira server

  • Jira password (it is encrypted)

Depending on whether it is the first time entering the application, a default project for the user will be determined. The procedure allows the application to estimate the project (by reading the KPIs data for the projects of which the user is the leader and considering those with the highest volume), or allowing the user to select it from the list of their projects. This value can always be edited from Preference | Explorer.

Another important setting in this category is Max number of months (0 all) for reading Jira project data.

All the configuration can be saved together with the image so that it is not necessary to repeat this process later. The user can edit the Story, create new Morphs with Signals using the existing KPIs or new ones created by the user using the domain language.

Important Application Files

bundles

script bundles folder

prefs

knownServers

contains server configuration files

knownServices

contains service configuration files

locale

english/spanish dictionaries

prototypes

folder where the "prototypes" pages (templates) are stored

uploads

upload files folder (legacy version)

configuration.json

file with definitions of key/value mappings (Maps)

kpi.json

file with predefined KPI definitions (Library)

data_ind.tsv

data file example 1 (industrial domain)

data_mov.tsv

data file example 2 (mobile telef domain)

data_soft.tsv

data file example 3 (software development domain)

index.html

Zeppelin Web home page

zeppelin.kpi

KPIs file (Library) of the user (using connection to Jira they are saved in Jira)

zeppelin.configuration

configuration file (Map) of the user (using connection to Jira they are saved in Jira)

zeppelin.image

cross platform image file of the application (allows to persist the state and retrieve it exactly)

Steps

In summary, a possible application lifecycle flow could be:

Setup

  • Complete Preferences

  • Generate your own data file (to know the application three complete examples are provided)

  • Complete the Maps

Explore

  • Do a Scan or open a Morph from the desktop menu

  • Use the Signals tool

  • Analyze data and system activity from the Halo menu of a Morph

Analyze

  • Add data pages to History

  • Write down the data

  • Establish baselines and process limits for monitoring

  • Add another type of pages to the Story (text, morphs, etc)

  • Argue using statistical tools and activity patterns

Share

  • History or pages as files

  • Publish an image to web (local network)

Develop

  • Create KPIs if necessary (in many cases it will not be necessary, a Library with typical indicators is provided)

  • Create more sophisticated scripts using domain specific language, which can be used as KPI sources or directly reusable as bundles from the menu

  • Create multiple desktops (each can have its own data source) for different purposes

  • Create multiple files with different Stories (accessible as shortcuts or from the menu)

  • No labels

Contact improvekit@gmail.com