Browse Prior Art Database

Method for creating dashboards using abstract templates

IP.com Disclosure Number: IPCOM000238391D
Publication Date: 2014-Aug-22
Document File: 3 page(s) / 46K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for creating dashboards using abstract templates. The core idea is to generalize the idea of classes of tools in order to create templates for the dashboards, not with specific widget slots, but with classes of widgets.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Method for creating dashboards using abstract templates

An existing platform for collaborative software delivery is intended to integrate development tools, from one or more manufacturers. One of the types of integration is dashboards, on which users can assemble widgets showing information from all associated tools in one place. Dashboard templates are useful for producing useful out-of-box content for new users and projects, and continue to be useful for newly created dashboards later. The problem is that, because the platform integrates an open-ended set of tools that are not known at development time, it is impossible to create a useful template out of the box. Developers do not know what tools

will be installed. Creating a template for all possible combinations is not feasible because there are too many , and the set of tools is open-ended.

While many possible tool combinations for software development exist , some classes of tools are similar (e.g., there is more than one system for tracking defects/features). These are called Change Management tools, in general. Similarly, other domains have testing tools (Quality Management).

The core idea of the present solution is to generalize the idea of these classes of tools in order to create templates for the dashboards, not with specific widget slots, but with classes of widgets. For example, regardless of which Change Management tool is installed, a developer dashboard might typically show a widget for work item/issues requiring triage, as well as high severity items and more. As such, the new approach can generalize the template and make it abstract so that at runtime , it can find appropriate widgets from the specific tools installed and use those to populate the dashboard .

A dashboard template can be represented and persisted in a manner similar to that used for persisting a real dashboard . For example, a dashboard might persist the list of widgets contained in the dashboard, the associated settings, the arrangement on the page, and allow multiple pages of widgets. An actual dashboard instance contains concrete widgets from specific applications , usually referred to by a Uniform Resource Locator (URL), as the URLs can be hosted from other applications. A template can be represented the same way, for example:

Concrete Template:

Column 1:
- Widget: Lifecycle Management System, work items widget, with query showing list of un-triaged work items for the user


- Widget: Lifecycle Management System, work items widget, with query showing list of high severity items owned by

1


Page 02 of 3

the u...