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?...

4
QUESTIONS AND ANSWERS
Name
Institutional Affiliation
Date
1. What are some of the differences between enterprise architecture (EA) and a systems-level planning approach?
Systems level planning by statistic also means failure, and Enterprise architecture prepare scalable as well as policy independent application architecture result.
2. Why is EA described as both a management program and an analysis and design method?
It gives enduring means and actionable synchronized views of an enterprise’s strategic way, company services, information circulation, as well as resource use.

3. What are the four elements of an EA management program and the six elements of an EA analysis and design method?
Management Program
Strategic position: maximize the competence as well as efficiency of these resources, which in turn will assist to support the enterprise’s aggressive potential.
Standardized strategy: Giving holistic, hierarchical outlook of existing as well as future resources.
Decision Support: gives support for the Information Technology resource decision­making at the managerial, management, as well as employees levels of the enterprise
Resource mistake: supports regulate advance for controlling the growth of ability and optimizing supporting assets.
EA analysis and design method
Framework: discovers the extent of the architecture to be developed as well as creates relations between the architecture’s regions
Enterprise Architecture components: variable goals, procedure, standards, as well as resources that could expand enterprise
Cu
ent architecture: The existing analysis of the Enterprise Architecture works to build a baseline record of existing assets and actions that is acknowledged in a reliable way with the expectations view of the Enterprise Architecture so that forecaster can see gaps of the work between prospect tactics as well as the existing competence.
Future architecture: new Enterprise Architecture components that require the enterprise to close the existing performance gap or hold a new strategic plan, ready condition, or technology resolution
Enterprise Architecture Management Plan: Gives description of existing as well as future outlook of the architecture for managing the change to the expectation business process
Threads: Information Technology related security, principles, as well as skill thought
4. What are some of the EA components and documentation artifacts that would be included in cu
ent and future views at each level of the EA³ Cube framework?
Vertical is goal, procedure, program that ca
ies out one line of business. Horizontal is goal, procedure, plan, or resource that ca
y out several lines of business. Components: goals as well as plan and information, systems and applications, skill and infrastructure. Artifacts: documents, diagrams, data, spreadsheets, charts,
5. Can EA be used by all types of enterprises? If so, why?
Yes because it aligns IT, operations and functional parts to the enterprise to make sustainable change in response to internal and external drivers.
6. How does an EA repository support the implementation methodology?
Implementation methodology supports the creation of cu
ent. Enterprise Architecture repository is a catalogue that keeps information as well as gives directions to Enterprise Architecture tools and other Enterprise Architecture program resources and it is planned to support certification.
7. Choose a...