SINGLE POINT OF ENTRY FOR WEB APPLICATIONS

• US 20090083104A1
• Filed: 07/23/2008
• Published: 03/26/2009
• Est. Priority Date: 07/10/2003
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Barrett, Kevin R.
• Granted Patent: US 8,271,614 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine

Abstract

A method for centralizing web application interaction, the method including handling a request, using a central point of entry, from a remote application, determining a local application suitable for processing the request, and handing out the request to the, local application determined to be suitable for processing the request.

Claims

1. A method for managing a project comprising:

storing information pertaining to a project item in an electronic memory, wherein the information indicates a first date associated with the project item and a second date associated with the project item;

calculating a difference between the first date and the second date;

comparing the difference to at least one tolerance associated with a particular status;

assigning a status to the project item based on the comparison; and

presenting the status to a user.

2. The method of claim 1, wherein at least one of the first date and the second date comprises a start date associated with the project item.

3. The method of claim 1, wherein at least one of the first date and the second date comprises a finish date associated with the project item.

4. The method of claim 1, wherein the first date comprises one of an actual start date and an actual finish date and the second date comprises one of a baseline start date and a baseline finish date and wherein assigning a status comprises assigning a critical status to the project if the difference is greater than a critical tolerance.

5. The method of claim 1, wherein the first date comprises one of a scheduled start date and a scheduled finish date and the second date comprises one of a baseline start date and a baseline finish date and wherein assigning a status comprises assigning a critical status to the project if the difference is greater than a critical tolerance.

6. The method of claim 1, wherein assigning a status to the project comprises:

assigning a critical status to the project if the difference is greater than a critical tolerance;

assigning a warning status to the project if the difference is greater than a warning tolerance and the difference is not greater than the critical tolerance; and

assigning a normal status to the project if the difference is not greater than the warning tolerance.

7. The method of claim 1, wherein calculating a difference between the first date and the second date comprises calculating a number of working days between the first date and the second date based on a project calendar, wherein the project calendar indicates whether at least one date between the first date and the second date is a working day.

8. The method of claim 1, wherein presenting the status to a user comprises:

creating a Gantt chart that includes information relating to the project item of the project; and

displaying the Gantt chart to the user.

9. The method of claim 8, wherein said Gantt chart is a drillable Gantt chart.

10. The method of claim 8, wherein:

the Gantt chart includes a plurality of color-coded bars;

each color-coded bar is associated with a project item of the project; and

each color-coded bar is colored based on a status of the project item associated with that bar.

11. The method of claim 10, wherein a color-coded bar associated with at least one project item is colored:

a first color if the particular project item has a critical status;

a second color if the particular project item has a warning status; and

a third color if the particular project item has a normal status.

12. The method of claim 1, wherein:

the project item comprises one of a plurality of project items associated with a project; and

presenting the status to the user comprises;

creating a report identifying the status of the project items; and

displaying the report to the user.

13. The method according to claim 12, wherein:

the project comprises one of a plurality of projects; and

creating the report comprises creating a report that indicates an amount of effort that has been expended on each of the plurality of projects.

14. The method according to claim 12, wherein:

the project comprises one of a plurality of projects; and

creating the report comprises creating a report that indicates a status of each of a plurality of project items associated with each of the projects.

15. A computer product comprising software encoded in computer-readable media, the software comprising instructions operable, when executed, to:

store information pertaining to a project item in an electronic memory, wherein the information indicates a first date associated with the project item and a second date associated with the project item;

calculate a difference between the first date and the second date;

compare the difference to at least one tolerance associated with a particular status;

assign a status to the project item based on the comparison; and

present the status to a user.

16. The computer product of claim 15, wherein the first date comprises one of an actual start date and an actual finish date and the second date comprises one of a baseline start date and a baseline finish date and wherein the instructions are operable to assign a status by assigning a critical status to the project if the difference is greater than a critical tolerance.

17. The computer product of claim 15, wherein the first date comprises one of a scheduled start date and a scheduled finish date and the second date comprises one of a baseline start date and a baseline finish date and wherein the instructions are operable to assign a status by assigning a critical status to the project if the difference is greater than a critical tolerance.

18. The computer product of claim 15, wherein the instructions are operable to assign a status by:

assigning a critical status to the project if the difference is greater than a critical tolerance;

assigning a warning status to the project if the difference is greater than a warning tolerance and the difference is not greater than the critical tolerance; and

assigning a normal status to the project if the difference is not greater than the warning tolerance.

19. The computer product of claim 15, wherein the instructions are operable to calculate a difference between the first date and the second date by calculating a number of working days between the first date and the second date based on a project calendar, wherein the project calendar indicates whether at least one date between the first date and the second date is a working day.

20. The computer product of claim 15, wherein the instructions are operable to present the status to a user by:

creating a Gantt chart that includes information relating to the project item of the project; and

displaying the Gantt chart to the user.