DOORS RBE Authors Training v1-2 PDF

Airbus A400M DOORS/RBE v1.
0
Authors Training Course v1.1
A Two-day course introducing the application of

DOORS to RBE in Airbus
1 © Telelogic AB
Course Structure
• Course includes exercises using Airbus information structure

with generic Telelogic data
• Course content
– Part 1: Airbus A400M RBE Process overview
– Part 2: DOORS Basics
– Part 3: A400M RBE Process using DOORS
2 © Telelogic AB
Part 1: Airbus A400M RBE Process overview
Setting the process Context
3 © Telelogic AB
What Is Requirements Based Engineering
(RBE)
• Requirements Based Engineering within Airbus is the discipline
of Systems Engineering that involves:
– Requirements Engineering (RE)
– Configuration Management (CM)
– Verification
– Validation
– Design.
• Systems engineering is the branch of engineering concerned

with the development of large and complex systems,
addressing:
– Customer and stakeholder needs
– Development lifecycle
– Processes for technical management of design and engineering
4 © Telelogic AB
System Development
An Airbus product is a system that is an integrated composite of
people, products, services and processes that provide a capability to
satisfy a stated need or objective.
Level 0
Level -1 Component A
Component A
Level -2
5 © Telelogic AB
Airbus Systems decomposition
User Needs Final Product (Aircraft)
Systems are defined via Development at

Level ‘0’
many levels of
decomposition from User
TLARs Final Product (Aircraft)
Needs down to
component manufacture
Development at
Level ‘-1’
e.g Wing,
Fuselage & Requirements for MajorComponent
Component
??Major Parts??? Major
Major Component
Empennages, ??Major Parts???
Major Component
Aircraft Systems
Developmentat
Development
Development at
at
Level ‘-2’
Level ‘-2’
Level ‘-2’
e.g for Wing: Wing Box,
Ailerons, Spoilers
for Aircraft System:
Fuel, Hydraulics, Requirementsfor
Requirements
Requirements for
for LowerLevel
Lower Level
Level
Lower
Navigation Lower
Lower Level
LowerLevel
Level Component
Component
Component
Component
Component
Component
Further product
breakdown Manufacturing
6 © Telelogic AB
Many levels of decomposition
User Needs Final Product (Aircraft)
The same process is Development at

Level ‘0’
employed at each level
TLARs Final Product (Aircraft)
Development at
Level ‘-1’
Level 0
Requirements for MajorComponent
Component
??Major Parts??? Major
Major Component
??Major Parts???
Major Component
Level -1 Developmentat at
Development
Development at
Level ‘-2’
Level ‘-2’
Level ‘-2’
Requirementsfor
Requirements
Requirements for
for LowerLevel
Lower Level
Level
Lower
Lower Level
LowerLevel
Lower Level Component
Component
Component
Level -2 Component
Component
Component
Manufacturing
7 © Telelogic AB
A400M Airbus Document Generation Cascade
Level 0
Specialist Domains:
TLARs A/C Requirements JARs, FARs, Airbus TDDs, ABDs,
Exhibit A & P Safety, Supportability,
ATA Chapters Manufacturability
Level -1 Generate FRD Generate SRD

Generate SRD
(SAT) Generate SRD
(Per System)
(Per System) Generate
(Per System) 1 Per TLStRD
System
FRD
FRD FDD
FDD FRD
FRD
FRD FDD SRD FRD
FRD
TLStRD
1 Per
CMIT
Level -2 Generate PTS
Generate PTS
Generate PTS FRD
FRD
Generate
StRD
SIRD
FRD
FRD
FRD
FRD StRD
PTS
1 Per
CDBT
Generate Task
Generate Task
Level -3 Generate
FWS
FWS
FWS
Task
FRD
Task
FRD
FWS
8 © Telelogic AB
Development at each level
• Each level takes requirements from the level above

• Generates requirements for level below
• Receives development products from level below
• Integrates development products to produce deliverable to level
above
Requirements Product
from to
level above level above
Development at Level n
Requirements
Requirements
Requirements Product(s)
Product
Product
to
to
to from
from
from
level below level
level
level below
below levelbelow
level below
below
9 © Telelogic AB
• Each level must also address requirements from the specialist
domains:
– Certification
– Safety
– Supportability
– Producibility
– Design Guidelines and Directives
from to
Requirements
from
specialist domains
Development at Level n
Requirements
Requirements
Product
Product
to
to
to from
from
from
level below level
level
level below
below levelbelow
level below
below
10 © Telelogic AB
• Each development team at each level may receive requirements from
another development team at the same or another level
– e.g. SIRD/EIRD
• Each development team may create requirements that must be

satisfied by other development teams – possibly at several levels
from to
Requirements
from
specialist domains
Requirements Development at Level n

from
other teams
Requirements Requirements Product(s)

Requirements
Product
to to from
to
to from
from
other teams level below level
level
level below
below levelbelow
level below
below
11 © Telelogic AB
All RBE Process Activities
Customer
Requirements Facing Tasks Product
from [8] to
Requirements RBE
from Agree Input Generic Process Verify own
specialist domains Requirements Product
[1] [6]
Requirements
from
other teams Verify
Produce and Integration
Verify Design Products
[2] [5]
Requirements Generate and Verify

to Validate Output Products from
other teams Requirements lower level
[3] [4]
Customer
Role in Configuration
Agreement Requirements
Product Management
Process [7] to
to from
from [9]
to from
level
level below
level below
below level
levelbelow
level below
below
12 © Telelogic AB
Author Process Activities
Customer
from [8] to
Requirements RBE
from Agree Input Generic Process Verify own
[1] [6]
Requirements
from
other teams Verify
[2] [5]

[3] [4]
Customer
Product Management
Process [7] to
to from
from [9]
to from
level
level below
level below
below level
levelbelow
level below
below
13 © Telelogic AB
Instantiating the Generic Process - clarification
• Each instance of the Generic Process:

– takes requirements from level above (and potentially from
specialists and other development teams)
= Input Requirements
– generates requirements for the lower level team (and potentially
transverse requirements for other development teams)
= Output Requirements
– may undertake design activity to aid in the creation of
Output Requirements
• Examples of Instances
– SAT takes ARs and generates FRDs
– F&E ACMT takes Aircraft Requirements (and possibly FRDs) and
generates F&E TLStRD
– Fuel CMIT takes Aircraft Requirements, FRDs (and specialist
requirements) and generates Fuel SRD
– Fuel CMIT takes Fuel SRD and generates Fuel SSRDs/PTSs
14 © Telelogic AB
Part 2: Using DOORS
Understanding the Tool
15 © Telelogic AB
Benefits of RBE in DOORS
• Traceability from highest level requirements to implementation

– Established via links through the database
• Impact assessments of proposed changes
– Analysis tools let you see which other requirements will be
affected by a change
• Controlled access to current project information
– A shared database ensures that all users are working with current
data
– A central repository allows controlled access to essential
information
• Change control
– The Change Proposal System implements a controlled process for
managing change
16 © Telelogic AB
Database Login
• To open the database you must login
– Access controls are applied based on user login
• The database Administrator creates the database users
– Individual user name for each person
– The login for the Airbus RBE Training Database is
• Username: Author
• Password: Author
17 © Telelogic AB
DOORS Help
• DOORS provides an extensive

on-line help library for you
– Contents follow the DOORS
User Manual
– Index and Find functions for
quick look-up
• DOORS dialogue boxes also
provide context sensitive help
18 © Telelogic AB
DOORS Database Structure
• The database contains

all data
• Data can be organized
in
– Folders
– Projects
– Modules
• Only Projects and
Folders are allowed at
the root level
= Folder
= Project
= Module
19 © Telelogic AB
The DOORS Explorer – Database View
• Operates like Windows Explorer

• Only shows folders and projects which you can access
• Have list of favourites
Additional Items inside Project or Folder
20 © Telelogic AB
Explorer Favourites
21 © Telelogic AB
Exercise 1
Browse the Database Using the DOORS Explorer
1. Launch DOORS and login to the database as user

“Author”, with the password "Author".
2. Since this is your first time looking at this database,

open the project and folders to note their contents.
3. To familiarize yourself with the DOORS Explorer

window - Look at the various elements of the Airbus
RBE database structure at each level of the
hierarchy.
22 © Telelogic AB
DOORS Formal Modules
23 © Telelogic AB
Formal Modules
• A formal module is a container for information (requirements,

graphics, etc.)
– Typically structured and displayed as a document
24 © Telelogic AB
Formal Module - standard view
• Module Explorer allows you to navigate and see the structure

