E-learning course editor

Abstract

A course editor includes an input to accept author commands. An interface processes and displays the author commands to facilitate the creation of a course. The interface may include a workspace to display and assemble the structural elements into the course. The workspace may include a menu of structural elements that may be added to the course. The workspace is configured to display a structural element in response to an author command selecting the structural element from the menu. The structural elements may be a sub-course, a learning unit, and/or a knowledge item.

Description

TECHNICAL FIELD

[0002] The following description relates generally to e-learning and in particular to a course editor for e-learning courses.

BACKGROUND

[0003] Systems and applications for delivering computer-based training (CBT) have existed for many years. However, CBT systems historically have not gained wide acceptance. A problem hindering the reception of CBTs as a means of training workers and learners is the compatibility between systems. A CBT system works as a stand-alone system that is unable to use content designed for use with other CBT systems.

[0004] Early CBTs also were based on hypermedia systems that statically linked content. User guidance was given by annotating the hyperlinks with descriptive information. The trainee could proceed through learning material by traversing the links embedded in the material. The structure associated with the material was very rigid, and the material could not be easily written, edited, or reused to create additional or new learning material.

[0005] Newer methods for intelligent tutoring and CBT systems are based on special domain models that must be defined prior to creation of the course or content. Once a course is created, the material may not be easily adapted or changed for different learners' specific training needs or learning styles. As a result, the courses often fail to meet the needs of the trainee and/or trainer.

[0006] The special domain models also have many complex rules that must be understood prior to designing a course. As a result, a course is too difficult for most authors to create who have not undergone extensive training in the use of the system. Even authors who receive sufficient training may find the system difficult and frustrating to use. In addition, the resulting courses may be incomprehensible due to incorrect use of the domain model by the authors creating the course. Therefore, for the above and other reasons, new methods and technology are needed to supplement traditional computer based training and instruction.

SUMMARY

[0007] According to one general aspect a course editor includes an input to accept author commands. An interface processes and displays the author commands to facilitate the creation of a course. The interface may include a workspace to display and assemble the structural elements into the course.

[0008] The workspace may include a menu of structural elements that may be added to the course. The workspace is configured to display a structural element in response to an author command selecting the structural element from the menu. The structural elements may be a sub-course, a learning unit, and/or a knowledge item.

[0009] The workspace also may include one or more tabs. Each tab corresponds to a content aggregation level and displays structural elements corresponding to the content aggregation level.

[0010] The workspace may be used to create relations between structural elements. The relations are used to indicate a dependency between the structural elements. The workspace includes a menu of relations configured to enable an author to select a relation from the menu and to insert the relation between two structural elements displayed in the workspace. The relation may be inserted by receiving an author command selecting a first structural element and dragging an indication of the relation (e.g., a line or an arrow) from the first structural element to the second structural element.

[0011] The relation may be subject taxonomic or non-subject taxonomic. A subject taxonomic relation may be hierarchical, such as a part/whole relation and an abstraction relation. The subject taxonomic relation also may be associative, such as determines, side-by-side, alternative to, opposite to, precedes, context of, process of, values, means of, and affinity. An example of a non-subject taxonomic relation includes a relation that indicates a structural element should be completed before proceeding to a related structural element or a relation that indicates that a structural element belongs to another structural element.

[0012] The interface may include a dialog box displaying one or more fields corresponding to a structural element displayed in the workspace. Examples of fields include a name field, a theme field, a content field, a media type field, a learning time field, a thumbnail field, and an attribute field. The dialog box also may include one or more tabs to select different fields. Examples of tabs include a general tab (e.g., with fields to receive information about the content associated with the structural element), an annotation tab (e.g., with a field to receive notes regarding the structural element), a keyword tab (e.g., including a field to receive keywords to help search for a corresponding structural element), and a competency tab (e.g., including fields to receive competencies gained from the content associated with structural element).

[0013] The interface may include a course overview to display structural elements and relations of the course. The interface may be configured to receive an author command selecting a structural element from the course overview and to display the selected structural element in the workspace. The dialog box may be configured to automatically correspond to the selected structural element. The interface may be configured to receive an author command selecting a relation from the course overview and to display the selected relation and associated structural elements in the workspace.

[0014] The interface also may be configured to receive an author command selecting a learning strategy and to generate a navigation path for display to the author based on the selected learning strategy.

[0015] According to another general concept, a graphical user interface for a course editor includes a workspace window to edit and display structural elements of a course, an overview window to display and select a representation of the structural elements of the course, and a dialog box window to display data fields corresponding to structural elements shown in the workspace window.

[0016] The graphical user interface may include a menu bar to display course edit menus including functions to control and interact with the course editor. The graphical user interface also may include a button bar including one or more button to invoke course editor function to interact with the windows and their displayed contents.

[0017] A structural element may be displayed as a rectangle in the workspace. The rectangle may be color-coded, each type of structural element having a different color.

[0018] The graphical user interface may be configured to display a learning strategy window to indicate a selected strategy and to generate a navigation path window to display a suggested sequence of structural elements based on the selected learning strategy.

[0019] The graphical user interface also may be configured to automatically size the windows to fit on a corresponding display. The windows may include a vertical scroll bar and/or a horizontal scroll bar to access and display portions of the window that are not displayed.

[0020] Other features and advantages will be apparent from the description, the drawings, and the claims.

DESCRIPTION OF DRAWINGS

[0021] FIG. 1 is an exemplary content aggregation model.

[0022] FIG. 2 is an example of an ontology of knowledge types.

[0023] FIG. 3 is an example of a course graph for e-learning.

[0024] FIG. 4 is an example of a sub-course graph for e-learning.

[0025] FIG. 5 is an example of a learning unit graph for e-learning.

[0026] FIGS. 6 and 7 are exemplary block diagrams of e-learning systems.

[0027] FIG. 8 is an exemplary course editor interface that may be implemented using an authoring tool.

[0028] FIG. 9 is an exemplary course overview of the course editor interface.

[0029] FIG. 10 is an exemplary dialog box of the course editor interface.

[0030] FIG. 11 is an exemplary workspace of the course editor.

[0031] FIG. 12 is an example showing v as the vertex that represents the learning unit LU where v1, v2 are the vertices.

[0032] Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

[0033] E-Learning Content Structure

[0034] The e-learning system and methodology structures content so that the content is reusable and flexible. For example, the content structure allows the creator of a course to reuse existing content to create new or additional courses. In addition, the content structure provides flexible content delivery that may be adapted to the learning styles of different learners.

[0035] E-learning content may be aggregated using a number of structural elements arranged at different aggregation levels. Each higher level structural element may refer to any instances of all structural elements of a lower level. At its lowest level, a structural element refers to content and may not be further divided. According to one implementation shown in FIG. 1, course material 100 may be divided into four structural elements: a course 110, a sub-course 120, a learning unit 130, and a knowledge item 140.

[0036] Starting from the lowest level, knowledge items 140 are the basis for the other structural elements and are the building blocks of the course content structure. Each knowledge item 140 may include content that illustrates, explains, practices, or tests an aspect of a thematic area or topic. Knowledge items 140 typically are small in size (i.e., of short duration, e.g., approximately five minutes or less).

[0037] A number of attributes may be used to describe a knowledge item 140, such as, for example, a name, a type of media, and a type of knowledge. The name may be used by a learning system to identify and locate the content associated with a knowledge item 140. The type of media describes the form of the content that is associated with the knowledge item 140. For example, media types include a presentation type, a communication type, and an interactive type. A presentation media type may include a text, a table, an illustration, a graphic, an image, an animation, an audio clip, and a video clip. A communication media type may include a chat session, a group (e.g., a newsgroup, a team, a class, and a group of peers), an email, a short message service (SMS), and an instant message. An interactive media type may include a computer based training, a simulation, and a test.

[0038] A knowledge item 140 also may be described by the attribute of knowledge type. For example, knowledge types include knowledge of orientation, knowledge of action, knowledge of explanation, and knowledge of source/reference. Knowledge types may differ in learning goal and content. For example, knowledge of orientation offers a point of reference to the learner, and, therefore, provides general information for a better understanding of the structure of interrelated structural elements. Each of the knowledge types is described in further detail below.

[0039] Knowledge items 140 may be generated using a wide range of technologies, however, a browser (including plug-in applications) should be able to interpret and display the appropriate file formats associated with each knowledge item. For example, markup languages (such as a Hypertext Markup language (HTML), a standard generalized markup language (SGML), a dynamic HTML (DHTML), or an extensible markup language (XML)), JavaScript (a client-side scripting language), and/or Flash may be used to create knowledge items 140.

[0040] HTML may be used to describe the logical elements and presentation of a document, such as, for example, text, headings, paragraphs, lists, tables, or image references.

[0041] Flash may be used as a file format for Flash movies and as a plug-in for playing Flash files in a browser. For example, Flash movies using vector and bitmap graphics, animations, transparencies, transitions, MP3 audio files, input forms, and interactions may be used. In addition, Flash allows a pixel-precise positioning of graphical elements to generate impressive and interactive applications for presentation of course material to a learner.

