DOORS(Dynamic Object Oriented Requirement System) Tool

Presenter: Sandhya Vijayakumar

Date: June 2020

1
Overview
• Introduction of Doors
• Key Concepts
• Creating documents in Doors
• Best practices
• Doors tool linking with other tools

2
DOORS - Introduction

3
➢Rational Doors is an IBM developed tool.
➢Dynamic Object Oriented Requirements System (DOORS) (formerly known as Telelogic DOORS) is a requirement
management application that contains features for capturing, tracking, and managing user requirements. It is a
client–server application, with a Windows-only client and servers for Linux, Windows, and Solaris. There is also a
web client, DOORS Web Access.
➢Rational DOORS has its own programming language called DOORS eXtension Language (DXL).
➢Rational DOORS Next Generation is now developed on the IBM Jazz platform. The Jazz platform leverages Open
Services for Lifecycle Collaboration (OSLC).
➢Rational DOORS has an open architecture that supports third-party plugins.

4
DOORS - Requirement Engineering

5
Requirement Engineering & Doors
High Quality Requirements must be:

correct modifiable non-ambiguous

consistent traceable understandable
complete verifiable annotated

Requirements Engineering
Requirements Development Requirements Management

Change Control
Elicitation

Version Control
Analysis
Tracing & Impact Analysis
Modeling & Specification

Status Tracking
Verification & Validation

Best Practices, Methods, Tools and Processes for Requirements Engineering

6
Doors user must have:

➢Basic knowledge of requirements management principles

➢How to create, organize and manage your own project data in DOORS
➢How to apply DOORS to manage requirements, Deign, Testcases and Test reports.

➢Aspects of Requirements Management:

❑ Traceability
❑ Change Control & History
❑ Verification & Validation

7
Challenges in Requirements stage

➢Requirements must be communicated to all stakeholders associated with the project

➢Requirement documents drive the development process
➢Requirement documents are the control mechanism for the entire lifecycle
➢Analyze requirements coverage to ensure customer satisfaction or compliance to regulations/contracts
➢Requirement based testing is critical to ensure the product is satisfying the user needs.
➢Design and implement system/software directly from a validated requirements-based model to ensure the right system is built
➢Communicate design to all project stakeholders

8
Impact of Requirements problems?
As much as a 200:1 cost savings results from finding errors in the requirements stage versus finding errors in the
maintenance stage of the software life-cycle.

56% of all bugs can be traced to errors made during the requirements stage

9
A Simple Project Model
Functional requirements Design specifications
User
requirements

Satisfies Satisfies
Tests

Tests

Tests
Standards

Acceptance tests Functional tests Unit tests

10
Key Concepts

11
➢ User login has an individual username and password.
➢ Access controls are applied based on user login

Login page

Home page

12
DOORS Database Explorer - Database View

Database

Projects
Modules and Documents

Folders
DOORS Database Explorer:
• Allows you to organize your data in the same way that you
might organize it in MS Windows Explorer –> explorer type
navigation

13
DOORS Explorer – Project view

Projects

** The above screen shows the project view and it only shows the projects which an individual user have access

14
 Using Projects and Folders

Folders
 Use a Folder to:
Projects
– Create structure and
organize it according to a
specific project

 Use a Project to:

– Organize data related
to a specific project
or product

15
Project and Folders in DOORS Database Explorer
➢You can rename Folders and Projects

▪ Folder names must be unique within the folder

▪ Project names must be unique within the database

➢You can Move, Cut, Copy Paste Folders and Projects in the DOORS Database
➢You can Restrict who can move, cut, copy, paste Folders and Projects

Ctrl+V, Ctrl+C, Ctrl+X, drag-drop move, Ctrl+drag-drop copy etc.. Options are possible

16
Creating Documents in DOORS

17
Documents in DOORS are referred to as “Formal Modules” or simply “Modules”
• A module is a container for information (requirements, graphics, etc.)
• Typically structured as a document
• May be structured as a data file

18
Default Document Display

