Ontological representation of knowledge

• US 20080255918A1
• Filed: 04/03/2008
• Published: 10/16/2008
• Est. Priority Date: 01/20/2001
• Status: Abandoned Application

• Current Assignee: PointCross, Inc.
• Original Assignee: PointCross, Inc.
• Inventors: Madhavan, Suresh
• Application Number:
  US12/080,592
• Publication Number:
  US 20080255918A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06F 16/367 Ontology
• CPC Class Codes: G06Q 10/063118 Staff planning in a project environment
• CPC Class Codes: G06Q 10/0635 Risk analysis of enterprise or organisation activities
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 10/06395 Quality analysis or management

Abstract

A technique for representing a project over a network involves developing requirements for the project and linking responses to the requirements. A user associated with the project is automatically linked to project data in accordance with the user'"'"'s role in the project. The project data includes the requirements, responses and other data.

Claims

1. A method comprising:

receiving registration information including a list of users;

creating a node in a hierarchical tree of project requirements, wherein the node of the hierarchical tree of project requirements includes a domain name associated with a domain that defines a specialty area or subject matter associated with the node;

assigning users from the list of users to the node, wherein users of the list of users assigned to the node are associated with a responsibility and arranged in a hierarchical tree of roles;

receiving a response to the requirement associated with the node;

creating a link between the requirement and response;

wherein creating the link automatically links the response to a user based on the role associated with the user.

2. The method of claim 1, further comprising receiving project information, wherein the project information includes a project identifier and a project description.

3. The method of claim 1, further comprising creating a project in association with the project information, and if a project owner of the project is not registered, creating a corporate account.

4. The method of claim 1, further comprising creating an organization breakdown structure associated with the project, wherein each user assigned to the node is associated with a role and arranged in a hierarchical tree of roles associated with the node.

5. The method of claim 1, further comprising developing a specification and a description of a project associated with the node.

6. The method of claim 1, further comprising sending a web page to a client computer after a user logs included in the list of users into a server computer, wherein the web page includes buttons for a user to add, delete, edit, export, and/or import data associated with the node.

7. The method of claim 1, further comprising sending a web page to a client computer after a user selects the node, wherein the web page includes a frame showing requirements or responses, an interface to a plurality of software, and notifications of messages to the user.

8. The method of claim 1, wherein the node is associated with a project, further comprising selecting a phase and associating a workflow process with the project, wherein the workflow process sends out alerts when manually triggered or automatically triggered by events specified by date, time, and action.

9. The method of claim 1, wherein the organization breakdown structure includes a user'"'"'s access and modification rights.

10. The method of claim 1, further comprising identifying, reviewing, or mitigating a risk associated with the requirement.

11. The method of claim 1, further comprising estimating costs of a project based on an estimate provided for the node in the hierarchical tree of project requirements.

12. The method of claim 1, further comprising coordinating or reviewing conferences associated with the node.

13. The method of claim 1, further comprising providing and managing a description, a specification, or a document in the node.

14. The method of claim 1, further comprising providing a compliance level for the response to indicate a degree to which the response meets the requirement.

15. A system comprising:

a server computer including a computer readable medium including a project management software;

a database storage;

a plurality of client computers;

wherein, in operation, a plurality of users exchange project requirements and responses by communicating using threaded and context-sensitive messages, the database storage saves project related data including the project requirements and the responses under a plurality of hierarchical tree structures wherein the project requirements include tasks, milestones, deliverable items, procured items, and/or specifications, and the plurality of hierarchical tree structures include a project hierarchical tree and a organization hierarchical tree, wherein each of the users is assigned to a node in the organization hierarchical tree associated with a responsibility and arranged in a hierarchical tree of roles; and

the server computer manages the database storage made accessible to the client computers using the project management software and controls data flow with client computers and the database storage, and links are made among data in the plurality of hierarchical trees based on relevance to the project requirements and communications among users so that linked data is searchable as an organized group.

16. The system of claim 15, wherein the project management software further includes a security and authority level control that limits a user'"'"'s access to information stored in the database based on the security and authority level assigned to the user.

17. The system of claim 15, wherein data in the project hierarchical tree includes a domain name associated with a domain that defines a specialty area or subject matter associated with a node in the project hierarchical tree.

18. The system of claim 15, wherein data in the plurality of hierarchical tree structures include a risk and/or mitigations for the risk, wherein the risk is associated with at least one project requirement.

19. The system of claim 15, wherein data in the plurality of hierarchical tree structures include an estimate of cost to fulfill a project requirement.

20. A system comprising:

means for receiving a list of users;

means for creating a node in a hierarchical tree including one or more requirements for the node;

means for assigning a user from the list of users to the node;

means for receiving a response to a requirement associated with the node from the user;

means for creating a link between the requirement and the response.