• Right hand pane shows Object ID column and the Object Heading
and Text column
25 © Telelogic AB
Displayed Information
Column Object or
Heading Section
“No change since baseline” Number Object Heading
change-bar (green)
Object
Identifier
Link
Indicator
“Changed this session”
change-bar, unsaved (red) Object
Text
“Changed since baseline” Current
change-bar, saved (yellow) Object
26 © Telelogic AB
Formal Module Display Options
Explorer Normal Outline
Tip View, Module Explorer Tip Shift + F5 to refresh explorer Tip View, Outline
27 © Telelogic AB
Formal Module Access Modes
Three opening modes:

Read-only read-only access, allows others to edit
Shareable Edit allows controlled, multi-user editing
Exclusive Edit exclusive read-write access
28 © Telelogic AB
Changing Edit Mode
• You can change edit mode without closing and re-opening

the module
29 © Telelogic AB
Exercise 2
Working with Formal Modules

1. Select the folder "/AS300/2- Top Level 4. Click on various items in the Explorer, and note
Requirements" . Open the module Top Level that DOORS makes this the current object in the
Requirements module in exclusive edit mode. module view on the right.
2. To view the structure of this module, turn 5. Since you do not plan to make any changes to
Outlining on. In the Outline view, click on a this module, switch to Read-only mode.(Hint:
Section 3.1 (Load and unload the trailer), then Edit, Edit Mode). Note how the background to
turn Outlining off so that you can see the the module is now grey.
contents of this section.
6. Now Close the module.

3. Next, expand the Module Explorer to locate
the Survive Accident section within Section
3.6. (Hint: Use +/- in the Explorer window)
30 © Telelogic AB
Objects and Structure
Working with objects within the module structure
31 © Telelogic AB
Object Concept
• Formal Modules are collections of Objects

• Objects may be used for
– Requirement text
– Headings
– Graphics
– Any other information
An object is an object, no matter what

information it contains
32 © Telelogic AB
Object Properties
• Detailed information
about an object
– General – Heading,
Short Text, Object
Text values for the
object
– Access – View or set
access rights
– History – log of
changes to the object
– Attributes – attribute
values for the object
– Links – relationships
to other objects
•Edit, Object Properties

Tip •Ctrl-E
•Right Click, Properties
33 © Telelogic AB
Object Structure Terminology
D
B
E
A
G
C F
H
Structure as a “Family”:
parent object A has children objects B and C
child objects D and E have B as their parent
siblings objects G and H have the same parent
ancestors object G has F, C, and A as ancestors
descendants object C has F, G, and H as descendants
Structure as a “Tree”:
leaf objects D, E, G, and H have no children
non-leaf objects A, B, C, and F are parent objects
34 © Telelogic AB
Object Drag and Drop
35 © Telelogic AB
Cut and Paste Objects
A DOORS tree can be rearranged with Cut and Paste

• Cut (Ctrl+X) - removes current object and all children
• Select insertion point
• Paste (Ctrl+V) or Paste objects one level down
Current
Object
Cut Paste
Remaining
objects are
renumbered
Renumbered Again
36 © Telelogic AB
Paste One Level Down
Current
Object Edit, Paste
Cut objects one
Insertion level down
Point
Remaining
objects are
renumbered
Renumbered Again
37 © Telelogic AB
Remember to Paste Your Cut Objects!
If an object is cut but never pasted, then the following message

will appear upon performing a subsequent cut operation or upon
closing or saving the module:
Delete will delete the objects on the clipboard

Restore will put the objects on the clipboard back from where
they were cut
Cancel will cancel either the second cut or the module close
or save
38 © Telelogic AB
Copy and Paste Objects
• A DOORS tree can be added to easily with Copy and Paste

• Copy
– Copy current object only (Ctrl+C), or
– Current object with hierarchy
• Select insertion point
• Paste (Ctrl+V) or Paste objects one level down
Edit, Copy objects
with hierarchy
Insertion
Point Renumbered
39 © Telelogic AB
Delete Objects
• A DOORS tree can be trimmed with the Delete function

• Applies to current or selected objects, including all child objects
• Objects are only marked for deletion
• Deleted objects can be undeleted, restoring them in the
module
• Deleted objects can be purged, permanently removing them
Current
Object Delete
Remaining Tip
objects are
renumbered Delete
object
40 © Telelogic AB
Exercise 3
Rearranging Information
1. Reopen the module Top Level Requirements 4. Since the items listed in Section 1 (Introduction)
module in exclusive edit mode. are not actually user requirements, delete this
section from the module.
2. Move a section (e.g. 3.4) after the next one
(3.5). Use drag and drop to accomplish this 5. When you are done, you save and close the
since these sections are adjacent to one Module
another.
3. Next, use cut and paste to move a section
(e.g. section 2) after another one, not
simultaneously visible on the screen (section
4).
41 © Telelogic AB
Information Content in DOORS
Working with your requirements and other

information in DOORS
42 © Telelogic AB
Edit Objects in Place
• For current
object, just type
to append text
at the end
• Double-click on
object to put
cursor on left
margin of the
first line of an
object
• Double-click,
then click in
desired position
to insert text
Tip Ctrl+H or Edit object heading Ctrl+T or Edit object text
43 © Telelogic AB
Creating Objects
Building a hierarchy of objects in DOORS is simple:

• Current object is always the insertion point
• Choose position of new object relative to current
Current
Object Insert, Object Insert, Object Below
Renumbered
Renumbered
Tip Ctrl-N Insert object at same level Ctrl-L Insert object below
44 © Telelogic AB
Creating New Objects from the Keyboard
• When editing any object, use Ctrl+Enter to create a new text

object at the same level
45 © Telelogic AB
Heading Objects and Text Objects
• Objects should contain headings OR text (but not both)

• Heading objects
– A heading object has a value for Object Heading, but not for Object Text
– Provide context for the requirements (or other objects) below them
– Have a Section Number displayed
• Text objects
– A text object has a value for Object Text, but not for Object Heading
– Requirements are entered in text objects
– Should be leaf objects in the module hierarchy
– Have a Section Number, but it is not displayed in the normal view of the
module
There should be no more than ONE concept in an object!
46 © Telelogic AB
Object Structure Guideline #1
Make text objects children of the heading objects under

which they occur.
No:
Yes:
47 © Telelogic AB
Object Structure Guideline #2
Don’t make text objects children of other text objects.
No: Yes:
48 © Telelogic AB
If You Follow the Guidelines Then...
All non-leaves will

be heading only
The implied
structure in the
Heading and
Text Column is
All leaves will the actual
be text only structure of the
objects in the
module
49 © Telelogic AB
Word Processing Functions
• DOORS provides a number of word processor-like functions

– Text formatting (bold, italics, underline, strikethrough, bullets,
increase/decrease indentations)
– Insert Symbols
– Spelling checker
– Undo function
– Search and search/replace
50 © Telelogic AB
Formatting Text
Strikethrough Bold
Right mouse
click to get
pop-up menu
Underline
Bullets
Italic
Increase/Decrease Indent
51 © Telelogic AB
Inserting Symbols
• While in edit-in-place mode
52 © Telelogic AB
Check Spelling
• Specify
attributes Tip Ctrl+K
• Specify range Check

spelling
• Click Start
53 © Telelogic AB
Managing the Dictionaries
• Two editable
dictionaries
– Database – all
users
– Client – specific
to client machine
• Modify Access to
Dictionary
• Enter New Word
• Click on Add new
word
You can also add new words when spell checking using the Add button
54 © Telelogic AB
Undo Function
Multiple level Undo function for object deletions, attribute

changes, and table cell formatting
Tip Ctrl+Z
55 © Telelogic AB
Using the History Window to Undo
“Restore” will set the attribute value to the “From” value of the selected
history record
56 © Telelogic AB
Export from Word to DOORS
• Initiate from Word

• Export to current Project or
Folder in DOORS
57 © Telelogic AB
Exercise 4
Working with Objects

2. Rearrange the order of the sections to appear in
1. Select the folder "/AS300/2- Top Level this order:
Requirements/System Design/Steering – 1 Introduction
– 2 Referenced Documents
Assembly" open the module "Steering Sub-
– 3 Requirements
system Requirements" module in exclusive – 4 Requirements Verification
edit mode, and do the following:

3. Apply formatting (bold, italics, underline, and
strikethrough, bullets and indents) to some of
• Create a Level 1 Heading Object as Section 1 the text in this module.
“Introduction”
• Create a Level 1 Heading Object as Section 2 4. When you are finished, you save and close the
“Requirements” module.
• Create a Level 2 Heading Object as Section 2.1
“Functional Requirements”
• Create a Text object below Section 2.1 “This
section contains functional requirements.”
• Create a Level 2 Heading Object as Section 2.2
“Non-Functional Requirements”
• Create a Text object below Section 2.2 “This
section contains non-functional requirements.”
• Create a Level 1 Heading Object as Section 3
“Requirements Verification”
• Create a Level 1 Heading Object as Section 4
“Referenced Documents”
58 © Telelogic AB
Using Attributes
Using and displaying attributes and other information