[0042] Learning units 130 may be assembled using one or more knowledge items 140 to represent, for example, a distinct, thematically-coherent unit. Consequently, learning units 130 may be considered containers for knowledge items 140 of the same topic. Learning units 130 also may be considered relatively small in size (i.e., duration) though larger than a knowledge item 140.

[0043] Sub-courses 120 may be assembled using other sub-courses 120, learning units 130, and/or knowledge items 140. The sub-course 120 may be used to split up an extensive course into several smaller subordinate courses. Sub-courses 120 may be used to build an arbitrarily deep nested structure by referring to other sub-courses 120.

[0044] Courses may be assembled from all of the subordinate structural elements including sub-courses 120, learning units 130, and knowledge items 140. To foster maximum reuse, all structural elements should be self-contained and context free.

[0045] Structural elements also may be tagged with metadata that is used to support adaptive delivery, reusability, and search/retrieval of content associated with the structural elements. For example, learning object metadata (LOM) defined by the IEEE “Learning Object Metadata Working Group” may be attached to individual course structure elements. The metadata may be used to indicate learner competencies associated with the structural elements. Other metadata may include a number of knowledge types (e.g., orientation, action, explanation, and resources) that may be used to categorize structural elements.

[0046] As shown in FIG. 2, structural elements may be categorized using a didactical ontology 200 of knowledge types 201 that includes orientation knowledge 210, action knowledge 220, explanation knowledge 230, and reference knowledge 240. Orientation knowledge 210 helps a learner to find their way through a topic without being able to act in a topic-specific manner and may be referred to as “know what.” Action knowledge 220 helps a learner to acquire topic related skills and may be referred to as “know how.” Explanation knowledge 230 provides a learner with an explanation of why something is the way it is and may be referred to as “know why.” Reference knowledge 240 teaches a learner where to find additional information on a specific topic and may be referred to as “know where.”

[0047] The four knowledge types (orientation, action, explanation, and reference) may be further divided into a fine grained ontology as shown in FIG. 2. For example, orientation knowledge 210 may refer to sub-types 250 that include a history, a scenario, a fact, an overview, and a summary. Action knowledge 220 may refer to sub-types 260 that include a strategy, a procedure, a rule, a principle, an order, a law, a comment on law, and a checklist. Explanation knowledge 230 may refer to sub-types 270 that include an example, a intention, a reflection, an explanation of why or what, and an argumentation. Resource knowledge 240 may refer to sub-types 280 that include a reference, a document reference, and an archival reference.

[0048] Dependencies between structural elements may be described by relations when assembling the structural elements at one aggregation level. A relation may be used to describe the natural, subject-taxonomic relation between the structural elements. A relation may be directional or non-directional. A directional relation may be used to indicate that the relation between structural elements is true only in one direction. Directional relations should be followed. Relations may be divided into two categories: subject-taxonomic and non-subject taxonomic.

[0049] Subject-taxonomic relations may be further divided into hierarchical relations and associative relations. Hierarchical relations may be used to express a relation between structural elements that have a relation of subordination or superordination. For example, a hierarchical relation between the knowledge items A and B exists if B is part of A. Hierarchical relations may be divided into two categories: the part/whole relation (i.e., “has part”) and the abstraction relation (i.e., “generalizes”). For example, the part/whole relation “A has part B,” describes that B is part of A. The abstraction relation “A generalizes B” implies that B is a specific type of A (e.g., an aircraft generalizes a jet or a jet is a specific type of aircraft).

[0050] Associative relations may be used refer to a kind of relation of relevancy between two structural elements. Associative relations may help a learner obtain a better understanding of facts associated with the structural elements. Associative relations describe a manifold relation between two structural elements and are mainly directional (i.e., the relation between structural elements is true only in one direction). Examples of associative relations include “determines,” “side-by-side,” “alternative to,” “opposite to,” “precedes,” “context of,” “process of,” “values,” “means of,” and “affinity.”

[0051] The “determines” relation describes a deterministic correlation between A and B (e.g., B causally depends on A). The “side-by-side” relation may be viewed from a spatial, conceptual, theoretical, or ontological perspective (e.g., A side-by-side with B is valid if both knowledge objects are part of a superordinate whole). The side-by-side relation may be subdivided into relations, such as “similar to,” “alternative to,” and “analogous to.” The “opposite to” relation implies that two structural elements are opposite in reference to at least one quality. The “precedes” relation describes a temporal relationship of succession (e.g., A occurs in time before B (and not that A is a prerequisite of B)). The “context of” relation describes the factual and situational relationship on a basis of which one of the related structural elements may be derived. An “affinity” between structural elements suggests that there is a close functional correlation between the structural elements (e.g., there is an affinity between books and the act of reading because reading is the main function of books).

[0052] Non Subject-Taxonomic relations may include the relations “prerequisite of” and “belongs to.” The “prerequisite of” and the “belongs to” relations do not refer to the subject-taxonomic interrelations of the knowledge to be imparted. Instead, these relations refer to the progression of the course in the learning environment (e.g., as the learner traverses the course). The “prerequisite of” relation is directional whereas the “belongs to” relation is non-directional. Both relations may be used for knowledge items 140 that cannot be further subdivided. For example, if the size of the screen is too small to display the entire content on one page, the page displaying the content may be split into two pages that are connected by the relation “prerequisite of.”

[0053] Another type of metadata is competencies. Competencies may be assigned to structural elements, such as, for example, a sub-course 120 or a learning unit 130. The competencies may be used to indicate and evaluate the performance of a learner as the learner traverse the course material. A competency may be classified as a cognitive skill, an emotional skill, an senso-motorical skill, or a social skill.

[0054] The content structure associated with a course may be represented as a set of graphs. A structural element may be represented as a node in a graph. Node attributes are used to convey the metadata attached to the corresponding structural element (e.g., a name, a knowledge type, a competency, and/or a media type). A relation between two structural elements may be represented as an edge. For example, FIG. 3 shows a graph 300 for a course. The course is divided into four structural elements or nodes (310, 320, 330, and 340): three sub-courses (e.g., knowledge structure, learning environment, and tools) and one learning unit (e.g., basic concepts). A node attribute 350 of each node is shown in brackets (e.g., the node labeled “Basic concepts” has an attribute that identifies it as a reference to a learning unit). In addition, an edge 380 expressing the relation “context of” has been specified for the learning unit with respect to each of the sub-courses. As a result, the basic concepts explained in the learning unit provide the context for the concepts covered in the three sub-courses.

[0055] FIG. 4 shows a graph 400 of the sub-course “Knowledge structure” 350 of FIG. 3. In this example, the sub-course “Knowledge structure” is further divided into three nodes (410, 420, and 430): a learning unit (e.g., on relations) and two sub-courses (e.g., covering the topics of methods and knowledge objects). The edge 440 expressing the relation “determines” has been provided between the structural elements (e.g., the sub-course “Methods” determines the sub-course “Knowledge objects” and the learning unit “Relations”.) In addition, the attribute 450 of each node is shown in brackets (e.g., nodes “Methods” and “Knowledge objects” have the attribute identifying them as references to other sub-courses; node “Relations” has the attribute of being a reference to a learning unit).

[0056] FIG. 5 shows a graph 500 for the learning unit “Relations” 450 shown in FIG. 4. The learning unit includes six nodes (510, 515, 520, 525, 530, 535, 540, and 545): six knowledge items (i.e., “Associative relations (1)”, “Associative relations (2)”, “Test on relations”, “Hierarchical relations”, “Non subject-taxonomic relations”, and “The different relations”). An edge 547 expressing the relation “prerequisite” has been provided between the knowledge items “Associative relations (1)” and “Associative relations (2).” In addition, attributes 550 of each node are specified in brackets (e.g., the node “Hierarchical relations” includes the attributes “Example” and “Picture”).

[0057] E-Learning Strategies

[0058] The above-described content aggregation and structure associated with a course does not automatically enforce any sequence that a learner may use to traverse the content associated with the course. As a result, different sequencing rules may be applied to the same course structure to provide different paths through the course. The sequencing rules applied to the knowledge structure of a course are learning strategies. The learning strategies may be used to pick specific structural elements to be suggested to the learner as the learner progresses through the course. The learner or supervisor (e.g., a tutor) may select from a number of different learning strategies while taking a course. In turn, the selected learning strategy considers both the requirements of the course structure and the preferences of the learner.

[0059] In the classical classroom, a teacher determines the learning strategy that is used to learn course material. For example, in this context the learning progression may start with a course orientation, followed by an explanation (with examples), an action, and practice. Using the e-learning system and methods, a learner may choose between one or more learning strategies to determine which path to take through the course. As a result, the progression of learners through the course may differ.

[0060] Learning strategies may be created using macro-strategies and micro-strategies. A learner may select from a number of different learning strategies when taking a course. The learning strategies are selected at run time of the presentation of course content to the learner (and not during the design of the knowledge structure of the course). As result, course authors are relieved from the burden of determining a sequence or an order of presentation of the course material. Instead, course authors may focus on structuring and annotating the course material. In addition, authors are not required to apply complex rules or Boolean expressions to domain models thus minimizing the training necessary to use the system. Furthermore, the course material may be easily adapted and reused to edit and create new courses.

