The document discusses aligning business requirements from strategy to process execution using enterprise architecture (EA) and requirements management tools. It proposes linking graphical EA models to textual requirements documents to enable informed decision making based on real-time data. The solution scope, current and future architectures are assessed, requirements are generated from the architecture and linked back to enable traceability, and the solution is delivered with the architecture updated.

1. Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations [email_address] iEA16 © 2009 IBM Corporation

10. Architecture Driven Requirements Process Scope Project End Start Assess against ‘ current’ architecture Architecture Views Define ‘ future’ architecture Update ‘ current’ architecture Deliver Project Solution Generate Solution Requirements Requirements Text Document

13.  Assess ‘ Current’ Architecture for Gaps or Redundancies Process Model Variant 1 (as-is) Process Model Variant 2 (to-be)

15.  Generate Requirements from Architecture

16. Requirements Structure (architecture) DOORs Internal Customer Functional System Functional Software Specification Software Load Plan User Acceptance Test Plan PITCO CMMI Process Strategy & Vision External Customer Test & Equipment Master Plan Tests System Standards Conforms to Technical Standards Conforms to Policy Conforms to Tests Satisfies Satisfies Satisfies Satisfies Tests

17. Requirements Coupled with Architecture System Architect OV-1 Concept Graphic OV-5 Operational Activity SV-4 System Function SV-5 OA to SF SV-10 System Process OV-6 Business Process OV-7 Logical Data DOORs Internal Customer Human Functional System Functional Software Specification Software Load Plan User Acceptance Test Plan PITCO CMMI Process Strategy & Vision External Customer Test & Equipment Master Plan Tests System Standards Conforms to Technical Standards Conforms to Policy Conforms to Tests Satisfies Satisfies Satisfies Satisfies Tests

19.  Update ‘Current’ Architecture to Reflect Solution

23. © Copyright IBM Corporation 2009. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.