Enterprise Architecture: Scope and TOGAF

• Enterprise Architecture involves aligning an organization's business processes, information systems, and technology infrastructure with its strategic objectives.

Scope of Enterprise Architecture

• Business Architecture entails understanding and modeling an organization's business strategy, structure, processes, capabilities, and value streams.
• Information Architecture involves managing and structuring an organization's data and information assets, including defining data models, information flows, databases, data governance, and information security practices.
• Application Architecture addresses the design and integration of software applications and systems within the organization.
• Technology Architecture deals with the organization's technology infrastructure, including hardware, networks, servers, operating systems, and cloud platforms.

TOGAF

• The Open Group Architecture Framework (TOGAF) includes the Architecture Development Method (ADM), a step-by-step process for developing architectures.
• TOGAF covers business, data, application, and technology architecture domains.

Architecture Development Method (ADM) Phases

• Architecture Vision defines a strategic goal and creates a unified IT system.
• Business Architecture maps out business processes, identifies redundancies and gaps, and standardizes procedures.
• Information Systems Architecture designs a central data repository and new cloud-based core.
• Technology Architecture secures cloud solutions and modern cybersecurity frameworks.
• Opportunities & Solutions identifies quick wins and creates a roadmap for gradual implementation.
• Migration Planning uses a phased rollout strategy, ensures IT teams receive training, and ensures minimal disruption.
• Implementation Governance ensures compliance; regular audits and feedback loops refine the implementation process.
• Architecture Change Management continuously monitors system performance and updates the architecture.

Zachman Framework

• The framework is a matrix with six rows (Planner, Owner, Designer, Builder, Implementer, User), representing different perspectives:
• Rows represent Planner, Scope, Owner, Designer, Builder, Implementer, and User.
• Columns represent What (Data), How (Function), Where (Network), Who (People), When (Time), and Why (Motivation).

Federal Enterprise Architecture Framework (FEAF)

• FEAF was developed specifically for the U.S. federal government.

Enterprise Architecture Development Process

• Preliminary Phase defines scope, objectives, stakeholders, and governance framework.
• Phase A: Architecture Vision defines current vs. future state plus business drivers, goals, and architecture vision.
• Phase B: Business Architecture defines business capabilities and performs gap analysis of processes and organizational structure.
• Phase C: Information Systems Architecture requires systems and includes centralized data lake data architecture, and standardized APIs for seamless system integration in the application architecture.
• Phase D: Technology Architecture defines technology standards, infrastructure requirements, and technology evaluation.
• Phase E: Opportunities & Solutions identifies opportunities, creates a roadmap, and performs impact analysis.
• Phase F: Migration Planning defines migration steps and risk mitigation strategies: pilot tests, employee training, and backup recovery plans.
• Phase G: Implementation Governance includes mechanisms, compliance checks, and progress tracking; ensures data security and regulatory adherence (e.g., GDPR).
• Phase H: Architecture Change Management involves continuous monitoring of system performance and business process improvements; regular assessment and realignment with business goals.
• Requirements Management involves ongoing evaluation by the EA team that refines system requirements based on business feedback
• Architecture Partitioning involves segmented approach uses CRM, ERP, and AI analytics, which are implemented separately, integrated seamlessly
• Architecture Governance ensures continued compliance, monitors system performance, and recommends improvements and is dedicated long-term

Information Architecture

• Information Architecture involves the practice of designing and organizing information in a structured and user-friendly manner to support effective navigation, understanding, and retrieval of information.

Normalization

• Normalization is a process to eliminate data redundancy and improve data integrity in a relational database design.

Normal Forms

• 1st Normal Form (1NF): removes duplicate columns, ensures atomic values (no multiple values in a single cell), and ensures each row has a unique identifier (primary key).

• 2nd Normal Form (2NF): removes partial dependencies (fields that depend only on part of a composite key) by separating Students, Courses, and Instructors into different tables.

• 3rd Normal Form (3NF): removes transitive dependencies (a non-key column depending on another non-key column).