Midlands State University

Bachelor of Commerce Honours

In Information System (HINFOSYS)

DEGREE LEVEL: SEMESTER 3, LEVEL 2(HARARE WEEKEND CLASS)

MODULE: INFO 437 ENTERPRISE ARCHITECTURE

STUDENT NAME: NIGEL NJOVO

REGISTRATION NUMBER: R213335V

LECTURER: MR JEKESE
1. Distinguish between enterprise architecture and IT architecture.

Enterprise architecture and IT architecture are two related but distinct concepts within the
field of information technology. While they are interconnected and often overlap, they
serve different purposes and focus on different aspects of an organization's technology
infrastructure. Here's a breakdown of their key distinctions:
Enterprise Architecture:
1. Scope: Enterprise architecture (EA) encompasses the entire organization, including its
structure, processes, people, and technology. It aligns IT strategy with business goals and
objectives.
2. Perspective: EA takes a holistic and strategic view, considering the organization as a
whole. It examines the interrelationships between different business units, functions, and
processes.
3. Focus: The primary focus of enterprise architecture is on the alignment and integration of
various elements such as business processes, data, applications, technology infrastructure,
and organizational structure. It aims to optimize the overall functioning and efficiency of
the organization.
4. Stakeholders: Enterprise architects engage with stakeholders from multiple business
domains, including executives, managers, subject matter experts, and IT professionals, to
determine the enterprise's strategic direction and ensure that technology supports business
objectives.
5. Time Horizon: EA typically operates with a long-term perspective, considering the
organization's current state, future goals, and the roadmap to achieve desired outcomes.

IT Architecture:
1. Scope: IT architecture (ITA) deals specifically with the design and structure of the
organization's technology infrastructure, systems, and applications. It focuses on the
implementation and operation of IT solutions.
2. Perspective: ITA takes a more technical and operational view, concentrating on the
details of the technology landscape, system components, and their interactions.
3. Focus: IT architecture focuses on defining the standards, protocols, frameworks, and
guidelines for developing, deploying, and managing technology solutions within the
organization. It addresses issues such as system integration, security, scalability,
performance, and reliability.
4. Stakeholders: IT architects collaborate with IT professionals, software developers,
infrastructure specialists, and other technical staff to design and implement IT solutions
that meet business requirements.
5. Time Horizon: IT architecture typically operates with a shorter time horizon, aligning
with project timelines, technology advancements, and immediate business needs.

2. How does EA support business goals and strategies?

Enterprise Architecture (EA) supports business goals and strategies in several ways:

Alignment: EA ensures that the organization's technology infrastructure, systems, and

processes are aligned with its business goals and strategies. It identifies the necessary
capabilities, resources, and technology investments required to support the achievement
of those goals.

Planning and Road mapping: EA provides a structured approach to planning and road
mapping technology initiatives. It helps identify gaps and overlaps in the current IT
landscape, defines future target architectures, and develops transition plans to bridge the
gap between the current state and the desired future state. This enables the organization to
prioritize technology initiatives and allocate resources effectively.

Risk Management: EA helps identify and mitigate risks associated with technology
investments and initiatives. By considering the interdependencies and potential impacts
of changes to the technology landscape, EA enables the organization to make informed
decisions and manage risks effectively.
 Decision Making: EA provides a framework for making technology-related decisions that
are aligned with business goals. It enables stakeholders to evaluate different options,
assess trade-offs, and make informed decisions based on the impact on the organization's
overall architecture and strategic objectives.

Standardization and Consistency: EA promotes standardization and consistency in

technology solutions and practices across the organization. By defining and enforcing
architecture principles, standards, and guidelines, it ensures that technology investments
are aligned with the organization's strategic direction, facilitates interoperability, and
reduces complexity.

3. Briefly describe three key pressures that advocate for the adoption of enterprise
architecture.

There are several key pressures that advocate for the adoption of Enterprise Architecture
(EA). Here are some of them:

Complexity and Integration Challenges: Modern organizations face increasing

complexity in their technology landscapes. They often have a wide range of systems,
applications, and data sources that need to work together seamlessly. Without a
comprehensive EA approach, organizations can struggle with integration challenges, data
inconsistencies, duplication of efforts, and inefficient business processes. EA helps
address these complexities by providing a structured framework to analyse, design, and
integrate technology components, ensuring coherence and alignment across the
organization.

Business Agility and Innovation: In today's rapidly changing business environment,

organizations need to be agile and responsive to market demands. They must quickly
 adapt their operations, processes, and technology to seize new opportunities and stay
ahead of the competition. EA enables business agility by providing a holistic view of the
organization, identifying areas for improvement, and enabling strategic decision-making.
By aligning technology investments with business goals, EA supports innovation and
facilitates the adoption of emerging technologies that drive competitive advantage.

Cost Optimization and Resource Efficiency: Organizations are under constant pressure to
optimize costs and achieve operational efficiency. Without a clear understanding of the
technology landscape, organizations may invest in redundant systems, duplicate efforts,
or face challenges in managing and maintaining their IT infrastructure. EA helps identify
opportunities for consolidation, rationalization, and resource optimization. It enables
organizations to streamline processes, eliminate duplicate systems, leverage shared
services, and make informed decisions about technology investments. By optimizing
costs and resources, EA contributes to overall operational efficiency and cost savings.

