WO2003041048A2

WO2003041048A2 - Methods and systems for developing electronic performance support systems

Info

Publication number: WO2003041048A2
Application number: PCT/US2002/035010
Authority: WO
Inventors: Linda Olsen
Original assignee: Mason & Hanger Corporation
Priority date: 2001-11-02
Filing date: 2002-11-01
Publication date: 2003-05-15
Also published as: WO2003041048A3

Abstract

The present invention relates to methods and systems of developing electronic performance support systems, and specifically to methods and systems of developing electronic performance support systems implemented in a computer system, and more specifically to methods and systems of developing electronic performance support systems in a graphical user interface (200). The present invention also relates to methods and systems of developing electronic performance support systems in a graphical user interface using a drag and drop screen design concept (210), and more specifically to methods and systems of developing electronic performance support systems in a graphical user interface using component wrappers for data recording.

Description

METHODS AND SYSTEMS FOR DEVELOPING ELECTRONIC PERFORMANCE

SUPPORT SYSTEMS

CROSS REFERENCE TO RELATED APPLICATIONS The present application is related to an claims under 35 U.S.C. § 119(e), the benefit of

U.S. Provisional Patent Application Serial No. 60/330,888, filed 2 November 2001, which is incorporated herein by reference.

FIELD OF THE INVENTION The present invention relates to methods and systems of developing electronic performance support systems, and specifically to methods and systems of developing electronic performance support systems implemented in a computer system, and more specifically to methods and systems of developing electronic performance support systems in a graphical user interface. The present invention also relates to methods and systems of developing electronic performance support systems in a graphical user interface using a drag and drop screen design concept, and more specifically to methods and systems of developing electronic performance support systems in a graphical user interface using component wrappers for data recording.

BACKGROUND OF THE INVENTION

An electronic performance support system ("EPSS") is a computer system that may integrate software tools, knowledge and learning experiences to improve business performance. This improvement may be achieved by allowing individuals to master complex concepts required for their profession in a shorter period of time and with minimal support from other individuals and by providing an electronic infrastructure which enables organizational learning by sharing collective corporate knowledge.

Currently, providers of electronic performance support systems act as consultants for end-users and perform custom programming tailored to the user's needs to develop electronic performance support systems. Thus, such systems are not directly customer-modifiable and may be relatively expensive because of their customized nature.

Additionally, two other electronic performance support systems are commercially available. First, Assistware by Baydon Solutions is a software solution that interoperates with a user's other business systems by offering "tutorial help" assistance when the user is performing common business tasks. In an example application, a call center operator may offer a new credit card to a consumer. If the consumer asks a question regarding the grace period for the credit card, the call center operator may drag the Assistware "bubble" over the grace period attribute for the credit card displayed on the operator's computer screen. Such an action may result in the display of a pop-up window that contains the information regarding the grace period of the credit card. The Assistware system does not allow a user to develop an electronic performance support system. Rather, the Assistware system merely allows a user to execute an electronic performance support system.

Second, Mentorworxx by Intelliworxx offers a browser platform for displaying an electronic performance support system. The content contained in the browser may be developed by the customer using other commercially available authoring software. The Mentorworxx system does not allow a user to develop and execute an electronic performance support system in a graphical user interface. The Mentorworxx system merely allows a user to execute an electronic performance support system in a graphical user interface. Moreover, no electronic performance support system supports automatic data recording when a component of the electronic performance support system is accessed. Such data recording would aid in generating real-time industrial engineering studies during the execution of the electronic performance support system, and may ultimately be used to improve processes and reduce cycle times, such as production or maintenance times, associated with the execution of a task.

What is needed is a software system that combines a system that provides a customer with the ability to develop, update, and/or maintain an electronic performance support system inexpensively and with a minimal learning curve with the ability to record data automatically during the execution of the system.

SUMMARY OF THE INVENTION The present invention relates to methods and systems of developing electronic performance support systems, and specifically to methods and systems of developing electronic performance support systems implemented in a computer system, and more specifically to methods and systems of developing electronic performance support systems in a graphical user interface. The present invention also relates to methods and systems of developing electronic performance support systems in a graphical user interface using a drag and drop screen design concept, and more specifically to methods and systems of developing electronic performance support systems in a graphical user interface using component wrappers for data recording.

In a specific embodiment, the present invention may consist of a method of developing an electronic performance support system in a graphical user interface by creating one or more pages that are used to define the electronic performance support system and adding one or more components to one or more of the pages. The method of the specific embodiment may further consist of assigning an action that gathers data from the electronic performance support system when the action is performed during execution.

In a further embodiment, a developer may arrange the placement of the components on each page in the graphical user interface. In a preferred embodiment, the step of arranging the components on each page may include placing one or more components on each page, aligning a component to a grid when the component is placed on a page, and/or aligning a component to a grid when the component is moved from one location to another on a page. In a preferred embodiment, the grid may be formed by a plurality of points of intersection between horizontal lines and vertical lines within a page.

In a preferred embodiment, the step of adding components may include selecting a component from a list of component types and modifying component properties for the component. In a preferred embodiment, component types may include, but are not limited to, backgrounds, buttons, text boxes, checkboxes, digital animations, digital videos, digital images, and dialog boxes such as a login window. In a preferred embodiment, the step of modifying component properties may encompass allowing a developer to modify the properties of a component including, but not limited to, a caption for the component, a color displayed when the component is active, a color displayed when the component is not active, a color displayed when the component is disabled, a color displayed when the component is selected, a color displayed when the component is highlighted, a flag denoting when the component is enabled, a flag denoting when the component is a page title, a flag denoting when the component is hidden, a text justification variable, a step index, a font type denoting a font used by the component, and/or one or more actions for the component.

