Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations...
Objective <ul><li>Align business requirements from strategy to front line process execution </li></ul><ul><li>Combine use ...
Session Benefits <ul><li>Users attending session can take away an understanding of: </li></ul><ul><ul><li>Enabling an ‘act...
Scenario <ul><li>Managers make many decisions - from simple to complex. </li></ul><ul><li>Most business decisions have dat...
Scenario <ul><li>EA, in today's world, cannot persist simply  as artifacts supporting compliance… </li></ul><ul><li>Not en...
Problem <ul><li>Little attention is paid to  human  usability (or reuse) of the finished product. </li></ul><ul><li>Requir...
Problem ( other side ) <ul><li>Most people are  graphical  learners – comprehending through pictures or models. </li></ul>
Problem ( other side ) <ul><li>Most requirements are  textual;  detailed and data rich. </li></ul>
Solution <ul><li>Enable rapid assessment of gaps in enterprise through architecture ensuring requirements meet relevant ne...
Architecture Driven Requirements Process Scope Project End Start Assess against ‘ current’  architecture Architecture View...
<ul><li>Scope Project Solution. </li></ul><ul><li>Assess  current  architecture for gaps or redundancies relevant to solut...
   Define Scope of Project Solution. <ul><li>Discuss with stakeholders and capture  scope  and  purpose   for solution. <...
   Assess ‘ Current’  Architecture for Gaps or Redundancies Process Model Variant 1 (as-is) Process Model Variant 2 (to-be)
   Define ‘Future’ Architecture to Address Solution  <ul><li>Use System Architect (SA) tool to graphically model architec...
   Generate Requirements from Architecture
Requirements Structure (architecture) DOORs Internal Customer Functional System Functional Software Specification Software...
Requirements Coupled with Architecture System Architect OV-1 Concept Graphic OV-5 Operational Activity SV-4 System Functio...
   Deliver Project Solution  <ul><li>Finished products generated in a variety of formats can be accomplished with feature...
   Update ‘Current’ Architecture to Reflect Solution
Results <ul><li>Actionable, executable  architecture  that is  tied  to  requirements  that enable informed decisions supp...
Results <ul><li>Informed  decisions  supported by  data  are crucial for the success of any  enterprise of the future.  </...
© Copyright IBM Corporation 2009.  All rights reserved.  The information contained in these materials is provided for info...
Upcoming SlideShare
Loading in...5
×

Defining and Aligning Requirements using System Architect and DOORS

1,182

Published on

Working with EA (graphical) tools enabled with requirements (textual) tools, 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

1 Comment
1 Like
Statistics
Notes
  • Very good points made here with an interesting perspective. I am in complete agreement with the concept of using enterprise architecture (graphic models) to define the functional and system requirements as this adds much needed clarity to the usually overly documented requirements.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
