Enterprise Architecture Essay Paper Example For Students

Enterprise Architecture Essay Paper February 12, 2011 This article includes my thoughts about the business architecture, Cloud Computing, Business Process Management (BPML), and Business Rules. This article consists of a conversation between the CIO and Enterprise Architect. It is a product of my imagination. CIO: I dont 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 dont want you to get involved in discussions about hanging 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: cuisines, 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 architecture is the foundation for the data, applications, and technology target architectures. This comparison answers the question, Are we satisfying our business requirements in the current architecture? The business architecture or model includes the following: Defines the mission and objectives, long-range strategies, tactical plans, performance measures, budgets, and business rules. Why) Defines the information and data that is shared, monitored, and tracked. (What) Defines the activities that are performed and a description of each. How) Defines the organizations and actors performing the activities. (Who) Defines where the activities are performed. (Where) Defines the business cycles and when activities or processes are performed. (When) In the business architecture, we develop mappings between all 6 of the Coach man interrogatories, including who, what, when, where, why, and how. The business architecture is mapped to the current architecture, and then opportunities for improvement are documented. Targets are developed for data, applications, and the technology layers of the architecture using the business architecture and other analyses. The business architecture constitutes our requirements at the agency level. CIO: This is the first time I have heard about opportunities for improvement. Are you going to produce a report with recommendations as a result of the comparison between the business architecture and the current architecture? Enterprise Architect: Yes. Here is the way it works: Create the Business Architecture We produce a business architecture, which reflects the current way of doing business and contains all sorts of information and data associated with the 6 interrogatives in the Coachman Framework. We also develop mappings between the interrogatives. The business architecture describes the current business practices, including, data, processes, etc. Map the Business Architecture to the Current Architecture and Identify Opportunities for Improvement We propose a draft listing of the conceptual projects and associated common applications/components and data objects and progressively refine it. We produce a current architecture, which tells us about the existing systems. We map the business architecture to the current architecture and we may find out, for example, that there are a large number of current systems associated with a single activity or no systems associated with other activities. All current projects are mapped to the conceptual projects. Create the Data, Applications, and Technology Target Architectures based on the Business Architecture and Other Analyses We produce data, applications, and technology target architectures, which are partially based on the business architecture. Also, we use BPML, technology forecasts, judgments about the future uses and characteristics of information, opportunities to automate aspects of work, future business trends, new 2 goals/objectives and plans, etc. As the basis for coming up with the target architectures. Compare the Current Architecture with the Target Architectures and Produce a Gap Analysis and a Migration Plan The business architecture helps us to evaluate the present and to propose the future. We use the business architecture as a resource wherever we can; for example, it might contribute to BPML and business rules and visa versa. We are concentrating on an application architecture now, and we will issue several versions. As more analyses are completed, we will refine the applications architecture. We will move to data and technology layers soon. CIO: How do I know what you are going to include in each version? Enterprise Architect: There is no overall version plan. We probably should include BPML in the second version of the applications architecture. We previously developed a longer plan to implement Enterprise Architecture. CIO: I think that there should be a version plan. Also, soon is not an adequate answer. I am beginning to be irritated with the staggered development of the Enterprise Architecture. Enterprise Architect: We can come up with a version plan, and give you the long-term plan for the completion of the application, data, and technology target architectures. CIO: You are going to produce a report entitled: Opportunities for Improvement after you have completed the business architecture and have compared it with the current architecture. Maybe you should consider it a rolling stone and Just keep updating it. Essay on Online Dating Should Not Be A Source EssayFinally, there are a number of 5 key data models that contain very important processes. All of this can be used to kick start BPML. BPML takes considerable time and effort to create improved processes, particularly if you are going to select a preferred alternative from a comparison of similar processes. A process may be undertaken in many ways by the bureaus, using different combinations of activities, data, people, time limitations, goals, objectives, and business rules. CIO: Following up on a comment you previously made, I want the citizen to have more responsibility. I think you are the logical person to do BPML. Enterprise Architect: In addition to the 40 value streams and other scenarios, we developed data models which include processes. In the data model Customers place orders, place orders is the process. We have tons of data models of this sort. I am willing to identify business rules associated with these data models. However, I think we need to depend on our BPML community to do BPML. CIO: There is no BPML community. I am afraid that you are it. I count on you to explore ways to improve how we can further serve the business. Talk to me about business rules. What do business rules have to do with BPML? Enterprise Architect: Business rules are important because you can change the behavior of the organization by changing the business rules. Both business rules and BPML focus on processes. According to Ron Ross, A business rule sets limitations and controls on a process. I have prepared an enclosure that explains business rules. (See: Enclosure (2)). You will note that both BPML and Enterprise Architecture use similar language. Additionally, I did not identify the business rules as part of business architecture and I think this was a mistake. John Coachman classifies business rules in his framework at a lower level. However, I no longer agree with this. I believe that the data model, processes, and business rules are closely interconnected and are critical to defining the business architecture. CIO: Maybe John Coachman wanted us to first develop the data models and later add the business rules to them. Just give me a plan for the versions that includes the ideas we have discussed. Also, when the time comes, I am not going to stop any of the existing projects. The new project managers can sort this out. Finally, I have assembled some Youth videos on Enterprise Architecture, BPML, and business rules. (See: Enclosure (3)) What I would like you to do is take a look at them, and come up with your own videos. If you want to hire experts to do the video that is fine. Maybe we should start with Enterprise Architecture. Enterprise Architect: Okay. George Brigandage received a B. A. From Wright State University and M. A. From the University of Cincinnati. He retired in June 2004, from the federal government and 6 lives in Ocean View, Delaware, and Alexandria, Virginia. He was an Enterprise Architect at the Department of the Treasury and the Department of Homeland Security. Before that, he Emceed the Architectures Program for several years at the General Services Administration (AS) and the Department of the Treasury. He may e reached at cell 703. 772. 7410 and at George. [emailprotected] Com. His articles are on the web at http://enterprisearchitectureit. Info. 7 Enclosure (1) Business Process Management This table summarizes the key points from the following publications. The categories in this table are merely groupings of BPML actions that were mentioned in the publications: President Beams book, The Audacity of Hope, published in 2006. Customer Service Excellence, Using Information Technologies to Improve Service Delivery in Government, Harvard University, 1994. Citizen-Enabling Open Government (EEOC) Executive Summary for ideas. This report was produced by ACT-IAC Enterprise Architecture Shared Interest Group (SIGH), September 2010. ) Federal Government Business Process Reengineering: Lessons Learned, February 1994, published by AS. Categories Share information and effectively manage programs. Responsive to citizens needs. Treat all with dignity and What BPML Has Done or Might Do Share information and data. Increase integration and standardization to prevent fragmentation. Provide one face to the citizens. Develop data standards and business rules. Provide suites of commonly shared services. Use technology effectively . Develop a citizen service strategy that includes technology, human resources, skill development, and incentives. Provide timely response to the citizen. Develop performance measures, associated with ended-end processes and outcomes. Take ownership of the entire process. Describe the business or make it explicit. (See: Identify the needs of the citizens. Use multiple vehicles to communicate with the public, including: web sites, videos (The success of Youth, which provides some degree of video training, is astounding. ), and video teleconferencing. Use focus groups, surveys. Provide the public with access to the governments databases. Provide education and training, includin g long distance 8 respect. Provide the same level of service to all. Gather needed information. Clearly explain things. Develop effective and efficient processes and use technology creatively. Do things better, faster, and cheaper. Protect the public from harm. Give citizens their moneys worth. Education, so citizens can obtain the benefits they need and budget for innovative training. Develop standards and consistently apply business rules (Business rules must be transparent, consistent, ND explicit to enable effective regulation. ) Provide language services. Use alternative locations and organizations like libraries and kiosks to obtain information and distribute benefits.