4. Let’s say you work for MSU and you want to start an EA program, what are the best
approaches to start this? Assumptions: You don’t yet have executive support; the organization
maturity is 3. No one else knows about EA at MSU except yourself. No one knows about EA
benefits. Hint: Discuss based on ADM phases.

Starting an Enterprise Architecture (EA) program at MSU without executive support and with
limited awareness of EA benefits can be a challenging task. However, you can adopt a proactive
approach and leverage the Architecture Development Method (ADM) phases to gradually
introduce and establish EA within the organization. Here's a suggested approach

Phase 1: Preliminary Activities

In this phase, focus on building awareness and gaining initial support for EA:
Educate Yourself: Deepen your understanding of EA concepts, frameworks, and best practices.
Familiarize yourself with the specific challenges and opportunities within MSU.

Identify Stakeholders: Identify key stakeholders within MSU who can potentially support and
champion the EA initiative. These can include influential individuals in IT, business units, and
senior management.

Define Value Proposition: Clearly articulate the potential benefits of EA for MSU, such as
improved alignment between technology and business goals, increased agility, cost optimization,
and better decision-making.

Develop a High-Level Roadmap: Create a high-level roadmap outlining the steps and activities
required to establish EA at MSU. Emphasize the value that each phase will bring to the
organization.

Phase 2: Architecture Vision

In this phase, focus on creating a compelling vision for EA:

Develop a Vision Statement: Craft a concise and persuasive vision statement that highlights the
benefits of EA and how it aligns with MSU's strategic goals. Emphasize the value proposition
and how EA can address current pain points or challenges.

Engage Stakeholders: Start engaging with key stakeholders, including IT leaders, department
heads, and influential individuals. Share the vision statement, explain the value of EA, and seek
their input and support.

Conduct Awareness Sessions: Organize workshops or presentations to introduce EA concepts

and benefits to a broader audience within the organization. Use real-life examples and case
studies to demonstrate the positive impact of EA in other similar organizations.

Phase 3: Architecture Definition

In this phase, focus on defining the EA framework and establishing governance:

Select an EA Framework: Choose an EA framework that aligns with MSU's goals and
requirements. Common frameworks include TOGAF, Zachman Framework, or a customized
approach.
Create Baseline Architectures: Identify and document the current state of MSU's architecture
across different domains, such as business, data, applications, and technology. Document
existing processes, systems, and interconnections.

Establish Governance Structures: Develop governance structures and processes to oversee and
guide the EA initiative. This includes defining roles and responsibilities, decision-making
processes, and communication channels.

Phase 4: Architecture Implementation

In this phase, start implementing EA practices and demonstrate tangible outcomes:

Prioritize Initiatives: Identify key business and technology initiatives where EA can make an
immediate impact. Select a few pilot projects that align with MSU's strategic goals and
demonstrate the value of EA.

Collaborate with Project Teams: Engage with project teams and provide architectural guidance
and support. Demonstrate how EA principles and standards can be applied to improve project
outcomes, such as reducing redundancy, improving integration, or enhancing scalability.

Monitor and Communicate Results: Continuously monitor and assess the impact of EA on the
selected initiatives. Document success stories, lessons learned, and measurable improvements.
Regularly communicate these results to stakeholders to build credibility and generate further
support.

Throughout the process, continue to advocate for EA, educate stakeholders, and emphasize the
value it brings to MSU. Seek opportunities to align EA with the organization's strategic goals
and demonstrate its benefits through practical examples and measurable outcomes. Gradually, as
the benefits become evident, you can seek executive support and expand the EA program further
within MSU.

5.Describe any three (3) Enterprise Architecture tools.

There are numerous Enterprise Architecture (EA) tools available in the market, each offering
different functionalities and features. Here are descriptions of three widely used EA tools:
TOGAF (The Open Group Architecture Framework):

TOGAF is not just a tool but a comprehensive framework for developing and managing
enterprise architectures. It provides a structured approach to EA development and includes a set
of guidelines, templates, and best practices. TOGAF tools support the entire architecture
development lifecycle, from creating architecture vision to implementing and managing
architectures. These tools assist in documenting architecture artifacts, managing requirements,
conducting impact analysis, and generating reports. Some popular TOGAF-compliant tools
include Sparx Systems Enterprise Architect, BiZZdesign Enterprise Studio, and Archi.

ARIS (Architecture of Integrated Information Systems):

ARIS is a comprehensive EA tool that focuses on business process modeling and analysis. It enables
architects to design, analyze, and optimize business processes and organizational structures. ARIS
provides a visual modeling environment where users can create process models, organizational charts,
data models, and other architectural artifacts. It supports process simulation, impact analysis, and
performance monitoring. ARIS also integrates with other systems, such as business process management
(BPM) and workflow management tools. It is widely used in industries such as banking, manufacturing,
and telecommunications.

MEGA:

MEGA is a powerful EA tool that supports a wide range of architecture domains, including business,
information, application, and technology. It provides capabilities for modelling, analysing, and
visualizing enterprise architectures. MEGA offers a rich set of features, including process modeling, data
modeling, application portfolio management, risk management, and compliance management. It supports
collaboration and allows multiple stakeholders to contribute to architecture development. MEGA also
provides advanced reporting and analytics capabilities to assess the impact of architectural changes and
make informed decisions. It is commonly used in large organizations across various industries.