TOGAF 9.1 Series — ADM Phase — Requirements Management

Have you ever heard of TOGAF and never really understood it? In my TOGAF 9.1 series of articles, I will give you summary points what TOGAF is and what you will learn in TOGAF.

I have written the TOGAF exam a while back. I thought that writing this series will let me review the TOGAF content and believe that it would be valuable to others. It is always a good practice to regularly review the contents of a topic that you have learned.

I’m not going to rewrite the official TOGAF books content in my article series. Some sections will only contain bullet points of key terms used in TOGAF. Always reference the official TOGAF book for more details.

Legal Points

TOGAF is a trademark of The Open Group. They maintain the TOGAF standard and release new versions of the framework. I highly recommend that you read the official website and content of TOGAF on the official site: http://www.opengroup.org/subjectareas/enterprise/togaf

The contents in my article series are my opinions and in no way reflects the views of The Open Group.

If you are interested in learning all the finer details of TOGAF or want to write the exam then buy the official book:

Figure 1: TOGAF Version 9.1 book

ADM Phase — Requirement Management

Objectives

  • Ensure that the Requirements Management process is sustained and operated for all relevant ADM phases.
  • Manage architecture requirements identified during any execution of the ADM cycle or a phase.
  • Ensure that relevant architecture requirements are available for use by each phase as the phase is executed.

Steps

  • Identify/document requirements
  • Baseline requirements
  • Monitor baseline requirements
  • Identify changed requirement and record priorities
  • Identify and resolve conflicts
  • Generate Requirements Impact Statements
  • Assess impact of changed requirements on current and previous ADM phases
  • Implement requirements arising from Phase H
  • Update the requirements repository
  • Implement change in the current phase
  • Assess and revise gap analysis for past phases

Inputs

  • The inputs to the Requirements Management process are the requirements-related outputs from each ADM phase.
  • The first high-level requirements are produced as part of the Architecture Vision.
  • Each architecture domain then generates detailed requirements.
  • Deliverables in later ADM phases contain mappings to new types of requirements.

Outputs

Changed requirements

Requirements Impact Assessment

  • Identifies the phases of the ADM that need to be revisited to address any changes.
  • Final version must include the full implications of the requirements (costs, timescales and business metrics)

Originally published at cecilblog.com on March 16, 2016.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.