Understanding Enterprise Architecture

• Building large, complex enterprise-wide information systems is difficult without an enterprise architecture.
• Creating a city without a plan is similar to creating information systems without architecture.

Township, State, and Enterprise Architectures

• Township architecture involves components like gated communities, residential towers, and urban houses.
• State architecture comprises sectors, departments, agencies, services, and requests.
• Enterprise and Partner Systems architecture includes ERP, CRM, SCM, FMIS, HRMS, packages, modules, and programs.

Complexity and Change in Enterprise Architecture

• Complexity arises due to the size and scale of modern systems
• Change is a constant dynamic that enterprise architecture must adapt to.

Enterprise Architecture Definitions

• An enterprise is a collection of organizations sharing common goals.
  • Examples of an enterprise include a union government, individual ministry, or state government
• Enterprise Architecture is a description of current and future services, processes, and information systems aligned with an enterprise's vision.

The Role of Enterprise Architects

• Many enterprises exist without enterprise architects
• Architecting an enterprise is preferrable to letting its architecture evolve by chance
• All enterprises have architecture, whether managed or not.

Enterprise Architecture Analogies

• Enterprise Architecture is like City Planning for an Enterprise
• Governance Strategy = IT Strategy
• Governance Architecture = IS/IT Architecture
• Government Processes & IT Systems = IT Solutions
• City Plan = Enterprise Architecture
• Building Design = Solution

EA Building Blocks

• Strategy & Performance Architecture provides the plan for decision-making and outcomes.
• Policy & Strategy Architecture involves the mission, goals, and measures for rational outcomes.
• Service & Process Architecture explains the "why" behind the service and the outcomes which are sought
• Services & Products offer an outside-in perspective
• Capabilities & Processes offer an inside-out perspective.
• Data Architecture manages data, information, knowledge, and wisdom.
• Application Architecture includes the software that supports business functions
• Technology Architecture includes the physical infrastructure for acting.
• Architecture Governance & Management encompasses decision rights and embracing the architecture

Enterprise Architecture Benefits

• Increased service delivery efficiency
• Improved scheme implementation effectiveness
• Higher ROI on technology investments through common, reusable components
• Increased innovation through defined architecture and governance
• Increased flexibility through quicker technology changes and dynamic business responses
• Seamless interoperability between systems

Decisions in Enterprise Architecture

• Should a common application set be used or independent ones developed?
• Which systems need development, enhancement, or retirement?
• What data areas or elements must be standardized across the enterprise?
• What enterprise-wide interfaces should systems provide?
• Should the technology be standardized?
• Which current or upcoming technologies should be invested in?

Key Takeaways on Enterprise Architecture

• Enterprise architecture holistically understands the enterprise environment (business, technology, operations)
• Enterprise architecture effectively directs the enterprise to achieve strategic goals
• This is done through aligned business and technology operations
• It is needed to improve service delivery efficiency and scheme implementation effectiveness
• It also helps increase agility and RoI from tech investments
• It does this through optimized landscapes using common, reusable components

EA Frameworks

• EA Frameworks Typically Include:
  • Processes & methods
  • Catalog of architecture deliverables and artifacts
  • Content model and repository structure
  • Reference models
  • Best practices, guidelines & techniques
  • Architecture capability development
  • Architecture governance and compliance
• Each framework has a specific philosophy which must be assessed to see if it fits an enterprises needs
• Implementers can mix and match to achieve the best fit for their requirements

EA Frameworks Evolution - Key facts:

• The development of frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UK and USA) and Industry (Microsoft and Oracle)
• Zachman Framework (1987): An enterprise ontology for structured viewing and definition.
• TAFIM (1994): Released.
• Clinger-Cohen Bill (1996): Passed.
• FEA replaces FAEF (2002)
• TOGAF 8.0 Enterprise Edition (2003): Released.
• FEA completed (~) (2006):
• TOGAF 9 (2009): Released.
• IndEA (2017): Created.
• TOGAF 9.2 (2018): Released.

Frameworks

• The federal enterprise architecture (FEA) Offers a common approach for integrating strategic, business, and technology management.
• The open group architectural framework (TOGAF) Serves as an enterprise architectural framework for designing, planning, implementing, and governing.
• The Zachman Framework is an Enterprise Ontology which provides a formal and structured way of viewing and defining an enterprise
• The Gartner Methodology works by combining the Gartner framework and Meta architecture development process.

Key Components of the Zachman Framework

• Schema is about the categorization based on intersection between two classifications
• The first set of classifications are primitive interrogatives: What, How, When, Who, Where and Why
• The second set of classifications are each derived from transforming abstract ideas: Identification, Definition, Representation, Specification, Configuration and Instantiation

Management Areas

• Strategic, general, and IT management are all relevant to enterprise architecture

Strategic Management

• Balanced Scorecard is a strategy which recommends a three-layered structure for perspectives
  • Mission (e.g., to become the customers’ preferred supplier)
  • Objectives (e.g., to provide the customers with new products)
  • Measures (e.g., percentage of turnover generated by new products)

Quality Management

• QMS may direct focus to an enterprise architecture initiative, by putting the emphasis on those processes and resources that are critical for the company's product or service quality.

IT Governance: COBIT

