Browse Prior Art Database

Checklist overview manual processes Disclosure Number: IPCOM000177773D
Original Publication Date: 2008-Dec-30
Included in the Prior Art Database: 2008-Dec-30
Document File: 2 page(s) / 28K

Publishing Venue



Immediate feedback in software applications

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Checklist overview manual processes

Disclosed is a software component that generates immediate feedback in software applications. This component gives immediately feedback of a task completed by a user in a certain software application. The action must be part of the workflow and the workflow has a defined start and end action. This component can be plugged in (coupled) in any software application containing a defined workflow.

The "immediate feedback" component is designed to inform the user about how the user is performing and advancing within a sequence of actions. One important feature is that, by comparing the user's performance with the performance from other users, it alerts the user on how the user could improve.

The application gives the user feedback after each action so that the user can immediately readapt, if necessary, in the coming action. When the user has finished the last action the final feedback is given showing the overall performance for the process.

So the basic elements of this software component would be:
a) Actions: Each step within the work-flow or sequenced actions
b) Users: The human performers of the actions
c) Indicator: The defined dimensions that are measured and compared for each action.

After each completed user action the feedback is given immediately in two-fold:
1. Feedback on the user action
2. Feedback on the completed actions

This sub-application can be used in a number of applications, which have a work-flow with defined start and end action. For example:

- Completion of multi-page forms

By giving the time the user takes to fill one page of the form compared to the average time of the users to fill the form.

- Tests

By giving the score of the answered question and the score of all answered questions.

- Etc.

The technical setup:

- A GUI (Graphical User Interface) showing the feedback to the user

- A database table containing the user action history. Where each result of the user action is stored

- A piece of code that stored the user action in the action history t...