In an embodiment, the types of actions that may be assigned to a component may include, but are not limited to, highlighting a component, hiding a component, showing a component, enabling a component, disabling a component, displaying an image, displaying an animation, displaying a video clip, playing an animation, playing a video clip, pausing an animation, pausing a video clip, loading a new page, displaying a login dialog box to enable the user to login to the electronic performance support system, authenticating a user attempting to login to the electronic performance support system, displaying a menu, displaying a keyboard screen for data entry or comments, and/or exiting the electronic performance support system. , In an embodiment, the data that is gathered when an action is performed on a component may include, but is not limited to, data associated with time, data associated with a date, data associated with text entered into a component, a tracking identifier, data that is measured when the action is performed, and/or data associated with a user who is currently executing the electronic performance support system. In a preferred embodiment, the gathered data may be stored in a database.

In a specific embodiment, the present invention may consist of a method of developing an electronic performance support system in a graphical user interface by creating one or more pages that are used to define the electronic performance support system, adding one or more steps to each page, and adding one or more components to one or more of the steps. The method of the specific embodiment may further consist of assigning an action that gathers data from the electronic performance support system when the action is performed during execution. In the specific embodiment, the sequence of steps may correspond to a sequence in which components are displayed in the electronic performance support system. In a further embodiment, a developer may also arrange the placement of the components on each page in the graphical user interface. In a further embodiment, a developer may also arrange the placement of the components on each page. In a preferred embodiment, the step of arranging the components on each page may include placing one or more components on each page, aligning a component to a grid when the component is placed on a page, and/or aligning a component to a grid when the component is moved from one location to another on a page. In a preferred embodiment, the grid may be formed by a plurality of points of intersection between horizontal lines and vertical lines within a page. In a preferred embodiment, the step of adding components may include selecting a component from a list of component types and modifying component properties for the component. In a preferred embodiment, component types may include, but are not limited to, backgrounds, buttons, text boxes, checkboxes, digital animations, digital videos, digital images, and dialog boxes such as a login window. In a preferred embodiment, the step of modifying component properties may encompass allowing a developer to modify the properties of a component including, but not limited to, a caption for the component, a color displayed when the component is active, a color displayed when the component is not active, a color displayed when the component is disabled, a color displayed when the component is selected, a color displayed when the component is highlighted, a flag denoting when the component is enabled, a flag denoting when the component is a page title, a flag denoting when the component is hidden, a text justification variable, a step index, a font type denoting a font used by the component, and/or one or more actions for the component.

In a specific embodiment, the present invention may consist of a method of developing a wrapper assigned to a component that executes one or more commands in an electronic performance support system when an action is performed on the component by selecting an action from a list of actions, assigning one or more commands selected from a command list to the action, and executing the commands when the action is performed.

In a preferred embodiment the list of commands that may be assigned to a component may include, but is not limited to, highlighting a component, hiding a component, showing a component, enabling a component, disabling a component, displaying an image, displaying an animation, displaying a video clip, playing an animation, playing a video clip, pausing an animation, pausing a video clip, loading a new page, displaying a login dialog box to enable the user to login to the electronic performance support system, authenticating a user attempting to login to the electronic performance support system, displaying a menu, displaying a keyboard screen for data entry or comments, exiting the electronic performance support system, recording data associated with time, recording data associated with a date, recording data associated with text entered into a component, recording a tracking identifier, recording data that is measured when the action is performed, and/or recording data associated with a user who is currently executing the electronic performance support system. In a specific embodiment, the present invention may consist of a computer system used to develop an electronic performance support system. In a specific embodiment, the computer system may include a computer processor, a memory that is operatively coupled to the processor, and a computer process stored in the memory that executes in the processor. In a specific embodiment, the computer process may consist of a method for developing an electronic performance support system in a graphical user interface by creating one or more pages that define an electronic performance support system, adding one or more steps to each page, and adding one or more components to one or more of the steps. The method of the computer process in the specific embodiment may further consist of assigning an action that gathers data from the electronic performance support system when the action is performed during execution. In the specific embodiment, the sequence of steps may correspond to a sequence in which components are displayed in the electronic performance support system.

In a further embodiment, a developer may also arrange the placement of the components on each page. In a preferred embodiment, the step of arranging the components on each page may include placing one or more components on each page, aligning a component to a grid when the component is placed on a page, and/or aligning a component to a grid when the component is moved from one location to another on a page. In a preferred embodiment, the grid may be formed by a plurality of points of intersection between horizontal lines and vertical lines within a page. In a preferred embodiment, the step of adding components may include selecting a component from a list of component types and modifying component properties for the component. In a preferred embodiment, component types may include, but are not limited to, backgrounds, buttons, text boxes, checkboxes, digital animations, digital videos, digital images, and dialog boxes such as a login window. In a preferred embodiment, the step of modifying component properties may encompass allowing a developer to modify the properties of a component including, but not limited to, a caption for the component, a color displayed when the component is active, a color displayed when the component is not active, a color displayed when the component is disabled, a color displayed when the component is selected, a color displayed when the component is highlighted, a flag denoting when the component is enabled, a flag denoting when the component is a page title, a flag denoting when the component is hidden, a text justification variable, a step index, a font type denoting a font used by the component, and/or one or more actions for the component.

In an embodiment of the present invention, the types of actions that may be assigned to a component may include, but are not limited to, highlighting a component, hiding a component, showing a component, enabling a component, disabling a component, displaying an image, displaying an animation, displaying a video clip, playing an animation, playing a video clip, pausing an animation, pausing a video clip, loading a new page, displaying a login dialog box to enable the user to login to the electronic performance support system, authenticating a user attempting to login to the electronic performance support system, displaying a menu, displaying a keyboard screen for data entry or comments, and/or exiting the electronic performance support system.

