ATOM Framework - Architectural Perspective

4
Working with Enterprise Architecture: The Architectural Perspective of the ATOM-framework. A O M T

description

A paper dealing with the ATOM-framework and how the architectural perspecitves can be dealt with.

Transcript of ATOM Framework - Architectural Perspective

Page 1: ATOM Framework - Architectural Perspective

Working with Enterprise Architecture:

The Architectural Perspective of the ATOM-framework.

A

O

M

T

Page 2: ATOM Framework - Architectural Perspective

When the chief architect has established an Enterprise Architecture then it is a necessity to continue working with the adaption of the framework.

In my opinion all organizations are unique since the people who interact in the social systems of the enterprise are also somehow unique and so are the social systems.

The ATOM-framework contains the Architectural, Technological, Organizational and the Managerial perspectives that needs to be addressed when the adaption process has begun and when the adoption of the framework is about to take place. This particular blog post deals with the architectural perspective.

The Architectural PerspectiveWhen working with the architectural perspective then it is a necessity to handle the various questions on how the Enterprise Architecture program will contribute to the enterprise, and how the program will impact the systems.

The focus of the framework is to identify artifacts for the various elements that is directly related to how the framework is adapted to the enterprise.

An example for an artifact within this particular perspective is the process of implementing Enterprise Architecture in the enterprise. However there are many different artifacts which can be identified and installed in the A-column of the ATOM-framework and these are dealt with below.

The architectural perspective does also deal with what initiatives that the enterprise works with to enable the implementation of Enterprise Architecture. In my opinion is Enterprise Architecture both a set of processes and a form of enterprise engineering (literally a factor that can change the enterprise).

Artifacts for the Architectural PerspectiveThere are many different kinds of artifacts that can be identified and then organized into a repository. I have in this section articulated some examples for how artifacts can be dealt with. In the approach to dealing with the artifacts I have identified the artifacts, described the artifacts and mentioned a method identify and make use of the system.

Artifact Description Identificationn

Enterprise Architecture Framework

Is the approach that the executives and the enterprise architects chooses to implement the enterprise architecture.

The methods that can be applied to the artifacts are through interviews with the executives and the chief architect or through going through the documents on how the framework is adapted.

theATOMFramework.com | Page 2

Page 3: ATOM Framework - Architectural Perspective

Program Management Office and processes

Is dealing with how the enterprise deals with the projects.

The methods that can be applied to identify the artifacts are through interviews of the executives or the project managers or program managers. Alternatively the architects can go through the papers for what projects that are initiated and by who.

Systems Evolutions Plans & Diagrams

Are the plans that states how the enterprise plans to manage, develop and retire their information systems.

Interview the CIO or person in charge of the IT / IS systems.

Repository Systems and Information Systems

Are the systems that the enterprise makes use of to expose the various artifacts and various data that has been collected. What is necessary to understand is that the information needs to be communicated.

Interview the chief architect and the CIO about the systems that have been purchased and applied. Alternatively the architects can go through the various purchase documents.

Business Operating Model(s) The way the business operates, and how it applies the usage of IT and business processes.

Interview the CIO, Chief Architect, and the executives for identifying the operating model of the enterprise. Alternatively then documentation and summaries from the various meetings.

Viable Organizational Systems

Various systems within the enterprise that is of some self-governance-ship (and of course these needs to be compatible with the definition that Stafford Beer introduced).

The architects would have to contact the various members of the social systems and it is clear that they would have to investigate the social systems through interviews to support their views then organigrams and employee profiles have to be a part of the data that is used in the investigation.

Management Information Systems

Are the systems that the management of the enterprise makes use of. These systems don’t need to be IT related systems but usually there are elements of IT involved in them.

Interview the executives on how they obtain the information they would need to take decisions. Likewise should the architects interview the various employees who are involved in the process.

Incentive Systems Are the systems that the enterprise has applied to

The architects should interview the executives,

theATOMFramework.com | Page 3

Page 4: ATOM Framework - Architectural Perspective

make the members of the enterprise work in a desired way.

members of the HR-department and not to forget the employees. Alternatively it is possible for the architects to investigate documents on how the various technologies works within the enterprise.

Knowledge Management Systems

Are systems that have been implemented in the enterprise to facilitate the sharing of important knowledge. These systems can both be IT systems as well as organizational systems.

When it comes to the knowledge management systems then it is a necessity to investigate the documents that have been developed over time.

When organizing each of the artifacts it becomes it is a necessity to plan how to identify them, if it hasn’t been done already.

What is the Impact of the Architectural LayerThe impact of the enterprise architecture program will lead to that some of the processes in the organization needs to be dealt with in a different way since the system will be altered. When the alteration has taken place then it is very likely that the social systems will be be anything but static and therefore would the process of identifying how the architectural element of the enterprise needs to be altered in accordance to achieve a more coherent enterprise.

In working with the ATOM-framework it is a necessity for the members of the enterprise to question how the enterprise works and that involves questioning the architecture procedures and the elements that facilitate the architecture process and for that matter question the processes of enterprise engineering.

Relevant Questions for the Perspective1. What can enable Enterprise Architecture for the particular enterprise.2. What tools are needed to apply the Enterprise Architecture program.3. What processes are important in the transition of the architecture of the enterprise?4. How can the artifact be organized into the framework?5. What value does the artifact communicate to the rest of the enterprise when it is

organized in the repository?6. How can the value and meaning of the artifacts be communicated better and to

whom?

theATOMFramework.com | Page 4