1,182
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide
  • Author Notes: This is the standard session track template for IBM Rational Software Conference 2009 Additional IBM presentation resource links available on W3: Rational Core Messaging Slides https://w3-03.ibm.com/software/marketing/markwh01.nsf/AllObjects/rt_mtb_cms/$file/RationalBrand_CoreSlides.ppt?OpenElement Rational Image Library https://w3-03.ibm.com/software/marketing/markwh01.nsf/AllObjects/rt_rsil/$file/Rational_Image+Library.ppt?OpenElement PowerPoint Best Practices Presentation https://w3-03.ibm.com/software/marketing/markwh01.nsf/AllObjects/rt_mtb_rpbp/$file/PowerPoint_BestPractices.ppt?OpenElement
  • Defining and Aligning Requirements using System Architect and DOORS

    1. 1. Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations [email_address] iEA16 © 2009 IBM Corporation
    2. 2. Objective <ul><li>Align business requirements from strategy to front line process execution </li></ul><ul><li>Combine use of Enterprise Architecture & Requirements tools. </li></ul>
    3. 3. Session Benefits <ul><li>Users attending session can take away an understanding of: </li></ul><ul><ul><li>Enabling an ‘actionable’ enterprise architecture </li></ul></ul><ul><ul><li>Value of linking enterprise architecture to requirements </li></ul></ul><ul><ul><li>Efficiencies of generating requirements from enterprise architecture </li></ul></ul><ul><ul><li>Process for managing requirements through enterprise architecture </li></ul></ul>
    4. 4. Scenario <ul><li>Managers make many decisions - from simple to complex. </li></ul><ul><li>Most business decisions have data dependencies captured as static snapshots in </li></ul><ul><ul><li>enterprise architecture products or </li></ul></ul><ul><ul><li>requirements documentation . </li></ul></ul><ul><li>Decisions are made without considering effects on enterprise touch points – un informed. </li></ul>
    5. 5. Scenario <ul><li>EA, in today's world, cannot persist simply as artifacts supporting compliance… </li></ul><ul><li>Not enough money to support both </li></ul><ul><ul><li>robust data management efforts </li></ul></ul><ul><ul><li>comprehensive EA efforts </li></ul></ul><ul><li>Go beyond static artifacts - an enterprise architecture that delivers decisions based on relevant data . </li></ul>
    6. 6. Problem <ul><li>Little attention is paid to human usability (or reuse) of the finished product. </li></ul><ul><li>Requirements ‘ documentation ’ is produced and the solution delivered. </li></ul><ul><li>Content is ‘shelved’ and neither visible nor usable to most people. </li></ul><ul><li>Most requirements gathering efforts center on generating large quantities of documentation to support ill-defined business needs. </li></ul>
    7. 7. Problem ( other side ) <ul><li>Most people are graphical learners – comprehending through pictures or models. </li></ul>
    8. 8. Problem ( other side ) <ul><li>Most requirements are textual; detailed and data rich. </li></ul>
    9. 9. Solution <ul><li>Enable rapid assessment of gaps in enterprise through architecture ensuring requirements meet relevant needs. </li></ul><ul><li>Use enterprise architecture products ( graphics ) to clearly depict desired solution. </li></ul><ul><li>Link or generate requirements from an enterprise-wide accessible architecture based on real time information. </li></ul>Link Requirements ( textual ) to Enterprise Architecture ( graphical )
    10. 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
    11. 11. <ul><li>Scope Project Solution. </li></ul><ul><li>Assess current architecture for gaps or redundancies relevant to solution. </li></ul><ul><li>Define future solution architecture (linked to requirements). </li></ul><ul><li>Write (or generate from architecture) requirements to address solution (linked to architecture). </li></ul><ul><li>Deliver project solution. </li></ul><ul><li>Update ‘ current’ EA to reflect solution capabilities. </li></ul>Solution Steps
    12. 12.  Define Scope of Project Solution. <ul><li>Discuss with stakeholders and capture scope and purpose for solution. </li></ul>Scope These two parameters provide initial “ frame ” for questions that architecture can answer. Purpose
    13. 13.  Assess ‘ Current’ Architecture for Gaps or Redundancies Process Model Variant 1 (as-is) Process Model Variant 2 (to-be)
    14. 14.  Define ‘Future’ Architecture to Address Solution <ul><li>Use System Architect (SA) tool to graphically model architecture. </li></ul>
    15. 15.  Generate Requirements from Architecture
    16. 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. 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
    18. 18.  Deliver Project Solution <ul><li>Finished products generated in a variety of formats can be accomplished with features in System Architect or DOORs: </li></ul><ul><ul><li>HTML output </li></ul></ul><ul><ul><li>Word Document </li></ul></ul><ul><ul><li>Detailed graphic diagrams </li></ul></ul><ul><ul><li>Database DDL </li></ul></ul><ul><li>SAXT provides real-time web-based access </li></ul><ul><li>SA Publisher provides: </li></ul><ul><ul><li>Dashboard views </li></ul></ul><ul><ul><li>Pie Charts, Bar Charts, “Heat Maps” </li></ul></ul><ul><ul><li>As-Is <> To-Be Comparisons </li></ul></ul>
    19. 19.  Update ‘Current’ Architecture to Reflect Solution
    20. 20. Results <ul><li>Actionable, executable architecture that is tied to requirements that enable informed decisions supported by real time data. </li></ul>Requirements Architecture
    21. 21. Results <ul><li>Informed decisions supported by data are crucial for the success of any enterprise of the future. </li></ul>Data
    22. 22.
    23. 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.
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×