​(In progress)


Requirements Traceback Structure


The link to the test DOORS-NG server is: https://cdv-doors-d.fnal.gov:9444/jts

12/27/17 Meet with Nandhini


Unde​r LBNF Project Template I've imported two spreadsheets: Glo sci objectives and Glo sci requirements. Have been documenting this (see link above). Plan to create traceback links next.

Plan for having thi​​ngs ready by March review:

Our side

  • Create test plan
  • Create go-live plan
  • Fix up all spreadsheets for import (fix column names, etc.)
  • Import most or all into test system and create links
  • Determine reporting needs and create needed reports (html, if possible)
  • Create instructions for updating requirements, producing reports, etc..​
  • Import all requirements into production (with traceback links)​​

Pawel's side

  • Make sure production instance works
  • Continue to respond to our questions!
  • Possibly copy requirements from test to production (TBD)

12/5 Prep for 12/6 session


  1. Understand NG terminology (see at right)
  2. Understand landscape (screens, labels, icons...)
  3. Verify template: correct attributes and correct choice lists?
  4. Learn to create, edit and navigate between:
    • Module
    • Requirement
    • Trace link
  5. Test various attributes - text entry vs choice list, rich text
  6. Learn to upload a CSV file into a module

12/1 Meet with Pawel

​No matter what format of artifact you want to create, you get the same create popup - it just may have different defaults set.

No prefix for id, but use tags. (not type)

Pawel and I went through the sample spreadsheet so he knows how to set up the attributes (=columns).  He plans to do that today or soon. Then I will "play" more.


  • Importing CSV so far seems to only work for up to 4 columns. PG will check into this.
  • Interface not quite as intuitive as old DOORs, PG will see if he can simplify it using permissions.

11/30 Going through video 'create a module and add an artifact'

(I can't get sound) The project they use (JKE) has more and different things in the blue ribbon menu than mine does. It has:

Project Dashboard - Artifacts - Collections - Modules - Reports

Mine has

Project Dashboard - Artifacts - Reviews - Reports

In video, they create a module: click "Modules" (in blue ribbon), it has "Create Module" option. Then "Create Artifact" popup lets  you pick an artifact type (they pick 'car module'), and artifact format is Module.

The Artifact type (field in popup) can be customized from "project properties artifact types" tab. It can have "preferred module content" set for heading and/or normal rows. Also "preferred link types". I wonder if "preferred" means "default" or "this is all that's available to this module"? Oh, maybe it just puts these types in a menu atop left column...

Headings get a "numbered row"; wonder if normal rows do


Back to Anne Test 2:

I go to Artifacts page. Click blue "Create" button. There is no "module" option so I choose "requirement specification". It comes up as format Module. I open it, give it a value, click Done, then go back to "Artifacts" page. It shows up as a folder, but when I select it, I see "No modules match the selected folder or filter." In fact I see that no matter which folder I select.

So, NO, a requirements specification is NOT a module.

​​(Earlier in Nov) To create a project:

From Dashboard, Start at gear symbol, choose Create Lifecycle Project

Choose default "Analyst" template

Process Project Template: choose Traditional

Hit Save (DOORS NG does some saving, then you have a page where you can click on your new project)

​​Click on it and you get to Overview.

I'm leaving all the defaults in terms of sharing/members/administrators etc. for now. I have Administrator and Configuration Administrator.

Click Configuration Management, in left sidebar. No, it's not clear what it does.

Go back to dashboard (I think). Somehow get to Artifacts page and hit Create. Let's try to create a heading.

DOORS​​ NG Glossary by Anne

DOORS NG Glossary​


Artifact is a general term for an object in a repository. You can manage artifacts in projects and folders, or you can use tags to filter groups of artifacts for a specific purpose. Artifacts can be of various types, which have customizable attributes and data types. (There is no default artifact type called "requirement," but sample project templates have defined some artifact types.)

Attribute: For our purposes it is a column heading; can take data of different forms, e.g., text, choice list, auto-pop, etc.

Base artifact: ??

Collection: A group of artifacts with no particular order or hierarchy. A collection is a set artifacts that you create for a specific purpose. (Could be an ad-hoc purpose.)

Format: Format differentiates one kind of artifact from another, e.g., a module from a requirement.

Module: A structured artifact that is composed of other artifacts. Structure is created by modifying the order and hierarchy of the artifacts. You can e.g., create an empty module and add artifacts to it, or you can create a module by importing a Microsoft Word document or rich-text file. Each of our spreadsheets will comprise a module.

Preferred (module content, link types, etc. in a module) ??

Requirements specification: ??(can be managed by/within a module)

Tag: As it sounds, it is a defined text string that you can associate with an artifact. It differs from an attribute in that it can be defined on the fly (check). Like an attribute, it can be shown as a column and used for sorting and filtering (again, check.)

Type: A list of types is defined in your template to attach to artifacts in your project. Types are just labels, no special functionality is associated with them. Our types will include Requirements, Objectives, Assumptions, etc. (plus Module, to distinguish it from the types within a module -- remember, EVERYTHING is an artifact).