AUTOMATED ENTERPRISE ARCHITECTURE ASSESSMENT

• US 20100145747A1
• 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/329,984
• Publication Number:
  US 20100145747A1
• 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

Abstract

A computer based system for assessing an automated enterprise architecture includes a database for storing artifacts, each artifact representing a portion of the enterprise architecture, the artifacts including a pattern artifact defining requirements for links between a first artifact and one or more additional artifacts, a user interaction module coupled to the database, and an analysis module configured to determine all patterns linked to a component and to determine the level of compliance of the component with the pattern.

Claims

1. A computer based system for assessing an automated enterprise architecture system, the system comprising:

a database for storing artifacts, each artifact representing a portion of the enterprise architecture, the artifacts including a pattern artifact defining requirements for links between a first artifact and one or more additional artifacts;

a user interaction module coupled to the database;

an analysis module configured to determine all patterns linked to a component and to determine the level of compliance of the component with the pattern.

2. The system of claim 1, wherein the first artifact is component.

3. The system of claim 1, further comprising:

logic and maintenance module coupled to the database; and

a persistence module coupled to the database.

4. The system of claim 3, wherein the persistence module further includes:

an artifact store for storing the artifacts;

a connection support document store for storing the connection support documents; and

a configuration store to store customizations to the system'"'"'s behavior

a metamodel store for storing definitions of each artifact type.

5. The system of claim 3, wherein the logic and maintenance module includes:

a connection maintenance module, the connection maintenance module configured to ensure that each connection between a first artifact and a second artifact is a bidirectional connection including a forward link stored in the first artifact and a reverse link stored in the second artifact.

6. The system of claim 5, wherein the connection maintenance module is invoked each time a connection is either created or deleted.

7. The system of claim 5, wherein the connection maintenance module is further configured to delete reverse in the event that the forward link is deleted.

8. The system of claim 5, wherein the connection maintenance module is configured to delete a connection support document associated with the bidirectional connection between the first and second link is deleted.

9. The system of claim 5, wherein the first artifact includes lifecycle information stored therein and wherein the logic and maintenance module further includes:

a lifecycle management module configured to examine the lifecycle information and to notify at least one user that the first artifact is nearing or at the end of a predefined lifecycle limit.

10. The system of claim 1, wherein each artifact includes a type, a name and a link section.

11. A method of evaluating enterprise architecture in a computer database, the method comprising:

creating a plurality of artifacts including a first artifact, a second artifact and pattern artifact, each artifact having a type and an identifier;

creating a connection between the first artifact and the second artifact, the connection including a forward link stored in the first artifact pointing from the first artifact to the second artifact and a reverse link stored in the second artifact pointing from the second artifact to the first artifact;

creating a link between the first artifact and the pattern artifact; and

creating a connection support document, the connection support document including a pointer to the first artifact and a pointer to the second artifact, the connection support document further including information contained in the pattern artifact defining requirements related to the link between the first artifact and the second artifact.

12. The method of claim 11, wherein the first artifact is component artifact.

13. The method of claim 11, wherein each artifact includes a link section for storing connections to other artifacts.

16. The method of claim 11, wherein one or more of the artifacts is a document such as a standard or principle.

17. The method of claim 11, wherein the connection between the first artifact and the pattern is a pattern connection that documents a desired state.

18. The method of claim 11, wherein the connection between the first and second artifact documents the to-be state.

19. The method of claim 11, wherein the connection between the second artifact and the component documents which as-is components are supposed to implement which to-be state.

20. The method of claim 11, wherein the connection to the connection support document includes link requirement information.