In an embodiment, the data that is gathered when an action is performed on a component may include, but is not limited to, data associated with time, data associated with a date, data associated with text entered into a component, a tracking identifier, data that is measured when the action is performed, and/or data associated with a user who is currently executing the electronic performance support system. In a preferred embodiment, the gathered data may be stored in a database.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic block diagram of a computer system that may be used to practice the present invention.

FIG. 2 is a graphical user interface used to develop an electronic performance support system according to an exemplary embodiment of the present invention.

FIG. 3 is a graphical user interface used to perform management of page development for an electronic performance support system according to an embodiment of the present invention.

FIG. 4 is a graphical user interface used to select a new component for a page of an electronic performance support system according to an embodiment of the present invention. FIG. 5 is a graphical user interface used to dynamically edit properties of a button component according to an embodiment of the present invention.

FIG. 6 is a graphical user interface used to dynamically edit properties of a text component according to an embodiment of the present invention. FIG. 7 is a graphical user interface used to define functions used in the development of the electronic performance support system according to an embodiment of the present invention.

FIG. 8 is a graphical user interface in a development workspace used to dynamically edit an action taken by a particular component in an electronic performance support system according to an embodiment of the present invention.

FIG. 9 is a graphical user interface used to perform file operations on an electronic performance support system according to an embodiment of the present invention.

FIG. 10 is a graphical user interface used to perform file operations on a single page of an electronic performance support system according to an embodiment of the present invention.

FIG. 11 is a graphical user interface used to import a database into an electronic performance support system according to an embodiment of the present invention. FIG. 12 is a graphical user interface used to select a database to import into an electronic performance support system according to an embodiment of the present invention.

FIG. 13 is a graphical user interface used to perform editing operations on a selected component of an electronic performance support system according to an embodiment of the present invention.

FIG. 14 is a graphical user interface used to create or delete components from a current page of an electronic performance support system according to an embodiment of the present invention.

FIG. 15 is a graphical user interface used to modify a selected component of an electronic performance support system according to an embodiment of the present invention.

FIG. 16 is a graphical user interface used to toggle functions values used in the development of the electronic performance support system according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present invention which will be limited only by the appended claims.

It must be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. Thus, for example, reference to "an icon" is a reference to one or more icons and includes equivalents thereof known to those skilled in the art, and so forth.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood to one of ordinary skill in the art to which this invention belongs. Although any methods, devices, and materials similar or equivalent to those described herein can be used in the practice or testing of the invention, preferred methods, devices and materials are now described.

All publications and patents mentioned herein are hereby incorporated herein by reference for the purpose of describing and disclosing, for example, the methodologies that are described in the publications which might be used in connection with the present

^■ invention. Publications discussed throughout the text are provided solely for their disclosure prior to the filing date of the present application. Nothing herein is to be construed as an admission that the inventors are not entitled to antedate such disclosure by virtue of prior invention.

Definitions For convenience, the meaning of certain terms and phrases employed in the specification, examples, and appended claims are provided below. The definitions are not meant to be limiting in nature and serve to provide a clearer understanding of certain aspects of the present invention.

The terms "Electronic Performance Support System" and "EPSS" refer to an interactive electronic procedure that provides multimedia-based work instructions to a user. The term "component" refers to a discrete element placed on a page of an EPSS. Component types may include, but are not limited to, buttons, text boxes, checkboxes, animations, videos, images, dialog windows, and databases.

The term "customer" as used herein refers generally to a person or entity that requires, uses, or provides for an EPSS.

The term "developer" refers, for example, to any employee or other agent of the customer who may develop or customize an EPSS to his principal's specifications.

The term "icon" refers to a "component selection icon" or "button" that is used to select an element from a list. Icons are used to select components that are placed on a page of an EPSS.

The term "user" or "end-user" refers to one who makes use of an EPSS for training or work-related purposes.

The verb "determine" includes both the causal and relative meanings of the word. For example, as "determine" is used in its relative sense, the phrase "A determines B" may mean that A permits a user, developer, or other person or computer system or subsystem to determine B.

Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings and the following description to refer to the same or like parts.

The present invention includes systems and methods that may permit an end user to add components used in the development of an electronic performance support system. The system may be implemented in means including, but not limited to, hardware, software or a combination of both. Components may be added to the electronic performance support system by means such as, but not limited to, "clicking and dragging," selecting from a menu, and/or selecting from a graphical user interface. The electronic performance support system may include, but is not limited to, components displaying text and or digital media. In a preferred embodiment of the present invention, the components may consist of wrappers including, but not limited to, the displayed component and embedded computer code that may customize the function of the component when an action is performed on the component by an end-user of an EPSS. In a preferred embodiment of the present invention, a component's wrapper may be used to automatically record data retrieved from operations performed on a component by an end-user. In an embodiment of the present invention, the data may be used to generate a real-time industrial engineering time study, which may be used by process engineers and/or managers to reduce process cycle times and improve product/process reliability. The recorded data may include, but is not limited to, data previously generated by actions of the end user, the procedure step that was performed by the end-user, the identity of the end-user that performed or supervised the procedure step, one or more data measurements measured substantially when the procedure step was performed, a tracking identifier, the time at which the procedure step was initiated, the date on which the procedure step was initiated, the time at which the procedure step was completed, and/or the date on which the procedure step was completed. A preferred embodiment of the present invention may automatically import and use a customer database containing procedural step information for EPSS development. Importing an existing database into the present invention may simplify the design process and allow developers without significant technical skill to develop an EPSS. Allowing EPSS development by developers without significant technical skill may realize a cost saving to the customer.

