DOORS RIF Capability

Uploaded on


More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • URD – User requirements document SOW – statement of work SRD – system requirements document
  • Optional IBM Rational “Questions” Breaker Slide
  • Mandatory IBM Rational standard closing slide to be included in all external presentations. Learn more links: IBM Rational software: Rational launch announcements: Rational Software Delivery Platform: Accelerate change and delivery: Deliver enduring quality: Enable enterprise modernization: Ensure Web site security and compliance: Improve project success: Manage architecture: Manage evolving requirements: Small and midsized business: Targeted solutions: Rational trial downloads: Leading Innovation Web site: developerWorks Rational: IBM Rational TV: IBM Rational Business Partners: IBM Rational Case Studies:


  • 1. DOORS RIF Capability Manageware
  • 2. A trend leading to complexity for data collaboration
    • URD, SOW, SRD…
    • Simplicity of requirement usage, format, traceability
    • Simple data management practices (Doc. Management)
    • Complex requirements using structure and relationships
    • Database management for requirements alignment
    • Tool alignment essential for data sharing
    Before Today 1…n Req 8.2 Req 3.2 Req 1.9 Req 1.2
  • 3. Today's DOORS Data Exchange Options
    • One of DOORS strengths is its communication of data
      • Principal focus on import and export
      • Or data exchange, limited to two databases, master and supplier
    • Existing interfaces include
      • Word Export/Import
      • Partition/Rejoin
      • Archive/Restore
      • CSV/TSV round trip
      • DXL based data Exchange Tools
        • Some internal to IBM
        • Others produced by partners
        • Several produced by customers
    There is a need to support more complex exchange scenarios
  • 4.
    • RIF (Requirements Interchange Format) from HIS (Hersteller-Initiative-Software)
      • Automotive industry initiative
    • Transition to Prostep iViP
      • Targeted to internationalize RIF
      • Not just focussed on Automotive
    • IBM to support RIF
      • Requirement to support open interfaces
      • Preference to support standards rather than IBM bespoke
      • Wish to harmonize data transfer in DOORS
        • Partition/rejoin, CSV roundtrip, more?
    An introduction to RIF – HIS Group and RIF
  • 5. An introduction to RIF – XML and RIF
    • eXtensible Markup Language (XML)
      • general purpose markup language
    • Facilitate the sharing of structured data across information systems
      • Data, Hierarchy, Tables, OLE, Relationships
    • Used to encode documents and serialize data
    • Defined XML Schema
    • Word, CSV, PDF ( lossless ) exchange replacement
    • Exchange model for structured requirements
    So… what is RIF? Requirements Interchange Format
  • 6. An introduction to RIF - Structured Data Possibilities
    • Standardised information schema for cross tool compatibility
    • Meta-model extraction and replication
      • Hierarchy structures
      • Link structures
    • Rich Text Support
    • Direct DOORS benefits
    • 3 rd party exchange possibilities
      • Schema Interpreters
      • Graphical Schema Representation
      • Document Generation
    Req 8.2 Req 3.2 Req 1.9 Req 1.2 1 2 3 4 1 2 3 4
  • 7. DOORS 9.2 introduces native support for RIF
    • Built-in component of DOORS
      • Support for
        • RIF Export / Import
        • Multiple modules
        • Links
        • Delegated Data Control
          • Control modification of requirements
          • Control modification of attributes
    • Schedule
      • DOORS 9.2, available June 2 nd 2009, will support RIF export/import
      • A subsequent patch, planned for September 2009, will offer the rest of the functionality overviewed in this presentation
  • 8. DOORS 9.2 introduces native support for RIF
    • Fundamental use case to support supplier relationships
    • Step 1:
      • Distribute data to supplier database(s)
    • Step 2:
      • Concurrent working on data
    • Step 3:
      • Managed merge of data
      • With resolution for overlapping data
    Initial database Mod. V1 First supplier Mod. V1 Mod. V1 Mod. V1.1a .1 Mod. V1 Second supplier Mod. V1.1b 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
  • 9. What would we like to do with RIF?
    • RIF ensures requirements can be distributed with an expectation to bring updates back to the original location
      • Support for one or more modules, each using varying levels of control
      • Support for one or more suppliers
        • Requirements might be distributed across several databases
    • Level of data control defined by “delegated data control ( DDC )”
      • Single direction export or import – No DDC
      • Publication of requirements – DDC Read only
      • Outsource requirements production – DDC Full module
      • Distributed requirements feedback – DDC by attribute
      • Distributed requirements production – DDC by Object
  • 10. Let’s take an example
    • Example RIF packages could include
      • Export
        • Client shares vision data with a colleague
        • No DDC – Export Vision document with no expectation to receive it back
      • Supplier1
        • Client exchanges information with supplier
        • DDC Read Only – Supplier reads Vision document
        • DDC Full Module – Supplier develops Stakeholder and system requirements Supplier creates links back to the Vision document
      • Sub-supplier
        • Supplier exchanges information with sub-suppliers
        • DDC By Attribute – Sub-suppliers give feedback on stakeholder requirements
        • DDC By Object – Sub-suppliers develop sections of the System requirements
    Satisfies Satisfies Vision Stakeholder System
  • 11. Configuration of a RIF package
    • Configured through properties of a project
      • 9.2 limited to modules in a single folder
      • Patch expected to support modules from anywhere in the selected project
      • Note: A RIF package will always be exported as a single XML file
    • Scope of data defined by a configuration view
      • View defines requirements and attributes
  • 12. Identification of scope
    • Scope defined by configuration views
      • Requirements, controlled by filter
      • Attributes, controlled by columns in view
      • Types – restricted to data in view
      • Views – all public views transferred
    • Scope of links controlled by
      • Inclusion of link module in the package
      • Scope of source data
      • Scope of target data
  • 13. Single direction export or import – No DDC
    • No DDC indicates simple export of data
    • Don’t expect data to be returned
      • Unable to merge data if it is returned
    • Multiple export / import possible
      • Possibility to re-export updated data into a target database
    • Scope of data defined by a configuration view
      • View defines requirements and attributes
  • 14. Publication of requirements – DDC Read only
    • DDC Read Only indicates data is not expected to change in the exported data
    • Subsequent patch to support module baselines, pre-defined as DDC Read Only
    • Source database
      • Can continue to modify module
    • Target database
      • Imported data imported read-only
    • Import back to source
      • No merge required, data is read-only
      • Might be part of a returned RIF package to facilitate links
  • 15. Outsource requirements production – DDC Full module
    • DDC Full Module indicates target database has full control over the requirements
    • Source database
      • Once data is exported module becomes fully read-only, no changes possible
    • Target database
      • Imported module can be fully modified
      • Create, modify, move requirements
      • Creation of links only controlled where the link module is included in the RIF package
    • Import back to source
      • Imported module would effectively replace original module
      • All updates made in the target reflected back in the source
      • Original object IDs preserved
      • New object IDs will diverge between databases
        • To interact with other RM solutions, specific “RIF IDs” used to control data merge
  • 16. Distributed requirements feedback – DDC by attribute
    • DDC by attribute indicates that some attributes are expected to be modified
    • Attributes to be modified controlled by an additional module view
    • Source module
      • Once data is exported configured attributes become read-only
    • Target module
      • Configured attribute values can be modified
      • All other attributes read-only
    • Import back to source
      • Configured attribute imported back and merges into original module
  • 17. Distributed requirements production – DDC by Object
    • DDC by object indicates that some object hierarchies are expected to be modified
    • Object selection controlled by an additional module view
    • Source module
      • Once data is exported configured objects become read-only
    • Target module
      • Configured objects can be modified
        • Modify top level object
        • Create, delete or move children object
      • All other object hierarchies read-only
    • Import back to source
      • Objects merged back into original module
  • 18. Two stage import and merge process
    • Data imported back to a intermediary folder prior to merge
    • Merge takes imported data and merge applicable data back to the original location
    • Fully automated import then merge controlled by import
    • Hands-free control over RIF import/export possible through DXL automation
  • 19. RIF Locks
    • Exported data governed by Delegated Data Control will be locked
      • Locks only created after data is exported, not when the RIF package definition is created
    • Locks govern access control over
      • Modules – DDC Full module
      • Attributes – DDC by attribute
      • Object hierarchies – DDC by Object
      • No lock required – No DDC
      • No lock required – DDC Read only
    • Lock management
      • Possible for specific users to manually manipulate RIF locks
      • Merge capability revoked where a RIF lock has been removed
        • Not reversible
  • 20. Access controls
    • Based on DOORS partition/rejoin
      • Definition of RIF packages controlled by “Partition Data” power assigned to users
    • RIF package definitions need to be signed with both the database and project
      • Not possibly to copy RIF package definitions where copying a project
      • RIF package definitions not possible in module archive/restore
    • Top level 1 objects are always controlled with the first database that exported data
      • Possible to modify level 1 objects in target databases but not delete or move
    • Access policies can be passed from target databases to other target databases
      • Must have been granted write access over data in order to pass this access control on
  • 21. Use of a different RM tool as the target database
    • There is no assumption that a target database is DOORS
    • Where DOORS is not the target
      • View definitions will be ignored in the target location
      • No guarantees target tool fully supports access policies defined by RIF
      • Control over data modification also managed by DOORS on the return of any data
        • Data defined as read-only when exported from DOORS
          • Should not be modified in target tool
          • Updates which break the rules can not be imported/merged back into DOORS
      • Where DOORS is the target tool
        • If RIF locks are removed, data changes can not be brought back to the source database
  • 22. Points to note
    • Views
      • All views with default access of at lest READ will be exported
      • Attribute DXL exported as Text
      • Layout DXL only supported after the subsequent patch
      • Filters within a view might behave differently in different databases where references to system attributes are used
        • absolute numbers, created-by etc.
    • History
      • Can be included in exported data if displayed in a DXL column
      • History of imported data reflects merge operation in core history records
  • 23. Contacts Contacts Solution Collateral and more Enablement Questions? Send a message to the “Ask Telelogic” Global mail ID: [email_address] Sales Contacts Mike Lundblad – Rational Worldwide Sales Executive Requirements & Quality Management Sales and Technical Enablement Judy Murphy – WW Sales & Tech Empowerment Robin Bater – Rational Definition & Management CoP Architect Product Management Dwayne Dreakford – Requisite/Pro/Rational Requirements Composer Product Manager Albert Ho - Rational Requirements Composer Product Manager Richard Watson – DOORS Product Manager Brian Massey , Product Manager, RQM Hazel Woodcock – QM Sales enablement Jared Pulham – DOORS Web Access Product Manager Keith Collyer –DOORS Requirements Lifecycle Management/Quality Management Market engineer Andrew Foster -DOORS Integrations Architect/Market Engineer
    • Requirements Definition and Management
      • RDM Sales Kit
      • Sales Acceleration Play – Pricing promotions
    • DOORS Collateral for Sellers
      • DOORS Sales Kit
      • 5 minute Demo
      • Sales Acceleration Play
    • DOORS Collateral for customers
      • DOORS web page
      • DOORS 5 minute on-line demo
      • Webcast: Aligning Business and IT through Connected Requirements
    • Rational Requirements Composer Collateral for customers
      • Webcasts
      • Datasheet
      • Whitepaper: Storyboarding in IBM Rational Requirements Management
      • Try RRC
    • Rational Requirements Composer Collateral for sellers
      • RRC Sales Kit
      • Customer Sales Presentation
      • Sales Acceleration Play
    • RequisitePro 7.1
      • ReqPro Sales Kit
      • Datasheet
  • 24.
  • 25. © 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.