INFORMATION TECHNOLOGY PLANNING BASED ON ENTERPRISE ARCHITECTURE

• US 20100145748A1
• Filed: 12/08/2008
• Published: 06/10/2010
• Est. Priority Date: 12/08/2008
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mayle, Wolfgang, Rothbucher, Sebastian
• Application Number:
  US12/330,182
• Publication Number:
  US 20100145748A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group

Abstract

A method of forming an IT plan for an enterprise utilizing an automated enterprise architecture (EA) system includes creating a project document, the project document describing a particular portion of operations of the enterprise; ranking the criticality of the project as compared to other projects of the enterprise; linking products, including product versions, that are related to the project to the project in the EA system, wherein the link is a two way link; receiving organization technology adoption preferences; and creating a list of products to be upgraded based on the technology adoption preferences and the ranking of the project.

Claims

1. A method of forming an IT plan for an enterprise utilizing an automated enterprise architecture (EA) system, the method comprising:

creating a project document, the project document describing a particular portion of operations of the enterprise;

ranking the criticality of the project as compared to other projects of the enterprise;

linking products, including product versions, that are related to the project project document in the EA system, wherein the link is a two way link;

receiving organization technology adoption preferences; and

creating a list of products to be upgraded based on the technology adoption preferences and the ranking of the project.

2. The method of claim 1, further comprising:

outputting the list to a user via a display.

3. The method of claim 1, wherein the project document is a component of the EA system and is linked to another artifact and to a connection support document.

4. The method of claim 3, wherein the link to the another artifact is two-way link.

5. The method of claim 1, further comprising:

obtaining product lifecycle information for one or more of the projects; and

including the product lifecycle information in the product.

6. The method of claim 1, further comprising:

collecting projects previously stored and linked to the project.

7. The method of claim 1, further comprising:

importing a list a new products; and

providing recommended products to upgrade to.

8. The method of claim 1, wherein is ranking is based upon predetermined factors affecting the enterprise.

9. A computer program product for producing an information technology (IT) plan for an enterprise in an enterprise architecture (EA), the computer program product comprising:

a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for facilitating a method including;

creating a project document, the project document describing a particular portion of operations of the enterprise;

ranking the criticality of the project as compared to other projects of the enterprise;

linking products, including product versions, that are related to the project document in the EA system, wherein the link is a two way link;

receiving organization technology adoption preferences; and

creating a list of products to be upgraded based on the technology adoption preferences and the ranking of the project.

10. The computer program product of claim 9, wherein the method further comprises:

outputting the list to a user via a display.

11. The computer program product of claim 10, wherein the project document is a component of an enterprise architecture (EA) system and is linked to another artifact and to a connection support document.

12. The computer program product of claim 11, wherein the link to the another artifact is two-way link.

13. The computer program product of claim 9, wherein the method further comprises:

obtaining product lifecycle information for one or more of the projects; and

including the product lifecycle information in the product.

14. The computer program product of claim 9, wherein the method further comprises:

collecting projects previously stored and linked to the project.

15. The computer program product of claim 12, wherein a desired product version can be computed by using the adoption preference based on business criticality.

16. The computer program product of claim 12, wherein a health or a deviation of a desired product to an actual product version is be determined

17. The computer program product of claim 16, wherein the deviation can be weighted with the business criticality.

18. The computer program product of claim 16, wherein the deviation can be measured as red/amber/green or as improvement points.

19. The computer program of claim 16 wherein, the deviation of current and desired version.

20. The computer program product of claim 19, wherein the deviation can be further aggregated into a global status.