Single point of entry for web applications

• US 8,271,614 B2
• Filed: 07/23/2008
• Issued: 09/18/2012
• Est. Priority Date: 07/10/2003
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Barrett, Kevin R.
• Primary Examiner(s): Fan, Hua
• Application Number:
  US12/177,958
• Publication Number:
  US 20090083104A1
• Time in Patent Office: 1,518 Days
• Field of Search: 705/8, 705/9, 709/204, 709/206, 715/764, 715/749
• US Class Current: 709/219
• 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 task in an electronic memory, wherein the information indicates a first date associated with the project task and a second date associated with the project task;

storing a project calendar in the electronic memory, the project calendar identifying whether each date on the project calendar is a working day or a non-working day;

calculating a difference between the first date and the second date, wherein the difference between the first date and the second data equals the number of total days between the first date and the second date minus the number of non-working days between the first date and the second date;

maintaining a plurality of tolerance ranges for the project task, wherein each of the plurality of tolerance ranges is customized for a particular one of a plurality of types of users;

comparing the difference between the first date and the second date to a particular one of the plurality of tolerance ranges, each one of the particular one of the plurality of tolerance ranges being uniquely associated with a particular one of the plurality of types of users;

assigning a status to the project task based on the comparison of the difference between the first date and the second date and the particular one of the plurality of tolerance ranges associated with the particular one of the plurality of types of users;

retrieving one or more parameters used for the generation of an image representing the status to the particular one of the plurality of types of users; and

presenting the image representing the status to user within the particular one of the plurality of types of users.

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 task.

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 task.

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 image representing the status of the project task to the user comprises:

creating a Gantt chart that includes information relating to the project task 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 task of the project; and

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

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

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

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

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

12. The method of claim 1, wherein:

the project task comprises one of a plurality of project tasks associated with a project; and

presenting the image representing the status of the project task to the user comprises;

creating a report identifying the status of the project tasks; 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 tasks associated with each of the projects.

23. The method of claim 1, wherein:

the information stored in the electronic memory identifies a resource comprising a piece of equipment that is required to perform the project task;

the information stored in the electronic memory identifies an availability date for when the piece of equipment is available for performing the task; and

the information stored in the electronic memory identifies a termination date for when the piece of equipment is no longer available for performing the task.

24. The method of claim 1, wherein:

the information stored in the electronic memory identifies a resource comprising a team member that is required to perform the project task;

the information stored in the electronic memory identifies an availability date for when the team member is available for performing the task; and

the information stored in the electronic memory identifies a termination date for when the team member is no longer available for performing the task.

25. The method of claim 1 wherein presenting the status to the user comprises presenting a Gantt chart that includes at least:

a first bar representing a baseline time frame between a baseline start associated with the original planned start date and a baseline finish associated with the original planned finish date;

a second bar representing an current time frame between an actual start date or a currently scheduled start date and an actual finish date or currently scheduled finish date;

a third bar representing a percent of completion of the project.

15. A non-transitory program storage device readable by the computer system, the non-transitory program storage device operable, when executed by the computer system, to:

store a project calendar in the electronic memory, the project calendar identifying whether each date on the project calendar is a working day or a non-working day;

store information pertaining to a project task in an electronic memory, wherein the information indicates a first date associated with the project task and a second date associated with the project task, wherein the difference between the first date and the second data equals the number of total days between the first date and the second date minus the number of non-working days between the first date and the second date;

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

maintain a plurality of tolerance ranges for the project task, wherein each of the plurality of tolerance ranges is customized for a particular one of a plurality of types of users;

compare the difference between the first date and the second date to a particular one of the plurality of tolerance ranges, each one of the particular one of the plurality of tolerance ranges being uniquely associated with a particular one of the plurality of types of users;

assign a status to the project task based on the comparison of the difference between the first date and the second date and the particular one of the plurality of tolerance ranges associated with the particular one of the plurality of types of users;

retrieve one or more parameters used for the generation of an image representing the status to the particular one of the plurality of types of users; and

present the image representing the status to user within the particular one of the plurality of types of users.

16. The non-transitory program storage device 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 non-transitory program storage device 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 non-transitory program storage device of claim 15, further operable when executed by the computer system 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 non-transitory program storage device of claim 15, further operable when executed by the computer system to present the image representing the status of the project task to the user by:

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

displaying the Gantt chart to the user.

20. The non-transitory program storage device of claim 15, wherein:

the information stored in the electronic memory identifies a resource comprising a piece of equipment that is required to perform the project task;

the information stored in the electronic memory identifies an availability date for when the piece of equipment is available for performing the task; and

the information stored in the electronic memory identifies a termination date for when the piece of equipment is no longer available for performing the task.

21. The non-transitory program storage device of claim 15, wherein:

the information stored in the electronic memory identifies a resource comprising a team member that is required to perform the project task;

the information stored in the electronic memory identifies an availability date for when the team member is first available for performing the task; and

the information stored in the electronic memory identifies a termination date for when the team member is no longer available for performing the task.

22. The non-transitory program storage device of claim 15, further operable when executed by the computer system to present the image representing the status of the project task to the user by presenting a Gantt chart that includes at least:

a first bar representing a baseline time frame between a baseline start associated with the original planned start date and a baseline finish associated with the original planned finish date;

a second bar representing an current time frame between an actual start date or a currently scheduled start date and an actual finish date or currently scheduled finish date;

a third bar representing a percent of completion of the project.