In a preferred embodiment of the present invention, the development tool for electronic performance support systems may be implemented to allow a developer to create an electronic performance support system by means of a graphical user interface. Use of the graphical user interface may minimize or eliminate human errors typically encountered during the performance of routine assembly, disassembly, and maintenance tasks. Use of the graphical user interface for an electronic performance support system may address such problems as unintentionally skipping a critical assembly step or inserting a component in an improper location. A graphical electronic performance support system interface that allows a customer to both develop an electronic performance support system and record data generated by the use of the electronic performance support system represents an improvement over non-graphical electronic performance support systems and interfaces that do not allow an end-user to develop, update, and maintain electronic performance support systems and electronic performance support systems that do not provide feedback information in the form of a real-time industrial engineering time study.

In another embodiment of the present invention, fees may be charged based upon, for example, use of generated systems, development of each electronic performance support system by the customer, or for specific actions within the user interface. Other embodiments may include selling licenses to customers that allow access to the various tools or interface. FIG. 1 illustrates an exemplary computer system that may be modified in accordance with the principles of the present invention. The exemplary computer system may comprise a computer subsystem for the developer.

One or more user interface devices, such as a terminal 110, a keyboard, and a monitor may be connected to a computer 120, such as a main frame computer, minicomputer, microprocessor, server, etc. The computer 120 may include one or more memory devices 130. The memory device 130 may include one or more of the following, but is not limited to, a server-based computer system, a hard drive, a RAM, or a ROM. The computer 120 may also include one or more I/O devices 140 such as, for example, a network interface card, a serial port, a parallel port, a USB port, a floppy disk drive, a CD drive, or a DND drive.

Certain I/O devices 140 may include devices that are also memory devices 130, such as, for example, a tape drive.

A computer process for developing electronic performance support systems may reside in the memory device 130 for operation on the computer 120. This computer process may present the developer with a variety of options including, but not limited to, the ability to create, modify, or delete electronic performance support systems.

FIG. 2 illustrates an exemplary Graphical User Interface ("GUI") that may allow a developer to develop an EPSS. In a preferred embodiment of the present invention, the GUI may include, but is not limited to, a Creator Window 200, a Design Page 210, and a Title Bar 220.

The Creator Window 200 may be used to manage page development for an EPSS. The Creator Window 200 is described in more detail in FIGS. 3-16 and the associated text. The Design Page 210 may contain components for a selected page and/or a selected step. The Design Page 210 may represent the viewable image portrayed to a user when the user views a page of an EPSS.

The Title Bar 220 may be used to assign a title to a step or page of an EPSS. The text in the Title Bar 220 may be assigned by the developer on a page-by-page and/or step-by-step basis to convey information to the user regarding the contents of the Design Page 210.

FIG. 3 illustrates an exemplary GUI that may allow a developer to manage page development for an EPSS. In a preferred embodiment of the present invention, the Page Manager 300 may be the main EPSS development and navigation screen. The Page Manager 300 may display a list of each page (e.g., screen) in an EPSS. This list may be referred to as a page listing sequence. The Page Manager 300 may also contain a number of icons, which, when clicked on by the developer, may perform different functions. These icons may include, without limitation, an Add Page icon 310, a Delete Page icon 320, an Add Step icon 330, a Delete Step icon 340, an Up icon 350, a Down icon 360, and a Run Project icon 370. The Add Page icon 310 may add an empty page to the page list contained in the Page

Manager 300 for the current EPSS. The Delete Page icon 320 may delete a selected page from the page list contained in the Page Manager 300 for the current EPSS. The Add Step icon 330 may add a step to a selected page in the page list contained in the Page Manager 300 for the current EPSS. The Delete Step icon 340 may delete a selected step from the page list contained in the Page Manager 300 for the current EPSS.

The Up icon 350 may allow the developer to move a selected page to an earlier position in a page listing sequence. The result of the operation of the Up icon 350 may be that the selected page may operate at an earlier time when the EPSS is accessed by the end- user. In an alternate embodiment of the present invention, one or more pages may be clicked and dragged to an earlier position in the page listing sequence.

The Down icon 360 may allow the developer to move a selected page to a later position in the page listing sequence. The result of the operation of the Down icon 360 may be that the selected page may operate at a later time when the EPSS is accessed by the end- user. In an alternate embodiment of the present invention, one or more pages may be clicked and dragged to a later position in the page listing sequence.

The Run Project icon 370 may allow the developer to compile, view, and execute the EPSS to view the result of the EPSS described in the Page Manager 300. FIG. 4 depicts an exemplary GUI that may allow a developer to insert components into a selected page. The Toolbar 400 may contain a list of components, represented in the exemplary embodiment by icons, including, without limitation, Arrow 405, Button One 410, Button Two 415, Text 420, Checkbox 425, Animation/Image 430, Database Key 435, Database Edit 440, Database Memo 445, Login 450, and Clear Page 455 icons.

The Arrow icon 405 may allow a developer to toggle between selecting a component from the Toolbar 400 and preventing selection of a component. In other words, when the Arrow icon 405 is enabled and a developer clicks on a component icon (410-450) and then clicks on the Design Page 210, a new icon may be placed on the Design Page 210 at the clicked-upon location. Subsequent clicks on the Design Page 210 may place an additional instance of a component on the Design Page 210. If a different component icon (410-450) is selected, the new component may be placed on the Design Page 210 when the developer clicks on the Design Page 210. When the Arrow icon 405 is deselected, clicking on the Design Page 210 may result in no component being placed on the Design Page 210. The Button One 410 icon may select a button component depicted in a first style for placement upon the Design Page 210. Actions may be assigned to a Button One 410 component by means of a Button Dynamic Property Editor 500, as depicted below in reference to FIG. 5.

The Button Two 415 icon may select a button component depicted in a second style for placement upon the Design Page 210. Actions may be assigned to a Button Two 415 component by means of a Button Dynamic Property Editor 500, as depicted below in reference to FIG. 5.

The depiction of Button One 410 components and Button Two 415 components in the Design Page 210 may differ in their default property settings, but otherwise may provide substantially identical functionality.

