Telelogic Doors Manuals

DOORS Extension Language (DXL) is a scripting language used to extend the functionality of IBM's Rational DOORS.^[1][2][3] This programming language is somewhat similar to C and C++.^[4] This language is specific to DOORS, and it has its own syntax, declaration, a forum to discuss the development,^[5] in addition to the specific reference manuals.^[6] DXL scripts were utilized to help the users of DOORS. Much of the native DOORS GUI is written in DXL. ^[7]

User Manual, FAA Requirements Quality Tool for IBM Rational Dynamic Object. It provides a detailed description of the 6 DOORS eXtension. Pivot and Hinged Doors by STANLEY Rush available in a variety of finishes and the quality craftsmanship for which STANLEY Rush is known. Balanced Doors by STANLEY Rush assist opening in specific site circumstances of wind tunnel or stack effect.

12 Nov HOTEL MANAGEMENT SYSTEM UML example designed by, last modified 12/11/ HOTEL MANAGEMENT SYSTEM usecase. You can edit this Class Diagram (UML) using Creately diagramming tool. Use case diagram for recruitment system.

DXL is used in the client-server based 'DOORS Classic'; it is not used in the newer web-based 'DOORS Next Generation'.

Usage of DXL[edit]

There are several of ways to use the DXL in the Rational DOORS.

1. 'Editor DXL' is DXL typed into the DXL Editor window and run from there. It may or may not also be saved in some file. This DXL typically has some user interface, if only print statements.
2. 'Menu DXL' is stored in Files and appear in DOORS windows, either the Explorer or open Module. The files must be of type .dxl, the files and the housing folders must be set up to display DOORS menus. It is otherwise like DXL Editor DXL.
3. 'Attribute DXL'^[8] is stored in an Attribute Definition and saved in a Module. It has the context of a single object. When the object-attr-value is retrieved (including being displayed) the code runs and calculates the value for that object. Calculated values are not saved in the module. Attr-DXL should be written to run without user interface and complete without any pauses.^[9]
4. 'Layout DXL' is defined in a Column and saved in a module's View. It runs for an object when that object's layout column is displayed in the GUI. It is otherwise similar to Attr-DXL. Layout DXL can be generated by the traceability Wizard, and can be converted to Attr-DXL. .^[10]
5. 'Batch DXL' is stored in files. It runs when DOORS is run in (background) batch mode as either 'Batch', 'DXL', or 'CLE' code defined in the batch process's command line. Since Batch mode as no GUI loaded, so DXL running in batch has some restrictions on what can run or how it is run, certainly it can have no GUI.
6. 'Trigger DXL' is defined in a 'Trigger' and stored either in a Module, a Project, or in the Database root. There is no native interface for Triggers; you would need some file based DXL to create or delete the Trigger. When the Trigger's specified Event occurs (such as Opening a Module) any Triggers associated with that event run in order of priority. There are some restrictions on what can run inside a Trigger, but it can and often does have some Interface (typically asking the user to proceed or not). 'Post' event trigger run after the event; 'Pre' event triggers run before the event and can prevent the event from happening. The most common types of events are opening/closing a module, selecting a new object, or saving an object-attr value. Dynamic triggers are not stored and exist only while DOORS is running on the client computer. A typical dynamic trigger would be a post-module-close trigger that will close a GUI (such as a 'print' dialog) associated with that module. A common mistake made while learning Triggers is to define a pre-module-close trigger that always prevents the module from closing.
7. 'Eval DXL' is invoked from other DXL and runs in its own context. It is generally reserved for nuanced advanced DXL. 'Top Eval' code gets deployed in the 'top context' and applies to all future DXL until DOORS closes.

DXL Script Extensions[edit]

DXL scripts are usually stored with extension of '.dxl', however they do use the library files with extension '.inc'.

'Hello, world' example[edit]

To print the 'Hello, World', the following code^[6] will be used,

DXL Editors[edit]

Sodius DXL Editor,^[11] built on top of Eclipse, is one tool which provides option to edit, browse, compile, execute, and debug DXL scripts. There are many open source and free editors like Notepad++ and jEdit that support DXL by custom properties.^[12]