• On the Left: Module Explorer allows you to navigate and see the structure
• Right hand pane shows Heading and Text in a Document-Centric Format – the way
you’re used to

19
What is an Object?

➢ Documents (or Formal Modules) are collections of Objects

➢ Objects may be used for
• Requirement text
• Headings
• Graphics
• Any other information

20
Creating an Object Structure in Module

CTRL+N: To Create a new

Object at same Level

CTRL+L: To Create a new

Object One Level Down

Building a hierarchy of objects in DOORS is simple:

• Current object is always the insertion point
• Choose position of new object relative to current
21
Objects Have Properties

Detailed information about an object

1. General – Heading, Short Text, Object Text values for the
object
2. Access – View or set access rights
3. History – log of changes to the object
4. Attributes – attribute values for the object
5. Links – relationships to other objects

** Right click on the object and select Properties

22
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

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

23
Object Structure Guidelines

Text View Graphics View Explorer View

Title
Text
1 Heading
Heading Text
Text Heading
1.1 Heading Text
Text
Text
Title
Heading
Text
Text
2 Heading
Text
Text Heading Heading
Text Text

3 Heading All non-leaves will be heading only

3.1 Heading

Text
All leaves will be text only
Text

24
What is an Attribute?

 Attributes are additional defined characteristics of a requirement; they provide essential information in
addition to requirement text
Source Who specified this requirement?
Priority What is the priority of this requirement?
Verifiability Is the requirement verifiable?
Accepted Has this requirement been accepted by the developers?
Review Review status of this requirement
Safety Is this a safety-critical requirement?
Comments Any comments on the requirement to clarify its meaning
Questions Any questions that must be clarified with the source

 You can define attributes that will support your process and make your database more productive for you

**User can decide on the Attributes to be used

25
Attribute Have:

Attribute Name

Type
Access
Definition

Change
Characteristics
Default Value

Attributes can be assigned to:

Documents (Modules), Objects (Requirements), and links

26
Object Attributes

Attributes allow additional information to be associated with each requirement

Attributes can also be defined for Documents (Modules) and Links

27
Filters

• Filters allow you to reduce the information in the display to an essential set that interest you
• Filters support your analysis of the requirements

28
Filters are used to:

 Limit the display to visualize specific information

– High Risk Requirements
– Requirements in Build 3.0
– Requirements assigned to a specific individual
– Requirements that failed test
 Set a specific value of an attribute to many objects at once.
– You may want to set all requirements that have the word “safe” in them to “Priority = High”

Filters are saved when you save the View whereas, Views are Dynamic Reports of your Data

29
Drop-downs & Views

30
Drop-downs

To set dropdown Go to Edit-> Types then new

create the color code or the drop downs which want to be set.

31
 Step 1

Step 2

32
Views

Saving a View
View
Drop-Down Menu

 Views define the layout of your data

– Columns, filters, sorts, window position, etc.
 Drop-Down list on left side of tool bar for easy access to your views
 Defaults for Users or Documents can be set

33
Using Views

 Views can be used to

– Save filter or sorting conditions
– Save a display that contains attribute
– Save a display that contains traceability
– Save a display that contains information of specific interest to certain users (e.g., managers,
test engineers, reviewers, coders)
– Save window positions to facilitate linking

34
Traceability and links

35
Links in DOORS

 A relationship between two requirements (objects) is established using a ‘link’

 Links can be followed in either direction
 Bi-directional 1 to 1, 1 to n, n to 1, & n to n are supported

“To” (Target)
“From” (Source)
36
Linking & Traceability

For Traceability
Automation see

Drag-and-drop to
link within a
document . . .
. . . or from
document to
document.
…or across
projects.

37
Use traceability to perform analysis

 Coverage analysis
 Impact analysis
 Derivation analysis

38
To get traceability reports

• Step 1: Go to analysis-> wizard

• Step 2: In the wizard window select for in link or outlink
• Step 3: Select for All modules and then Object text has to be selected mandatorily
• Step 4: Then select next
• Step 5 : You will get the info of the links in a separate column
• Step 6: You can export the report in excel format