The Text 420 icon may allow the developer to create text box components displaying procedural step information or associated reference information on the Design Page 210. The developer may enter text directly into the text box using a Text Dynamic Property Editor 600, described below in reference to FIG. 6, or by using the Add Step function 340 in the Page Manager 300.

Procedural step information may include, but is not limited to, a textual string contained in a Text 420 component and a step index. In operation, the step index may define the sequence in which a Text 420 component is presented to the user. The step index is described further in reference to FIGS. 6 and 12.

The Checkbox 425 icon may allow the developer to create checkbox components in the Design Page 210. Checkbox 425 components may aid end-users in performing step-by- step tasks in an EPSS. The Checkbox 425 component may be assigned a data-recording task as an action performed when the end-user clicks on it.

The Animation/Image 430 icon may allow the developer to add a digital animation/video component or a still digital graphics/picture component to the Design Page 210. The Login 450 icon may allow the developer to select a database containing the names and passwords of authorized EPSS users. In operation, the Login 450 component may allow an EPSS user to login to the EPSS and verify that the user is authorized to perform the specified EPSS.

The Clear Page 455 icon may allow the developer to remove all components from the Design Page 210.

FIG. 5 illustrates a Button Dynamic Property Editor 500 that may allow a developer to modify properties of a selected Button One 410 component or a selected Button Two 415 component. In the following exemplary embodiment, reference will only be made to a Button One 410 component. One of skill in the relevant art, based on the following description, would understand that this exemplary embodiment may be similarly applied to a Button Two 415 component. The description refers to a Button One 410 component only as a means of simplifying the description and is not meant to be limiting in any way.

When a Button One 410 component has been placed on the Design Page 210, the developer may right click on the Button One 410 component to open a Button Dynamic Property Editor 500. The developer may select each of the properties displayed in the Button Dynamic Property Editor 500 to modify the appearance of the selected Button One 410 component as desired. The properties for a Button One 410 component may include, without limitation, a Button Caption 510, an Up Color 520, a Down Color 530, a Disabled Color 540, an Enabled Flag 550, and a Button Font 560. The Button Caption 510 property may be used to define a text string associated with the Button One 410 component.

The Up Color 520 property may be used to define the color of the Button One 410 component when the Button One 410 component is, for example, not selected. The Down Color 530 property may be used to define the color of a Button One 410 component when the Button One 410 component is, for example, selected.

The Disabled Color 540 property may be used to define the color of the Button One 410 component when the Button One 410 component is disabled. The Enabled Flag 550 property may determine whether the Button One 410 component is enabled or disabled. When the Button One 410 component is disabled and the Button One 410 component is selected or deselected, the selection or deselection of the Button One 410 component may result in no action being taken.

The Button Font 560 property may be used to define the font of a text string associated with the Button One 410 component.

FIG. 6 illustrates an exemplary Text Dynamic Property Editor 600 that may allow a developer to modify properties of a Text 420 component. When a Text 420 component has been placed on the Design Page 210, the developer may open the Text Dynamic Property Editor 600 by clicking on the Text 420 component. The developer may select each of the properties displayed in the Text Dynamic Property Editor 600 to modify the appearance of the selected Text 420 component as desired. The properties for a Text 420 component may include, without limitation, a Text Caption 610, a Highlight Color 620, a Color 630, a Text Font 640, a Text Alignment 650, a Step Index 660, a Page Title Flag 670, and a Hide Text Flag 680. The Text Caption 610 property may be used to define the text string associated with the Text 420 component.

The Highlight Color 620 property may be used to define the color of the Text 420 component when it is highlighted. All of the text in a Text 420 component may appear in the color defined by the Highlight Color 620 property during execution of an EPSS. This may be performed by assigning a Highlight Text 810 action, as described below in reference to FIG. 8, to the selection of a Button One 410 component or a Button Two 415 component that has been associated with the Text 420 component.

The Color 630 property may be used to define the color of the Text 420 component when it is, for example, not highlighted. The Text Font 640 property may be used to define the font of the text string associated with the Text 420 component.

The Text Alignment 650 property may be used to define the alignment of the text string associated with the Text 420 component. The Text Alignment 650 property may be assigned values including, but not limited to, left alignment, center alignment, right alignment, and justified alignment.

The Step Index 660 property may be used to define the step of the given page with which the Text 420 component is associated. In operation, text from a database may be displayed sequentially based on the Step Index 660 property assigned to a given Text 420 component. The first selected text database record displayed in the Text 420 component may be the record with a Step Index 660 equal to 1. The next text database record displayed in the

Text 420 component may be the record with a Step Index 660 equal to 2, and so on. The Page Title Flag 670 property may be used to define whether the Text 420 component is used to supply the text for the Title Bar 220.

The Hide Text Flag 680 property may be used to define whether the Text 420 component is hidden.

Each component within the Design Page 210 may have a different Dynamic Property

Editor associated with it. The properties assigned by the Dynamic Property Editor may vary based upon the component type. The developer may select each of the property types in a

Dynamic Property Editor to modify the appearance of the selected component. Software components may include wrappers encompassing the basic component (e.g., a Checkbox

425) and custom coding for EPSS functionality (e.g., automatic data recording triggered when the checkbox is checked). FIG. 7 depicts an exemplary GUI that may allow a developer to define variables associated with the screen workspace used in developing an EPSS. The Settings 700 may include properties, represented in the exemplary embodiment by icons, including, without limitation, Snap On 710, Grid On 720, Selection Color 730, and Background Color 740 icons. The Snap On 710 icon may be used, for example, to set the components to automatically "snap" to grid intersections when placed or moved on the Design Page 210.

This function may be toggled on or off before individual components are placed on the

Design Page 210.