to capture additional information about your data
59 © Telelogic AB
What is an Attribute?
Attributes are additional characteristics of an object
– They can be used to provide essential information in addition to
requirement text
Is Req? Is the object a managed requirement?

Rationale Reason or justification of the requirement
Source Where does the requirement originate from?
Req. Status Status of the requirement, progress in its life cycle
Stakeholders Who has an interest or a stake in the requirement?
Additional Information Any comments on the requirement to clarify it
Priority What is the priority of this requirement?

Verifiability Is the requirement verifiable?
Safety Is this a safety-critical requirement?
Questions Any questions that must be clarified with the source
Attributes help you manage your requirements more

effectively and more efficiently
60 © Telelogic AB
Object Attributes
Attributes allow additional information to be
associated with each requirement
Attributes can also be defined for Modules and Links
61 © Telelogic AB
Attribute Applications
• Filtering
– Using attributes the user can collect only those objects that meet
simple and compound filtering criteria.
• Sorting
– The user can re-arrange the order (top to bottom) of the objects in
a module based on a single or multiple sort keys.
• Searching
– The same rules that can be applied for filtering can be used to find
objects in the module.
62 © Telelogic AB
Column Concepts
• DOORS uses columns to display data
• The default display, “Standard view”, for a Formal Module shows:
– Object ID column
– Main column (Object Number, Object Heading and Object Text)
63 © Telelogic AB
Using Columns
• You can modify the column display to present your data in

a manner that is more productive for you
• For example, you could add columns to display Criticality
and Verification Method attributes for your requirements
64 © Telelogic AB
Types of Columns
Modules can display three kinds of columns:
Attribute Displays the value of an object attribute

DXL Displays virtual data generated via wizard or dxl
script
Object Heading Displays Object Number, Object
and Text Heading, and Object Text attributes in a document
format
Object Heading and Text Attribute DXL
65 © Telelogic AB
Columns and Attributes
• Data in the database are independent of the display

– Not all attributes need to be displayed
– DOORS can display a maximum of 32 columns
• Removing a column does NOT delete the data

– The information is removed from the view, but remains in the
database
66 © Telelogic AB
Creating a New Attribute Column
• Insert a new column to display information

from your database
– Select ‘Column’ from the ‘Insert’ menu Tip
Insert
– Select ‘Attribute’ radio button, then select the
column
attribute from the pulldown menu
67 © Telelogic AB
Column Titles
Title field always overrides defaults
Default title for an attribute

column is the attribute name
Use the Title field for DXL columns

(no default)
Default title for the text

column is the module description
68 © Telelogic AB
Column Operations
Edit Column Properties Remove Column

Insert Column Set Column
Justification
Drag for
column
width
69 © Telelogic AB
Column Drag and Drop
70 © Telelogic AB
Edit Attribute Values - in Place
Edit in place
• Double-click on
attribute cell
• Enter or select value
• Click on ‘discard
changes’ icon to reject
• Click on ‘accept’ icon or
another cell to accept
Efficient method for one-

at-a-time edits
• Ctrl+A to move to next
column for the current
object
• Return to move to same
attribute for the next
When in edit mode, the attribute values
object
may be reset to the default by typing
Ctrl+R or selecting “Reset to Default”
71 © Telelogic AB
Attribute Values Editor
Select attribute from

the list, click Edit
Select or enter value (based on

type)
Tip Ctrl+E,
Ctrl-Double-click
72 © Telelogic AB
Exercise 5

1. Select the Folder "/AS300/2- Top Level 5. Set rbe Object Type to Requirement and rbe
Requirements". Open the module Top Level Requirement Status to Proposed for the the
Requirements in Exclusive Edit mode to edit
same textual objects in Section 2. (Hint: Right
attribute values.
click on the first object, select Properties, select
Attributes Tab – use previous and next to scroll
2. To make more room in the display, remove the through the objects).
Object ID column and deselect the Module
Explorer.
6. Save and Close the module
3. First, insert columns for the following attributes:
rbe Object Type, rbe Requirement Status,
rbe Allocation. (Tip – adjust column widths as
necessary to fit the columns on the screen.)
4. Set rbe Object Type to Requirement for all

textual objects in section 2 (General
Description), using the Edit in Place method.
73 © Telelogic AB
Finding and Displaying the Data
Finding, filtering, and sorting the database to set up

views which focus on specific data of interest
74 © Telelogic AB
Search Capabilities
• Search the database for folders, projects, or modules based on

text in name
• Search the database for modules based on text in Object Text
or Object Heading
• Search a module for objects based on text contents, attribute
values, links, position in hierarchy
• Filter to show (only) all objects which meet search criteria
• Find and replace text
• Go to object based on absolute number or section number
75 © Telelogic AB
Search the DOORS Database Explorer
Tip Tools, Find • Find Folders, Projects, or

Modules by name
– Enter full name or partial
name with wildcards (* or ?)
• Find Modules by Object
Heading or Text content
– If desired, enter Name
information
– Enter text string in
‘Containing text’ field
• Check the appropriate check
boxes
– Use Wildcards (for text field
only)
– Match case
• If the “Named” field and the
“Containing text” field are
populated, the search criteria
is the logical AND of both
criteria
76 © Telelogic AB
Search a Module
Tip Ctrl+F Edit, Find • Find objects in the

current display
• Fill in text string to
search for
• Match case?
• Use regular expression?
• Specify attribute(s) to be
searched
• Find Next or Previous
– Takes you to the object
in the current display
77 © Telelogic AB
Module Find/Replace
• Replace text within the

Tip Edit, Replace current display
– One at a time, or
Replace All
• Select Text attribute(s)
• Match Case?
• Find Next/Previous
• Replace/Replace All
78 © Telelogic AB
Go To Object
• Locate a specific object by

– Absolute Number
– Section Number
• Enter number
• Click Go To
• Takes you to the object, if it
is in the current display
Tip Ctrl+G Edit, Go To
79 © Telelogic AB
Filter Concept
• Used to display ALL objects that satisfy the rules

– Access Filter function from Tools menu
– Objects that do not meet the rules are not displayed
• Allows you to focus on specific groups of objects
80 © Telelogic AB
Filter Applications
• Limit Display Set to specific objects

– Requirements with no outgoing links
– Requirements with a Verification Method of Test
– Requirements allocated to a given team or equipment
• Print subsets, generate targeted documents
• Generate metrics
– Record and report the filter results on a regular basis to show
project progress
• Number requirements that have actually been tested
• Number of requirements that PASSED their tests
• Apply a specific value to an attribute for an entire set of objects
that match a filter rule
• Save a View that contains a filter
81 © Telelogic AB
Define a Simple Filter
Display filter Note: Toggling the filter tool bar button

Tip results does not re-apply the filter criteria
82 © Telelogic AB
Simple Filter - Attributes
From Attributes tab

• Select Attribute
• Select operator
• Enter or select
value
• Match Case?
• Regular
Expression?
83 © Telelogic AB
Simple Filter - Links
From Links tab

• Select link condition
– Have
– Do not have
• Select link direction
– Any in or out links
– Incoming links
– Outgoing links
• Select Link Module
– Any link module
– Specific link module
84 © Telelogic AB
Simple Filter - Objects
From Objects tab

• Select position in
module hierarchy
– Object is a leaf
– Object is not a leaf
OR
• Specify current or
not current object
85 © Telelogic AB
Simple Filter - Columns
From Columns tab

• Select from
among the
displayed
Columns
• Specify the
string to match
in that column
• Can be used to
search for data
from Layout DXL
column
• Not used to
search for
specific attribute
values
86 © Telelogic AB
Define a Compound Filter
• Click Advanced button

from Filter or Find window
• Specify simple rules
• Combine simple rules
using And, Or, or Not
• Select filter options
– Show ancestors
– Show descendants
– Hide non-matching table
cells
• Filter
• Results displayed
87 © Telelogic AB
Selecting Multiple Objects
• Select by clicking on first object, shift-click to add

• Only a contiguous set of objects can be selected
• Deselect with a second shift-click
Current
Object
Delete, link, cut,

copy, paste, or
assign attribute
value as a set
Shift- Tip F3 Select

Click
Ctrl F3 Deselect
88 © Telelogic AB
Group Attribute Operations
Objects in current view

Applies selected value to
all displayed objects
•If inheritance is
enabled, the value will
applied to the children,
regardless if they are in
the current view
Selected objects
Applies selected value to current selection
(shift-click to select a range of objects)
89 © Telelogic AB
Exercise 6

