Sia 2
Sia 2
LEARNING OBJECTIVES:
Define what enterprise architecture is and why it is essential for organizations.
Explain the key concepts and principles of enterprise architecture.
Describe how enterprise architecture helps align business goals and IT strategies.
Demonstrate the ability to identify and analyze the impact of IT decisions on the overall business
strategy.
Describe how enterprise architecture helps align business goals and IT strategies.
Demonstrate the ability to identify and analyze the impact of IT decisions on the overall business
strategy.
MODULE CONTENT:
Enterprise architecture (EA) is a practice for understanding and managing the structure and behavior of
an organization. It is a holistic approach to aligning an organization's business goals, information
systems, and technology infrastructure.
Enterprise architecture is a complex and challenging discipline, but it can be a valuable tool for
organizations that want to improve their performance and achieve their goals.
If you are considering implementing enterprise architecture in your organization, there are a few things
you should keep in mind:
Start with a clear understanding of your organization's goals and objectives.
Get buy-in from key stakeholders.
Use a well-defined methodology.
Be prepared to invest time and resources.
Enterprise architecture is a long-term investment, but it can be a valuable way to improve your
organization's performance and achieve its goals.
Enterprise structure is the way an organization is organized and divided into smaller units. It defines the
roles, responsibilities, and relationships between different parts of the organization. The enterprise
structure should be align with the organization's goals and objectives, and it should be flexible enough
to adapt to change.
There are many different types of enterprise structures, and the best type for an organization will
depend on its size, industry, and culture. Some common types of enterprise structures include:
Functional structure: This is a traditional type of structure in which the organization is divided
into functional departments, such as sales, marketing, finance, and operations.
Divisional structure: This structure is based on product lines, geographic regions, or customer
segments.
Matrix structure: This structure combines functional and divisional structures, with employees
reporting to both a functional manager and a divisional manager.
Network structure: This structure is made up of independent organizations that work together
to achieve a common goal.
The enterprise structure should be designed to achieve the following goals:
Effectively achieve the organization's goals and objectives.
Promote communication and collaboration between different parts of the organization.
Enable the organization to adapt to change.
Minimize duplication of effort and resources.
Provide a clear chain of command.
Define roles and responsibilities.
The enterprise structure should be reviewed regularly and updated as needed to ensure that it is still
aligned with the organization's goals and objectives.
Here are some of the factors that should be considered when designing an enterprise structure:
4. DoDAF (Department of Defense Architecture Framework): Specifically designed for the U.S.
Department of Defense, it provides guidance on how to develop architectures to support
defense missions.
5. MODAF (Ministry of Defence Architecture Framework): Similar to DoDAF but used by the
United Kingdom's Ministry of Defence.
6. PEAF (Pragmatic Enterprise Architecture Framework): Emphasizes pragmatism and simplicity in
enterprise architecture to make it more accessible and actionable.
7. ArchiMate: A graphical modeling language that complements other frameworks by providing a
standardized way to represent architecture.
8. ITIL (Information Technology Infrastructure Library): Focuses on IT service management and
aligning IT services with the needs of the business.
9. SABSA (Sherwood Applied Business Security Architecture): Concentrates on security
architecture, helping organizations integrate security into their overall enterprise architecture.
10. Dragon1: A digital platform that combines elements of various frameworks and methodologies
to enable dynamic visualization and management of enterprise architecture.
The choice of framework depends on an organization's specific needs, industry, and goals. Many
organizations adapt and combine elements from multiple frameworks to create a custom approach that
suits their unique requirements.
TOGAF, which stands for "The Open Group Architecture Framework," is a widely recognized and used
enterprise architecture framework. It's developed and maintained by The Open Group, a global
consortium of organizations focused on developing open standards and best practices for various
aspects of information technology.
Key points about TOGAF include:
1. Methodology: TOGAF provides a comprehensive methodology for enterprise architecture. It
outlines a systematic process for developing and managing enterprise architectures.
2. ADM (Architecture Development Method): The core of TOGAF is its Architecture Development
Method, which guides practitioners through the phases of architecture development, from
defining business requirements to creating and maintaining the architecture.
3. ADM Phases: The ADM consists of various phases, including Preliminary, Architecture Vision,
Business Architecture, Information Systems Architecture, Technology Architecture,
Opportunities, and Solutions, Migration Planning, Implementation Governance, and
Architecture Change Management.
4. ADM Guidelines and Techniques: TOGAF offers guidelines and techniques for each phase,
helping architects make informed decisions and develop high-quality architectures.
5. Architecture Repository: TOGAF promotes the use of an Architecture Repository to store
architecture artifacts, making it easier to manage and reuse architectural information.
6. TOGAF Architecture Content Framework: It defines a standardized way of categorizing and
structuring architecture artifacts.
7. Certification: TOGAF offers certification programs for individuals, allowing them to become
certified as TOGAF Architects at various levels.
8. Ecosystem: TOGAF is often used in conjunction with other frameworks and standards, such as
ArchiMate for modeling or ITIL for service management.
TOGAF is particularly valuable for organizations looking to align their business and IT strategies, improve
decision-making, and enhance the overall management of their architecture. It provides a structured
approach to architecture development and is widely adopted in various industries globally.
The Zachman Framework, named after its creator John A. Zachman, is a widely recognized framework
for enterprise architecture. It's often used to structure and organize the various aspects of an
organization's architecture, including processes, data, systems, and more. The framework is known for
its grid-like structure, which categorizes architectural artifacts based on six perspectives (rows) and six
interrogatives (columns). These perspectives and interrogatives are as follows:
Perspectives (Rows):
1. Planner's Perspective: Focuses on the high-level strategic view of an organization's architecture,
addressing questions like "What" and "Why."
2. Owner's Perspective: Concerned with the business processes and operational aspects,
answering questions like "How" and "Where."
3. Designer's Perspective: Deals with the logical design of systems and data, answering questions
like "Logical" and "When."
4. Builder's Perspective: Involves the physical implementation of systems and technology,
addressing questions like "Physical" and "Who."
5. Sub-Contractor's Perspective: Concerned with the technical details and components, answering
questions like "Component" and "Which."
6. User's Perspective: Represents the end-user experience and needs, addressing questions like
"Operation" and "Went."
Interrogatives (Columns):
1. What: Describes the data, function, and network that are relevant to an organization.
2. How: Focuses on the processes and functions that transform data within an organization.
3. Where: Specifies the location or geography where architectural elements are applicable.
4. Who: Identifies the people, roles, and organizations responsible for various architectural
aspects.
5. When: Addresses the timing and sequence of architectural elements and processes.
6. Why: Explores the motivations and reasons behind architectural decisions and objectives.
The Zachman Framework provides a structured way to document and analyze an organization's
architecture from multiple perspectives, making it a valuable tool for aligning business and IT, facilitating
communication between different stakeholders, and improving overall enterprise architecture
governance. It's important to note that the framework doesn't prescribe a specific methodology but
serves as a taxonomy for organizing architectural artifacts.
REFERENCES:
Prepared by:
MR. NELSON D. TACADENA