IS 103 (QUIZ)

• Enterprise Architecture


  is the process of designing and managing an enterprise’s information systems by creating a model that shows how the enterprise works.
• TOGAF


  is the most used framework for enterprise architecture (EA) as of 2020 that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture.
• TOGAF


  is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology.
• 1995


  The 1st version of TOGAF was published by the Open Group in
• TOGAF


  is a framework that provides guidelines and best practices for designing and managing the architecture of an organization's information technology (IT) systems
• TOGAF


  serves as a comprehensive framework that supports organizations in developing and managing their enterprise architectures
• TOGAF GOALS IN EA

  DESIGN

  PLAN

  IMPLEMENT

  MANAGE
• Enterprise Architect


  is responsible for the upkeep and maintenance of an organization's IT networks.
• Enterprise Architect


  is responsible for the overall design and successful implementation of an organization's technology infrastructure.
• The Preliminary Phase


  describes the preparation and initiation activities required to prepare to meet the business directive for new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles.
• Phase A: Architecture Vision


  describes the initial phase of an architecture development cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
• Phase B: Business Architecture


  describes the development of a Business Architecture to support an agreed Architecture Vision.
• Phase C: Information Systems Architectures


  describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
• Phase D: Technology Architecture


  describes the development of the Technology Architecture for an architecture project.
• Phase E: Opportunities & Solutions


  conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases.
• Phase F: Migration Planning


  addresses the formulation of a set of detailed sequences of transition architectures with a supporting Implementation and Migration Plan.
• Phase G: Implementation Governance


  provides architectural oversight of the implementation.
• Phase H: Architecture Change Management


  establishes procedures for managing change to the new architecture.
• Requirements Management


  examines the process of managing architecture requirements throughout the ADM.
• ARCHITECTURE PRINCIPLES


  are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission.
• ARCHITECTURE PRINCIPLES


  Depending on the organization, principles may be established within different domains and at different levels.
• Enterprise Principles


  provide a basis for decision-making throughout an enterprise and inform how the organization sets about fulfilling its mission.
• Architecture Principles


  are a set of principles that relate to architecture work.
• Understandable


  the underlying tenets can be quickly grasped and understood by individuals throughout the organization.
• Robust


  enable good quality decisions about architectures and plans to be made, and enforceable policies and standards to be created
• Consistent


  strict adherence to one principle may require a loose interpretation of another principle.
• Stable


  principles should be enduring, yet able to accommodate changes.
• Complete


  every potentially important principle governing the management of information and technology for the organization is defined - the principles cover every situation perceived.
• Stakeholder management


  is an important discipline that successful architecture practitioners can use to win support from others. It helps them ensure that their projects succeed where others fail.
• Identify Stakeholders


  The first task is to brainstorm who the main Enterprise Architecture stakeholders are.
• Classify Stakeholder Positions


  Develop a good understanding of the most important stakeholders and record this analysis for reference and refresh during the project.
• Determine Stakeholder Management

  Approach


  This step enables the team to easily see which stakeholders are expected to be blockers or critics, and which stakeholders are likely to be advocates and supporters of the initiative.
• Tailor Engagement Deliverables


  It is important to pay particular attention to stakeholder interests by defining specific catalogs, matrices, and diagrams that are relevant for a particular Enterprise Architecture model.
• GAP ANALYSIS


  A key step in validating an architecture is to consider what may have been forgotten.
• interoperability


  is "the ability to share information and services".
• Business Transformation Readiness Assessment


  Understanding the readiness of the organization to accept change, identifying the issues, and then dealing with them in the Implementation and Migration Plans is key to successful architecture transformation in Phases E and F.
• RISK MANAGEMENT


  There will always be risk with any architecture/business transformation effort
• Capability-based planning


  focuses on the planning, engineering, and delivery of strategic business capabilities to the enterprise
• Capability-based planning


  accommodates most, if not all, of the corporate business models and is especially useful in organizations where a latent capability to respond (e.g., an emergency preparedness unit) is required and the same resources are involved in multiple capabilities
• DELIVERABLE


  Is a work product that is contractually specified and in turn, formally reviewed, agreed and signed off by the stakeholders