1. Select the Folder "/AS300/2- Top Level
Requirements". Open the module Top Level
attribute values.
2. Using Filters, display all items the Object Text

of which include Safety
3. Set the value of the attribute "rbe Additional

Information" to “Critical” for displayed
objects using the Properties window.
4. Using Advanced filters, display objects that

are Requirements that have been allocated to
the Hull (Hint: Use rbe Object Type and rbe
Allocation)
90 © Telelogic AB
Sorting
Sorting re-orders your current display data
• DOORS allows you to sort by attribute values in:

– Ascending order (e.g., increasing ‘Priority’)
– Descending order (e.g., decreasing ‘Cost’)
• DOORS allows you to define simple or compound sorts

– Simple:
• Ascending or descending order for one attribute only
– Compound:
• Ascending or descending order for one attribute AND ascending or
descending order for another attribute
91 © Telelogic AB
Compound Sorts
The compound sort places objects into

ordered groups
First, sort this column Next, where the Weighting

by attribute value values are the same, sort by
(Weighting, descending) the Priority attribute to
determine display order
92 © Telelogic AB
Using Sorting
• Select attribute to sort on
• Select sort order
• Click OK to use selected attribute
• Use Advanced to define a compound sort
• Click OK in the Advanced Sort window to apply the compound
order displayed in the list
Tip Tools, Sort Display sort results
93 © Telelogic AB
Sorting Hints and Tips
• Sorting changes the order of display of formal module objects

– The left-hand pane of the Module Explorer is not affected, but the
right-hand pane is
– Objects cannot be created, cut, copied, pasted, deleted, or moved
while sorting is active
• Sorting ignores objects in DOORS tables
– “>>Table” indicates the existence of a table
• Sort conditions can be saved with a view
94 © Telelogic AB
Views
• Define display layouts for your data

– Columns, filters, sorts, window position, etc.
– Used to save a display that contains attribute or relationship report
data of interest
• Can be saved within a Module (Module-specific)

• Can be reloaded from drop-down list on toolbar
– Allows you to quickly and easily re-create a set of display
conditions
• A view can also be reloaded from the menu View -> Reload
95 © Telelogic AB
Saving the Current View
• Saves the current display

layout
• Enter a name
avoid
• Select the display settings to
if appropriate
be saved
• Set as default, if desired
• Set the Access to the View –
Public or Private
• Click OK to save
NOTE: This saves the layout,
not the data! Use File, Save
to save data.
Tip View, Save As
96 © Telelogic AB
Exercise 7
Working with Views

1. Select the Folder "/AS300/2- Top Level
Requirements". Open the module Top Level
attribute values.
2. First Select the Standard View using the view

pulldown on the toolbar.
3. Next, insert columns for the following attributes:

rbe Object Type, rbe Requirement Status,
rbe Allocation. (Tip – adjust column widths as
necessary to fit the columns on the screen.)
4. Apply a filter to show object where the value of

rbe Requirement Status is equal to
"Requirement".
5. Save this view as “Requirements Only”.
97 © Telelogic AB
Printing and Reports
Standard functions
98 © Telelogic AB
Printing
• Formal modules can be printed directly from DOORS

• The current view is printed
– All objects in the current view
– All attributes currently displayed
99 © Telelogic AB
Table Format
Page 1A Page 1B
100 © Telelogic AB
Book Format
Book format: attributes

appear under the text
101 © Telelogic AB
Page Setup
• Select existing
setup
Or
• Create new
– Apply
– Save As
• Format tab
– Table or book
– Cell Borders
– Column titles
– Book Format
Options
Note: Page Setups apply to the entire DOORS database

102 © Telelogic AB
Page Setup – Layout and Size
• Layout tab
– Include title page?
– Include filter or sort
criteria on title
page?
– Include Signature?
– Include table of
contents?
– To what level?
– Page break level?
– Show change bars?
• Paper size tab
– Paper size
– Orientation
103 © Telelogic AB
Page Setup – Margins and Headers
• Margins tab
– Top
– Bottom
– Left
– Right
• Headers and footers

tab
– Left, middle, right
– Title page, table of
contents pages,
body pages
– Rich Text Marking of
headers and footers
(right mouse click
only)
104 © Telelogic AB
Print Preview
View your
output
before
sending it
to the
printer
105 © Telelogic AB
Links and Traceability
Defining and using relationships between objects
106 © Telelogic AB
Why Define Relationships?
Requirements in real projects are inter-related
• These relationships can be used to understand dependencies

between requirements and assess impact of change
• Analysis of dependencies helps ensure 100% traceability
• Requirements also have relationships to other objects in the
database for the project lifecycle
• “Maintain bi-directional traceability among the requirements
and the project plans and work products” (CMMI v1.02, pg 378)
107 © Telelogic AB
Link Concepts
• A relationship between two objects in the DOORS database is

established using a “link”
• Source and Target Objects
– Source is the “from” object
– Target is the “to” object
• Links can be followed in either direction
108 © Telelogic AB
Link Scope
• Creating an individual link establishes a relationship between

two objects
• This relationship can be defined between any two objects in
the database
• Users must have at least Modify access to the source object
and Read access to the target to create a link
109 © Telelogic AB
Link Tools
Methods for creating links
110 © Telelogic AB
Methods for Creating Links
Drag and drop • Simple and fast

• Can create many-to-one links
• Copy objects and link
• Creates links according to the defined model
Menu-driven linking • Menu driven

• Can create one-to-many links
• Creates links according to the defined model
111 © Telelogic AB
Drag and Drop Linking
112 © Telelogic AB
Menu-Driven Linking
• Select source object

and Start Link
• Select target object(s)
and Make Link from
Start
These functions are also

available from the pop-up
menu when you click the
right mouse button.
113 © Telelogic AB
Delete Links
114 © Telelogic AB
Exercise 8
Creating Relationships
1. To establish the traceability between two modules 2. Spend about 5 minutes creating links from
open /AS300/2- Top Level Requirements/Top various sub-system requirements to appropriate
Level Requirements and /AS300/2- Top Level system requirements using Drag and Drop.
Requirements/System Design/Mast Assembly
/Mast Sub-system Requirements and display

3. Spend about 5 more minutes creating links from
them on your screen as shown below. (Tip - turn off
various sub-system requirements to appropriate
the Module Explorer in both modules to conserve
system requirements using menu-driven linking.
screen space.) Then save the view in each module
as Link View, including Window size and position
in its definition. 4. Try making a link in the wrong direction, and see
how DOORS behaves.
Top Level Sub-system

Requirements Requirements
115 © Telelogic AB
Link Analysis
Using links to manage change and to show full

traceability
116 © Telelogic AB
Link Analysis Tasks
• Use links to assess the impact of a change

– For example: assess the impact of
• A user requirement change
• A component design change
• A test failure, etc.
• Link reports
– Generate viewable and printable reports
117 © Telelogic AB
Using Link Indicators
• Position cursor over link indicator

• Right mouse button to select module and object
118 © Telelogic AB
Filtering on Links
• Use “have” to show objects that currently are linked

• Use “do not have” to show objects that are orphaned
or childless requirements
119 © Telelogic AB
Suspect Links
If a source or target object is modified after the corresponding

link is created or “cleared of suspicion”, then the link is
suspect.
Suspect! Brake efficiency 50%

70% ?►
70m
Stop in 100m
passengers
Carry 5 passengers
Five seats ?►
120 © Telelogic AB
Suspect Links Perspective
• Links are considered “suspect” based on a perspective.

– DOORS assumes that the person who is modifying an object is
conscious of the link and is making changes that are appropriate
in the presence of the link. Therefore, from the perspective of the
modified object, the link is not suspect!
– Once this change is made, the link becomes suspect from the
perspective of the object that it’s linked to.
A link is suspect only from the perspective of the unchanged object
121 © Telelogic AB
Displaying Suspect Link Indicators
This In Link is suspect from the perspective of the target

object (i.e. the source object has been modified)
122 © Telelogic AB
Displaying Suspect Link Information
This In Link is suspect