References[edit]

1. ^Thurimella, Anil Kumar; Janzen, Dirk (2011). metadoc Feature Modeler A Plug-in for IBM Rational DOORS(PDF) (Thesis). 2011 15th International Software Product Line Conference.
2. ^Rahman, Anisur; Amyot, Daniel (2014). 'A DSL for importing models in a requirements management system'. 2014 IEEE 4th International Model-Driven Requirements Engineering Workshop (MoDRE): 37–46. doi:10.1109/MoDRE.2014.6890824.
3. ^Dale, Chris; Anderson, Tom (2009). Safety-Critical Systems: Problems, Process and Practice: Proceedings of the Seventeenth Safety-Critical Systems Symposium Brighton, UK, 3 - 5 February 2009. Springer Science & Business Media. pp. 80–89. ISBN9781848823495. Retrieved 28 December 2018.
4. ^'User Manual, FAA Requirements Quality Tool (FRQT) For The IBM Rational Dynamic Object Oriented Requirements System (DOORS), Version 1.0'(PDF). March 2017.
5. ^'Forum: Rational DOORS DXL'.
6. ^ ^ab'The DXL Reference Manual'(PDF).
7. ^'LESSONS LEARNED IMPLEMENTING DOORS IN A CITRIX ENVIRONMENT'(PDF).
8. ^'DXL attributes and layout DXL columns'.
9. ^'DXL attributes and layout DXL columns'.
10. ^'Layout DXL'.
11. ^Sodius DXL Editor
12. ^DXL Editors

External links[edit]

• Introduction to IBM Rational DOORS eXtension Language (DXL).

Telelogic AB was a software business headquartered in Malmö, Sweden. Telelogic was founded in 1983 as a research and development arm of Televerket, the Swedish department of telecom (now part of TeliaSonera). It was later acquired by IBM Rational, and exists under the IBM software group.^[1]

Telelogic had operations in 22 countries and had been publicly traded since 1999. On June 11, 2007, IBM announced that it had made a cash offer to acquire Telelogic.^[2] On August 29, 2007, the European Union opened an investigation ^[3] into the acquisition. On March 5, 2008, European regulators approved the acquisition of Telelogic by the Swedish IBM subsidiary Watchtower AB.^[4] On April 28, 2008, IBM completed its purchase of Telelogic.^[5]

Former Products[edit]

• - System for management of product and project portfolios.
• DOORS - Requirements tracking tool.
• System Architect - Enterprise Architecture and Business Architecture modeling tool.
• Tau - SDL and UML modeling tool.
• Synergy - Task-based version control and configuration management system.
• Rhapsody - Systems engineering and executable UML modeling tool.
• DocExpress - Technical documentation tool, discontinued after the acquisition and superseded by Publishing Engine.
• Publishing Engine - Technical documentation tool

All of these products have been continued under IBM's Rational Software division in the systems engineering and Product lifecycle management (PLM) 'solutions' software line.

Acquisitions[edit]

Telelogic acquired the following companies between 1999 and 2007:

References[edit]

1. ^'IBM Completes Acquisition of Telelogic AB' (Press release). IBM. 2008-04-03. Retrieved 2009-05-29.
2. ^'Telelogic's Board of Directors recommends the offer from IBM'(PDF) (Press release). Telelogic AB. 2007-06-11. Retrieved 2008-07-21.
3. ^'EUROPA - Competition - Cases from 4700 to 4749'. Retrieved 2008-07-22.
4. ^'Rapid - Press Releases - EUROPA' (Press release). EUROPA. 2008-05-03. Retrieved 2008-07-21.
5. ^'IBM Acquires Telelogic'. CXO Today. ITNation India Pvt. Ltd. Apr 28, 2008. Retrieved 2008-07-21.
6. ^'Telelogic, the world leader acquires Verilog, the first runner-up'. CisionWire. Cision. Dec 22, 1999. Retrieved 2011-06-11.