Dec 082015

TornadoThis 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 new options. I am going to look at this fresh and go over the pros and cons for the various methods in DOORS Next Generation.

I will look at the following methods:

  1. Attributes
  2. External link
  3. Separate module and link
  4. Separate module and reuse
  5. Separate module, reuse and link
  6. Glossary terms
  7. Glossary and link

Continue reading »

Dec 032015

Rational Quality Manager has a huge number of options. Paring that back to make a simpler tool is possible, and I am going to look here at some of the configuration options.

rqmsettingsmenuFrom the Settings menu at the top right, the gear wheel, I will go through some of the important parts of the Project Properties and the Artifact Templates, and Manage this Project Area.

A thorough look at all the items accessible from here will give you many hours of entertainment and wondering at exactly what you have done.  Please play with these on a sandbox project before trying them in production.
Continue reading »

Sep 092015

Now that the DOORS Next Generation V6.0 has been out for a little while, I thought I should share some of my thoughts on how and why to use configurations.
I am pleased to see that from an end user perspective, this is really easy to use – you get a work item linking to a change set and you go do your work there, no need to understand the big picture.
There are two main reasons for wanting the CM capability, one is variant management and the other is version management. Variant management is the more complex of the two, so consider for now just the version management. This is where you have two (or more) versions of the requirements that are live at the same time. Unless you are working in a pure waterfall then you are very likely to want this. A version for the current iteration of the work, and a version for the next iteration of the work. We need to keep them separate because the design, test and other project documentation can be very different as the project develops.Sketch93171618 Continue reading »

Jun 152015

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 managing small amounts of test data all within DOORS Next Generation (DNG).

Because of the underlying differences in the database architecture, just copying the DOORS Classic model is not ideal, so what I have done is to create a model that will allow for relatively painless transition to RQM at a later date, and one which takes advantage of some of the DNG features.

I created a data model which is shown here. I will work through that and describe some of the process that needs to go around it. The details follow on from here.


Continue reading »

Oct 242014

connectorSoloDocumenting 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 system requirements, I am missing some aspects that are hidden away in various interface specifications. It would be nice to have all my environmental requirements in one place, all my physical requirements in one place and so on. For complicated interfaces, perhaps a separate document is a good idea, but for simple interfaces, I think there is a better way. Continue reading »

Jul 232014
A basic CM Flow in DOORS Next Generation

A little while ago, I posted about Real Configuration Management for Requirements, but I didn’t go in to any detail about HOW it should, or could be used.  Requirements engineers/managers are not typically working with configuration management at this level on a daily basis, so I have set out a very basic flow here. First […]

Jun 272014
Real Configuration Management for Requirements

DOORS Next Generation is getting Configuration Management capabilities. This is a huge step for DOORS NG, a requirements management tool. The CM capability is similar to what you might expect for source control, with similar language, like ‘streams’, ‘deliver’, ‘workspace’, and others. I think that we will find that many requirements management users (or Business […]