© Jeremy.Dick@telelogic.com Requirement Boilerplates in DOORS jeremy.dick@telelogic.com Version 2.0

© Jeremy.Dick@telelogic.com

Requirement Boilerplates in DOORS

jeremy.dick@telelogic.com

Version 2.0

© Jeremy.Dick@telelogic.com

Introduction

• Instructions on how to use DXL customisation to support requirements boilerplates in DOORS

© Jeremy.Dick@telelogic.com

Set up

• Close down any DOORS client that may be running (the server is unaffected)

• Extract the files from boilerplatedxl.zip into doors/lib

• (DOORS 5 only) Place the following line at the end of doors/lib/dxl/startup.dxl:#include <addins/BoilerPlate/include/bp_startup_doors5.dxl>

© Jeremy.Dick@telelogic.com

Check Installation (1)

• Restart DOORS

• If you get DXL errors, then the installation was unsuccessful

• If in DOORS 5, check the entry in startup.dxl

• Otherwise just try again more carefully!

© Jeremy.Dick@telelogic.com

Restore the example data

• From the DOORS database window, do File->Restore->Project…

• Find boilerplates DOORS x.dpa (where x = your DOORS version)

• Do the restore

© Jeremy.Dick@telelogic.com

Checking Installation (2)

• Open the module “Car User Reqs” from the BoilerPlates project.

• If you get DXL errors, then the installation was unsuccessful

• If in DOORS 5, check the entry in startup.dxl

© Jeremy.Dick@telelogic.com

Checking Installation (3)

• If the “BoilerPlates” menu is not visible in the “Car User Reqs” module, then the installation was unsuccessful.

• Please check that you have installed into the right location, and try and again.

© Jeremy.Dick@telelogic.com

Getting started

• Examine the module “Car User Reqs”

• An outgoing link attaches a requirements to its boilerplate in the “Common Boilerplate Repository” module

• The Object Text contains the completed boilerplate

© Jeremy.Dick@telelogic.com

Editing Requirements

• Select a requirement with an outgoing link

• Invoke “Boilerplates->Edit attributes”

© Jeremy.Dick@telelogic.com

Editing Requirements

© Jeremy.Dick@telelogic.com

Editing Attributes

• This tool shows the complete requirement text with attributes highlighted in blue.

• You can edit the attributes by double-clicking in them:

© Jeremy.Dick@telelogic.com

Attribute Editor• Here you either enter a

new value for the attribute, or select a value from the list of those used in other requirements

© Jeremy.Dick@telelogic.com

Boilerplates and Attributes

• The values entered are held in object attributes:

© Jeremy.Dick@telelogic.com

The Boilerplate Module

• Open the Boilerplate module:

© Jeremy.Dick@telelogic.com

The Boilerplate Module

• The boilerpate is held in Object Text

• Attributes are used to classify the kind of statement contained in the boilerplate

© Jeremy.Dick@telelogic.com

Creating a New Requirement

• Go back to the “Car User Reqs” module.

• Create an empty object at the end of the module.

• Invoke the boilerplate “Edit attributes” tool:-

© Jeremy.Dick@telelogic.com

Linking to a boilerplate

• Click “Start Link” to link to a boilerplate, then select the boilerplate object in the Boilerplate module, then click “End Link”:

© Jeremy.Dick@telelogic.com

New boilerplate

• This has created a link to the boilerplate

• Now edit the attributes by double-clicking as before

© Jeremy.Dick@telelogic.com

New Requirement Complete

• The new requirement is stored in Object Text, and the other attributes values set

• If you want to see the boilerplate in the requirements module, use the standard DOORS Analysis Wizard to display the Object Text from the boilerplate repository

© Jeremy.Dick@telelogic.com

Changing Boilerplates

• If you change a boilerplate in the boilerplate module, requirements that use that boilerplate can be updated in each requirements module

• Invoke “Boilerplates->Refesh requirements from boilerplates”

• (Rich Text is taken into account)

© Jeremy.Dick@telelogic.com

Sub-Clauses

• Boilerplates can be used for sub-clauses of requirements

• This allows traceability within complete requirements statements

• Place these as children of the main requirement so that the relationship between clauses is managed

© Jeremy.Dick@telelogic.com

Tracing to Requirements• When you link to a sub-clause, you may

like to see the complete requirement (not just the sub-clause) in traceability columns

• To achieve this, the tool“Boilerplates->Create boilerplate attributes…”creates a DXL attribute in the requirements module than contains the complete requirement

• Invoke this, and display the attribute “Complete Requirement” in a column:

© Jeremy.Dick@telelogic.com

© Jeremy.Dick@telelogic.com

Traceability Columns

• Now the Analysis Wizard can be used to create traceability columns that display the Complete Requirement attribute

© Jeremy.Dick@telelogic.com

Tell me about it!

• Please tell me what you think about the tool!

• Email me: jeremy.dick@telelogic.com