© 2013 IBM Corporation

DOORS Hints and Tips: What happens when you open a module?

Hazel Woodcock, IBM Rational

© 2013 IBM Corporation

Enabling Product and Service Innovation | Rational

Step 1: Get the data from the server

DOORS Database

Server

DOORS Client

Full current version of Module including history

Full current version of module held locally and only passed back to the database server on save.

Exclusive Edit: Module locked and only accessible read onlyShareable Edit: Module only accessible in shareable edit or read only. Sections only locked when requested from client.Read Only: Module remains fully accessible

12

6

39

© 2013 IBM Corporation

Enabling Product and Service Innovation | Rational

Step 2: Client processing

TriggersTriggers set to fire on Module open will fire

DXL Scripts will be executed.

OpenModule open and available to user

Exclusive edit, shareable edit, or read only.

Load View Default view loadedAny layout DXL in default view will be executed.

DXL Attributes

All DXL Attributes in current view calculated

Any Attribute DXL in default view will be executed.

Links No activity No processing overhead

12

6

39

12

6

39

12

6

39

© 2013 IBM Corporation

Enabling Product and Service Innovation | Rational

Step 3: Reducing module open times

TriggersTriggers set to fire on Module open will fire

Remove any unnecessary scripts with triggers

BaselinesBaseline regularly to reduce the data being transferred.

Only history since the last baseline is loaded.

Default View Default view loadedKeep the default view simple with no DXL attributes or layout DXL.

Shareable Edit

Shared sections increase the module open time

Use shareable edit sparingly and keep the number of sections to a minimum

Module SizeKeep module sizes small

Link to OLEs in CCM tool, keep the contents to a single topic. Consider splitting modules if there is a performance problem.

12

6

39

12

6

39

12

6

39

12

6

39

12

6

39