BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to mind mapping systems, and, more particularly, to a method for creating and tracking external system data via a mind map.

2. Description of the Background Art

A mind map is a diagram that represents ideas and/or information around a central topic. Mind maps are increasingly used to help people generate, classify, and/or organize ideas and information and to see such ideas and information in a hierarchical, visual layout. Mind maps are made up of hierarchically-arranged “topics.”

There are software programs that enable people to easily create mind maps. Mindjet, Inc.'s Mind Manager software is an example of such software.

One of the most common uses of mind mapping software is in group meetings for planning projects, tasks, processes, etc. FIG. 8 is an example of a mind map that organizes information and ideas related to a website update project. A group may use mind mapping software to organize data related to a project task, or process, and, subsequently, an individual often will manually enter data from the map into a separate project management, requirements management (e.g., Microsoft Visual Studio Team System, Telelogic Doors), workflow management (e.g., CRM systems, Oracle Workflow), and business process modeling software system. As entering data manually into such systems can be tedious, it is desirable to have mind mapping software that can interface with such systems in order to upload data from a mind map to such systems. Moreover, if changes are made to the data in such systems, it is desirable to update the mind map with such changes. This would allow a person managing a project, task, or process to easily track the status of the project, task, or process through the mind map.

SUMMARY

The present invention provides a system and method for uploading mind map data to an external system and tracking changes to such data in the external system through the mind map. The invention enables a user to create data objects in an external system through a mind map by classifying topics in the mind map, where the mind map is generated through a mind mapping system.

The mind mapping system presents the user with classification categories that correspond to data types in the external system. By classifying a topic in accordance with such classification categories, a user is essentially mapping the topic to a data type in the external system. The mind mapping system interfaces with the external system to upload data in classified topics to the external system.

At a later point, the user can then track any changes made to the data in the external system through the mind map. Specifically, at the user's request or upon another trigger event (e.g., user opens map), the mind mapping system (in one embodiment) queries the external system for any updates to data objects in the external system that were created through the mind map.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart that illustrates a method for uploading mind map data to an external system and tracking such data via a mind map.

FIG. 2 is a flowchart that that illustrates one way in which a mind mapping system can implement the method of FIG. 1.

FIG. 3 is a flow chart that illustrates a more detailed, example implementation of the method of FIG. 1.

FIG. 4 is a mind map that illustrates an example of developer and mind mapping system requirements to create one embodiment of the invention.

FIG. 5 illustrates a block diagram of a mind mapping system.

FIG. 6 is a mind map that illustrates an example implementation in which a mind mapping system interfaces with Microsoft's Visual Studio Team Server.

FIGS. 7a-g are screen shots that correspond to the example discussed with respect to FIG. 6.

FIG. 8 is an example of a mind map.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 illustrates a method for uploading mind map data to an external system and tracking such data via a mind map. The method comprises creating a mind map (step 110), classifying one or more topics in the mind map in accordance with data types in the external system (step 120), uploading data in classified topics to data objects in an external system (step 130); and subsequently receiving one or more updates for the data objects from the external system and updating the classified topics in the mind map in accordance with the updates from the external system (step 140).

The mind map may be created manually by a user, or it may be generated by a mind mapping system that queries and formats data from one or more data sources. Topics can be manually classified by the user, or the mind map can be based on a template in which the outline of the map equates to classification categories. The steps of mapping and writing data to an external system are performed by a mind mapping system. In one embodiment, a mind mapping system comprises mind mapping software running on a computer.

The invention is particularly useful in task/project management. Elements of a project or task can be set forth in a mind map during a group meeting, and the data from such mind map can then be automatically uploaded to a task/project management system. A project manager can track the status of the project/task through the mind map by initiating requests to “refresh” the mind map with any changes to the data made in the task/project management system.

FIG. 2 illustrates one way in which a mind mapping system implements the method illustrated in FIG. 1 and enables the user to classify topics. The mind mapping system presents the user with classification categories (step 210). Each classification category corresponds to a data type in the external system. The mind mapping system enables the user to classify one or more topics using the classification categories (step 220). For instance, the mind mapping system may enable a user to classify a topic by tagging a topic with an icon that represents a classification category.

For each topic classified with a classification category, the mind mapping system uploads data from the classified topic to the external system, where the data is uploaded into an object of a data type corresponding to the classification category of the topic (step 230). At a later point (which may be determined by the user or upon the occurrence of a triggering event), the mind mapping system requests an update from the external system for objects in the external system corresponding to classified topics (step 240). In response to receiving updates for such objects from the external system, the mind mapping system updates the data associated with the classified topics (step 250).

