< Previous | Next >

Lesson 1: Confirming and opening the Gateway from Rhapsody

This lesson guides you through how to establish the environment you need to work with Rhapsody® Gateway.
The Rhapsody Gateway is an add-on product to Rhapsody that requires a separate license. Gateway operates in the following environments:
Note: For a detailed explanation of the Rhapsody Gateway functionality, see the Gateway Add On user manual. To access the manual, from the Rhapsody Gateway main menu, click Help > Documentation > User Manual.

To confirm that the Gateway is installed:

  1. Create or open an existing C or C++ Rational® Rhapsody project.
  2. In Rational Rhapsody for C or C++, select the project, right click and select Rational Rhapsody Gateway from the drop down list. The Rhapsody Gateway Coverage Analysis View opens.

    main viewconfirming gate

    There are fundamentally two interfaces in Gateway, the main interface and the configuration dialog window. Each of these offers various views; a view is a way of presenting information to the user. Unique views offer different ways to view and manipulate the data. Coverage of a requirement means it is linked to an element.
    Note: For more details about the views and their tabs, see the Rational Rhapsody Gateway Add On user manual.
    • Management View – The default view of the main interface presents documents with their coverage information and general information about the project. There is a summary of violated rules if any and list of reports that can be generated for the project.
    • Coverage Analysis View – Allows you to select elements from a project document and displays requirement coverage one level upstream and one level downstream from the selected document.
    • Impact Analysis View – Displays for a selected element of a document, for all levels of covering elements, N-m, and for all levels of covered elements, N+p, from other documents as defined by the project.
    • Graphical View – Displays the documents of the projects with their links in a graphical format.
    • Requirement Details – Presents only one document, selected from the dropdown list in the upper left corner of the view. For this document, all the requirements, derived requirements, macro requirements, and entities are presented in the first column with dynamically created columns presenting a global view of attributes.
    The configuration window offers several configuration views which are as follows:
    • Project – Allows you to configure the project by specifying the documents to include, the type of each document, and the covering relationship between documents.
    • Types – Allows you to create new types or customize existing types for your project.
    • Snapshots – Allows you to create, manage and compare snapshots of your project.
    • Filters – Allows you to define custom filters to analyze requirements and only display requirements from documents that meet specific criteria.
    • Reports – Allows you to define new custom reports. You can generate a default report or a custom report using the Reports > Library Reports submenu on the main window.
    • Expressions – Allows you to test regular expressions used by Types to analyze the intermediate files.
    • XML - Allows you to test XML syntaxes used by Types to analyze the intermediate files.
    • Options – Allows you to set the default font for text in the application, set the password on the project, define environment variables, and other miscellaneous settings for the application.
    The Type of Analysis defines how to capture each element in a given analyzed file. It is chosen by the user and defined using the Types Editor when requirements are brought into the Gateway for analysis. The three default predefined types of analysis for DOORS® are the following:
    • Doors - The intermediate file is parsed in order to match a Regular expression to acquire the requirements information
    • Doors XML – The intermediate file is created in XML and XML is used to acquire the requirements information
    • Doors-Advanced – Rarely chosen as a type of analysis for DOORS; it is a customized type which uses an attribute ReqID as the requirement ID rather than the auto-generated DOORS Object ID. It contains a set of custom link types to identify Allocation, Satisfaction, Verification.
    An intermediate file is automatically saved for both the Doors and Doors XML options.

    Types can be viewed in the Types Editor by selecting Types from the configuration view or the main view.

    The predefined types are:
    • Section captures the structure of the analyzed input file
    • Macro-requirement supports hierarchy between requirements
    • Requirement captures all the requirements IDs
    • Entity forces analysis of specific elements in order to highlight elements without coverage
    • Reference captures the coverage links
    • Attribute captures requirement attributes
    • Reference attribute captures additional information applied on a coverage link
    • Link captures any other link besides a coverage link
    • Text captures a requirement text
    • Picture captures pictures and diagrams

    You can customize the requirements to be extracted using the Types configuration view. This can be done if the requirements are not imported as expected, or if the format of the requirements needs changing.

    A customized type of analysis can be created from scratch, however it is usually better to start with a default type and make only the appropriate changes.

< Previous | Next >

Feedback