© 2013 IBM Corporation
DOORS Hints and Tips: Linking and views
Hazel Woodcock, IBM Rational
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
Why use a link schema?
 Control
– Only allow va...
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
What does a link schema look like?
Stakeholder
R...
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
What should / shouldn’t I do?
 Draw out expecte...
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
What does a link schema look like?
Link modules ...
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
What can / can’t I do?
 Enforce allowable relat...
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
Traceability - using the power of the link schem...
© 2013 IBM Corporation
Enabling Product and Service Innovation | Rational
Saving analysis views
Select pre-saved views fro...
Upcoming SlideShare
Loading in …5
×

Doors hints and tips schema

1,110 views
988 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,110
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
23
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Doors hints and tips schema

  1. 1. © 2013 IBM Corporation DOORS Hints and Tips: Linking and views Hazel Woodcock, IBM Rational
  2. 2. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational Why use a link schema?  Control – Only allow valid relationships – Supports organizational definitions of good practice  Analysis – Improve analysis opportunities  Consistency – Use the same schema across projects for consistency – More efficient transfers of staff between projects – Easier cross project reporting – Support organizational processes
  3. 3. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational What does a link schema look like? Stakeholder Requirements System Requirements Subsystem Requirements Subsystem Requirements User Acceptance Tests Systems Tests Subsystem Tests Design Rationale Risks Subsystem Tests Subsystem Tests Subsystem Requirements satisfies satisfies tests tests tests identified from mitigates contributes to is justified by Stakeholder Requirements tests Formal Module Linkset
  4. 4. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational What should / shouldn’t I do?  Draw out expected information types and the relationships between them – Part of an information architecture workshop  Plan links from logically later information to logically earlier information – Links are created when the later information goes in – Access rights within DOORS make this a better option – Use requirement ‘satisfies’ higher level requirement, not requirement ‘is satisfied by’ lower level requirement. Links can be analysed in either direction later.  Don’t have round trip links – If you have a link from module A to module B, there should not be a link from module B to module A  Don’t link within a module – Links within a module usually indicate a sub-optimal partitioning of formal modules  Don’t use the default DOORS Links module – Describe the relationship between the two linked pieces of data (requirement satisfies requirement) and use the verb as the name of the link module.       Stakeholder Requirements System Requirements Subsystem Requirements Subsystem Requirements User Acceptance Tests Systems Tests Subsystem Tests Design Rationale Risks Subsystem Tests Subsystem Tests Subsystem Requirements satisfies satisfies tests tests tests identified from mitigates contributes to is justified by Stakeholder Requirements System Requirements Subsystem Requirements Subsystem Requirements User Acceptance Tests Systems Tests Subsystem Tests Design Rationale Risks Subsystem Tests Subsystem Tests Subsystem Requirements satisfies satisfies tests tests tests identified from mitigates contributes to is justified by
  5. 5. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational What does a link schema look like? Link modules in an Admin folder for the projec DOORS Links module deleted so that ad-hoc links cannot be created Permitted link relationships defined Ad-hoc linking disallowed
  6. 6. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational What can / can’t I do?  Enforce allowable relationships – Link direction and module to module relationships defined  Enforce individual link validity – Individual links still have to be checked for correctness  Create project templates – Cross project consistency  Analyse a single link type (for example, satisfies, or tests) to report on coverage – Easily check for test coverage, look at impact analysis, check for gold plating etc.  Show analysis in a column – Show selected information about the other end of a link in a column  Save an analysis view – Save the view and make it visible to the whole team      
  7. 7. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational Traceability - using the power of the link schema Stakeholder Requirements System Requirements Subsystem Requirements Subsystem Requirements User Acceptance Tests Systems Tests Subsystem Tests Design Rationale Risks Subsystem Tests Subsystem Tests Subsystem Requirements satisfies satisfies tests tests tests identified from mitigates contributes to is justified by Requirements coverage analysis From Stakeholder requirements, analyse all incoming links through ‘satisfies’ link module, for multiple levels.
  8. 8. © 2013 IBM Corporation Enabling Product and Service Innovation | Rational Saving analysis views Select pre-saved views from list Column displays selected information from far end of link View may also include filters, sort, selected attributes, Layout DXL.

×