6.1.1 Stakeholder Engagement and Requirements Management
The TOGAF framework places requirements management and stakeholder engagement at the center of architecture development. Practitioners develop EA in accordance with the preferences and priorities of their organization’s stakeholders. Architecture is never sold to a stakeholder. Stakeholder preferences are never manipulated.
C reflects that requirements are continuously managed throughout the entire architecture development process, across all phases of the ADM cycle.
It is the visual representation of the ADM cycle that gives you the impression that Requirements are "at the center" but this is not in a literal sense
*changing my mind, I think it is A*
This statement about Requirements Management is most correct because it reflects the central role of Requirements Management and stakeholder engagement in the ADM cycle. Requirements Management is not a step of all ADM Phases, but rather an ongoing process that ensures that all relevant requirements are elicited, analyzed, prioritized, and addressed throughout the architecture development and transition. Stakeholder engagement is also a continuous activity that involves identifying, communicating, and managing stakeholder expectations and concerns
requirements management is central to the ADM and a perpetual process.
upvoted 1 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
orbpig
3 weeks, 4 days agokyle942
1 month, 1 week agoDespinaA
1 month, 2 weeks agoB__keeper
2 months, 2 weeks agoMoStRo4
2 months, 3 weeks agoChiquitabandita
3 months, 3 weeks agoChiquitabandita
3 months, 3 weeks agojtc77
3 months, 3 weeks ago