Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "© 2009 IBM Corporation iEA16 Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations."— Presentation transcript:

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

2 IBM Rational Software Conference 2009 iEA16 Objective Align business requirements from strategy to front line process execution Combine use of Enterprise Architecture & Requirements tools. 2

3 IBM Rational Software Conference 2009 iEA16 Session Benefits Users attending session can take away an understanding of: Enabling an actionable enterprise architecture Value of linking enterprise architecture to requirements Efficiencies of generating requirements from enterprise architecture Process for managing requirements through enterprise architecture 3

4 IBM Rational Software Conference 2009 iEA16 Scenario Managers make many decisions - from simple to complex. Most business decisions have data dependencies captured as static snapshots in enterprise architecture products or requirements documentation. Decisions are made without considering effects on enterprise touch points – uninformed. 4

5 IBM Rational Software Conference 2009 iEA16 Scenario EA, in today's world, cannot persist simply as artifacts supporting compliance… Not enough money to support both robust data management efforts comprehensive EA efforts Go beyond static artifacts - an enterprise architecture that delivers decisions based on relevant data. 5

6 IBM Rational Software Conference 2009 iEA16 Problem Little attention is paid to human usability (or reuse) of the finished product. Requirements documentation is produced and the solution delivered. Content is shelved and neither visible nor usable to most people. 6 Most requirements gathering efforts center on generating large quantities of documentation to support ill-defined business needs.

7 IBM Rational Software Conference 2009 iEA16 Problem (other side) Most people are graphical learners – comprehending through pictures or models. 7

8 IBM Rational Software Conference 2009 iEA16 Problem (other side) Most requirements are textual; detailed and data rich. 8

9 IBM Rational Software Conference 2009 iEA16 Solution Enable rapid assessment of gaps in enterprise through architecture ensuring requirements meet relevant needs. Use enterprise architecture products (graphics) to clearly depict desired solution. Link or generate requirements from an enterprise-wide accessible architecture based on real time information. 9 Link Requirements (textual) to Enterprise Architecture (graphical)

10 IBM Rational Software Conference 2009 iEA16 Architecture Driven Requirements Process 10 Scope Project End Start Assess againstcurrent architecture Architecture Views Definefuture architecture Updatecurrent architecture Deliver Project Solution Generate Solution Requirements Requirements Text Document

11 IBM Rational Software Conference 2009 iEA16 Scope Project Solution. Assess current architecture for gaps or redundancies relevant to solution. Define future solution architecture (linked to requirements). Write (or generate from architecture) requirements to address solution (linked to architecture). Deliver project solution. Update current EA to reflect solution capabilities. Solution Steps 11

12 IBM Rational Software Conference 2009 iEA16 Define Scope of Project Solution. 12 Discuss with stakeholders and capture scope and purpose for solution. Purpose Scope These two parameters provide initial frame for questions that architecture can answer.

13 IBM Rational Software Conference 2009 iEA16 Assess Current Architecture for Gaps or Redundancies 13 Process Model Variant 1 (as-is) Process Model Variant 2 (to-be)

14 IBM Rational Software Conference 2009 iEA16 Define Future Architecture to Address Solution 14 Use System Architect (SA) tool to graphically model architecture.

15 IBM Rational Software Conference 2009 iEA16 Generate Requirements from Architecture 15

16 IBM Rational Software Conference 2009 iEA16 Requirements Structure (architecture) 16 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 Tests

17 IBM Rational Software Conference 2009 iEA16 Requirements Coupled with Architecture 17 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 Tests

18 IBM Rational Software Conference 2009 iEA16 Deliver Project Solution 18 Finished products generated in a variety of formats can be accomplished with features in System Architect or DOORs: HTML output Word Document Detailed graphic diagrams Database DDL SAXT provides real-time web-based access SA Publisher provides: Dashboard views Pie Charts, Bar Charts, Heat Maps As-Is <> To-Be Comparisons

19 IBM Rational Software Conference 2009 iEA16 Update Current Architecture to Reflect Solution 19

20 IBM Rational Software Conference 2009 iEA16 Results Actionable, executable architecture that is tied to requirements that enable informed decisions supported by real time data. 20 Requirements Architecture

21 IBM Rational Software Conference 2009 iEA16 Results Informed decisions supported by data are crucial for the success of any enterprise of the future. 21 Data

22 IBM Rational Software Conference 2009 iEA16 22

23 IBM Rational Software Conference 2009 iEA16 23 © Copyright IBM Corporation 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 IBMs 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.


Download ppt "© 2009 IBM Corporation iEA16 Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations."

Similar presentations


Ads by Google