Tag: data-model
-
How to handle Standards in DOORS Next Generation
This is not a new question. We have been struggling with managing traceability to standards for as long as we have had the concept of traceability to standards. In the DOORS Classic World we had a few options, and we still have those options with DOORS Next Generation, but we also have a couple of…
-
Managing test data in DOORS Next Generation
The topic of test management comes up every now and again. Some people might remember the Test Tracking Toolkit from DOORS Classic, some might even have been using it recently. We also have a decent test management tool in Rational Quality Manager (RQM). I have been thinking about the options for a simplified way of…
-
Documenting Interfaces
Documenting interfaces has always been a challenge. We put the interface requirements in a separate document and give that as a part of the documentation to the groups designing on both sides of the interface. Now I have a single document with all aspects of the interface neatly covered, but when I look at my…
-
Documenting a DOORS Database Schema
Following on from the Information Architecture Workshop series, I want to show an example of how some of that information should be documented. A comprehensive document should be made available, but also a summary document for quick reference and guidance. Some years ago we produced a quick reference document for a generic schema and process,…
-
DOORS Next Artifact Types
One of the really nice features of DOORS Next is that artifact* types are defined for the project, and artifacts used in a module can be of various types.
-
DOORS Classic vs DOORS Next
I was at UK IBM Innovate last week and one very interesting presentation was from Jeremy Dick of Integrate. Jeremy highlighted some of the key differences between DOORS Classic and DOORS Next Generation. I will draw from that discussion here, but also add my own commentary.