[0061] Macro-strategies are used in learning strategies to refer to the coarse-grained structure of a course (i.e., the organization of sub-courses 120 and learning units 130). The macro-strategy determines the sequence that sub-courses 120 and learning units 130 of a course are presented to the learner. Basic macro-strategies include “inductive” and “deductive,” which allow the learner to work through the course from the general to the specific or the specific to the general, respectively. Other examples of macro-strategies include “goal-based, top-down,” “goal-based, bottom-up,” and “table of contents.”

[0062] Goal-based, top-down follows a deductive approach. The structural hierarchies are traversed from top to bottom. Relations within one structural element are ignored if the relation does not specify a hierarchical dependency. Goal-based bottom-up follows an inductive approach by doing a depth first traversal of the course material. The table of contents simply ignores all relations.

[0063] Micro-strategies, implemented by the learning strategies, target the learning progression within a learning unit. The micro-strategies determine the order that knowledge items of a learning unit are presented. Micro-strategies refer to the attributes describing the knowledge items. Examples of micro-strategies include “orientation only”, “action oriented”, “explanation-oriented”, and “table of contents”).

[0064] The micro-strategy “orientation only” ignores all knowledge items that are not classified as orientation knowledge. The “orientation only” strategy may be best suited to implement an overview of the course. The micro-strategy “action oriented” first picks knowledge items that are classified as action knowledge. All other knowledge items are sorted in their natural order (i.e., as they appear in the knowledge structure of the learning unit). The micro-strategy “explanation oriented” is similar to action oriented and focuses on explanation knowledge. Orientation oriented is similar to action oriented and focuses on orientation knowledge. The micro-strategy “table of contents” operates like the macro-strategy table of contents (but on a learning unit level).

[0065] In one implementation, no dependencies between macro-strategies and micro-strategies exist. Therefore, any combination of macro and micro-strategies may be used when taking a course. Application of learning strategies to the knowledge structure of a course is described in further detail below.

[0066] E-Learning System

[0067] As shown in FIG. 6 an e-learning architecture 600 may include a learning station 610 and a learning system 620. The learner may access course material using a learning station 610 (e.g., using a learning portal). The learning station 610 may be implemented using a work station, a computer, a portable computing device, or any intelligent device capable of executing instructions and connecting to a network. The learning station 610 may include any number of devices and/or peripherals (e.g., displays, memory/storage devices, input devices, interfaces, printers, communication cards, and speakers) that facilitate access to and use of course material.

[0068] The learning station 610 may execute any number of software applications, including an application that is configured to access, interpret, and present courses and related information to a learner. The software may be implemented using a browser, such as, for example, Netscape communicator, Microsoft's Internet explorer, or any other software application that may be used to interpret and process a markup language, such as HTML, SGML, DHTML, or XML.

[0069] The browser also may include software plug-in applications that allow the browser to interpret, process, and present different types of information. The browser may include any number of application tools, such as, for example, Java, Active X, JavaScript, and Flash.

[0070] The browser may be used to implement a learning portal that allows a learner to access the learning system 620. A link 621 between the learning portal and the learning system 620 may be configured to send and receive signals (e.g., electrical, electromagnetic, or optical). In addition, the link may be a wireless link that uses electromagnetic signals (e.g., radio, infrared, to microwave) to convey information between the learning station and the learning system.

[0071] The learning system may include one or more servers. As shown in FIG. 6, the learning system 620 includes a learning management system 623, a content management system 625, and an administration management system 627. Each of these systems may be implemented using one or more servers, processors, or intelligent network devices.

[0072] As shown in FIGS. 6 and 7, the administration management system 627 may be implemented using a server, such as, for example, the SAP R/3 4.6C+LSO Add-On. The administration management system 627 may include a database of learner accounts and course information. For example, the learner account may include demographic data about the learner (e.g., a name, an age, a sex, an address, a company, a school, an account number, and a bill) and his/her progress through the course material (e.g., places visited, tests completed, skills gained, knowledge acquired, and competency using the material). The administration management system 627 also may provide additional information about courses, such as course title, description, courses offered, the author/instructor of a course, and the most popular courses.

[0073] The content management system 625 may include a learning content server 730. The learning content server 730 may be implemented using a WebDAV server. The learning content server may include a content repository. The content repository may store course files and media files that are used to present a course to a learner at the learning station 610. The course files may include the structural elements that make up a course and may be stored as XML files. The media files may be used to store the content that is included in the course and assembled for presentation to the learner at the learning station 610.

[0074] The learning management system 623 may include a content player 720. The content player 720 may be implemented using a server, such as an SAP J2EE Engine. The content player 720 is used to obtain course material from the content repository. The content player 720 also applies the learning strategies to the obtained course material to generate a navigation tree or path for the learner. The navigation tree or path is used to suggest a route through the course material for the learner and to generate a presentation of course material to the learner based on the learning strategy selected by the learner. Course navigation is described in further detail below.

[0075] The learning management system 623 also may include an interface for exchanging information with the administration management system 627. For example, the content player 720 may update the learner account information as the learner progresses through the course material to indicate, for example, competencies gained, tests passed, courses completed.

[0076] Course Author Station

[0077] As shown in FIGS. 6 and 7 an e-learning system may also include an author station 630. The author station 630 may be implemented using a workstation, a computer, a portable computing device, or any intelligent device capable of executing instructions and connecting to a network. The author station 630 may include any number of devices and/or peripherals (e.g., displays, memory/storage devices, input devices, interfaces, printers, communication cards, and speakers) that facilitate access to, presentation of, and creation of courses and their associated content.

[0078] The author station 630 may execute any number of software applications including an author tool 740 that is configured to create, access, interpret, and present courses (and related course data/information). The author tool 740 may include a course editor 750 and a browser, such as, for example, Netscape communicator, Microsoft's Internet explorer, or any other software application that may be used to interpret and process a markup language, such as HTML, SGML, DHTML, or XML. The browser also may include software plug-in applications that allow the browser to interpret, process, create, and present different types of information. The browser may include any number of application tools, such as, for example, Java, Active X, JavaScript, and Flash.

[0079] The course author tool 740 may access content and associate the content with structural elements. The author tool 740 also may associate knowledge types, relations, and metadata with the structural elements. The author tool 740 may be used to build the structure of a course, i.e., its structural elements and relations. The author tool 740 may save the structural elements and metadata as course files and the associated content as media files.

[0080] The author station 630 also may include an embedded learning management system 760. The embedded learning management system 760 is an application program that is similar to the learning management system 623 and enables the author to preview a course by applying learning strategies to the course (e.g., that is being created/modified by the author) in order to view the navigation path that is suggested to a learner based on the applied strategy. Based on the different suggested navigation paths, the author may determine how to create structure for the course and how the created structure is interpreted by the learning management system 623. As a result, the author may edit, modify, or add structure to the course before publishing the course to the learning system 620.

[0081] The author station 630 also may include a communications interface 631. After a course is created, the author station 630 may use the communication interface 631 to connect to the learning system 620 to publish the course so that a learner may book and take the course. In particular, the communication interface 631 of the author station 630 may connect to the content management system 625 using a communications link 635. To publish the course on the learning system 620, the author station 630 transfers the course structure and content (e.g., the course files and media files) to the content management system 625. As previously described, the course files may be formatted according to a markup language (e.g., XML). The communications link 635 may be implemented using any permanent or temporary communications link configured to transfer the course files and associated media files (e.g., a communications medium configured to transfer data signals as electrical, electromagnetic, or optical waves). The content management system 625 stores the course files and associated media files in the content repository for access by the content player 720.

[0082] The communication interface 631 of the author station 630 also may connect to the administration management system 627 using a communication link 637. The communication link may be implemented by any communication medium that may be configured to send and receive signals (e.g., electrical, electromagnetic, or optical). The author station 630 provides the administration management system 627 with course information (e.g., title, author, description, credits, prerequisites, and competencies gained/required) that is used by a learner, for example, to book a course. Once the course is published, the administration management system 627 makes the course information available to the learning station 610 using the learning portal.

[0083] Course Editor

[0084] The author tool 740 and author station 630 may include a course editor 750 that can be used in conjunction with a browser to create, modify, build, assemble, and preview course structures and their associated content. The course editor 750 may be used to structure content for use in a course. The course editor 750 includes a course editor interface.

[0085] The course editor 750 may be used to create the structure for the course content. The structure may be saved as metadata. The metadata may be interpreted by the content player 720 of the learning management system 623 to present a course to a learner according to a learning strategy selected at run time. In particular, the course editor 750 enables the author to classify and describe structural elements, assign attributes to structural elements, assign relations between structural elements, and build a subject-taxonomic course structure. The course editor 750 primarily generates the structure of the course and not structure of the content (although structure of content may be provided for as well).

[0086] As shown in FIG. 8, the course editor interface 800 may include a menu bar 810, a button bar 820, a course overview 830, a dialog box 850, and work space 860. The menu bar 810 may include various drop-down menus, such as, for example, file, edit, tools, options, and help. The drop-down menus may include functions, such as create a new course, open an existing course, edit a course, or save a course. The button bar 820 may include a number of buttons. The buttons may be shortcuts to functions in the drop down menus that are used frequently and that active tools and functions for use with the course editor 750. The remaining portions of the course editor interface 800 may be divided in to three primary sections or windows: a course overview 830, a dialog box 850, and a workspace 860.