• COBIT (Control Objectives for Information and related Technology)
• It offers a maturity model for IT governance consisting of 5 layers:
  • Ad hoc business activity is dedicated
  • Repeatable management Aware of issues
  • Defined
  • Managed
  • Optimized - Continuous improvement is the defining characteristic

Information Technology Infrastructure Library

• Service Delivery delivers service-level and availability, as well as financial and contingency management.
• Service Support cover problem, incident, service desk, change, and release management.

IT Implementation

• The different steps of implementation are:
  • Initial - Processes are ad hoc
  • Managed - Requirements are managed and processes are planned
  • Defined - Processes are characterized and understood. projects are establish consistency among standards.
  • Quantitatively Managed - Quantitative objectives are followed and established.
  • Optimizing - Process performance is being improved technologically.

Enterprise IT Definition and Purpose

• Enterprise IT is large-scale technological solutions used to streamline operations, improve efficiency, and manage resources for large companies or organizations.

Key Components

• It Can include software, systems, and hardware that help achieve the organization’s goals
• It can organize data, mange resources, track sales, and improve communication between employees.
• For instance, a company might need an enterprise IT solution to handle accounting, sales, and other processes. The IT solution helps connect and manage all these tasks.

Design Stage In Enterprise

• The design phase involves planning and structuring the IT solution.
• The goal is to define how the solution will work and how it will be built for the company-specific needs.
• It Key details include:
  • Understanding the requirements, and identifying problems it solves
  • Creating a Blueprint which Includes the system’s structure and how different components interact.
  • Choosing the architecture and deciding if the system runs on company servers and how.
  • Security Considerations like implementing protection from cyber-attacks via security measures.
  • Compatibility with Existing Systems by ensuring the new solution doesn't cause conflict with existing.

Selection Stage In Enterprise

• The selection phase is where The tools and technologies needed to implement the design are determined.
• Key Details:
  • Selecting software for the company's use.
  • Selecting hardware to work.
  • Selecting the type of network that connects everything.
  • Choosing Vendors to provide tools or services.
  • Following budget considerations

Implementation Stage In Enterprise

• The implementation stage is when Systems Architecture is being created and hardware is being integrated with software.
• Its a large-scaling technical system
• Key Details:
  • Planning - Identifying objectives and defining scope for IT solution.
  • Requirement Analysis - Ensuring the solution aligns with the organization's goals.
  • Design and Development
  • Testing and Deployment
  • Training and Support

Management Stage In Enterprise

• The management stage maintains enterprise IT to ensure performance, security, and scalability
• Key Details:
  • Monitoring & Optimization - Regular performance and the resources being used.
  • Protection from IT infrastructure from cyber threats.
  • Control User access and security on sensitive documents.
  • Data Management and Compliance to regulations.
  • Keeping Upgrades & Scalability to the latest tech.

Applications Role in Enterprise IT

• Applications offer software designed for a business's needs and functions

Applications Considerations

• Business needs alignment between applications and business goals is key in enterprise design
• Focus On applications providing The most use and value for friendly user experience
• Ensure they provide Scalability to handle growth
• Make sure It can provide Intergration of different systems.
• Customization Vs. Off the shelf tools needs assessing

Example Applications

• CRM’s (Customer-relationship management) for helping customers is like Salesforce
• Streamline finance and ERP (Enterprise resource planning) is like Oracles
• Remote Tool Collaboration is teams or slack

Infrastructure

• Infrastructure is The foundation of business operations,
• It consists of hardware, software, network and service data to ensure operational security

Infrastructure Considerations

• Reliability, Security and cost efficiency are all consideration for the disaster recovery.
• The flexibility of scalability helps meet businesses demands.
• Compliance with regulations is a key in keeping sensitive data.

Infrastructure Examples

• Traditional enterprise on premises is traditional data centers.
• A cloud offers a WS, azure and google
• Hybrid on premises and cloud solutions

Fit with Business

• Aligning various infrastructures with the business will prove critical for operational efficiency
• Digital transformation will be needed for customer experience

Strategic Alignment: Short-Term vs. Long-Term Goals

• Short-Term Goals: Focus on cost-effective solutions for immediate needs.
• Long-Term Goals: Invest in scalable, future-proof technologies for growth and innovation.

Challenges in Enterprise IT

• Complexity
• Legacy Systems
• Security Risks
• Cost Management

Best Practices

• Collaboration Between IT and Business is useful for planning
• Cloud Technologies and Agile DevOps provide support and flexibility
• Security Compliance is important

Framework vs Strategy

• A framework is an organizational structure
• Strategy Is the process to implement the organizational frameworks.

Benefits of IT Frameworks

• productivity and efficiency
• Better standardized processes and risk management.
• Improved easier audit and continuous improvement of IT
• More transparency

Example Frameworks

• ITIL (Library)
• COBIT (Technologies)
• TOGAF (Framework)
• Agile and Scrum Framework
• DevOps
• Six Sigma for IT
• ISO/IEC 27001 (Information Security Management)
• PMBOK (Project Management Body of Knowledge) for IT Projects

Benefits of IT Strategies

• Improved efficiency
• Enhanced security and risk management

Hybrid strategy

• Leveraging on premises for workload identification and cloud migration

System Administration frameworks

• They Improve efficiency and provide regular training for administrators