Consider the following descriptions of deliverables consumed and produced across the TOGAF ADM cycle. 1. General rules and guidelines, intended to be enduring and seldom amended, that inform and…

Question

Options

• A1 Architecture Principles -2 Architecture Contracts - 3 Request for Architecture Work - 4
• B1 Architecture Contracts - 2 Architecture Requirements Specification - 3 Architecture Vision - 4
• C1 Architecture Requirements Specification -2 Architecture Principles - 3 Architecture Vision - 4
• D1 Architecture Principles -2 Architecture Contracts - 3 Architecture Requirements Specification-4

• A
  59% (22)
• B
  5% (2)
• C
  22% (8)
• D
  14% (5)

Explanation

According to the TOGAF standard, the deliverables that match the descriptions are as follows: 1. Architecture Principles: These 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. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. 2. Architecture Contracts: These are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture. They are used to ensure that the architecture is implemented and governed according to the agreed-upon specifications and standards. 3. Request for Architecture Work: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle. It defines the scope, schedule, budget, deliverables, and stakeholders of the architecture 4. Architecture Requirements Specification: This is a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture. It defines the requirements for each architecture domain, as well as the relationships and dependencies among

No community discussion yet for this question.