1. What are some of the differences between enterprise architecture (EA) and a systems-level planning approach? 2. Why is EA described as both a management program and an analysis and design method?...

Enterprise Architecture
Enterprise Architecture
` Enterprise Architecture
Student Name:
University Name:
Unit Name:
Date:
Contents
Solution 1    3
Solution 2    3
Solution 3    3
Four elements of an EA management program    3
Six elements of an EA analysis and design method    4
Solution 4    4
Solution 5    5
Solution 6    5
Solution 7    5
Solution 8    6
Solution 9    6
Solution 10    7
Solution 11    7
Solution 12    8
Solution 13    8
Solution 14    9
Solution 15    9
Solution 16    10
Solution 17    10
Solution 18    11
Solution 19    11
Solution 20    12
Solution 21    12
Solution 22    12
Solution 23    12
Solution 24    13
Solution 25    13
Solution 26    14
References    15
Solution 1
EA is both a management process and an analytical as well as design approach. The system level planning method is just an analysis and design method. It limits its plans to a single system. For example, in our case study of Danforth Manufacturing, both CMO and CFO want to buy new systems with overlapping capabilities. CMO Kate Jarvis wants a new sales and inventory tracking system so she can access real-time data on inventory and prices. Chief Financial Officer Jim Gorman wants a new accounting system to better track prices. Both plans were developed at the system planning level rather than at the EA level, which is why when they are presented side by side, their overlapping functions become apparent and measures are taken to determine a uniform approach (Arango Serna, Londoño Salazar and Branch Bedoya, 2015).
Solution 2
As an analytical and design way, EA provides: EA methods: frameworks, analysis/design methods, or cu
ent set of artifact sets: as-is strategies, process and views of resources. A Future views: pending strategies, processes, and resources EA management plan: From Cu
ent EA migration to future EA plans. EA is an ongoing management programs that provide strategic, integrated approaches to capacity or resource strategy/decision. EA may help to determine performance differences in line-of-business plans/ activities and the ability to support IT services, networks and systems (Chelliah, 2014).
Solution 3
Four elements of an EA management program
1. Decision Support
2. Strategic Alignment
3. Standardized Policy
4. Resources Oversight
Six elements of an EA analysis and design method
1. Element: The Frameworks
2. Element: EA Component
3. Element: Present Architecture
4. Element: Future Architecture
5. Element: EA Management strategy
6. Element: Threads
Solution 4
EA components are processes, variable goals, standards, moreover resources that can be extended across the enterprise or included in particular business and market segment. The main Examples of the components include planned objectives and initiatives; commercial services and products; knowledge warehouses, information flows as well as data objects; software applications, data systems, ERP, and other websites; data, voice and video networks; Buildings, server rooms, capital equipment and wiring or closets (Dale, 2016).
"Artifacts" that identify the methods and types of the documents to be use in every sub-architectural area, also including internal controls, strategic analysis or workflow models, security controls and databases, networks, and systems (Guo and Yin, 2014). This core factors include an online repository for storing artifacts.
Solution 5
Enterprise Architecture (EA) is widely used by companies around the world and is often associated with most popular EA frameworks (FEAF, TOGAF, etc.). But, the EA framework is simply a typical management fashion with a huge history of the unsuccessful implementation, 1 and the successful Enterprise Architecture practices are not similar to the recommendation of any real Enterprise Architecture framework.
Solution 6
The Enterprise Architecture Repository is an online archive of Enterprise Architecture information as well as document artifacts described in the EA Management Plan. Providing simple access to Enterprise Architecture documents is critical to planning or decision making. This can be done by building an online EA repository to archive documentation of the Enterprise Architecture components in different areas of Enterprise Architecture framework (Javadi, Ra
animehr and Foruzan, 2012).
Solution 7
Part a: While most executives believe their existing IT team has not cut it, they recognize that IT is growing as a strategic asset. Most executives believe that change is needed to help their business incorporate IT into their business strategy. The important factor is that the executive team is not satisfied with the effectiveness of its IT resources. Most executive teams say they have to make changes to their cu
ent IT team to make IT changes to their business.
Part b: Although there is no single enterprise architecture definition, it is understood as the practice or rules of organizational logic that can promote a healthy IT infrastructure that is meaningful to successful business practices. Importantly, the result of an enterprise architecture is more than just an organization (Kamei and Ohashi, 2014).
Part c: Because many best practices are implemented and maintained in a resource-intensive manner, and scopes are not exhaustive, organizations face the decision to decide which approach to adopt, how to implement it, and how to overlap and create conflicts from the final set. When EA is an organization's architecture in all aspects, it becomes the totality of standards and practices, the highest level of discipline and authoritative reference. EA can help determine performance differences in line-of-company activities/plans, moreover the ability to support IT services, networks and systems.
Solution 8
It is important to understand the “personal aspects” of EA. EAs are authorized within the federal government, so EA programs are under development, but they are not always used (Koch and Mitlöhner, 2010). In addition, because some of the EA team did not assume a delivery role for a period of time, they may overlook the need for a delivery-focused team. Many IT leaders say that the biggest challenge they face is finding...