|
 |
Test 000-046: DOORS v9
| |
 |
|
|
Section 1 - Requirements Management basics (10%)
a. Importance of RM.
b. How RM fits in lifecycle
c. Basic RM Lifecycle
d. Characteristics of good requirements
e. Writing pitfallsSection 2 - DOORS Installation (10%)
a. Identify the system and software requirements upon which the client and server can be installed
b. Install the DOORS server
c. Install the DOORS client
d. Define backup strategy for DOORS
e. Define migration steps to migrate DOORS 8.3 to 9.x
f. Create an additional DOORS Server
g. Create a DOORS Shortcut to point to new ServerSection 3 - DOORS Setup (10%)
a. Define the three user types
b. Define the six levels of access (RMCDA and None)
c. Create DOORS users and groups
d. Set access rights on a group
e. Define best practice for setting access rights
f. Modify registry of server to all archive on serverSection 4 - Schema Definition (15%)
a. Define criteria for including migrating information in DOORS
b. With an example set of documents, define a schema diagram
c. Define purpose of link module, linkset and link
d. Specify differences between Projects and Folders
e. Specify what type of user can create Projects, Folders and modules
f. Define attributes needed
g. Define views neededSection 5 - Schema Implementation (15%)
a. Create the projects, folders, modules and link modules to support schema
b. Define default linkset pairings
c. Enforce the link schema in the project
d. Create the attributes in one module
e. Create a custom DXL attribute
f. Import attribute definitions
g. Create a view defined from schema definition
h. Insert a Layout DXL Column from Layout DXL Library
i. Demonstrate how to modify Layout DXL column
j. Convert Public to Custom View
k. Set access rights at projectSection 6 - DOORS Operations (25%)
a. Create links according to schema using drag/drop and menu
b. Create compound filter to show missing requirements
c. Create two traceability columns one for inlinks and one for outlinks, filter and save view
d. Perform three level recursive traceability
e. Define Suspect link
f. Perform suspect link analysis, filtering on suspect links, analyzing and clearing suspect links
g. Perform group attribute operation on a current view
h. Explain process for Exporting from Word to DOORS
i. Reformat a Word document to optimize export to DOORS
j. Export a document from Word to DOORS
k. Perform round trip operation from DOORS to spreadsheets and back again
l. Submit a discussion comment
m. Close a discussion
n. Insert discussion column and filter on the column contents
o. Export project data to HTML
p. Access history through change bars and properties for module and objects
q. Generate report on history of module filtering on dates
r. Modify the prefix of module
s. Create Test Case Definitons and Entry Form
t. Perform two test runs then run test run comparisonSection 7 - DOORS Management (15%)
a. Define user type(s) and access rights needed for CPS
b. Setup and configure CPS for two formal modules
c. Submit a single change
d. Submit a group change against several object in same module
e. Submit master group change
f. Review, approve and apply all changes.
g. Define a baseline set definition for the modules in Project
h. Baseline individual module as part of baseline set
i. Baseline remaining modules en masse
j. Perform a compare modules
k. Setup module for shareable editing at level 1
l. Disable shareable editing for the sections
m. Perform project archive to archive on server
n. Create partition definition
o. Partition out and import partition in second DB
p. Modify data, synchronize then return partition
|
|
|
|
| |
|