The Grid On 720 icon may allow the developer to toggle the appearance of grid dots on and off in the Design Page 210. If the Grid On 720 icon is not selected, the property set by the Snap On 710 icon may still snap components placed or moved on the Design Page 210 to grid intersections. The Selection Color 730 icon may allow the developer to select the highlight color of a currently selected component.

The Background Color 740 icon may allow the developer to set the background color of the Design Page 210. FIG. 8 illustrates an exemplary GUI that may allow a developer to assign an action to a currently selected component. A single component may perform more than one operation. A single component likewise may perform more than one operation based upon a single event, such as a selection of the component. To assign an action to a particular component, the developer may click upon the component that initiates the action and may select the Assign Action option. The developer may then click on a component to which the action is assigned. In this manner, the developer may establish an association between two components and may cause a trigger for an event. The Actions 800 that may be assigned to components may include, without limitation, Highlight Text 810, Hide Text, Show Text, Enable Button, Disable Button, Show Animation/Image 820, Goto Page 830, Quality Checkoff 840, Special Notes 850, Main Menu 860, Keyboard 870, Pause Animation 880, and Exit 890.

The Highlight Text 810 action may assign an action to a Text 420 component that may cause the Text 420 component to be highlighted. In operation, the Highlight Text 810 action may cause a Text 420 component to be highlighted. The Hide Text action may assign an action to cause the Hide Text Flag 680 of the selected Text 420 component to be enabled. In operation, the Text 420 component may be hidden when the Hide Text action is performed.

The Show Text action may assign an action to cause the Hide Text Flag 680- of the selected Text 420 component to be disabled. In operation, the Text 420 component may be displayed when the Show Text operation is performed.

The Enable Button action may assign an action to cause the Enabled Flag 550 of a selected Button One 410 or Button Two 415 component to be enabled. In operation, the Enable Button action may enable the Button One 410 or Button Two 415 component.

The Disable Button action may assign an action to cause the Enabled Flag 550 of a selected Button One 410 or Button Two 415 component to be disabled. In operation, the Disable Button action may disable the Button One 410 or Button Two 415 component.

The Show Animation/Image 820 action may assign an action to cause a digital image, a digital animation, or a digital video 430 component to be displayed. In addition, a digital animation or digital video 430 component may play once it is displayed. In operation, the Show Animation/Image 820 action may cause a digital image 430 component to be displayed, or a digital animation or digital video 430 component to be displayed and played.

The Goto Page 830 action may assign an action to cause a Select Page dialog box to be displayed for the developer. The developer may then enter an identifier into the Select Page dialog box identifying the page that should be displayed next. In operation, the Goto Page 830 action may open the selected page for the user.

The Quality Checkoff 840 action may assign an action to a component that may cause an authorized user login screen to be displayed. In operation, the Quality Checkoff 840 action may cause an authorized user login screen to be displayed to confirm the authorization of the user.

The Special Notes 850 action may assign an action to cause a keyboard or memo screen to be displayed. In operation, the Special Notes 850 action may cause a keyboard or memo screen to be displayed. The user may then be permitted to enter comments associated with a particular procedure step.

The Main Menu 860 action may assign an action to cause a menu screen to be displayed. In operation, the Main Menu 860 action may cause a menu screen to be displayed for the user.

The Keyboard 870 action may assign an action to cause an on-screen keyboard to be displayed. In operation, the Keyboard 870 action may cause an on-screen keyboard to be displayed for the user. The user may then use the keyboard to enter information as on a touch-screen computer monitor.

The Pause Animation 880 action may assign an action to a component to cause a digital animation or digital video 430 component to pause if the digital animation or digital video 430 component was currently playing. In operation, the Pause Animation 880 action would allow the user to pause a currently playing digital animation or digital video 430 component.

The Exit 890 action may assign an action to a component that may cause the EPSS to complete operation. In operation, the Exit 890 action may allow the user to end the operation of the EPSS.

FIG. 9 illustrates exemplary functions available from the File menu 900. Using the File menu 900, the developer may start a New Project 910, Save the currently open Project 920, or Load a previously saved Project 930. FIG. 10 depicts exemplary functions available from the Page menu 1000. The developer may Save a Template Page 1010 for use throughout an EPSS or Load a Template Page 1020 that was previously saved. A template page may be used to provide a homogeneous design to the EPSS developed by the developer. By using the Load a Template Page 1020 function, a developer may develop the EPSS more rapidly.

FIG. 11 shows an exemplary function available from the DataBase menu 1100. The developer may Import a Database 1110 using this function. In a preferred embodiment of the present invention, if EPSS step information is available in a database format, the developer may directly Import 1110 the database steps into the present invention. When the developer selects the Import 1110 function, an Import Database dialog box 1200 may appear, as shown in FIG. 12.

FIG. 12 depicts an exemplary Import Database dialog box 1200. The Import Database dialog box 1200 may display a listing 1210 of all of the databases that are automatically detected on the developer's computer system. The developer may select the table that contains the step information to be imported and the field in the database containing the information for the Page Field 1220.

The Page Field 1220 may display the text from the database in a text box that, for example, may be aligned to the top of the computer screen. The developer may then select the field in the table containing the information for the Step Field 1230. The Step Field 1230 may display the text from the database in the Text 420 components to which a Step Index 660 was previously assigned. In operation, the text from the database may be displayed sequentially with the currently selected record in the database displayed in the Text 420 component with a Step Index 660 equal to 1. The next text record from the database may be displayed in the Text 420 component with a Step Index 660 equal to 2, and so on.

FIG. 13 shows exemplary functions available from the Edit menu 1300. When a component is selected on the Design Page 210, the developer may Copy 1310, Modify 1330, or Delete 1340 the selected component. In addition, the developer may Paste 1320 a previously copied component. The Copy 1310 function may store the information associated with the selected component. The Paste 1320 function may then create a new component containing the information stored by the Copy 1310 function. If a second component is copied, the information associated with a previously copied component may, for example, no longer be stored.

