Difference between revisions of "Dashboard"

From W3C Wiki
Jump to: navigation, search
(Requirements)
m (Editorial formatting nits)
Line 55: Line 55:
  
 
* The level of information should be structured with the following hierarchy
 
* The level of information should be structured with the following hierarchy
- general summary of the activity (business driver, supporters)
+
**General summary of the activity (business driver, supporters)
 +
**Roadmap of the activity (major achievement, coming challenges, potential known blockers or imperative deadline)
 +
**List of deliverables
 +
** Summary of each deliverable (including purpose, problem solved, companies involved, associated product)
  
- roadmap of the activity (major achievement, coming challenges, potential known blockers or imperative deadline)
+
* For each summary of activity the set of relevant references should be made available (e.g. wiki, mailing list, chair/staff contact/editors name)
 
+
- list of deliverables
+
 
+
- summary of each deliverable (including purpose, problem solved, companies involved, associated product)
+
 
+
* For each summary of activity a bundle of references should be made available (wiki, mailing list, chair/staff contact/editors name)
+
  
 
== Potential Solutions ==
 
== Potential Solutions ==

Revision as of 10:40, 4 April 2014

This wiki is about so-called dashboards where the use of dashboard is similar to a Business Dashboard as defined by wikipedia.org.

This document is very much a Work In Progress. Input from others is strong encouraged! If you are unable to directly edit this document, please send comments, feedback, etc. to the public-w3process @ w3.org mail list (archive).

Open Actions and Issues for this document are tracked by the W3C's Tracker.


What do we mean by Dashboard?

The basic idea of a dashboard is to provide at-a-glance views of a particular group or organization. The amount of detail in a dashboard varies considerably, depending on the purpose of the dashboard.

Examples of Dashboards in the W3C

Problem Statement

  • It is difficult for W3C Members to get an overview of the current status of existing groups such as their publication status, hot issues, etc.
  • It is difficult for prospective Members to get an overview of the current status specific groups they might want to participate
  • It is difficult for other Standards Setting Organizations to get an overview of the current status of specific groups
  • Groups provide dashboard type information in various ways and have some consistency could be helpful
  • Milestones in Working Group charters typically become out-of-date soon after a charter is approved by the Director. In such cases, the WG should provide current status of the group's publication status (in some type of dashboard like style).

Types of Dashboards

Within the Consortium, there different types of dashboards are needed:

  • Domains and/or Activity level
  • Working Groups
  • Interest Groups
  • Community Groups

Use Cases

  • AC rep wants to know the current publication status of Working Group X
  • AC rep wants to know the current status of Domain Y
  • AC rep wants to know the current status of Community Group Z
  • AC rep wants to know the impact of one given technology on Working Group roadmaps (or specific specifications)

Requirements

  • It should be possible to retrieve a summary of activity for a domain, a working group, a task force, a community group, a business group.
  • The level of information should be structured with the following hierarchy
    • General summary of the activity (business driver, supporters)
    • Roadmap of the activity (major achievement, coming challenges, potential known blockers or imperative deadline)
    • List of deliverables
    • Summary of each deliverable (including purpose, problem solved, companies involved, associated product)
  • For each summary of activity the set of relevant references should be made available (e.g. wiki, mailing list, chair/staff contact/editors name)

Potential Solutions