Scenario You are working as an Enterprise Architect within an Enterprise Architecture (EA) team at a large government agency. The agency has multiple divisions. The agency has a well-established EA practice and follows the TOGAF standard as its method for architecture development. Along with the EA program, the agency also uses various management frameworks, including business planning, project/portfolio management, and operations management. The EA program is sponsored by the Chief Information Officer (CIO), who has actively promoted architecting with agility within the EA department as her preferred approach for projects. The government has mandated that the agency prepare themselves for an Artificial Intelligence (AI)- first world, which they have called their “AI-first” plan. As a result, the agency is looking to determine the impact and role that AI will play moving forward. The CIO has approved a Request for Architecture Work to look at how AI can be used for services across the agency. She has noted that digital platforms will be a priority for investment in order to scale the AI applications planned. Using AI to automate tasks and make things run smoother is seen as a big advantage. Process automation and improved efficiency from manual, repetitive activities have been identified as the key benefits of applying generative AI to their agency’s business. This will include back-office automation, for example, for help center agents who receive hundreds of email inquiries. This should also improve services for citizens by making them more efficient and personalized, tailored to each individual’s needs. Many of the agency leaders are worried about relying too much on AI. Some leaders think their employees will need to learn new skills. Some employees are worried they might lose their jobs to AI. Other leaders worry about security and cyber resilience in the digital platforms needed for AI to be successful. The leader of the Enterprise Architecture team has asked for your suggestions on how to address the concerns, and how to manage the risks of a new architecture for the AI-first project. Based on the TOGAF standard, which of the following is the best answer?

This option provides the most comprehensive and TOGAF-aligned approach. It correctly follows the Stakeholder Management technique by analyzing stakeholder concerns, issues, and positions. Crucially, it links these concerns to the creation of specific views and their documentation within the Architecture Vision, which is a key output of Phase A. Furthermore, it accurately describes the TOGAF method for risk management, where risks are identified, and mitigation requirements are captured in the Architecture Requirements Specification. This specification is a living document, managed and reviewed throughout the ADM cycle, ensuring that risks are continuously addressed. This integrated approach to managing stakeholder concerns and risks is central to the TOGAF framework.

A. This is incorrect because it narrowly confines risk management to the Security Architecture development, whereas TOGAF treats risk management as an ongoing activity across all ADM phases.

B. This option is less specific than C. Its description of risk management as "making sure the architecture...addresses risk" lacks the procedural detail of using the Architecture Requirements Specification.

D. This option is vague, referring to developing a "model for each stakeholder category" without specifying its purpose or type, and its description of risk management is generic and not tied to specific TOGAF artifacts.

1. The TOGAF® Standard

10th Edition

Part III: ADM Guidelines and Techniques

Chapter 24

Stakeholder Management. Section 24.3

"Steps in the Stakeholder Management Process

" details the process of identifying stakeholders

classifying their positions

and determining their requirements and concerns

which directly supports the stakeholder analysis mentioned in option C.

2. The TOGAF® Standard

10th Edition

Part II: Architecture Development Method (ADM)

Chapter 6

Phase A: Architecture Vision. Section 6.4.3

"Create the Architecture Vision

" specifies that this document should articulate a summary view of the architecture

addressing the key stakeholder concerns. This aligns with recording concerns in the Architecture Vision.

3. The TOGAF® Standard

10th Edition

Part III: ADM Guidelines and Techniques

Chapter 21

Risk Management. This chapter establishes that risk management is an integral and continuous activity throughout the ADM cycle

which contradicts the narrow view in option A. Section 21.4 describes the risk mitigation process

which often results in new requirements.

4. The TOGAF® Standard

10th Edition

Part III: ADM Guidelines and Techniques

Chapter 17

Architecture Requirements Management. This chapter describes the process of managing architecture requirements throughout the ADM. The Architecture Requirements Specification is identified as the living document for logging

prioritizing

and managing all requirements

including those for risk mitigation

as stated in option C.