METHOD AND SYSTEM FOR ROLE BASED SITUATION AWARE SOFTWARE

• US 20090210408A1
• Filed: 02/19/2008
• Published: 08/20/2009
• Est. Priority Date: 02/19/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kelley, Edward E., Boyer, John E., Lane, Eoin
• Granted Patent: US 8,805,774 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually

Abstract

A method for role based situation aware software includes: mapping one or more users to one or more communities of practice (CoP); aggregating a series of tags from the one or more CoP to form an initial set of role-based tags; filtering the initial set of role-based tags based on user context elements to form context sensitive user-role tags; querying one or more information services based on the context sensitive user-role tags; aggregating information obtained from querying the one or more information services; and providing the aggregated information to the user as dynamic context related content.

Claims

1. A method for role based situationally aware software, the method comprising:

mapping one or more users to one or more communities of practice (CoP);

aggregating a series of tags from the one or more CoP to form an initial set of role-based tags;

filtering the initial set of role-based tags based on user context elements to form context sensitive user-role tags;

querying one or more information services based on the context sensitive user-role tags;

aggregating information obtained from querying the one or more information services; and

providing the aggregated information to the user as dynamic context related content.

2. The method of claim 1, wherein the mapping of a user to one or more CoP is based on defined user roles.

3. The method of claim 1, wherein the user context elements comprise at least one of:

a skill level the user has in the role;

a preferred language of the user in the role;

an industry vertical the user in the role is in;

a method the user in the role is using;

where the user in the role is in the method;

what tool, including the tool'"'"'s version, the user in the role is using;

what file type the user in the role is using;

what file type the user in the role is using with the tool;

custom context as supplied by a team leader; and

the location of the user in that role.

4. The method of claim 1, wherein the user services comprise at least one of:

bookmark services, media services, asset services, people services, educational services, social software services, blogs, and wikis.

5. The method of claim 1, wherein a service oriented architecture (SOA) is utilized for implementing the method.

6. The method of claim 1, wherein the initial set of role-based tags is context independent.

7. The method of claim 1, wherein the initial set role-based tags are filtered using a set of user defined personal tags to form a set of user in role-based tags;

and

wherein the set of user in role-based tags are further filtered with a set of context elements to form a set of context sensitive user-role tags.

8. An article comprising one or more computer-readable storage media containing instructions that when executed by a computer enables a role based situationally aware software application that maps user roles to a consistent set of tags, wherein the method further comprises:

mapping one or more users to one or more communities of practice (CoP);

aggregating a series of tags from the one or more CoP to form an initial set of role-based tags;

filtering the initial set of role-based tags based on user context elements to form context sensitive user-role tags;

querying one or more information services based on the context sensitive user-role tags;

aggregating information obtained from querying the one or more information services; and

providing the aggregated information to the user as dynamic context related content.

9. The article of claim 8, wherein the mapping of a user to one or more CoP is based on defined user roles.

10. The article of claim 8, wherein the user context elements comprise at least one of:

a skill level the user has in the role;

a preferred language of the user in the role;

an industry vertical the user in the role is in;

a method the user in the role is using;

where the user in the role is in the method;

what tool, including the tool'"'"'s version, the user in the role is using;

what file type the user in the role is using;

what file type the user in the role is using with the tool;

custom context as supplied by a team leader; and

the location of the user in that role.

11. The article of claim 8, wherein the user services comprise at least one of:

bookmark services, media services, asset services, people services, educational services, social software services, blogs, and wikis.

12. The article of claim 8, wherein a service oriented architecture (SOA) is utilized to implement the article.

13. The article of claim 8, wherein the initial set of role-based tags is context independent.

14. The article of claim 8, wherein the initial set role-based tags are filtered using a set of user defined personal tags to form a set of user in role-based tags;

and

wherein the set of user in role-based tags are further filtered with a set of context elements to form a set of context sensitive user-role tags.

15. A system for a role based situationally aware software information tool that maps user roles to a consistent set of tags, the system comprising:

one or more server devices in communication with one or more client devices through a network;

the server devices and the client devices configured to execute electronic software;

wherein the electronic software is resident on storage mediums in signal communication with the client and server devices;

wherein the electronic software comprises a series of instructions configured for;

mapping one or more users to one or more communities of practice (CoP);

aggregating a series of tags from the one or more CoP to form an initial set of role-based tags;

filtering the initial set of role-based tags based on user context elements to form context sensitive user-role tags;

querying one or more information services based on the context sensitive user-role tags;

aggregating information obtained from querying the one or more information services; and

providing the aggregated information to the user as dynamic context related content.

16. The system of claim 15, wherein the mapping of a user to one or more CoP is based on defined user roles.

17. The system of claim 15, wherein the user context elements comprise at least one of:

a skill level the user has in the role;

a preferred language of the user in the role;

an industry vertical the user in the role is in;

a method the user in the role is using;

where the user in the role is in the method;

what tool, including the tool'"'"'s version, the user in the role is using;

what file type the user in the role is using;

what file type the user in the role is using with the tool;

custom context as supplied by a team leader; and

the location of the user in that role.

18. The system of claim 15, wherein the user services comprise at least one of:

bookmark services, media services, asset services, people services, educational services, social software services, blogs, and wikis.

19. The system of claim 15, wherein a service oriented architecture (SOA) is utilized within the system.

20. The system of claim 15, wherein the initial set of role-based tags is context independent.