The Modify 1330 function may cause the Dynamic Property Editor containing the properties of the selected component to be displayed. The developer may then modify the properties in the component's Dynamic Property Editor.

The Delete 1340 function may remove the selected component from the Design Page 210.

FIG. 14 illustrates exemplary functions available from the ToolBar menu 1400. The ToolBar 1400 menu may allow the developer to select a new component to be placed on the Design Page 210. Components that may be selected may include, without limitation, Buttons 1410, Text 1420, Checkboxes 1430, and Animation/Images 1440. These components may correspond to the similarly named buttons described above in reference to FIG. 4 except that Buttons 1410 may be used to select either Button One 410 or Button 415 components. In addition, the developer may select the Clear Page 1450 function. This function may be similar to the Clear Page 455 button described above in reference to FIG. 4.

FIG. 15 shows an exemplary function available from the Properties menu 1500. Selecting the Modify Current Selection 1510 function from the Properties menu 1500 may cause a Dynamic Property Editor to be displayed for a currently selected component on the Design Page 210. FIG. 16 illustrates exemplary functions available from the Settings menu 1600. The developer may modify the appearance of the Design Page 210 by selecting or deselecting the displayed functions. The Settings menu 1600 may allow the developer to modify the Snap On flag 1610, the Grid display flag 1620, the Selection Color 1630, and the Background Color 1640 associated with the Design Page 210. The operation of these functions may be substantially the same as the description of the like-named buttons described above in reference to FIG. 7

The invention has been described in detail with particular reference to a preferred embodiment thereof. However, it will be appreciated that those skilled in the art, upon consideration of this disclosure may make variations and modifications within the spirit and scope of the invention. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

Claims

What is claimed is:

1. A method of developing an electronic performance support system comprising the steps of: creating one or more pages used to define an electronic performance support system in a graphical user interface; adding one or more components to one or more said pages in said graphical user interface; and assigning one or more commands that gather data when an action is performed on at least one of said one or more components.

2. The method of claim 1 , further comprising the step of arranging one or more said components in said graphical user interface.

3. The method of claim 2, wherein said step of arranging one or more said components comprises one or more of the following: placing one or more said components on at least one of said one or more pages; aligning one or more said components to a grid when one or more said components are placed on at least one of said one or more pages, wherein said grid comprises a plurality of points of intersection of horizontal lines and vertical lines within one or more said pages; and aligning one or more said components to said grid when one or more said components are moved within at least one of said one or more pages.

4. The method of claim 1 , wherein said step of adding one or more components comprises the steps of: selecting a component from a list of component types; and modifying component properties for said component.

5. The method of claim 4, wherein said component types comprise one or more of the following: a background; a button; a text box; a checkbox; a digital animation; a digital video; a digital image; and a dialog box.

6. The method of claim 4, wherein said step of modifying component properties for said component comprises modifying one or more of the following: a caption; a color for said component displayed when said component is active; a color for said component displayed when said component is inactive; a color for said component displayed when said component is disabled; a color for said component displayed when said component is selected; a color for said component displayed when said component is highlighted; a flag denoting when said component is enabled; a flag denoting when said component is a page title; a flag denoting when said component is hidden; a text justification variable; a step index; a font type denoting a font used by said component; and one or more actions for said component.

7. The method of claim 6, wherein one or more said actions for said component comprise one or more of the following: highlighting a component; hiding a component; showing a component; enabling a component; disabling a component; displaying an image; displaying an animation; displaying a video clip; playing an animation; playing a video clip; pausing an animation; pausing a video clip; loading a page from one or more said pages; displaying a login box for said electronic performance support system; authenticating a user of said electronic performance support system; displaying a menu; displaying a keyboard screen for data entry or comments; and exiting said electronic performance support system.

8. The method of claim 1 , wherein said step of assigning one or more commands that gather data when an action is performed on at least one of said one or more components comprises one or more of the following: recording time information; recording date information; recording text from at least one of said one or more components; recording a tracking identifier when said action is performed; recording data measured when said action is performed; and recording user information associated with a user performing said action.

9. The method of claim 1 , wherein said data gathered when an action is performed on at least one of said one or more components is stored in a database.

10. A method of developing an electronic performance support system comprising the steps of: creating one or more pages used to define said electronic performance support system in a graphical user interface; adding one or more steps to one or more said pages in said graphical user interface, wherein one or more said steps correspond to a sequence of displays within a page; adding one or more components to. one or more said steps in said graphical user interface; and assigning one or more commands that gather data when an action is performed on at least one of said one or more components.

11. The method of claim 10, further comprising the step of arranging one or more said components in said graphical user interface.

12. The method of claim 11 , wherein said step of arranging one or more said components comprises one or more of the following: placing one or more said components on at least one of said one or more pages; aligning one or more said components to a grid when one or more said components are placed on at least one of said one or more pages, wherein said grid comprises a plurality of points of intersection of horizontal lines and vertical lines within one or more said pages; and aligning one or more said components to said grid when one or more said components are moved within at least one of said one or more pages.

13. The method of claim 10, wherein said step of adding one or more components comprises the steps of: selecting a component from a list of component types; and modifying component properties for said component.

14. The method of claim 13, wherein said component types comprise one or more of the following: a background; a button; a text box; a checkbox; a digital animation; a digital video; a digital image; and a dialog box.

15. The method of claim 13, wherein said step of modifying component properties for said component comprises modifying one or more of the following: a caption; a color for said component displayed when said component is active; a color for said component displayed when said component is inactive; a color for said component displayed when said component is disabled; a color for said component displayed when said component is selected; a color for said component displayed when said component is highlighted; a flag denoting when said component is enabled; a flag denoting when said component is a page title; a flag denoting when said component is hidden; a text justification variable; a step index; a font type denoting a font used by said component; and one or more actions for said component.