from the perspective of
the target object
(i.e. the source object has
been modified)
123 © Telelogic AB
Clearing a Suspect Link
“Details” will
show the pre-edit
value and the
post-edit value of
the attribute that
was changed
124 © Telelogic AB
Recording a Cleared Suspicion in History
125 © Telelogic AB
Suspect Link Filter
• Filters objects just to show those with suspect links.
126 © Telelogic AB
Exercise 9
Creating Relationships
1. Open the modules that you have just created 3. Make new modifications on linked objects (e.g.
links to/from (I.e /AS300/2- Top Level in the Top Level Requirements) to see they are
Requirements/Top Level Requirements and reflected in the Sub-system Requirements (Hint:
/AS300/2- Top Level Requirements/System Analysis, Suspect Links, Display… and Filter).
Design/Mast Assembly /Mast Sub-system

Requirements), and see that these links
4. Change a suspect object and see that suspicion
are displayed in views A2.Respond to
is cleared automatically.
(you may need to deactivate the filter)
and D2. Satisfied by.
2. See that the views are updated automatically
1. if links are created or
2. if linked objects are modified.
127 © Telelogic AB
History
128 © Telelogic AB
Modification History
• History records change

– Who made the change
– When the change was made
– What was changed
• Operations that are recorded include
– Object moves, copies and other structural changes
– Object text modifications
– Attribute value modifications, conditionally
– Sessions
129 © Telelogic AB
Module History
• History is a Module
Property
• Choose Redlining
• Select range
– All
– Module
– Sessions
• Filter History output
– By date
– By user
• Refresh
• Export to a text file
130 © Telelogic AB
Object History
• View History of a
specific object
• Double-click on
Object’s change bar
• Choose Redlining
• Filter History output
– By date
– By user
• Refresh
• Click Details to see
changes in a separate
window
• Export to a text file
• Move to Next or
Previous object
131 © Telelogic AB
Exercise 10
Viewing History
1. Open the modules you modified to view
the History of some of the requirements
there.
2. Double-click on the yellow change bar for

one of the requirements to see the history
of the requirement.
3. Next, display all history of the changes

that you have made in your work in this
module today. To do so, open the Module
Properties window, and on the History
tab, click the All button, click the Dates
checkbox, enter yesterday’s date in the
From field and today’s date in the To field,
and hit Refresh.
132 © Telelogic AB
Part 3: Using DOORS for RBE
Applying the RBE Process and Method in DOORS

for “Authors”
133 © Telelogic AB
Requirements Based Engineering
• RBE Policy
– Document issued
• RBE Process
– Document issued
• RBE Method
– Draft 10 ready for issue
• RBE Implementation in DOORS
– DOORS has been configured to support the method
– Installation Guide for database administrators
– Authors Guide for people writing requirements
– Specialist Guide for DOORS specialists (supporting authors)
– Authors training – this course
– Reviewers training – for people who will review requirements
134 © Telelogic AB
Using DOORS for RBE
• DOORS implementation
– Module types
– Module attributes
– Module views
• Using the DOORS implementation for the RBE Method steps

– based on a scenario that is concerned with
requirements development at a particular level
– explains how to use the modules and views that have been
produced
– exercises to give practical experience of the use of DOORS
135 © Telelogic AB
DOORS module types
• Mandatory
– Requirement Set (RS)
• holds a set of requirements developed by a single team
• teams may create one or more sets of requirements
– Requirements Validation Actions (RVal)
• what actions will be undertaken to ensure that the requirement set is
valid
– Product Verification actions (PVer)
• what actions will be undertaken to prove that the delivered “product”
satisfies its requirements
• Optional
– Design Material References (DMR)
• identifies design materials generated (can be the actual material)
– Design Verification Actions (Dver)
• what actions will be undertaken to prove that the intended design
satisfies its requirements
136 © Telelogic AB
Data Model – how do the module types fit together?
Input Requirements Level Above
RS
for this level
Verifies Product
Product Verification
Verification
RVer
Actions References
Evidence
Satisfies
This Level
Requirement
Output Requirements Validates Requirements Validation
Validation
RS
from this level RVal
Actions References
Evidence
Product
Level Below Verifies Product Verification Verification
Product
ProductActions
Verification References
RVer Evidence
Verification
RVer
Actions References
Evidence
137 © Telelogic AB
Data Model – Optional Design Modules
RS
for this level
Verifies Product
Verification
RVer
Actions References
Evidence
Satisfies
Design
Satisfies
Design Verification
Verification
DVer
Actions References
Evidence
Justifies
Design
Derived
Design Material
Materials
from DMR
References References
Requirement
Validation
RS
Actions References
Evidence
Product
Level Below Product Verification
Verifies Verification
Product
ProductActions
RVer
Verification Evidence
Actions Verification
RVer References
Evidence
138 © Telelogic AB
Data Model – Optional Integration modules
RS
for this level
Verifies Product
Verification
RVer
Actions References
Evidence
Verifies
Satisfies
Integration
Integration Verification
Link module Verification
Actions
RVer This Level
References
Evidence
name is
“…..satisfies”
Requirement
Validation
RS
Actions References
Evidence
Product
Level Below Product Verification
Verifies Verification
Product
ProductActions
RVer
Verification Evidence
Actions Verification
RVer References
Evidence
139 © Telelogic AB
A400M Airbus Document Generation Cascade
Level 0
Specialist Domains:
TLARs A/C Requirements JARs, FARs, Airbus TDDs, ABDs,
Exhibit A & P Safety, Supportability,
ATA Chapters Manufacturability
Level -1 Generate FRD Generate SRD

Generate SRD
(SAT) Generate SRD
(Per System)
(Per System) Generate
(Per System) 1 Per TLStRD
System
FRD
FRD FDD
FDD FRD
FRD
FRD FDD SRD FRD
FRD
TLStRD
1 Per
CMIT
Level -2 Generate PTS
Generate PTS
Generate PTS FRD
FRD
Generate
StRD
SIRD
FRD
FRD
FRD
FRD StRD
PTS
1 Per
CDBT
Generate Task
Generate Task
Level -3 Generate
FWS
FWS
FWS
Task
FRD
Task
FRD
FWS
140 © Telelogic AB
DOORS Database Structure
2 Screen-shots of Airbus Database folder/project structure

one in structures area
one in systems area
Will have to be taken from the actual Airbus Database
141 © Telelogic AB
Creating DOORS Modules for your team
• Module options decided by Team Leader
• Modules will be created by DOORS specialist
• Training database has been set up to provide a development

layer
• DOORS specialist also creates:

– Link Modules to hold the relationships (e.g. Satisfies, Verifies)
– Link Set pairings to enable DOORS to enforce:
• the types of links allowed
• the direction of links
• the agreed sources and destinations of links (e.g. from Output
Requirements module(s) to all valid input requirements modules)
142 © Telelogic AB
Requirements Module Views
Views looking at requirements at level Above • A1. Agree Input Requirements

Follows upward Satisfies links in the data model
• A2. Respond to
• B1. Main attributes
Views Based on attriButes at this level
• B2. Other attributes
• C1. Validated by
Views of Checking actions • C2. Verified by
Follows “horizontal” links in data model
• C3. Derived from design
material
Views looking at requirements at level below (Down) • D1. Allocate to
Follows downward Satisfies links in the data model • D2. Satisfied by
• U1. Checks
Utility views • U2. Attached Actions and
Decisions
143 © Telelogic AB
View rationale
Note Requirements at level above
All views are
filtered to Satisfies
show only
requirements A1 A2
Validated
Output Requirements by Validation
C1 C1 Actions
from Validates
requirements
this level
Verified
by Verification
B1 B2 C2 C2
Verifies Actions
Issues U1 requirements
and Derived
Decisions Refers to from Design
U2 C3 C3 Material
Derived
Requirements
Reference
D1 D2
Satisfies
Requirements at level below
144 © Telelogic AB
Requirements Validation Module Views
Views looking at requirements at level Above

Upward Satisfies links in the data model
• B1. Attributes
• C1. Validates Requirements

Views of Checking actions
Horizontal links in data model
Views looking at requirements at level below (Down)

Downward Satisfies links in the data model
Utility views
• U1. Checks
• U2. Attached Actions and
Decisions
145 © Telelogic AB
Product Verification Module Views
Views looking at requirements at level Above

Upward Satisfies links in the data model
• B1. Attributes
Views of Checking actions • C2. Verifies Requirements

Horizontal links in data model
Views looking at requirements at level below (Down)

Downward Satisfies links in the data model
Utility views
• U1. Checks
• U2. Attached Actions and
Decisions
146 © Telelogic AB
Exercise 11
Review Module Views

1. Switch to using the AS310 Project.
2. Open each of the RBE modules in turn.
3. Review the content of the module and See which attributes are visible and what each
column contains.
147 © Telelogic AB
Using DOORS for RBE
• Using the DOORS implementation for the RBE Method steps
– the approach follows the process sequence for developing
requirements and other information
– the Author Course excludes the creation of design material
148 © Telelogic AB
Author Process Activities
Customer
from [8] to
These
These
Requirements RBEare
activities
activities
from Agree Input Generic
not are Process
covered
not Verify own
in this in
covered
[1] [6]
course
this course
Requirements
from
other teams Verify
[2] [5]

