2. IBM Rational Software Conference 2009
AGENDA
Overview of DOORS
Project Architecture in DOORS
Database schema
Module framework
Setting linking schema
Application of access rights
Importing legacy data from Word
Baselines/Baseline sets
Summary
Demo
Questions
2
4. IBM Rational Software Conference 2009
What is DOORS?
Rational DOORS is the market and technology leader for
Requirements Management
A requirements management tool with:
Multi-user document access
Extensive access controls
Change control & tracking
Requirement linking
Filtering & sorting of data
Traceability & impact analysis support
7. IBM Rational Software Conference 2009
DOORS Item Entity Relationship
Items Users* Access Rights
• Project • Individuals • Read
• Folder • Groups • Create
have with
• Module • Everyone • Modify
• Object • Delete
• Admin
are of
Powers
User Types *
• Create Project
• Standard • Archive Data
• Project Manager
can have • Partition Data
• Database Manager • Create Groups
• Custom • Create Users
• Manage Database
8. IBM Rational Software Conference 2009
DOORS Data Exchange Options
Other options include
* Partition/Rejoin, RIF
* Archive/Restore
* DXL based data Exchange Tools
9. IBM Rational Software Conference 2009
DOORS Integrations - Current
Focal Point
Rational ClearCase MS Team
& ClearQuest Foundation
Server
Change
System Architect
Eclipse DOORS
TAU
Rhapsody
Publishing Engine
Rational Rose
Rational Quality Manager
Rational Software
Development Platform
11. IBM Rational Software Conference 2009
Database Schema
How to organize data?
When use projects and folders?
Naming convention?
12. IBM Rational Software Conference 2009
Database Schema contd.
Example of Project Template
13. IBM Rational Software Conference 2009
Module framework
Template Example
Create a new module or use an
archetype
Using archetypes enables re-use
of the consistent schema and the
best practices in the organization.
16. IBM Rational Software Conference 2009
Shareable edit
Setup for sharing the
module at levels 1, 2 or 3.
Open the module in
exclusive edit mode and
save on a periodic basis
20. IBM Rational Software Conference 2009
Tables
Use OLE for tables if:
The entire table represents a single requirement
The table does not contain requirements, and the data can be easily displayed in an
OLE object
Convert the table to DOORS text objects if:
Entire rows or columns represent single requirements
You want to be able to display and modify attribute values in a separate column for
each requirement in the table
21. IBM Rational Software Conference 2009
Setting linking schema
Direction and Type of Links
Use of DOORS Links
Link Enforcement
22. IBM Rational Software Conference 2009
Direction and Type of Links
Direction of links
Architecture System Stakeholder
design requirements requirements
Type of Links
Satisfies links
Verification links
Recursive links
Confirms to links
23. IBM Rational Software Conference 2009
Use of DOORS Links
“DOORS Links” is the default
24. IBM Rational Software Conference 2009
Link Enforcement
Only allow outgoing links as specified in the above list
Ensure every rule has a defined linkset
25. IBM Rational Software Conference 2009
Access Rights Application
Database
Items Folder or Project
Sub-items Folder or Project or Module
Views
Attribute Objects Attribute
Definitions Types
Attribute
Values
26. IBM Rational Software Conference 2009
Access Control Strategies
Use strict controls at top levels
Prevent accidental data moves and copies
Use propagation to allow easier access
Each project/level can have separate access
Use groups rather than named users
Use groups for common permissions
Set project access to “None”
Explicitly allocate rights through groups
No one (except the Admin Groups) should have access to anything as a
default.
Users who are both Admins and Engineers should have two accounts to keep the work
done separate.
27. IBM Rational Software Conference 2009
Access Control Strategies - Example
Users: Project A
Project A
User1 Objects
User2 Module
User3
User4
User5
DB
User6 Project B
Project B
Access: Objects
Everyone: R
Module
Access :
Project B Group:RC Access :
Everyone Else: None Project B Group:RMDC
Propagate with C: MD Everyone Else: None
Group Project A Group Project B Group
User1 User2
Definitions User2 User4
User3 User5
User6
28. IBM Rational Software Conference 2009
Baselines
changes changes changes
current 0.0 current current 1.0 current 1.1
0.1
Baseline 0.1 Baseline 1.0 Baseline 1.1
Module
history Time
Some basic guidelines :
Minor baseline after initial import, after reformat , prior to purge of deleted objects
Major baseline after Review, consensus, Build Definition.
29. IBM Rational Software Conference 2009
Baseline sets
Stakeholder
requirements
System
requirements Test Cases
Baseline 1.1 Baseline 2.1 Baseline 1.3
Stakeholder System
Test Cases Baseline Set
Requirements Requirements
Release Candidate 1
35. IBM Rational Software Conference 2009
Benefits
Re-usability
Performance optimization
Traceability/Impact Analysis
Effective word imports
Effective Management of Access Controls
36. IBM Rational Software Conference 2009
What RM Best Practice Means to Stakeholders
Engineers Middle Managers Executives
Customer
Demonstrate Satisfaction/
Regulatory / Stakeholder
Contractual Needs
Manage Scope Compliance
Improvement in Requirements Quality
& Impact of Conform with
Change Standards
(CMMI. SPICE,
Handle ISO)
Complexity Deliver to Cost
& Schedule
Reqts
Constraints
Distribution
Multi-level
Visible
Re-use Traceability
between Reqts
Role-Based
Access
Visible Context
Tailorable RM
Scalable
Process
Common
Repository
Audit Trail
Increased use of Requirements Management Good Practices
37. IBM Rational Software Conference 2009
Acknowledgement
Ian Zimmermann, IBM Software Group
Bob Parro, River North Solutions