Once a topic has been classified and its data uploaded to an external system, subsequent changes to such topic also can be uploaded to the external system. If changes have been made to both the classified topic and the corresponding data object in the external system since the last update was downloaded from the external system, a conflict can occur. In such case, the mind mapping system and/or the external system may employ conflict resolution rules. An example of a conflict resolution rule is allowing changes in an external system to trump changes in mind map and vice versa. Other more complex conflict resolution rules can be implemented, and rules for resolving conflicts between two data sources are well known in the art.

FIGS. 3a-b illustrate an example of a more detailed implementation of the method illustrated in FIG. 2. FIGS. 3a-b illustrate just one way to implement this method and the invention is no way limited to this implementation.

When the mind mapping system receives a request from user to connect with an external system, the mind mapping system retrieves classification categories corresponding to data types in the external system (step 310). The mind mapping system either requests these classification categories real time from the external system or retrieves them from local storage.

The mind mapping system then displays the classification categories to the user (step 320). Examples of ways in which classification categories can be displayed include displaying the classification categories within a sub-window in the mind mapping system user interface, where the classification categories are listed in text form and/or represented by icons. The hierarchy of the mind map can also represent classifications.

In response to the user classifying topics in accordance with the classification categories and then initiating a “publish request” (i.e., a request to upload the data in the classified topics to the external system), the mind mapping system uploads data to the external system. More specifically, for each classified topic, the mind mapping system asks the external system to create a data “object” of the applicable data type (i.e., the data type corresponding to the topic's classification) (step 330). In one embodiment, such object is an instance of a class for the applicable data type. After the external system creates the requested objects, its sends the mind mapping system a unique ID for each of the objects. The mind mapping system stores the unique IDs as part of the topic properties for the classified topics (step 340). For each classified topic, the mind mapping system uploads data associated with the topic into the applicable object in the external system using the applicable unique ID (step 350).

Data in classified topics is refreshed with updates from the external system upon the occurrence of a refresh trigger event (e.g., user enters a refresh command, certain amount of time passes, mind map is opened again, etc.). When a refresh trigger event occurs, the mind mapping system scans the map metadata for all topics with unique IDs from the external system (step 360). For each unique ID found, the mind mapping system queries the external system for a record associated with the unique ID (step 370). If the external system has a record with the unique ID, it sends the mind mapping system updates for that record, and the mind mapping system updates the applicable topic accordingly (step 380). Otherwise, it informs the mind mapping system that the record does not exist in the external system. The mind mapping system then either generates an error message or deletes the topic corresponding to such unique ID from the mind map (step 390).

FIG. 4 is a mind map that illustrates developer and mind mapping system requirements to create one embodiment of the above-described methods. These requirements are based on one embodiment of the invention, and the invention is not limited to these requirements. Moreover, FIG. 4 is not intended to be a comprehensive list of all requirements, just the key requirements for this one embodiment.

With respect to developer requirements (410), the developer of the mind mapping system must be able to understand the data types in the external system (420). This means that the data schemas of the data types must be accessible to the developer. Instances of the data types selected by the developer must be uniquely identifiable (such as objects with unique IDs).

The developer (according to one embodiment) also needs to determine which data types are creatable and which, if any, are not creatable (430). For instance, in a project management system, tasks and projects are creatable, but resources (such as people) may be fixed and not-creatable. Creatable data types can be potentially created in a mind mapping system. Non-creatable data types cannot be created in the mind mapping system, but they can be associated with creatable data types (e.g., a particular person can be assigned to a task or a resource can be allocated to a project).

The developer (according to one embodiment) also must determine the way(s) in which a user can classify a topic in a mind map in order to transform topic data into external system data (440). Examples include having an icon or text for each classification category and having the user tag topics with such icons or texts. Other graphical elements of the topic, such as the color or shape can be associated with classification categories. Also, links between topics, as well as the overall hierarchy of the mind map, also can be used to represent classifications.

The developer (according to one embodiment) must also write rules as to how topic data will be validated and mapped into data schemas for data types in the external system (450).

With respect to the requirements for the mind mapping system (according to one embodiment) (460), the mind mapping system must be able to retrieve and display the classification categories (470). The classification categories are just the data types in the external system that can be created or assigned through the mind mapping system. These data types could be stored in local storage associated with the mind mapping system or the mind mapping system could query the external system for the data types.

The mind mapping system (according to one embodiment) must be able to create data objects in the external system and upload data to such objects (480). In one embodiment, the mind mapping system uses rules created by the developer to validate the data in classified topics and map validated data to a data object. The mind mapping system also must be able to query the external system for information associated with an object and modify the map accordingly (step 490).

The mind mapping system (according to one embodiment) must support triggering events to initiate data upload (495). Examples of triggering events are: a user initiated command (e.g., users clicks on “upload” or “refresh” button); time-based events (e.g., every hour); opening map, closing map, call by external system, user makes changes to topic, etc.

FIG. 5 illustrates an example of a mind mapping system 500. The mind mapping system 500 includes a mind mapping application 510 that enables users to create, edit, and save mind maps. Examples of a mind mapping application 510 include Mindjet's MindManager software. The mind mapping system 500 also includes an interface application 520 that interfaces with an external system 530. The interface application 520 performs the uploading and downloading steps described with respect to FIGS. 2 and 3 (including data validation). In an alternate embodiment, the functionality of the interface application 520 is built into the mind mapping application 510.

FIGS. 7a-g and FIG. 6 illustrate an example implementation the invention in which the mind mapping system interfaces with Microsoft's Visual Studio Team Server Software (“Visual Studio”). Visual Studio includes project management software in which users can create and track “Work Items” for a project. FIG. 6 lists the steps in this example, and FIGS. 7a-g illustrate corresponding screen shots.

In this example, the user creates a map that defines the requirements of a software project (step 610; FIG. 7a). The project is broken down into tasks, bugs, and scenarios.

The user then connects to Visual Studio, where the user suppliers the server name, user name, and password and where the user selects “test” as the project type (step 620, FIG. 7b). Classification categories for a “test” project are then downloaded from Visual Studio (FIG. 7c). These classification categories correspond to “Work Items” in Visual Studio for projects of the type “test.” As illustrated in window 710 of FIG. 7c, these classification categories are “Bug,” “Task,” “Quality of Service Requirement,” “Scenario,” and “Risk.”

The user classifies the topics in the mind map in accordance with these classification categories (step 630). In this example, the user classifies a topic by selecting a topic and then double clicking on one of the classification categories. In the example, illustrated in FIG. 7d, the user has classified the “Sync Button” topic 740 as a “task” Work Item. When the user does this, a form appears for the user to enter data for the task “Sync Button.” In one embodiment, classified topics are implemented as “content-specific topics”, which are described in U.S. patent application Ser. No. 11/478,220, titled “System and Method for Providing Content-Specific Topics in a Mind Mapping System,” and filed on Jun. 29, 2006, the contents of which are incorporated by reference as if fully disclosed herein.

When a user enters a command to upload the classified topics to Visual Studio, the mind mapping system requests that Visual Studio create a “Work Item” object for each of the classified topics (step 640). For instance, the mind mapping system request that Visual Studio create a “Task” Work Item object for the classified “Sync Button” topic 740. Visual Studio then creates the requested objects and sends the mind mapping system a unique ID for each of the created objects (step 650). The mind mapping system then uploads the data to the external system using the unique IDs (step 660). For example, with respect to the “Sync Button” topic 740, the mind mapping system uploads data entered into form 720 (FIG. 7d) to Visual Studio with the unique ID for the Task Work Item object created for the Sync Button topic 740. FIG. 7e is a screen shot of Visual Studio in which “Sync Button” appears as a “Task” Work Item. The data entered into form 720 in the mind map appears in the Visual Studio interface illustrated in FIG. 7e. The data sent from the mind mapping system to Visual Studio is either validated by the mind mapping system and/or Visual Studio.

In the map illustrated in FIG. 7a there is a relationship between the task “Sync Button” and the bug “Hanging Reference Issue” 730 which is formed by the dotted line connecting the topics. In this example, the business rules for mapping classified topics to Visual Studio Work Items specify that a relationship in the mind map translates to a related “Link” in a Work Item. Consequently, as illustrated in FIG. 7f, the Hanging Reference Issue bug appears under the “Link” tab of the “Sync Button” Work Item in Visual Studio.

In this example, after work for the Sync Button is complete, someone modifies the “Sync Button” Work Item through Visual Studio to reflect this. Specifically, status is changed from “active” to “closed” and reason is changed from “new” to “complete,” as shown in FIG. 7f.

When a user of the mind mapping system opens up the mind map for the “test” project at a later point and initiates a refresh command to track the status of the software project (step 670), the mind mapping system queries Visual Studio for updates to Work Items corresponding to the classified topics, including the Sync Button Work Item. The Visual Studio then sends the updates (e.g., the changes to the fields “status” and “reason” in the Sync Button Work Item), and the mind mapping software updates the classified topics accordingly (step 680). The changes to the Sync Button topic 740 are displayed in FIG. 7g.

If the mind map user changes the data in an existing classified topic and enters a “refresh” command, these changes are uploaded to Visual Studio. If changes have also been made to the data in Visual Studio since the last update from Visual Studio, the mind mapping system them employs applicable conflict resolution rules to determine whether the changes should be written to the Visual Studio data.

In an alternate embodiment of the invention, when the mind mapping system displays classification categories corresponding to creatable data types, it also displays representations of non-creatable data types (e.g., such as human, machine, and monetary resources for a project). The non-creatable data types can then be linked to classified objects. For instance, in the above example, the mind mapping system could retrieve a list of “software developer” resources from the external system. One of the software developers could then be linked to the “Sync Button” topic 740.

As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the above disclosure of the present invention is intended to be illustrative and not limiting of the invention.