[3] [4]
Customer
Product Management
Process [7] to
to from
from [9]
to from
level
level below
level below
below level
levelbelow
level below
below
149 © Telelogic AB
Activity 1
Agree Input Requirements
150 © Telelogic AB
Activity 1 – Agree Input Requirement
• For each source of requirements:

– from the level above (Task 1.1)
– from specialists (Task 1.2)
– from other teams (Task 1.3)
• Perform the following steps:
– Step1: Identify relevant requirements
– Step2: Create Placeholders for response
– Step3: Agree requirements identified
151 © Telelogic AB
Activity 1: Agree Input Requirements
Requirements
These modules
Input
InputRequirements
Requirements are outside your
from
Before
BeforeAgreement
Agreement area!
level above
Agree Requirements
from level above
[1.1]
Requirements Agree Requirements Input

from from specialist Requirements
specialist domains domains for this level
[1.2]
Requirements Agree Requirements

from from other teams
other teams [1.3]
152 © Telelogic AB
Activity 1: Step 1- Identify relevant requirements
• Find the formal modules that contain possible sources of
requirements for your team
• Open the module
• Select the view “D1. Allocate to”
• If pre-allocation has been done
– Allocation column contains information
• examine each requirement allocated to your team
• is the requirement relevant to your team?
– In any case:
• examine all the requirements to determine whether they are relevant
(whether or not they have been pre-allocated)
Input Requirements Modules

(from other teams:
Tasks 1.1, 1.2, 1.3
D1. Allocate to higher,
Step 1
specialist,
transverse)
153 © Telelogic AB
D1. Allocate to
Information here indicates that

pre-allocation has been done.
154 © Telelogic AB
Exercise 12
Review Allocation
1. Open the module "/AS310/2- Top Level Requirements/Top Level Requirements"
2. Select the view “D1. Allocate to”
3. Identify Requirements that have been allocated to the Mast.
4. Are these allocations relevant to the Mast "Team".
5. Identify requirements that have not been allocated to the Mast but should have been.
• set values for the Allocation attribute
6. Save and Close the Module
155 © Telelogic AB
Activity 1: Step 2 - Create Placeholders for
response
• For each relevant requirement that has been identified in Step 1,
create a placeholder in the relevant Output Requirements module
for your team and link the placeholder to the relevant Input
Requirement.
– Open the Output Requirements module
– Select the view “A1. Agree Input Requirements"
– Use the "Create Response” function from the RBE menu in Level n+1
using view “D1. Allocate to”.
• All allocated Input Requirements must be addressed.
• Place the response object in the most appropriate section of the Output
Requirements module.
• To do this select the object in the Output Requirements object that the new
object will either follow or be below
Output
Requirements
Tasks 1.1, 1.2, 1.3 Step 2 A1. Agree Input Requirements
Modules
(from team at this level)
156 © Telelogic AB
Create Response Placeholders
Output Requirement Placeholder

is created with link back to
Original Input Requirement
157 © Telelogic AB
Sequence of actions
• It is a good idea to create the structure of the output

requirements module before performing Step 2 of this task.
• The structure of the output requirements can be provided by:
– using a pre-defined structure from a template (prepared by the
DOORS specialist)
– creating the structure required by performaing steps 1 and 2 of
Task 3.1 (see later)
158 © Telelogic AB
Exercise 13
Creating Response Placeholders
1. Open the module Input Requirements Module

/AS310/2- Top Level Requirements/ Top Level Requirements in Exclusive edit mode
2. Select the view "D1.Allocate to"
3. Open the module Output Requirements Module

/AS310/2- Top Level Requirements/ System Design/System Design/Mast
Assembly/Mast Sub-system Requirements Select the view "A1. Agree Input
Requirements"
4. For each requirement allocated to the Mast
• use the create Response tool to create an empty Response object the Output
Requirements Module in an appropriate location.
159 © Telelogic AB
Activity 1: Step 3 - Agree requirements identified
• For each response object created in Step 2, determine whether the
wording of the Input Requirement and the value of attributes (Owner,
Stakeholders, MoPVer, Requirement Status) is acceptable.
• Open the Output Requirements module Select the view “A1. Agree
Input Requirements" also Navigate to the Input Requirement and
use one of the “B” views to inspect the relevant attributes.
– In the Output Requirement Module set the Alloc. Agreement attribute in
the response object (Output Requirement Module) to Accepted or
Rejected.
– If Rejected the rationale for rejection should be stated in the Object Text
that appears in the main column
Input
Requirements
B1. Main Attributes
Modules
Tasks 1.1, 1.2, 1.3 Step 3 B2. Other Attributes

Output
Requirements
A1. Agree Input Requirements Modules
160 © Telelogic AB
Agree Requirements Identified
“Alloc. Agreement” column set to

Accepted or Rejected.
161 © Telelogic AB
If Rejected then the Reason for

Rejection is entered into the
Main Text column.
162 © Telelogic AB
Exercise 14
1. Open the module Output Requirements Module

Requirements"
2. For each place holder requirement:
• Set the Accept/Reject status of the Allocation Agreement Attribute.
• here the status is set to Reject enter the reason fro rejection in the Main Text Column
3. Follow the outgoing link from the place holder object (to the input requirements module) and
select the view “D2. Satisfied by” in that module. Notice that the higher level team can see
your response.
4. Save Output Requirements Module. Close all modules.
163 © Telelogic AB
Activity 3
Generate and Validate Output Requirements
164 © Telelogic AB
Activity 3 – Generate & Validate Output
Requirements
• Task 1 – Create Output Requirements for Lower level
– Step 1: Decide Output Requirements module structure
– Step 2: Create Output Requirements structure
– Step 3: Generate Output Requirement responses
– Step 4: Logically order the Output Requirement responses
– Step 5: Identify Owner and Stakeholders
– Step 6: Identify design area responsible for each Output
Requirement
– Step 7: Set Requirement Status
• Task 2 - Create Output Requirements for Other Teams
– Steps 1 – 7: as Task 1
165 © Telelogic AB
Activity 3: Generate and Validate Output
Requirements
Input
Requirements Design Materials
for this level for this level
Seek Approval
for Output Requirements
Requirements from Validation
this level Plan
[3.5] from this level
Validate Output
Requirements from Requirements
this level Validation
[3.3] Evidence
Create Create
Approve Output from this level
Requirements
for lower level for other teams
from lower level
[3.1] [3.2]
[3.4]
Output
Requirements
forother
for Responsibility
forlevel
levelbelow for
from this level for level below
below for otherteams
other teams
teams
of this level
Requirements Requirements Responsibility

Validation Validation of level below
Plan Evidence
for level below for level below
166 © Telelogic AB
Activity 3: Tasks 1&2 – Create Output
Requirements
• Step 1: Decide Output Requirements module structure

• Open Output Requirements Module
• Select view “A2. Responds to”
• Deselect the Filter Option (so that all objects are visible).
• Decide on the structure that your team will use. Note that the module may
have been created with an initital structure already set from a template.
Output
Requirements
Tasks 3.1,3.2 Step 1 A2. Responds to
Modules
167 © Telelogic AB
Requirements
• Step 2: Create Output Requirements structure

• Select view “A2. Responds to” with filter de-selected
• Create the Heading Structure using Heading Objects
Output
Requirements
Tasks 3.1,3.2 Step 2 A2. Responds to
Modules
168 © Telelogic AB
A2. Responds to
Heading structure is
created to receive
requirements.
169 © Telelogic AB
Exercise 15
Creating Output requirements Structure
1. Open the module:

/AS310/2- Top Level Requirements/ System Design/System Design/Hull
Assembly/Hull Sub-system Requirements in Exclusive edit mode.
2. Select the view "A2. Responds" and deselect the filter option
• Create a Level 1 Heading Object as Section 1 “Hull Assembly”

• Create a Level 2 Heading Object as Section 2.1 “Hull”
• Create a Level 2 Heading Object as Section 2.2 “Floats”
• Create a Level 2 Heading Object as Section 2.3 “Seats"
• Create a Level 2 Heading Object as Section 2.4 “Centre Plate"
• Create a Level 2 Heading Object as Section 2.5 “Righting Handles"
• Create a Level 2 Heading Object as Section 2.6 “Towing Cleat"
170 © Telelogic AB
Requirements
• Step 3: Generate Output Requirement content

• Use view “A2. Responds to" to record the Requirement response text.
• Consider the following questions:
– Is the Output Requirement
the same as the Input Requirement?
derived from a design object?
– Is it necessary to generate more than one Output Requirement for an Input