[0087] Each of the sections may be provided with horizontal or vertical scroll bars or other means allowing the windows to be sized to fit on different displays while providing access to elements that may not appear in the window.

[0088] As shown in FIG. 9, the course overview 830 may be used to select and view components within a course. The author may select various components within the course overview 830 to open and close the components, for example, the structural elements. The components in the course overview 830 may be arranged in an explorer format. The course overview 830 may include a directory 920 of components including files and folders. Files and folders may be expanded to view their contents. However, unlike an explorer, the course overview 830 distinguishes between structural elements 930 and relations 940 (e.g., which may contain learning content). Sub-courses 120, learning units 130, and knowledge items 140, as well as their relations, may be displayed in the course overview 830 using icons. To access a sub-course 120 or learning unit 130 shown in the overview, the author may right click and select open sub-course 120 or learning unit 130. Knowledge items 140 may be opened by double clicking on the associated icon.

[0089] As shown in FIG. 10, the dialog box 850 may be used to interact with and edit course components. For example, the dialog box 850 may be arranged with tabs (e.g., general, annotations, keywords, and competency) that may be used to describe the structural elements. Each tab may be used to edit a structural element. The dialog box 850 shown in FIG. 10 includes the tabs general 1010, annotations 1020, and keywords 1030. The dialog box 850 shown in FIG. 10 also includes the fields theme 1040, content 1050, learning time 1060, LOM file 1070, and thumbnail 1080. An author may add content (e.g., an HTML page) and attributes (e.g., a name, a knowledge type, a media type, a LOM, and a competency) to the structural elements using the dialog box 850. The dialog box 850 is automatically configured to correspond to any structural element that has been selected or created in the workspace 860.

[0090] The general tab 1010 enables the author to determine general information and/or attributes that are associated with a selected structural element. A name of a structural element may be provided in a name field (not shown). A thumbnail 1080 may be used to give the author an impression of the content associated with the structural element. A theme 1040 may be included to describe a topic, an attribute, or a knowledge type of the structural element. A learning time 1060 may be used to indicate the average amount of time that a learner may need to complete the content associated with the structural element. A LOM file 1060 may be included to add comprehensive metadata to the structural element.

[0091] The competency tab (not shown) may be used to classify competencies that are acquired by completing or viewing the structural elements. Examples of competencies include, cognitive, emotional, sensomotoric, and social. Competencies also may be included that are needed or recommended to use the associated structural element.

[0092] The annotations tab 1020 may be used to insert comments regarding the content associated with a structural element. For example, notes or a description of the content associated with the structural element may be inserted.

[0093] The keyword tab 1030 may be used to enter keywords that are used to search for and/or organize structural elements. Keywords also may be used to classify a structural element.

[0094] As shown in FIG. 11, the workspace 860 may be used to create the structure of a course. The workspace 860 displays structural elements and relations between the structural elements. Structural elements selected in the overview may be displayed in the workspace 860. Similarly, new structural elements and any associated relation may be created in the workspace 860.

[0095] Structural elements may be represented in the workspace 860 as rectangles. The rectangles may be color coordinated to indicate the type of structural element (e.g., sub-course 120, learning unit 130, knowledge item 140) and whether the structural element is selected or active. Alternatively, the structural elements may be represented in the workspace by a thumbnail indicative of the content associated with the structural element (e.g., as specified in 1080). Relations may be indicated as lines (i.e., non directional relations) or arrows (i.e. directional relations). The displayed rectangles, lines, and arrows may be labeled with a corresponding name (e.g., assigned using the dialog box 850). The workspace 860 also may include tabs 1110 that correspond to each aggregation level. For example, the structural elements belonging to each aggregation level may be accessed by selecting a corresponding tab.

[0096] As shown in FIG. 11, the tab “Course Creation With L3” indicates the course that is currently viewed in the workspace. The tabs “course”, “basic concepts”, and “knowledge structure” correspond to the aggregation levels within the course. The tab “knowledge structure” is selected and the corresponding structural elements and relations are shown. The tab may be populated with a name corresponding to a structural element or aggregation level, which may be assigned using the dialog box 850.

[0097] Structural elements may be added to a course and structured using the workspace 860. For example, a pop-up menu may be accessed by right clicking on the workspace 860. The pop-up menu includes any available structural elements that may be added to the selected tab. To generate a structural element, the author chooses the appropriate button from the pup-up menu corresponding to the type of structural element to be added.

[0098] For example, to generate a sub-course 120, the author selects sub-course 120 from the pop-up menu. Upon selecting the button new sub-course 120, the menu presents a choice of Empty or User. The empty option may be selected to open an empty sub-course 120. The user option may used to open a sub-course 120 with predefined content, such as learning units 130 and/or knowledge items 140. A dialog box 850 corresponding to the sub-course 120 is automatically configured. Using the corresponding dialog box 850 the author may enter a name, attributes, annotations, and keywords for the sub-course 120. The sub-course 120 is added to the course overview 830 and a rectangle with the color-coding corresponding to a sub-course (e.g. green) is added to the workspace 860.

[0099] To generate a learning unit 130, the author may choose the appropriate button from the pop-up menu. Upon selecting the button new learning unit 130, the menu presents a choice of Empty or User. The empty option may be selected to open an empty learning unit 130. The user option may used to open a learning unit 130 with predefined content, such as knowledge items 140. A corresponding dialog box 850 prompts the author to enter a name, attributes, annotations, and keywords for the learning unit 130. The learning unit 130 is displayed in the course overview 830 and appears as a rectangle with the corresponding color-coding (e.g. violet) in the workspace 860. To create a knowledge item 140, the author chooses the appropriate button from the pop-up menu. For example, selecting the button create knowledge item 140 automatically configures a dialog box 850 corresponding to the knowledge item 140. The dialog box 850 may be used to enter a name, attributes, annotations, and keywords corresponding to the knowledge item 140. The knowledge item 140 appears in the course overview 830, and the workspace 860 is populated with a rectangle with the corresponding color-coding (e.g. brown). The dialog box 850 also enables the author to assign content to the knowledge item 140. For example, the content field 1050 in the dialog box 850 may be used to establish a reference to a media file corresponding to the knowledge item 140. The media file may be any media that may displayed by a browser. The author also may assign an appropriate knowledge type (e.g., orientation, explanation, action, reference) and media type (e.g., text, images, diagrams, pictures, sounds, films, video, audio, chat groups, email, video conferences, whiteboards, phones, and PDAs) to the knowledge item 140.