39
Remaining Features

40
Edit and baseline

41
Sharable Mode Operation: Defining Shareable Sections

 Shareable Edit is based on Sections

 Sections are defined in the Exclusive Edit mode

42
Prioritizing, categorizing, or assigning requirements

• Annotate requirements with an “unlimited”

set of user-defined attributes
• Standard NOS template

Analyze requirements through multiple views

43
Tracking changes

Change History

Previous
Baseline

Current Version

44
About tracking changes

45
Lock and Unlock in the feature of a Module

46
Procedure to Import a DMA file

To import a DMA file go to file-> then select restore option -> choose
either project or module

47
Creating New Documents (Formal Modules)

48
Document/Module Paradigm
Document Default Display

49
Displayed Information

Column Heading

Unique Identifier
Paragraph Number
Link
Object Heading Indicators

Current
Selection
Object Text

Change Bars: Read-Only

Red: unsaved change
Yellow: changed since baseline
Green: no change since baseline

50
 Current Object

Just Right-click, and select

Delete – parents and children
Are deleted

51
Continuation….

To make display the deleted object: To make display the object right click the object and do undelete option

52
Inserting Tables

To insert table

Tables can be inserted with after

or below option

53
OLE Support

DOORS provides OLE support on Windows

• You can embed an OLE object

• Use edit-in-place to make changes after embedded

• You can link an OLE object

• Changes are made to the file in its original location

Embed or link in a DOORS object:

• Table, Spreadsheet, Equation, Chart/graph
• Picture, Audio clip, Video clip

The choice is only limited by what is installed on your system

54
OLE Link or Embedding

• Select insertion point in module

• Insert / OLE object
– Create New
– Select type
– Create from File
– Browse to select
– ‘Link’ or embedd
• Double-click
– Launches source application

• Maintain as any DOORS object

– Move, Copy
– Attributes
– Link

55
Export from Word to DOORS

•Initiate from Word

•Export to current Project or Folder in DOORS

56
Incorporating existing documentation

MS-Word

MS-Word RTF

OLE

Automated
import
Spreadsheet

FrameMaker

Migrating existing project information to DOORS

57
Publishing and Report Generation

Printer
Word
PowerPoint
Microsoft
Excel
Outlook
Automated HTML
report RTF MS-Word
generation
from any
view Spreadsheet

FrameMaker

Publish reports with the required content and format

58
Printing Documents Directly from DOORS

 Documents can be printed directly from DOORS

 The current view is printed
– All objects in the current view
– All attributes currently displayed

 Page Layouts can be created and saved

 Reports combine Views and Page Layouts

59
Print Preview

60
The Best Practices Effect: Early Defect Prevention & Reduction

Current

Defect
Rate of Discovery

Prevention
Proposed & Reduction

Requirements Design & Release Release

Build to Test to Field
TIME

Source*: Boehm, Barry. Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, Inc. 1981.
Boehm, Basili. “Software Management.” IEEE Computer, January 2001.

61
Doors tool linking with other tools

62
Linking Doors with Reqtify tool
Step2: Goto connections tab and right click
Step1: Select options DOORS and add a new profile

Step3: Add the server details

63
Linking Doors requirement with Matlab

• By linking Matlab model with requirements in Doors tool we can ensure 100% traceability
• The linking from Matlab tool to Doors is done by running a script.

64
65
Sandhya Vijayakumar
Quality - Automotive Business Unit
TATA ELXSI, Yamuna Building, 4th Floor,
Techno park Phase III Main Rd, Techno park Campus,
Thiruvananthapuram, Kerala 695581
Tel: +91 471 6660552 | Cell +91 9567456034
www.tataelxsi.com

Confidentiality Notice
Thi s document a nd all i nformation contained herein is the sole property of Ta ta Elxsi Limited and s hall not be reproduced or
di s closed to a third party wi thout the express written consent of Tata Elxsi Limited.
66