INTEGRATION OF COMPUTERIZED PROJECT PLANNING AND PROJECT DIAGRAMMING

• US 20130110730A1
• Filed: 10/28/2011
• Published: 05/02/2013
• Est. Priority Date: 10/28/2011
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bostick, James E., Ganci, John M. Jr., Kaemmerer, John P., Trim, Craig M.
• Application Number:
  US13/284,560
• Publication Number:
  US 20130110730A1
• Time in Patent Office: Days
• US Class Current: 705/301
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A computer implemented system and method for integrating project architecture diagramming with project planning is disclosed. A project template is stored in a database, the project template comprising at least two component tasks. The project template is associated with an architecture entity identifier. A project architecture diagram is received comprising at least one diagram entity, each diagram entity being associated with at least one diagram entity identifier. The diagram entity identifier is compared to the architecture entity identifier to identify the project template as the project template associated with the diagram entity. A project component is generated from the identified project template, the project component corresponding to the diagram entity and populated with the component tasks from the identified project template. A project work plan is populated with the project component.

Claims

1. A computer implemented method for integrating project architecture diagramming with project planning, comprising:

storing in a database a project template, the project template comprising at least two component tasks;

associating, using a processor, the project template with an architecture entity identifier;

receiving a project architecture diagram comprising at least one diagram entity, each diagram entity being associated with at least one diagram entity identifier;

comparing, using the processor, the diagram entity identifier to the architecture entity identifier to identify the project template as the project template associated with the diagram entity;

generating, using the processor, a project component from the identified project template, the project component corresponding to the diagram entity and populated with the component tasks from the identified project template; and

populating a project work plan with the project component.

2. The method of claim 1, further comprising:

parsing the diagram entity identifier to retrieve a first text;

parsing the architecture entity identifier to retrieve a second text; and

comparing the first text and the second text to execute the comparing of the diagram entity identifier to the architecture entity identifier.

3. The method of claim 1, further comprising:

obtaining shape information from the diagram entity identifier to retrieve a first shape;

obtaining shape information from the architecture entity identifier to retrieve a second shape; and

comparing the first shape to the second shape to execute the comparing of the diagram entity identifier to the architecture entity identifier.

4. The method of claim 1, further comprising:

updating the project work plan to comport with a received update to the project architecture diagram; and

updating the project architecture diagram to comport with a received update to the project work plan.

5. The method of claim 1, further comprising:

storing in the database an association between users and component tasks; and

automatically assigning users to component tasks of the project component based on the association.

6. The method of claim 1, further comprising:

accepting an indicator that a first diagram entity is a predecessor of a second diagram entity; and

automatically setting, in the project work plan, a first project component, associated with the first diagram entity, as a prerequisite dependency for a second project component, associated with the second diagram entity.

7. The method of claim 1, further comprising:

associating a work investment percentage with each component task;

receiving a component work investment necessary to complete each project component; and

determining, for each component task, a task work investment, the task work investment being a portion of the component work investment necessary to complete the component task, as based on the work investment percentage.

8. The method of claim 7, further comprising determining a completion date for the project component, based at least on a start date, the component work investment, and the task work investments for each component task of the project component.

9. The method of claim 8, further comprising determining a project completion date for the project work plan using at least the completion dates and the component work investments for each project component in the project work plan.

10. The method of claim 9, further comprising populating the received project architecture diagram with the completion dates, the component work investments, the task work investments, and the project completion date.

11. The method of claim 10, further comprising accepting edits to the start dates, component work investments, task work investments and the project completion date within the project work plan and in the project architecture diagram.

12. The method of claim 1, wherein the diagram shape is associated with a release phase indicator, the method further comprising:

designating the project work plan for a current release phase of a plurality of release phases; and

populating the project work plan with a project component corresponding to the diagram entity only when the release phase indicator for the diagram entity corresponds to the current release phase.

13. A system for integrating project architecture diagramming with project planning, comprising:

a computer processor;

a database; and

memory comprising program instructions, the program instructions executable by the processor to;

store in the database a project template, the project template comprising at least two component tasks;

associate, using the processor, the project template with an architecture entity identifier;

receive a project architecture diagram comprising at least one diagram entity, each diagram entity being associated with at least one diagram entity identifier;

compare, using the processor, the diagram entity identifier to the architecture entity identifier to identify the project template as the project template associated with the diagram entity;

generate, using the processor, a project component from the identified project template, the project component corresponding to the diagram entity and populated with the component tasks from the identified project template; and

populate a project work plan with the project component.

14. The system of claim 13, wherein the architecture entity identifier and at least one diagram entity identifier are text-based.

15. The system of claim 13, wherein the architecture entity identifier and at least one diagram entity identifier are shape-based.

16. The system of claim 13, wherein the program instructions are executable by the processor to further:

update the project work plan to comport with a received update to the project architecture diagram; and

update the project architecture diagram to comport with a received update to the project work plan.

17. The system of claim 13, wherein the program instructions are executable by the processor to further:

store in the database an association between users and component tasks; and

automatically assign users to component tasks of the project component based on the association.

18. The system of claim 13, wherein the program instructions are executable by the processor to further:

accept an indicator that a first diagram entity is a predecessor of a second diagram entity; and

automatically set, in the project work plan, a first project component, associated with the first diagram entity, as a prerequisite dependency for a second project component, associated with the second diagram entity.

19. The system of claim 13, wherein the program instructions are executable by the processor to further:

associate a work investment percentage with each component task;

receive a component work investment necessary to complete each project component; and

determine, for each component task, a task work investment, the task work investment being a portion of the component work investment necessary to complete the component task, as based on the work investment percentage.

20. The system of claim 19, wherein the program instructions are executable by the processor to further determine a completion date for the project component, based at least on a start date, the component work investment, and the task work investments for each component task of the project component.

21. The system of claim 20, wherein the program instructions are executable by the processor to further determine a project completion date for the project work plan using at least the completion dates and the component work investments for each project component in the project work plan.

22. The system of claim 21, wherein the program instructions are executable by the processor to further populate the received project architecture diagram with the completion dates, the component work investments, the task work investments, and the project completion date.

23. The system of claim 22, wherein the program instructions are executable by the processor to further accept edits to the start dates, component work investments, task work investments and the project completion date within the project work plan and in the project architecture diagram.

24. The system of claim 13, wherein the diagram shape is associated with a release phase indicator, wherein the program instructions are executable by the processor to further:

designate the project work plan for a current release phase of a plurality of release phases; and

populate the project work plan with a project component corresponding to the diagram entity only when the release phase indicator for the diagram entity corresponds to the current release phase.