3. The following window appears after login. Now Click the box next to the requirement/artifact to review as shown below.
4. Upon completion of the approval/disapproval process click "DONE". This ends the "review" of the artifacts/requirements.
5. NOTE: If you have somehow navigated away from this page, please use browser back button to bring you back or just go back to your email and click the link again.
DOORS Next-Generation is web-based. It is designed with the intention that manipulation and review of requirements be conducted within the app, rather externally, using exported information. That said, the latter option is always available.
Fermilab owns two floating licesnces for this product. If you try to access but can't, you'll have to try back later. We don't expect there to be much if any conflict given the number of people likely to use it at any given time. To get access:
Make sure your spreadsheet corresponds exactly to the template.
Notice the folder structure. Folders can contain other folders, or they can contain artifacts directly. A module is an artifact; so is a requirement (a row in a module).
We want to set up a structure of folders for our project that follows our traceback structure, more or less.
Remember: one spreadsheet equals one module.
If you get errors, read what they are, fix them in the orig spreadsheet, copy to new one, then try the import again.
The IDs will be assigned in the order of the spreadsheet rows. To see the requirements in the order they were imported, order them by the "ID" column in DOORS.
You can update a module from an updated spreadsheet. Set up the data properly, make sure the ID column is included. In step 10 above for Import options, select one of the two options that start with "Update artifacts that match entries, and..." according to your needs.
Reviews at the top of the page.
In the popup window please give your review a name in the form
Near the top, center-right of your screen click on the down arrow to the right of
Project name Initial Stream (exact text depends on your project). On the dropdown menu, select "Create Baseline..."
In the pop-up window, choose a name for your baseline according to this system -- this will allow everyone to identify all baselines easily:
Use the same naming conventions as for "Review" above.
E.g., 2018-03-19-ah-test (currently the image below shows it without hyphens - please use hyphens!)
Near the top, center-right of your screen click on the down arrow to the right of Project name Initial Stream (exact text depends on your project). On the dropdown menu, select "Compare Configuration..." The system will compare the open project (Project name) to the baseline that you will select.
In the pop-up window under "Component:" choose "Baselines." Search for your baseline, e.g., 2018, or ah or test. Do not use asterisks with the search text.
It takes a moment to load, then tells you that no differences exist. THIS IS A GLITCH! Click "Next" in upper right corner of screen. On the following screen it looks like you can click on a portion of the project, but no matter what you select, it will show you a comparison of the entire project. Click "Next" again.
It shows you the current state (initial stream in our case) on the left and the selected baseline on the right. This first image shows new folders (and/or modules) have been added (to the initial stream which is also the current stream) since the 3 March baseline.
The second image shows a single requirement that has been changed (its primary text field).
(I do not see how to compare two older baselines to each other.)
Go to the "Artifacts" page for the folder that contains the requirements (objectives, ...) that you want to delete.
Click the box to the left of the requirement(s) you want to delete. In my example, I selected three.
Click the edit button on one of the selected rows.