Requirement?
– Can the more than one input requirement be satisfied by a single output
requirement?
Output
A2. Responds to
Requirements
Tasks 3.1,3.2 Step 3 C1. Derived from Modules
171 © Telelogic AB
Step 3: Generate Output Requirements
• Ifthe Output Requirement is the same as the Input
Requirement:
– use the RBE function “Copy Through link” to copy the
requirement text from the Input Requirement to the Output
Requirement (via the outgoing satisfies link).
172 © Telelogic AB
Step 3: Generate Output Requirement
• If the Output Requirement isresponses
different to the Input Requirement then:
– Type in the appropriate text for the requirement
OR
– Use the RBE function “Copy Through link” to copy the requirement text from the Input
Requirement to the Output Requirement (via the outgoing satisfies link).
– As necessary Amend text
173 © Telelogic AB
• If the Output Requirement is derived from a design object:

– link it to the relevant Design Material Reference object and use
the “C1. Derived from” view to check that the link has been
placed correctly.
174 © Telelogic AB
Types of Mappings Between Levels
Level n+1 Level n+1 Level n+1 Level n+1

requirement requirement requirement requirement
A B C D
Level n Level n Level n Level n

requirement requirement requirement requirement
P Q R S
Situation 1 Situation 2 Situation 3
175 © Telelogic AB
Exercise 16
Generate Output Requirement content
1. Open the module:

Requirements" in Exclusive edit mode.
2. For Place holder Requirements that have been agreed complete the following:
• Use the “Copy Through link” function to copy the requirement text from the Input
Requirement to the Output Requirement (via the outgoing satisfies link).
• Use copy and paste to copy placeholder object with requirements text. (Note how the
links are copied)
• Edit the text of the copied requirement.
176 © Telelogic AB
Requirements
• Step 4: Logically order the Output Requirement responses

• Use “A2. Responds to" view.
• Move the Output Requirements, if necessary, to create a more logical
sequence that will enhance readability and understandability of the set of
Output Requirements.
Output
A2. Responds to
Requirements
Tasks 3.1,3.2 Step 4
Modules
177 © Telelogic AB
Exercise 18
Logically order the Output Requirement responses
1. Open the module:

Assembly/Mast Sub-system Requirements Select the view "A2. Responds to" in
Exclusive edit mode.
2. Spend 5 minutes using drag and drop to move output requirement into different positions
within the Module structure
3. Save and Close the Module.
178 © Telelogic AB
Requirements
• Step 5: Identify Owner and Stakeholders

• Select “B1.Main Attributes" view
• Set the Owner and Stakeholders attributes.
Output
Requirements
Tasks 3.1,3.2 Step 5 B1. Main Attributes
Modules
179 © Telelogic AB
Identify Owner and Stakeholders
For each Requirement For each team the set of

there is one Owner but stakeholders must be set (by the
there can be several DOORS specialist) in the “rbe
Stakeholders Stakeholders” attribute type
180 © Telelogic AB
Exercise 19
Identify Owner and Stakeholders
1. Open the module:

Assembly/Mast Sub-system Requirements in Exclusive edit mode.
2. Select the view "B1. Main Attributes"
3. Spend 5 Minutes entering possible owners and stakeholders for the requirements.
181 © Telelogic AB
Requirements
• Step 6: Identify design area responsible for each Output Requirement

• Use Output Requirements Module, Decide which design areas could be
impacted by the set of Output Requirements
• Use “D1.Allocated to" view.
• If using pre-allocation record Allocation in the attribute (rbe Allocation).
• If not using pre-allocation then record responsibility in the Stakeholders
attribute (RBEStakeholders).
• Both attributes can be set to indicate the Allocation and Stakeholders but
remember to keep both lists updated as the project develops.
Output
Requirements
Tasks 3.1,3.2 Step 6 D1. Allocate to
Modules
182 © Telelogic AB
Identify design area responsible for each Output
Requirement
Requirement Allocation
to subsystems is
performed at each level
183 © Telelogic AB
Exercise 20
Identify design area responsible for each Output Requirement
1. Open the module:

2. Using the view "D1. Allocate to" set values for the Allocation attribute
1. The enumeration has already been set up with appropriate values
2. Note that this attribute can be multi-valued (since a requirement can be applicable to
more than one sub-system)
184 © Telelogic AB
Requirements
• Step 7: Set Requirement Status

• Use Output Requirements Module,
• Use “B1. Main Attributes" view.
• Set the requirement status of each requirement that has been through steps 1
to 6 above to Proposed.
Output
Requirements
Tasks 3.1,3.2 Step 7 B1. Main Attributes
Modules
185 © Telelogic AB
Set Requirement Status
The "B1. Main attributes"

view is used to set the status
of requirements to 'Proposed'
186 © Telelogic AB
Exercise 21
Set Requirement Status
1. Open the module:

2. Using the view "B1. Main Attributes" set Requirement objects Req. Status attribute to
Proposed.
187 © Telelogic AB
Activity 3: Task 3.3 – Validate Output Requirements
• Step 1: Set Requirements Validation Means
• Select view “C1. Validated by”
• Set means of Requirements Validation in the column “Means of Req. Val.”
Output
Requirements
Task 3.3 Step 1 C2. Validated by
Modules
188 © Telelogic AB
Set Requirements Validation Means
Use the "C1. Validated

by" view to set means
of Requirement
Validation - multi-valued
attribute
189 © Telelogic AB
Exercise 22
Set Requirements Validation Means
1. Open the module:

2. Using the view "C1. Validated by" set Requirement objects Means of Req. Val attribute as
you believe is appropriate.
190 © Telelogic AB
• Step 2: Plan Requirements Validation actions
• Open Requirements Validation Actions module
• Select view “C1. Validated Requirements”
• Create a new object for each validation action and place in the appropriate
section of the module
(The module has sections for each type of action)
• Create Traceability to associated Requirements (optional) and set the
Attributes values using the "B1. Attributes" view.
C2. Validated by Output Requirements Modules

Task 3.3 Step 2 (from team at this level)
B1. Attributes
Requirement Validation Actions Module
C1. Validated (at this level)
Requirements
191 © Telelogic AB
Plan Requirements Validation actions
Not Necessary to create links

At this point it is optional as to whether
links are created to the requirements to be
validated.
192 © Telelogic AB
Exercise 23
Plan Requirements Validation actions
1. Open the modules:

Assembly/Mast Requirements Validation Actions in Exclusive edit mode.

Assembly/Mast Sub-system Requirements in readonly mode.
2. Using the view "C1. Validated Requirements" create validation action objects that you
believe would be appropriate for the Requirements Means of Req. Val identified in the
previous exercise.
3. Save and Close the modules
193 © Telelogic AB
• Step 3: Do Requirements Validation actions
• When each action is completed record the results in the Requirements
Validation Actions module
• Open Requirements Validation Actions module
• Select view “B1. Attributes”
• Fill in the following columns:
– Date
– Validation Summary
• Create Traceability to Requirements

Output
B1. Main Attributes
Requirements
B1. Other Attributes Modules
D1. Allocate to
Task 3.3 Step 3 C2. Validated by Requirement
Validation
Actions
Module
B1. Attributes (at this level)
194 © Telelogic AB
Do Requirements Validation actions
Use "B1.Attributes" view

to complete the action and
record the results and
reference to evidence
195 © Telelogic AB
Exercise 24
Do Requirements Validation actions

Assembly/Mast Requirements Validation Actions in Exclusive edit mode.

Assembly/Mast Sub-system Requirements in read only mode.
2. Using the view "C1. Validated Requirements" create links as appropriate between
validation actions and requirements in the Output Requirements Module
3. Set the values of Date and Validation summary to appropriate values
196 © Telelogic AB
• Step 4: Set Validation status and baseline
– Use the “C2.Validated by” view to set the requirements status of each
validated requirement to “Validated”.
Output Requirements Modules

Task 3.3 Step 4 C2. Validated by
197 © Telelogic AB
Set Validation status and baseline
Use the "C1. Validated By" view

to set the Status to validated.
Then Baseline the module
198 © Telelogic AB
Exercise 25
Set Validation status and baseline

Assembly/Mast Sub-system Requirements in exclusive edit mode.
2. Using the view "C1. Validated by" set the status of Requirements Status for those
requirements with associated Validation actions validation date and validation summary.
199 © Telelogic AB
Activity 3: Task 3.4 – Approve Output requirements
from lower level
• Step 1: Approve Output requirements from lower level
– Review Output Requirements and associated Validation actions
– If Approval is granted issue documentary evidence of the approval (Held
external to DOORS)
Output
Requirements
D2. Satisfied by
Modules
A2. Responds to
Output
Task 3.4 Step 1 B1. Main Attributes
Requirements
B2. Other Attributes Modules
(from lower level teams)
C3. Verified by
Requirement
Validation
C3. Validated Requirements Actions
Module
(at this level)
200 © Telelogic AB
Approve Output Requirements from lower
Level
• Review lower-level requirements & traceability for:
– Completeness
– Correctness
– Requirement Status n-1 = Approved
• Authorize release of lower level requirements