[0100] The pop-up menu also may be used to create tests and collaborative scenarios. When test is selected from the pop-up menu the dialog box 850 appears. The dialog box 850 includes the tabs general, test parameters, annotations, and keywords. The user may use the general tab to insert a name, content, time, and LOM file. In addition, a rectangle test with the corresponding color-coding appears in the workspace. The test parameters tab may be used to indicate a type of test (e.g., pre-test, exercise, self test, or post test. A collaboration scenario may be used to provide an opportunity for the learner to interact with other learners.

[0101] To create a relation between structural elements, the author selects a structural element in the workspace 860. The author then selects a relation from the pop-up menu. The author may drag a line or arrow corresponding to the relation from the selected structural element to a second structural element. The author also may edit and remove unwanted relations by selecting an existing relation in the workspace and using the pop-up menu to edit or delete the relation.

[0102] After completing the course and the associated course structure, the author may activate the embedded learning management system 760 to preview the course. The embedded learning management system 760 applies selected strategies to the course. To preview the course, the author activates the embedded learning management system 760 using the authoring tool. The author then selects a strategy. The embedded learning management system 760 applies the selected strategy to the course structure and determines a navigation path. The navigation path is presented to the author (in a manner that is similar to the display a learner would receive). The author may continue to select other strategies and view the corresponding course navigation path views. Once the author is satisfied with the course structure, the author may transfer the course to the learning system 620 to publish the course.

[0103] Course Navigation

[0104] The structure of a course is made up of a number of graphs of the structural elements included in the course. A navigation tree may be determined from the graphs by applying a selected learning strategy to the graphs. The navigation tree may be used to navigate a path through the course for the learner. Only parts of the navigation tree are displayed to the learner at the learning portal based on the position of the learner within the course.

[0105] As described above, learning strategies are applied to the static course structure including the structural elements (nodes), metadata (attributes), and relations (edges). This data is created when the course structure is determined (e.g., by a course author). Once the course structure is created, the course player processes the course structure using a strategy to present the material to the learner at the learning portal.

[0106] To process courses, the content player 720 grants strategies access to the course data and the corresponding attributes. The strategy is used to prepare a record of predicates, functions, operations, and orders that are used to calculate navigation suggestions, which is explained in further detail below.

[0107] The content player 720 accesses files (e.g., XML files storing course graphs and associated media content) in the content repository and applies the learning strategies to the files to generate a path through the course. By applying the learning strategies the content player 720 produces a set of course-related graphs (which is simply an ordered list of nodes) that are used to generate a navigation tree of nodes. The set of nodes may be sorted to generate an order list of nodes that may be used to present a path through the material for a learner. A path maybe generated using the embedded learning management system 760 in the same manner. In general graphs and strategies may “interact” in the following ways:

[0108] 1. A strategy implements a set of Boolean predicates that can be applied to graph nodes. For example: isCompleted(node).

[0109] 2. A strategy may be informed by an event that some sort of action has been performed on a graph node. For example: navigated(node).

[0110] 3. A strategy may provide functions that are used to compute new node sets for a given node. For example: NavigationNodes(node).

[0111] 4. A strategy provides an ordering function that turns node sets computed number 3 into ordered lists.

[0112] 5. A strategy may decide to alter certain strategy-related node attributes. For example: node.setVisited(true).

[0113] Note that the last point is used because a strategy does not keep any internal state. Instead, any strategy-related information is stored in graph nodes' attributes allowing strategies to be changed “on the fly” during graph traversal.

[0114] As described there are sets of nodes that may be used to generate a path through a course. One set of nodes is “navigation nodes.” Navigation nodes may include all nodes that the strategy identifies that may be immediately reached from the current node. In other words, the navigation nodes represent potential direct successors from a current node. Another set of nodes is “start nodes.” Start nodes are potential starting points when entering a new graph. The more starting points this set contains, the more choices a learner has when entering the unit. As a consequence, any strategy should implement at least two functions that can compute these sets and the ordering function that transforms those sets into ordered lists. The functions are described in further detail below using the following examples.

[0115] In the following examples, these definitions are used:

[0116] C is the set of all courses.

[0117] G is a set of graphs.

[0118] V is a set of vertices (e.g., knowledge items, references to learning units, references to sub courses, and test) Vertices are used when talking about graphs in a mathematical sense (whereas nodes may used to refer to the resulting course structure)

[0119] E is a set of edges (e.g., relations types as used in a mathematical sense).

[0120] TG={sc,lu} is the set of graph types such that:

[0121] sc=sub-course; and

[0122] lu=learning unit.

[0123] TC={sc,lu,co,tst} is the set of content types such that:

[0124] sc=sub-course;

[0125] lu=learning unit;

[0126] co=content; and

[0127] tst=test.

[0128] (With respect to assigning competences to a learner when passing a test, only pretests and posttests are defined as tests; self-tests and exercises are content rather than tests.)

[0129] TK={ . . . } is the set of all knowledge types (e.g., as described in the section E-learning content structure).

[0130] TR={ . . . } is the set of all relation types(e.g., as described in the section E-learning content structure).

[0131] BOOL={true,false} is the Boolean set with the values true and false.

[0132] MAC={ . . . } is the set of macro-strategies (e.g., as described in the section E-learning strategies).

[0133] MIC={ . . . } is the set of micro-strategies (e.g., as described in the section E-learning strategies).

[0134] COMP={ . . . } is the set of all competences.

[0135] LCOMP⊂COMP is the set of a learner's competences.

[0136] TST={pre,post} is the set of test types, such that:

[0137] pre=pretest; and

[0138] post=posttest.

[0139] A course c=(Gc,gs,mac,mic)∈C may be defined such that:

[0140] Gc is the set of all sub-courses and learning units that are members of c;

[0141] gs is the start graph of course c, in particular gs∈G;

[0142] mac∈MAC is the macro-strategy that has been chosen for navigating the course; and

[0143] mic∈MIC is the micro-strategy that has been chosen for navigating the course.

[0144] Processing of the course begins with the start graph.

[0145] A graph g=(Vg,Eg,tg,compg)∈G may be defined such that:

[0146] Vg is the set of all vertices in g;

[0147] Eg⊂Vg×Vg×TR is the set of all edges in g;

[0148] tg∈TG is the graph type of g; and

[0149] compg⊂COMP Are the competencies of the graph.

[0150] In the following description the term content graph is used to identify the sub-graph to which a vertex refers, rather than a graph that includes the vertex. One can think of the vertex representing the “placeholder” of the sub-graph.

[0151] A vertex v=(vsv,tcv,gcc,tkv,ttv,mscorev,ascorev)∈V is defined such that:

[0152] vsv∈BOOL is the visited status of v;

[0153] tcv∈TC is the content type of v;

[0154] gcv∈G is the content graph of v;

[0155] tkv∈TK is the knowledge type of v;

[0156] ttv∈TST is the test type of v;

[0157] mscorev is the maximum possible test score of v; and

[0158] ascorev is the test score actually attained for v.

[0159] An edge or relation type e=(VS,VE,tre)∈E may be defined such that:

[0160] VS∈V is the starting vertex of e;

[0161] VE∈V is the end vertex of e; and

[0162] tre∈TR is the relation type of e.

[0163] A predicate is a mapping p:V→BOOL that assigns a value bp∈BOOL to each vertex v∈V. Therefore:

[0164] bp=p(v).

[0165] An order is a mapping ord:V×V→BOOL that assigns a value bord∈BOOL to a pair of vertices v1,v2∈V. Therefore:

[0166] bord=ord(v1,v2).

[0167] The mapping sort:Vn,ord→Vn is a sorting function from a set of vertices Vn to a set of vertices (v1, . . . , vn) {overscore (V)}n with the order ord, provided that:

[0168] (v1, . . . , vn)=sort(Vn,ord) such that 1$\underset{i,j\in \left(1\dots n\right),i\ne j}{\forall }{v}_i,v_j\in V^n:\mathrm{ord}\left(v_i,v_j\right)=\mathrm{true}$

[0169] for i≦j.

[0170] The following description explains the use of attributes. Attributes are used to define and implement the learning strategies.

[0171] Let g=(Vg,Eg,tg,compg)∈G be a graph with the following attributes:

[0172] g.nodes=Vg Are the vertices of g;

[0173] g.type=tg is the type of g; and

[0174] g.comp=compg is the graph's competencies.

[0175] Let v=(vsv,tcv,gcc,tkv,ttv,mscorev,ascorev)∈V be a vertex with the following attributes:

[0176] v.visited=vsv is the visited status of vertex v (initially this value is false);

[0177] v.graph={g=(Vg,Eg,tg)∈G|v∈Vg} is the graph that contains v;

[0178] v.contentType=tcv is the content type of v; 2$v.\mathrm{contentGraph}=\{\begin{array}{c}{g}^{\prime }\in G:{\mathrm{tc}}_v=\mathrm{sc}\bigvee {\mathrm{tc}}_v=\mathrm{lu}\\ \mathrm{undef}:\mathrm{otherwise}\end{array}$

[0179]  is the content graph of v;

[0180] v.knowType=tkv is the knowledge type of v; 3$v.\mathrm{testType}=\{\begin{array}{c}{\mathrm{tt}}_v\in \mathrm{TST}:{\mathrm{tc}}_v=\mathrm{tst}\\ \mathrm{undef}:\mathrm{otherwise}\end{array}$

[0181]  is the test type of v;

[0182] v.mscore=mscorev is the maximum possible test score of v (initially this value is 0);

[0183] v.ascore=ascorev is the actual test score attained for v (initially this value is −1

[0184] Let e=(vS,vE,tre)∈E be an edge with the following attributes:

[0185] e.start=vS is the starting vertex of e;

[0186] e.end=vE is the end point of e;

[0187] e.type=tre is the relation type of e;

[0188] An edge's logical direction does not necessarily have to agree with the direction indicated by the course player, because the course player displays an edge in the “read direction.” This applies to the following edge, for example, e=(vS,vE,“is a subset of”). The following explanation refers to the logical direction, in other words, the direction of the edge in the above-described cases is considered to be “rotated.” In the following, undirected edges are treated as two edges in opposite directions.

[0189] Predicates are “dynamic attributes” of vertices. The strategy computes the dynamic attributes for an individual vertex when necessary.

[0190] The following are examples of predicates:

[0191] Visited(v): the vertex v has already been visited;

[0192] Suggested(v): the vertex v is suggested;

[0193] CanNavigate(v): the vertex v can be navigated; and

[0194] Done(v): the vertex v is done.

[0195] If a vertex is within a learning unit (i.e., v.graph.type=lu), then the micro-strategy is used to compute the predicates. The macro-strategy that is chosen is responsible for determining all other vertices.

[0196] Functions are used to compute the navigation sets (vertices that are displayed). A function should return a set of vertices. The strategies implement the functions.

[0197] For example, the following functions are:

[0198] {overscore (V)}=StartNodes(g)={{overscore (v)}|{overscore (v)} is a starting vertex of g} is the set of all starting vertices of graph g. Starting vertices are the vertices of a graph from which navigation within the graph may be initiated in accordance with a chosen strategy.

[0199] {overscore (V)}=NextNodes(v)={{overscore (v)}|{overscore (v)} is a successor of v} is the set of all successor vertices of vertex v.

[0200] For micro-strategies, the chosen macro-strategy calls the functions as needed. When entering a learning unit the macro-strategy selects the appropriate (selected) micro-strategy.

[0201] Operations provide information to the chosen strategy about particular events that occur during navigation of a course. The strategy may use them to change the attributes. The operations are:

[0202] navigate(v); The runtime environment calls this operation as soon as the vertex v is navigated during the navigation of the course.

[0203] testDone(v,MaxScore,ActScore); The runtime environment calls this operation if the vertex v is a test (v.contentType=tst) that has been done. MaxScore contains the maximum possible score, ActScore the score actually attained.

[0204] If a vertex is in a learning unit, which means that v.graph.type=lu, then the micro-strategy computes these operations. The macro-strategy is responsible for all other vertices.

[0205] The runtime environment uses the sorting function to order the navigation sets that have been computed. The order determines the sequence in which the vertices are to be drawn. The “most important” vertex (e.g., from the strategy's point of view) is placed at the start of the list (as the next vertex suggested). The strategies implement these sorting functions and the runtime environment provides them. The following examples of sorting functions may be defined:

[0206] sortNav(V) is used to sort the set of navigation vertices.

[0207] The sorting functions are called automatically as soon as the functions have returned sets of vertices to the strategy in question. It is consequently necessary that each macro and micro-strategy have a sorting function at its disposal.

[0208] The following description explains the predicates, operations, functions, and sorting functions associated with macro-strategies.

[0209] The following is an example of how a top-down (deductive) learning strategy may be realized.

[0210] The predicates for the top-down strategy may be defined as follows:

[0211] Visited (v):v.visited

[0212] The vertex's “visited” attribute is set.

[0213] Suggested(v):∀({overscore (v)},v,tr)∈E such that tr=prerequisite we have: Done({overscore (v)})=true

[0214] All of the vertex's prerequisites are satisfied.

[0215] CanNavigate(v):Suggested(v)

[0216] Is used in this example like Suggested.

[0217] Done(v):

[0218] (v.contentType∈{sc,lu}v.contentGraph.comp≠Ø⊂LCOMP)

[0219] (v.contentType≠tstv.visited=true(∀{overscore (v)}∈StartNodes(v.contentGraph):Done({overscore (v)})=true))

[0220] (c.contentType≠tst(v.ascore*2)≧v.mscore)

[0221] The vertex v is considered done if at least one of the following conditions holds:

[0222] It includes a learning unit or sub-course that has at its disposal a nonempty set of competences that the learner already possesses;

[0223] It does not contain a test, is visited, and all of the content graph's starting vertices have been done; and/or

[0224] It deals with a test and at least half of the maximum score has been attained.

[0225] The functions for the top-down strategy may be defined as follows: 4$\mathrm{StarNodes}\left(g\right)=\{\begin{array}{c}g=\mathrm{undef}:Ø\\ g.\mathrm{type}=\mathrm{lu}:c.\mathrm{mic}.\mathrm{StartNodes}\left(g\right)\\ g.\mathrm{type}=\mathrm{sc}:\left\{v\in V_g|\forall \left(v^{*},v,\mathrm{tr}\right)\in E:\mathrm{tr}\ne \mathrm{heirarchical}\right\}\end{array}$

[0226] If g is undefined, which means that vertex does not have any content graphs, then the set is empty.

[0227] If g is a learning unit, the StartNodes( ) function of the chosen micro-strategy will be used.

[0228] If g is a sub-course, all vertices that do not have any hierarchical relations referring to them will be returned.

[0229] NextNodes(v)={{overscore (v)}∈Vvgraph|∃(v,{overscore (v)},tr)}∪StartNodes(v.contentGraph)

[0230] All vertices connected to v by an externally directed relation, plus all vertices that are starting vertices of the content graph of v.

[0231] The operations for top-down may be defined as follows:

[0232] navigate(v):v.visited=true

[0233] The vertex's “visited” attribute is set to true.

[0234] testDone(v,MaxScore,ActScore):v.mscore=MaxScore,v.ascore=ActScore

[0235] if 5$\{\begin{array}{c}\mathrm{Done}\left(v\right)=\mathrm{true}:\mathrm{LCOMP}=\mathrm{LCOMP}\bigcup v.\mathrm{graph}.\mathrm{comp},\forall \stackrel{\_}{v}\in v.\mathrm{graph}:\stackrel{\_}{v}.\mathrm{visited}=\mathrm{true}\\ \mathrm{Done}\left(v\right)=\mathrm{false}:\forall \stackrel{\_}{v}\in v.\mathrm{graph}:\stackrel{\_}{v}.\mathrm{visited}=\mathrm{false}\end{array}$

[0236] The maximum test score and the test score actually attained for the vertex are both set.

[0237] If the test is passed, the learner competences will be enlarged to include the competences of the graph, and all of the graph's vertices will be set to “visited.”

[0238] If the test is not passed, all of the graph's vertices are reset to “not visited.”

[0239] The sorting function sortNav(V) may be defined upon an order relation <:V1×V2→bool on a set of vertices. This requires that the following auxiliary functions be defined:

[0240] 1. An order relation for vertices with respect to the vertex ID

[0241] <id:V×V→bool

[0242] v1≦idv2:v1.id<v2.id

[0243] 2. A comparison relation for vertices with respect to the vertex ID

[0244] =:V×V→bool,

[0245] v1=v2:v1.id=v2.id

[0246] 3. An order relation on the test types and unit types

[0247] <test:(TC×TST)×(TC×TST)→bool

[0248] (tst,pre)<(co,undef)<(lu,undef)<(tst,post)

[0249] 4. An order relation based on 3. for vertices with respect to the test types and unit types.

[0250] <test:V×V→bool

[0251] v1<testv2:(v1.contentType,v1.testType)<test(v2.contentType,v2.testType)

[0252] 5. A comparison relation for vertices with respect to the test types and unit types

[0253] =test:V×V→bool

[0254] v1=test v2:(v1.contentType,v1.testType)=(v2.contentType,v2.testType)

[0255] 6. An order relation on the knowledge types based on one of the micro-strategies (see micro-strategies)

[0256] <micro:TK×TK→bool

[0257] 7. An order relation based on 6. on the vertices with respect to the micro-strategies.

[0258] <microV×V→bool

[0259] v1<microV2:v1.knowType<microv2.knowType

[0260] 8. A comparison relation to the vertices in regard to the knowledge types

[0261] =micro:V×V→bool

[0262] v1=microv2:v1.knowType=v2.knowType

[0263] Using these definitions the function <:V1×V2→bool may be defined as follows: 6$v_1<v_2\text{:⇔}\{\begin{array}{ccc}{v}_1.\mathrm{contentType}\ne \mathrm{tst}\bigwedge & & \\ \exists v\in V_1:\left[\left(v_1,v,\mathrm{prereq}\right)\in E_1\bigwedge v.\mathrm{contentType}\ne \mathrm{tst}\bigwedge v_1<v\bigwedge v\le v_2\right]& & \\ \bigvee v_1{<}_{\mathrm{test}}{v}_2& & \\ \bigvee v_1{=}_{\mathrm{test}}{v}_2\bigwedge v_1{<}_{\mathrm{id}}{v}_2& \mathrm{if}& g_1=g_2,t_1\ne \mathrm{lu}\\ & & \\ v_1.\mathrm{contentType}\ne \mathrm{tst}\bigwedge & & \\ \exists v\in V_1:\left[\left(v_1,v,\mathrm{prereq}\right)\in E_1\bigwedge v.\mathrm{contentType}\ne \mathrm{tst}\bigwedge v_1<v\bigwedge v\le v_2\right]& & \\ \bigvee v_1{<}_{\mathrm{test}}{v}_2& & \\ \bigvee v_1{=}_{\mathrm{test}}{v}_2\bigwedge v_1{<}_{\mathrm{micro}}{v}_2& & \\ \bigvee v_1{=}_{\mathrm{test}}{v}_2\bigwedge v_1{=}_{\mathrm{micro}}{v}_2\bigwedge v_1{<}_{\mathrm{id}}{v}_2& \mathrm{if}& g_1=g_2,t_1=\mathrm{lu}\\ & & \\ \exists v=\left(\mathrm{vs},t_1,g_1,\mathrm{tk},\mathrm{tt},\mathrm{ms},\mathrm{as}\right)\in V_2:\left(v,v_2,\mathrm{tr}\right)\in E_2\bigwedge \mathrm{tr}\in \left\{\mathrm{prereq},\mathrm{hierarchical}\right\}& \mathrm{if}& g_1\ne g_2,t_1=\mathrm{lu},t_2\ne \mathrm{lu}\\ \mathrm{false}& \mathrm{otherwise}& \end{array}$

[0264] Note, if g1=g2, then it is obvious that V1=V2, E1=E2, t1=t2 and comp1=comp2. In addition, in case 3, a situation is maintained in which no direct relation between the vertices exists, but there does exist a relation to the higher-order vertex. The order relation will then also apply to all of the vertices in this vertex's content graph. This situation is depicted in FIG. 12, where v is the vertex that represents the learning unit and v1,v2 are the vertices under consideration.

[0265] The function sortNav(V) is the sort of the set V in accordance with the order relation <.

[0266] The following process is one method of implementing the function sortNav(V):

[0267] 1. VpreTest={v∈V|v.contentType=tstv.testType=pre}: the set of all pretests.

[0268] 2. V=V−VpreTest: remove all pretests from V.

[0269] 3. VpostTest={v∈V|v.contentType=tstv.testType=post}: the set of all posttests.

[0270] 4. V=V−VpostTest: remove all posttests from V.

[0271] 5. VpreReq={v∈V|∃({overscore (v)},v,tr)∈E:tr=prerequisite}: the set of all vertices that have a prerequisite relation directed toward them.

[0272] 6. V=V−VpreReq: remove all vertices in VpreReq from V.

[0273] 7. L=VpreTest: add all pretests into the sorted list.

[0274] 8. L=L∪{v∈V|v.contentType=co},V=V−L: enlarge the sorted list to include all vertices that have a learning unit and then remove these vertices from V.

[0275] 9. L=LÅ{v∈V|v.contentType=lu},V=V−L: enlarge the sorted list to include all vertices that contain a learning unit and then remove these vertices from V.

[0276] 10. L=LÅV: enlarge the sorted list to include the remaining vertices from V.

[0277] 11. Search for all vertices in v∈VpreReq:

[0278] the vertex v EL such that (v*,v,prerequisite)∈Edist(v*)=MAX (the vertex that is located farthest back in Land that possesses a prerequisite relation to v).

[0279] Add v into L behind v*.

[0280] 12. L=L∪VpostTest: enlarge the sorted list to include all posttests.

[0281] 13. Return the sorted list L as the result.

[0282] The subsets determined in steps 7-12 are themselves sorted by the order relation <id.

[0283] The following is an example of how a bottom-up (Inductive) learning strategy may be implemented.

[0284] The predicates for this strategy may be the same as those used for the macro-strategy, top-down. The functions for bottom-up may be defined as follows: 7$\mathrm{StartNodes}\left(g\right)=\{\begin{array}{c}g=\mathrm{undef}:\varnothing \\ g.\mathrm{type}=\mathrm{lu}:c.\mathrm{mic}.\mathrm{StartNodes}\left(g\right)\\ g.\mathrm{type}=\mathrm{sc}:\left\{v\in V_g|\forall \left(v^{*},v,\mathrm{tr}\right)\in E:\mathrm{tr}\ne \mathrm{hierarchical}\right\}\end{array}$

[0285] If g is undefined, the vertex doesn't have a content graph and the set is empty.

[0286] If g is a learning unit, then the StartNodes( ) function of the chosen micro-strategy will be used.

[0287] If g is a sub-course, then all vertices that do not have any hierarchical relations referring to them will be returned.

[0288] NextNodes(v)={{overscore (v)}∈Vvgraph|∃({overscore (v)},v,tr)}∪ 8$\left\{\begin{array}{c}v.\mathrm{contentType}=\mathrm{le}\bigwedge \exists \left(v,v^{*},\mathrm{tr}\right)\in E:\mathrm{tr}=\mathrm{hierarchic}\bigwedge \mathrm{Done}\left(v^{*}\right)=\mathrm{false}:\\ \mathrm{OrientationOnly}.\mathrm{StartNodes}\left(v.\mathrm{contentGraph}\right)\\ \mathrm{else}:\\ \mathrm{StartNodes}\left(v.\mathrm{contentGraph}\right)\end{array}\right\}\&AutoLeftMatch;$

[0289] All vertices that are connected to v by an externally directed relation.

[0290] If the vertex contains a learning unit and one of the hierarchically subordinate vertices has not yet been visited, enlarge the set to include the learning unit's starting vertex using the micro-strategy “orientation only.” Otherwise, enlarge the set to include all vertices that are starting vertices of the content graph of v.

[0291] The operations and sorting function for the bottom-up strategy are the similar to the macro-strategy top-down and therefore are not repeated.

[0292] Linear macro-strategies represent a special case of the macro-strategies that have already been described. In linear macro-strategies, the elements of the sorted sets of vertices are offered for navigation sequentially, rather than simultaneously. This linearization may be applied to any combination of macro and micro-strategies.

[0293] The following description includes examples of how a micro-strategy may be realized. In this example, an orientation only micro-strategy is described.

[0294] The predicates for the micro-strategies may be defined as follows:

[0295] Visited (v):v.visited

[0296] The vertex's “visited” attribute is set.

[0297] Suggested(v):∀({overscore (v)},v,tr)∈E such that tr=prerequisite we have: Done({overscore (v)})=true

[0298] All of the vertex's prerequisites are already satisfied.

[0299] CanNavigate(v):Suggested(v)

[0300] This may be used like Suggested.

[0301] Done(v):

[0302] (v.contentType≠tstv.visited=true)

[0303] (c.contentType=tst(v.ascore*2)≧v.mscore)

[0304] The vertex v is considered done if:

[0305] It does not contain a test and has already been visited.

[0306] It deals with a test and at least half of the maximum score has been attained.

[0307] The functions may be defined as follows:

[0308] StartNodes(g)={v∈Vg|v.knowType=Orientation}∪

[0309] {v∈Vg|∃(v,{overscore (v)},tr)∈E:tr=prereq{overscore (v)}.knowType=Orientation}

[0310] The set of all vertices with knowledge type orientation, plus all vertices that have a prerequisite relation to a vertex with knowledge type orientation.

[0311] NextNodes(v)=Ø

[0312] For this micro-strategy, this is always the empty set. In other words, no successor vertices exist because all relevant vertices are contained in the set of starting vertices.

[0313] The operations may be defined as follows:

[0314] navigate(v):v.visited=true

[0315] The vertex's “visited” attribute is set to true.

[0316] testDone(v,MaxScore,ActScore):v.mscore=MaxScore,v.ascore=ActScore

[0317] if 9$\{\begin{array}{c}\mathrm{Done}\left(v\right)=\mathrm{true}:\mathrm{LCOMP}=\mathrm{LCOMP}\bigcup v.\mathrm{graph}.\mathrm{comp},\forall \stackrel{\_}{v}\in v.\mathrm{graph}:\stackrel{\_}{v}.\mathrm{visited}=\mathrm{true}\\ \mathrm{Done}\left(v\right)=\mathrm{false}:\forall \stackrel{\_}{v}\in v.\mathrm{graph}:\stackrel{\_}{v}.\mathrm{visited}=\mathrm{false}\end{array}$

[0318] The maximum test score and the test score actually attained for the vertex are both set.

[0319] If the test is passed, the learner competences will be enlarged to include the competences of the graph, and all of the graph's vertices will be set to “visited.”

[0320] If the test is not passed, all of the graph's vertices are reset to “not visited.”

[0321] The micro-strategy orientation only may use a sorting function that is similar to sorting function for the macro-strategy top-down and, therefore is not repeated.

[0322] The following is an example of the implementation of an example oriented micro-strategy. The predicates for this strategy are identical to those for the micro-strategy orientation only and are not repeated.

[0323] The functions may be defined as follows:

[0324] StartNodes(g)=Vg

[0325] All vertices that are contained in the learning unit.

[0326] NextNodes(v)=Ø

[0327] For this micro-strategy, this is always the empty set. In other words, no successor vertices exist because all relevant vertices are contained in the set of starting vertices.

[0328] The operations for the example-oriented micro-strategy are identical to those for the micro-strategy “orientation only,” and, therefore, are not repeated.

[0329] The sorting function for example-oriented is defined as follows: 10$v_1<v_2\text{:⇔}\{\begin{array}{ccc}{v}_1{<}_{\mathrm{test}}{v}_2\bigvee & & \\ v_1{=}_{\mathrm{test}}{v}_2\bigwedge v_1{<}_{\mathrm{td}}{v}_2& \mathrm{if}& v_2.\mathrm{contentType}=\mathrm{tst}\\ \exists \left(v_1,v_2,\mathrm{tr}\right)\in E:\mathrm{tr}=\mathrm{prereq}\bigvee & & \\ \left(v_1.\mathrm{knowType}=\mathrm{Example}\bigwedge v_1{<}_{\mathrm{id}}{v}_2\right)& \mathrm{if}& v_2.\mathrm{knowType}=\mathrm{Example}\\ v_1.\mathrm{knowType}=\mathrm{Example}\bigvee & & \\ v_1{<}_{\mathrm{id}}{v}_2& \mathrm{otherwise}& \end{array}$

[0330] Steps for executing sortNav(V):

[0331] 1. Vexamp={v∈V|v.knowType=Example}∪

[0332] {v∈V|∃(v,{overscore (v)},tr)∈E:tr=prereq{overscore (v)}.knowType=Example}: the set of all vertices that contain examples, plus the prerequisites of these vertices.

[0333] 2. Vremain=V−Vexamp: the remaining vertices from V.

[0334] 3. Lexamp=TopDown.sortNav(Vexamp): sort the set of examples using the sorting algorithm from the top-down strategy.

[0335] 4. Lremain=TopDown.sortNav(Vremain): sort the set of remaining vertices using the sorting algorithm from the top-down strategy.

[0336] 5. L=Lexamp∪Lremain: form the union of the two sorted lists.

[0337] 6. Return the sorted list L as the result.

[0338] The predicates, functions, and operations for the micro-strategy explanation-oriented are identical to those for the micro-strategy example-oriented, and, therefore are not repeated. The sorting function for the explanation-oriented micro-strategy is similar to the sorting function of the micro-strategy example-oriented (the only difference being that explanations, rather than examples, are used to form the two sets).

[0339] The predicates, functions, and operations for the micro-strategy action-oriented are identical to those for the micro-strategy example-oriented, and, therefore are not repeated. The sorting function for the action-oriented micro-strategy is similar to the sorting function of the micro-strategy example-oriented (the only difference being that actions, rather than examples, are used to form the two sets).

[0340] A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, advantageous results may be achieved if the steps of the disclosed techniques are performed in a different order and/or if components in a disclosed system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components. Accordingly, other implementations are within the scope of the following claims.

Claims

1. A course editor comprising: an input to accept author commands; and an interface to process and display the author commands to facilitate the creation of a course, the interface including, a work space to display and assemble structural elements into the course.

2. The course editor of claim 1 wherein the workspace includes a menu of structural elements that may be added to the course.

3. The course editor of claim 2 wherein the workspace is configured to display a structural element in response to an author command selecting the structural element from the menu.

4. The course editor of claim 1 wherein the structural elements are one of a sub-course, a learning unit, and a knowledge item.

5. The course editor of claim 1 wherein the work space includes one or more tabs, each tab corresponding to a content aggregation level to display structural elements corresponding to the content aggregation level.

6. The course editor of claim 1 wherein the workspace is configured to create a relation between structural elements that is used to indicate a dependency between the structural elements.

7. The course editor of claim 1 wherein the workspace includes a menu of relations configured to enable an author to select a relation from the menu and to insert the relation between a first structural element and a second structural element displayed in the workspace.

8. The course editor of claim 7 wherein the interface is configured to insert the relation by receiving an author command selecting the first structural element and dragging the relation from the first structural element to the second structural element.

9. The course editor of claim 6 wherein the relation is true in one direction only.

10. The course editor of claim 6 wherein the relation is true in two directions.

11. The course editor of claim 6 wherein the relation is subject taxonomic.

12. The course editor of claim 11 wherein the subject taxonomic relation is hierarchical.

13. The course editor of claim 12 wherein the hierarchical relation is one of a part/whole relation and an abstraction relation.

14. The course editor of claim 11 wherein the subject taxonomic relation is associative.

15. The course editor of claim 14 wherein the associative relation is one of determines, side-by-side, alternative to, opposite to, precedes, context of, process of, values, means of, and affinity.

16. The course editor of claim 6 wherein the relation is non-subject taxonomic.

17. The course editor of claim 16 wherein the non-subject taxonomic relation is a relation that indicates a structural element should be completed before proceeding to a related structural element.

18. The course editor of claim 16 wherein the non-subject taxonomic relation is a relation that indicates that a structural element belongs to another structural element.

19. The course editor of claim 1 wherein the interface includes a dialog box displaying one or more fields corresponding to a structural element displayed in the workspace.

20. The course editor of claim 19 wherein the one or more fields include a name field.

21. The course editor of claim 19 wherein the one or more fields include a theme field.

22. The course editor of claim 19 wherein the one or more fields include a content field to assign content to a structural element.

23. The course editor of claim 19 wherein the one or more fields include a media type field.

24. The course editor of claim 19 wherein the one or more fields include a learning time field.

25. The course editor of claim 19 wherein the one or more fields include a thumbnail field.

26. The course editor of claim 19 wherein the one or more fields include an attribute field to assign a knowledge type.

27. The course editor of claim 19 wherein the dialog box includes one or more tabs to select different fields.

28. The course editor of claim 27 wherein the one or more tabs include a general tab includes fields to receive information about content associated with the structural elements.

29. The course editor of claim 27 wherein the one or more tabs include an annotation tab that includes a field to receive notes regarding content associated with the structural elements.

30. The course editor of claim 27 wherein the one or more tabs include keyword tab including a field to receive keywords to help search for a corresponding structural element.

31. The course editor of claim 27 wherein the one or more tabs include a competency tab including fields to receive competencies gained from content associated with the structural element.

32. The course editor of claim 1 wherein the interface includes a course overview to display structural elements and relations of the course.

33. The course editor of claim 32 wherein the interface is configured to receive an author command selecting a structural element from the course overview and to display the selected structural element in the workspace.

34. The course editor of claim 33 wherein the interface is configured to automatically display a dialog box corresponding to the selected structural element.

35. The course editor of claim 32 wherein the interface is configured to receive an author command selecting a relation from the course overview and to display the selected relation and associated structural elements in the workspace.

36. The course editor of claim 1 wherein the interface is configured to receive an author command selecting a learning strategy to generate a navigation path for display to the author based on the selected learning strategy.

37. A graphical user interface for a course editor comprising: a workspace window to edit and display structural elements of a course; an overview window to display and select a representation of the structural elements of the course; and a dialog box window to display data fields corresponding to structural elements shown in the workspace window.

38. The graphical user interface of claim 37 further comprising a menu bar to display course editor menus including functions to control and interact with the course editor.

39. The graphical user interface of claim 37 further comprising a button bar including one or more buttons to invoke course editor functions to interact with the windows and their displayed contents.

40. The graphical user interface of claim 37 wherein a structural element is displayed as a rectangle in the workspace.

41. The graphical user interface of claim 40 wherein the rectangle is color-coded, each type of structural element having a different color.

42. The graphical user interface of claim 37 wherein the workspace includes a menu of structural elements that may be added to the course.

43. The graphical user interface of claim 42 wherein the workspace is configured to display a structural element selected from the workspace menu.

44. The graphical user interface of claim 37 wherein the structural elements are one of a sub-course, a learning unit, and a knowledge item.

45. The graphical user interface of claim 37 wherein the work space includes one or more tabs, each tab corresponding to a content aggregation level to display structural elements corresponding to the content aggregation level.

46. The graphical user interface of claim 37 wherein the workspace is configured to create a relation between structural elements that is used to indicate a dependency between the structural elements.

47. The graphical user interface of claim 37 wherein the workspace includes a menu of relations and the workspace is configured to display a relation selected from the menu.

48. The graphical user interface of claim 47 wherein the interface is configured to insert the relation by indicating a first structural element that is selected in the workspace window, displaying an indication of a relation extending from the first structural element, and connecting the extended relation to a second structural element displayed in the workspace.

49. The graphical user interface of claim 46 wherein the indication of a relation that is true in one direction only is an arrow.

50. The graphical user interface of claim 46 wherein the indication of a relation that is true in two directions is a line.

51. The graphical user interface of claim 46 wherein the dialog box may be used to specify the relation is subject taxonomic.

52. The graphical user interface of claim 51 wherein the dialog box may be used to specify relation is hierarchical.

53. The graphical user interface of claim 52 wherein the dialog box may be used to specify the relation is one of a part/whole relation and an abstraction relation.

54. The graphical user interface of claim 51 wherein the dialog box may be used to specify the relation is one of determines, side-by-side, alternative to, opposite to, precedes, context of, process of, values, means of, and affinity.

55. The graphical user interface of claim 46 wherein the dialog box may be used to specify the relation is non-subject taxonomic.

56. The graphical user interface of claim 55 wherein the dialog box may be used to specify the non-subject taxonomic relation is a relation that indicates a structural element should be completed before proceeding to a related structural element.

57. The graphical user interface of claim 55 wherein the dialog box may be used to specify the non-subject taxonomic relation is a relation that indicates that a structural element belongs to another structural element.

58. The graphical user interface of claim 37 wherein the dialog box is configured to display one or more fields corresponding to a structural element displayed in the workspace.

59. The graphical user interface of claim 58 wherein the one or more fields are configured to receive data characterizing a structural element.

60. The graphical user interface of claim 58 wherein the one or more fields include a name field.

61. The graphical user interface of claim 58 wherein the one or more fields include a theme field.

62. The graphical user interface of claim 58 wherein the one or more fields include a content field to assign content to a structural element.

63. The graphical user interface of claim 58 wherein the one or more fields include a media type field.

64. The graphical user interface of claim 58 wherein the one or more fields include a learning time field.

65. The graphical user interface of claim 58 wherein the one or more fields include a thumbnail field.

66. The graphical user interface of claim 58 wherein the one or more fields include an attribute field to assign a knowledge type.

67. The graphical user interface of claim 58 wherein the dialog box includes one or more tabs each populated with one or more fields.

68. The graphical user interface of claim 67 wherein the one or more tabs include a general tab including fields to receive information about content associated with the structural elements.

69. The graphical user interface of claim 67 wherein the one or more tabs include an annotation tab including a field to receive notes regarding content associated with the structural elements.

70. The graphical user interface of claim 67 wherein the one or more tabs include a keyword tab including a field to receive keywords to help search for a corresponding structural element.

71. The graphical user interface of claim 67 wherein the one or more tabs include a competency tab including a field to receive competencies gained from the content associated with the structural elements.

72. The graphical user interface of claim 37 wherein the overview window is configured to display an indication of a selected structural element and the workspace window is configured to display the indicated structural element.

73. The graphical user interface of claim 72 wherein the dialog box window is configured to automatically correspond to the selected structural element.

74. The graphical user interface of claim 37 wherein the interface is configured to display a learning strategy window to indicate a selected strategy and to generate a navigation path window to display a suggested sequence of structural elements based on the selected learning strategy.

75. The graphical user interface of claim 37 wherein the windows are automatically sized to fit on a corresponding display.

76. The graphical user interface of claim 75 wherein one or more of the windows include a vertical scroll bar to access and display portions of the window that are not displayed.

77. The graphical user interface of claim 75 wherein one or more of the windows include a horizontal scroll bar to access and display portions of the window that are not displayed.