Browse Prior Art Database

A Relational Schema to Support Task and Workflow, Data Collection and Analysis

IP.com Disclosure Number: IPCOM000013323D
Original Publication Date: 1999-Oct-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 2 page(s) / 48K

Publishing Venue

IBM

Related People

H SLUIMAN: AUTHOR

Abstract

A design of a relational data model that can be used to store task data is disclosed. The relational data model is optimized for retrieval of task data therefrom and is extendible to add new types of task data. Each task artifact is stored with a unique identity and any view of the task data stored in the relational data model can be done through a logical view that associates these identities as needed. Today, task data is collected either on paper, or entered into various proprietary tools. The tools tend to be biased to a single analysis paradigm such as work flow, or task definition. While other disclosures Research Disclosure, March 1998, No. 40780 and No. 40781) describe how to solve the problems of collecting task data properly, this disclosure separately addresses the issue of making the data generally available for broader usage, rather than be constrained by the paradigms introduced by other tools, or by disjoint and proprietary data sources. The simple answer is to develop an extendible relational database schema that can be optimally used for data collection as well as retrieval and analysis. The logical model maps out to the following list of objects (which objects are further described in Research Disclosure, March 1998, No. 40782). By the name you can see the purpose of many objects is to provide context to other objects. project task tool unit of information task following task parallel task task input information task output information task uses tool Project references task Project references tool Project references information Project references task following task Project references parallel task Project references task input information Project references task output information Project references task using tool Each of the following entities has an identity, as well as a name and a description attribute.

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

Page 1 of 2

A Relational Schema to Support Task and Workflow, Data Collection and Analysis

A design of a relational data model that can be used to store task data is disclosed. The relational data model is optimized for retrieval of task data therefrom and is extendible to add new types of task data. Each task artifact is stored with a unique identity and any view of the task data stored in the relational data model can be done through a logical view that associates these identities as needed.

Today, task data is collected either on paper, or entered into various proprietary tools. The tools tend to be biased to a single analysis paradigm such as work flow, or task definition. While other disclosures ( Research Disclosure, March 1998, No. 40780 and No. 40781) describe how to solve the problems of collecting task data properly, this disclosure separately addresses the issue of making the data generally available for broader usage, rather than be constrained by the paradigms introduced by other tools, or by disjoint and proprietary data sources. The simple answer is to develop an extendible relational database schema that can be optimally used for data collection as well as retrieval and analysis. The logical model maps out to the following list of objects (which objects are further described in Research Disclosure, March 1998, No. 40782). By the name you can see the purpose of many objects is to provide context to other objects.

project task tool unit of information task following task parallel task task input information task output information task uses tool Project references task Project references tool Project references information Project references task following task Project references parallel task Project references task input information Project references task output information Project references task using tool

Each of the following entities has an identity, as well as a name and a description attribute.

Entity list project task tool unit of information Each of the following relationships has a many to many semantic and a unique identity of its own that does not include the identity of the source or target object.

Relationship list task follows task task is parallel to task task has input information task has output information task uses tool

1

Page 2 of 2

Project references task Project references tool Project references information Project references task follows task Project references task is parallel to task Project references task has input information Project references task has output information Project references task using tool All of the tables have a single identity column that is a unique...