– Baseline
201 © Telelogic AB
Approve Output requirements from lower
level
Use "D2. Satisfied by" view to

review the Output requirements
generated by the level below.
202 © Telelogic AB
Exercise 26
Approve Output requirements from lower level
1. Open the module

/AS310/2- Top Level Requirements/Top Level Requirements module in read only mode
2. Select the View "D2.Satisfied By"
3. Open the Module

/AS310/2- Top Level Requirements/System Design/Hull Assembly/Mast Sub-System
Requirements module in read only mode
4. Select the View "A2. Respond to"
5. Browse through the modules using the view to see what is linked to allocated requirements.
Check:
• Consistency between allocation and responses.
• Quality and completeness of responses.
6. Save and close the modules
203 © Telelogic AB
Activity 3: Task 3.5 – Seek Approval for Output
Requirements from this level
• Step 1: Seek Approval for Output Requirements from this level
– The output requirements from this level together with the information
generated to Validate this levels requirements are submitted for approval
by this levels approval authority.
– No Direct DOORS Actions
204 © Telelogic AB
Activity 6
Verify Own Products
205 © Telelogic AB
Activity 6 – Verify Own Products
• Task 1 – Create Verification Plan for Own Product Verification

– Step 1: Construct Product Verification Evidence Objects
• Task 2 – Create Own Product
• Task 3 – Create Verification Evidence for Own Product
Verification
– Step 1: Capture Product Verification Evidence
206 © Telelogic AB
Activity 6: Verify Own Product
Input Create
Requirements Verification Plan
for this level for Own Product Verification Plan
[6.1] for
Design Materials Own Product
for this level
Create
Own
Product
[6.2]
Own
Product
Create Verification Evidence

Verification Evidence for
for Own Product Own Products
[6.3] Responsibility
of this level
Product(s) Responsibility
Product
Product
from of level below
from
from
level
level below
level below
below
207 © Telelogic AB
Activity 6: Task 6.1 – Create Verification Plan for
Own Product Verification
• Step 1: Construct Product Verification Evidence Objects
– Use “C2. Verified by” view in Input Requirements module at this level to
understand how each requirement will be verified.
– Use “C2. Verified Requirement” view in Product Verification Action
module at this level to record the planned verification actions.
– Use both the “C2. Verified Requirement” and the “C2. Verified by” to
understand the need for special test rigs and to also to understand when
and how each requirement will be verified.
Output
Requirements
C2. Verified by
Modules
Task 6.1 Step 1
Product
Verification
C2. Verified Requirements Actions
Module
(at this level)
208 © Telelogic AB
Construct Product Verification Evidence
Objects
Use the "C2.Verified By" view in you

input requirements to determine the
mean of Product Verification.
209 © Telelogic AB
Construct Product Verification Evidence
Objects
C2. Verified Requirements
Use the "B1. Verified requirement" Product

Verification Action module at this level to record
the planned verification actions
210 © Telelogic AB
Exercise 27
Construct Product Verification Evidence Objects
1. Open the module

/AS310/2- Top Level Requirements/Top Level Requirements module in exclusive edit
mode.
2. Select the View "C2. Verified By" and filter on Requirements allocated to the Mast.
3. Review the requirements and set appropriate Means of Prod Verif.
4. Open the Module

/AS310/2- Top Level Requirements/System Design/Hull Assembly/Mast Product
Verification Actions module in exclusive edit mode
5. Select the View "B1. Verified Requirement"
6. Create Verification actions in the verification module and link these to requirements with
appropriate Means of Prod.Verif in the Input Requirement module.
7. Save and Close the modules.
211 © Telelogic AB
Activity 6: Task 6.2 – Create Own Product
– The Product is created!
– No DOORS Actions.
212 © Telelogic AB
Activity 6: Task 6.3 – Create Verification Evidence
for Own Product Verification
• Step 1: Capture Product Verification Evidence
– Use “C2. Verified Requirements” view to review associated requirement
– Use “B1. Attributes" view in Product Verification Action module to record
the evidence from the Product Verification actions.
C2. Verified Requirements Product

Task 6.3 Step 1 Verification
Actions
B1. Attributes
Module
(at this level)
213 © Telelogic AB
Capture Product Verification Evidence
B1. Attributes
Use view “B1. Attributes"

to record verification
evidence
214 © Telelogic AB
Activity 4
Verify Product from Lower level
215 © Telelogic AB
Activity 4: Verify Products from lower level
Output
Requirements Verify products from
from this level level below
[4.1]
Requirements
for lower level
Requirements
for other teams
Responsibility
of this level
Product Responsibility
ProductVerification
Verification Product
ProductVerification
Verification Product(s)
Product
Product of level below
Plan
Plan
Plan Evidence
Evidence
Evidence from
from
from
for
for lower
for lower level
levelproduct(s)
lower level product(s)
product(s) for
for lower
lowerlevel
for lower levelproduct(s)
level product(s)
product(s) level
levelbelow
level below
below
216 © Telelogic AB
Activity 4 – Verify Product from Lower level
• Task 1 – Verify Products from Level Below

– The Team at this level examine the evidence provided by the
Team at the level below (from the Verify Product from this level
process) to determine whether the product is adequate for
purpose.
– Use “C2. Verified by” view on lower level Output Requirements to
check that the verification actions are relevant and use the
“B1.Verified Requirements” view on the lower level Product
Verification Action module to check that the evidence of
verification is acceptable. Output
Requirements
– No Resulting DOORS Actions Modules
(from lower level teams)
C2. Verified by
Task 4.1 Step 1 Product
B1. Verified Requirements Verification
Actions
Module
(at lower level)
217 © Telelogic AB
Exercise 28
Capture Product Verification Evidence
1. Open the module

/AS310/2- Top Level Requirements/System Design/Hull Assembly/Mast Product
Verification Actions module in exclusive edit mode
2. Select the View “B1. Attributes"
3. Enter appropriate values in Verification Evidence Reference, Verif. Status, Product

Verification Summary attributes
4. Save and close the module
218 © Telelogic AB

DOORS RBE Authors Training v1-2 PDF

Uploaded by

Copyright:

Available Formats

You might also like

DOORS RBE Authors Training v1-2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DOORS RBE Authors Training v1-2 PDF

Uploaded by

Copyright:

Available Formats

Airbus A400M DOORS/RBE v1.

A Two-day course introducing the application of

• Course includes exercises using Airbus information structure

Setting the process Context

• Systems engineering is the branch of engineering concerned

Systems are defined via Development at

The same process is Development at

TLARs Final Product (Aircraft)

Level -1 Generate FRD Generate SRD

• Each level takes requirements from the level above

• Each development team may create requirements that must be

Requirements Development at Level n

Requirements Requirements Product(s)

Requirements Generate and Verify

Requirements Generate and Verify

• Each instance of the Generic Process:

Understanding the Tool

• Traceability from highest level requirements to implementation

• DOORS provides an extensive

• The database contains

• Operates like Windows Explorer

Additional Items inside Project or Folder

Browse the Database Using the DOORS Explorer

1. Launch DOORS and login to the database as user

2. Since this is your first time looking at this database,

3. To familiarize yourself with the DOORS Explorer

• A formal module is a container for information (requirements,

• Module Explorer allows you to navigate and see the structure

Explorer Normal Outline

Three opening modes:

• You can change edit mode without closing and re-opening

Working with Formal Modules

6. Now Close the module.

the Survive Accident section within Section

3.6. (Hint: Use +/- in the Explorer window)

Working with objects within the module structure

• Formal Modules are collections of Objects

An object is an object, no matter what

•Edit, Object Properties

A DOORS tree can be rearranged with Cut and Paste

If an object is cut but never pasted, then the following message

Delete will delete the objects on the clipboard

• A DOORS tree can be added to easily with Copy and Paste

• A DOORS tree can be trimmed with the Delete function

section from the module.

2. Move a section (e.g. 3.4) after the next one

3. Next, use cut and paste to move a section

(e.g. section 2) after another one, not

simultaneously visible on the screen (section

Working with your requirements and other

Tip Ctrl+H or Edit object heading Ctrl+T or Edit object text

Building a hierarchy of objects in DOORS is simple:

• When editing any object, use Ctrl+Enter to create a new text

• Objects should contain headings OR text (but not both)

There should be no more than ONE concept in an object!

Make text objects children of the heading objects under

Don’t make text objects children of other text objects.

All non-leaves will