16. The method of claim 15, wherein one or more said actions for said component comprise one or more of the following: highlighting a component; hiding a component; showing a component; enabling a component; disabling a component; displaying an image; displaying an animation; displaying a video clip; playing an animation; playing a video clip; pausing an animation; pausing a video clip; loading a page from one or more said pages; displaying a login box for said electronic performance support system; authenticating a user of said electronic performance support system; displaying a menu; displaying a keyboard screen for data entry or comments; and exiting said electronic performance support system.

17. The method of claim 10, wherein said step of assigning commands that gather data when an action is performed on at least one of said one or more components comprises one or more of the following: recording time information; recording date information; recording text from at least one of said one or more components; recording a tracking identifier when said action is performed; recording data measured when said action is performed; and recording user information associated with a user performing said action.

18. The method of claim 10, wherein said data gathered when an action is performed on at least one of said one or more components is stored in a database.

19. A method of developing a wrapper assigned to a component that executes one or more commands in an electronic performance support system when an action is performed on said component comprising: selecting said action from an action list; assigning one or more said commands from a command list to said action; and executing one or more said commands when said action is performed.

20. The method of claim 19, wherein said command list comprises one or more of the following commands: highlighting a component; hiding a component; showing a component; enabling a component; disabling a component; displaying an image; displaying an animation; displaying a video clip; playing an animation; playing a video clip; pausing an animation; pausing a video clip; loading a page from one or more said pages; displaying a login box for said electronic performance support system; authenticating a user of said electronic performance support system; displaying a menu; displaying a keyboard screen for data entry or comments; exiting said electronic performance support system; recording time information; recording date information; recording text from a component; recording a tracking identifier when said action is performed; recording data measured when said action is performed; and recording user information associated with a user performing said action.

21. A computer system for providing users with the ability to develop an electronic performance support system comprising: a computer processor; a memory which is operatively coupled to said computer processor; and a computer process stored in said memory which executes in said computer processor and which comprises: means for creating one or more pages used to define said electronic performance support system in a graphical user interface; means for adding one or more steps to one or more said pages in said graphical user interface, wherein one or more said steps correspond to a sequence of displays within a page; means for adding one or more components one or more said steps in said graphical user interface; and means for assigning one or more commands that gather data when an action is performed on at least one of said one or more components.

22. The computer system of claim 21 , wherein said computer process further comprises means for arranging one or more said components within one or more said pages in said graphical user interface.

23. The computer system of claim 22, wherein said means for arranging one or more said components comprises one or more of the following: means for placing one or more said components on one or more said pages; means for aligning one or more said components to a grid when one or more said components are placed on one or more said pages, wherein said grid comprises a plurality of points of intersection between horizontal lines and vertical lines within one or more said pages; and means for aligning one or more said components to said grid when one or more said components are moved within at least one of said one or more pages.

24. The computer system of claim 21 , wherein said means for adding one or more components comprises: means for selecting a component from a list of component types; and means for modifying component properties for said component.

25. The computer system of claim 24, wherein said component types comprise one or more of the following: a background; a button; a text box; a checkbox; a digital animation; a digital video; a digital image; and a dialog box.

26. The computer system of claim 24, wherein said means for modifying component properties for said component comprises modifying one or more of the following: a caption; a color for said component displayed when said component is active; a color for said component displayed when said component is inactive; a color for said component displayed when said component is disabled; a color for said component displayed when said component is selected; a color for said component displayed when said component is highlighted; a flag denoting when said component is enabled; a flag denoting when said component is a page title; a flag denoting when said component is hidden; a text justification variable; a step index; a font type denoting a font used by said component; and one or more actions for said component.

27. The computer system of claim 26, wherein one or more said actions for said component comprise one or more of the following: means for highlighting a component; means for hiding a component; means for showing a component; means for enabling a component; means for disabling a component; means for displaying an image; means for displaying an animation; means for displaying a video clip; means for playing an animation; means for playing a video clip; means for pausing an animation; means for pausing a video clip; means for loading a page from one or more said pages; means for displaying a login box for said electronic performance support system; means for authenticating a user of said electronic performance support system; means for displaying a menu; means for displaying a keyboard screen for data entry or comments; and means for exiting said electronic performance support system.

28. The computer system of claim 21 , wherein said means for assigning commands that gather data when an action is performed on at least one of said one or more components comprises one or more of the following: means for recording time information; means for recording date information; means for recording text from at least one of said one or more components; means for recording a tracking identifier when said action is performed; means for recording data measured when said action is performed; and means for recording user information associated with a user performing said action.

29. The computer system of claim 21, wherein said data gathered when an action is performed on at least one of said one or more components is stored in a database.

30. A method for providing electronic performance support comprising the step of providing a tool for managing an electronic performance support system in a graphical user interface to a consumer, wherein said tool enables said consumer to develop said electronic performance support system in said graphical user interface.

31. The method of claim 30, wherein said tool enables said consumer to maintain said electronic performance support system in said graphical user interface.

32. The method of claim 30, wherein said tool enables said consumer to update said electronic performance support system in said graphical user interface.

33. The method of claim 30, wherein said tool enables said consumer to gather data using said electronic performance support system.

34. The method of claim 30, wherein said tool enables said consumer to record data using said electronic performance support system.

35. The method of claim 30 further comprising the step of charging a fee to said consumer for providing said tool to said consumer.

36. The method of claim 35, wherein said step of charging a fee to said consumer for providing said matched sequence database is selected from one or more of the group consisting of: selling a license to said consumer that allows said consumer to access said tool; charging a fee to said consumer for each electronic performance support system developed by said consumer; and charging a one-time fee to said consumer for use of said tool.