enterprise architecture
Enterprise Architecture Article – 10
By: George Brundage
February 12, 2011
This article includes my thoughts about the business architecture, Cloud Computing,
Business Process Management (BPM), and Business Rules. This article consists of a conversation between the CIO and Enterprise Architect. It is a product of my imagination. ____________________
CIO: I don’t want you to use the word “consolidation.” Instead, use the word
“integration.” I am worried that someone will think that we are working on the consolidation of programs or organizations, rather than improving our architecture to serve the business. Again, I don’t want you to get involved in discussions about changing the organization structure of the agency. How do you see your roll vs. the rolls of the other directors?
Enterprise Architect: I would like to support them with the knowledge I have at my disposal, but they are not interested. One day they may realize how they can use the
Enterprise Architecture.
I think of Enterprise Architecture as the substructure, which supports the business, the superstructure. The Director of Capital Planning and Investment Control should use the
Enterprise Architecture migration plan to formulate future investments. A portion of the
Enterprise Architecture has security concerns, including all 4 layers: business, applications, data, and technology. We develop standards for all layers of the Enterprise
Architecture, except business standards; although, we may be asked to coordinate some business standards. Both communications and security should use the models contained in the Enterprise Architecture Framework or propose changes to the models in the framework. CIO: What do you want me to do?
Enterprise Architect: Get the cooperation of your direct reports.
CIO: You will get it. Go over the business architecture, current architecture, and target architectures again.
Enterprise Architect: The comparison between the business and current
By: George Brundage
February 12, 2011
This article includes my thoughts about the business architecture, Cloud Computing,
Business Process Management (BPM), and Business Rules. This article consists of a conversation between the CIO and Enterprise Architect. It is a product of my imagination. ____________________
CIO: I don’t want you to use the word “consolidation.” Instead, use the word
“integration.” I am worried that someone will think that we are working on the consolidation of programs or organizations, rather than improving our architecture to serve the business. Again, I don’t want you to get involved in discussions about changing the organization structure of the agency. How do you see your roll vs. the rolls of the other directors?
Enterprise Architect: I would like to support them with the knowledge I have at my disposal, but they are not interested. One day they may realize how they can use the
Enterprise Architecture.
I think of Enterprise Architecture as the substructure, which supports the business, the superstructure. The Director of Capital Planning and Investment Control should use the
Enterprise Architecture migration plan to formulate future investments. A portion of the
Enterprise Architecture has security concerns, including all 4 layers: business, applications, data, and technology. We develop standards for all layers of the Enterprise
Architecture, except business standards; although, we may be asked to coordinate some business standards. Both communications and security should use the models contained in the Enterprise Architecture Framework or propose changes to the models in the framework. CIO: What do you want me to do?
Enterprise Architect: Get the cooperation of your direct reports.
CIO: You will get it. Go over the business architecture, current architecture, and target architectures again.
Enterprise Architect: The comparison between the business and current