The TOGAF Standard - Structure and Documents

Overview The Architecture Repository is a central repository for all architecture artifacts and work products. It stores different classes of architectural output at different levels. Part of the Enterprise Repository of artifacts. This is often implement by modelling software (e.g. BizzDesign), analytic tools, file repositories or document/content management systems. Architecture Landscape The architectural representation of assets deployed within the enterprise at a particular point in time - This will reflect the baseline, transition(s) and target states often at multiple levels of detail. ...

Building Blocks Overview These are potentially re-usable components that can be used to deliver an Architecture. TOGAF will group these into the abstract Logical - Application Building Blocks and the Physical Building Blocks - Solution Building Blocks (SBB). Without being too prescriptive, a building block should meet the following criteria: Is a package of functionality defined to meet a business need or capability. It should be recognisable as a discrete thing. Should normally correspond to one of the types defined in the Enterprise Metamodel - Actor, Business Service, Application or Data Entity. Can be defined at various levels of detail depending on the objective of the Architecture and also the Phase. There is a general benefit of composing functionality through building blocks in that it should improve integration and interoperability through defined interfaces and contracts. It may also improve reusability and flexibility through the creation of new re-usable applictions or components. ...

TOGAF Architecture Development Method (ADM) TOGAF uses a “crop circle” diagram to show the progress of the different phases of the ADM. Prior to commencing the ADM, the Preliminary phase should be completed, which will provide the framework and principles for the ADM. The phases may occur in parallel. The circle theme is used to show the possible iterations of the architecture over time. Requirements are in the centre as they will be updated and managed throughout the ADM phases. ...

Purpose The primary purpose of Architecture Principles are: Enable decision-making - it is important to set precedence during trade-off discussions and authority of tie-breaking if it must occur Align the enterprise - principles take subjectivity and bias out of the equation and drive critical conversations that are objective and aligned to the enterprise’s values Governance - how will the enterprise ensure that the right decisions are surfaced at the right time and with the right decision-makers, and, moreover, how to monitor the decisions and approach taken to arrive at the decision? Values and Culture - provide a better understanding about the enterprise’s culture and values; provide an approach and insight into how well the enterprise reacts to change Characteristics The following are some primary characteristics of Architecture Principles: ...

AI guardrails are essential safeguards that prevent large language models (LLMs) from generating harmful or undesirable content. These guardrails can be broadly categorized into several types: Content Filtering: This is the first line of defense, working on both the input (prompt) and output (response) to block the generation of harmful material, such as hate speech, violence, or inappropriate content. Behavioral Constraints: These guardrails limit the AI system’s actions and capabilities, preventing it from accessing specific resources or performing unauthorized actions. Alignment Mechanisms: These are sophisticated techniques that ensure the AI’s goals align with human values and intentions, preventing it from pursuing unexpected or harmful objectives. Technical Safeguards: This category includes engineering-focused measures like output monitoring for real-time risk detection, rate limiting to prevent misuse, and sandboxing to isolate AI operations. Training-Based Guardrails: These safeguards are integrated directly into the AI during its development, using techniques like Reinforcement Learning from Human Feedback (RLHF) to minimize problematic patterns from the outset. Implementing Guardrails in the SDLC Building a safe and responsible AI system requires integrating guardrails throughout the entire Software Development Life Cycle (SDLC). The biggest challenge with off-the-shelf developer tools like GitHub Copilot or GitLab Duo is that they primarily operate within the Code phase. This shifts the focus from controlling the AI model itself to validating and securing its output as it moves through your pipeline. ...

Architecture Abstraction The concept of abstraction is a means to enable reasoning about an Architecture. Dividing a problem into smaller problems is a common approach to making an Architecture easier to model and create solutions for. We can have one or more of the abstraction levels at each of the Strategic, Segment or Capability Architecture. Introduction We can consider multiple simple questions in order to structure the approach to abstraction: ...

Architecture Board The cross-enterprise architecture board is the highest level of architecture governance and is represnted by architecture stakeholders. Role The Group of executives responsible for the review and maintenance of the architecture and to oversee the implementation of the strategy within Phase H - Architecture Change Management of the ADM. Possesses identifiable and articulated responsibilities, decision-making capabilities, remit and authority limits. Distinguishes between local (domain experts, line responsibility) and global (organisation-wide responsiblity) representatives in larger enterprises Scope may be Global, Regional or Business Line General Responsibilities The board is reponsible and accountable for achieving different goals: ...

Architecture Capability The Enterprise Architecture is a business capability that supports 4 different types of business capabilities: Architecture to Support Strategy Architecture to Support Portfolio Architecture to Support Projects Architecture to Support Solution Delivery Overview Posseses organisation structures with roles, responsibilities, skills and processes for Enterprise Architecture work. Treated like any other operational unit within the business. Establishes management capabilities for the architecture capability. Purposes Purpose Capability Description Architecture to Support Strategy Provide Target Architecture and Roadmaps Change & synergies, governance Multiple programmes and portfolios Architecture to Support Portfolio Ensure alignment, synergies between architectures and governance Single portfolio of projects Support of Cross-functional and multi-phase architectures Architecture to Support Projects Integration between projects Integration between projects Value and Compliance per project Support the project delivery method Architecture to Support Solution Delivery Support the solution deployment for an architecture Governance Framework for change Single project or a significant part of a project Architecture to Support Strategy Provide end-to-end Target Architecture Develop Roadmaps for change over a period of 3 to 10 years ...

Governance Overview Within TOGAF the focus is on Architecture Governance and how it supports other forms of governance within an enterprise. Definition Given the focus on architecture governance within TOGAF, we can define governance as the system by which the current and future state are directed and controlled. A committed and hierarchical decision-making process with a defined structure of relationships to direct and control the enterprise to achieve stated goals. Enables the equality of concerns and transparency (making sure all Stakeholders concerns are reflected), protecting the rights and interests of the business. It can be used to drive a set of behaviours controlled via measurements and metrics. Customisation A customised governance approach should define - How, When, Why and What? ...