Serena Prototype ComposerIntegration Guide for

Serena Dimensions RMSERENA PROPRIETARY AND CONFIDENTIAL INFORMATION

Copyright 20012007 Serena Software, Inc. All rights reserved.This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Serena. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification.This document contains proprietary and confidential information, and no reproduction or dissemination of any information contained herein is allowed without the express permission of Serena Software.The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Serena. Serena assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.

TrademarksSerena, TeamTrack, StarTool, PVCS, Collage, and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Dimensions, Professional, Tracker, Version Manager, Builder, Meritage, and Mover are trademarks of Serena Software, Inc.Microsoft, Visual Studio and the Visual Studio logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

U.S. Government RightsAny Software product acquired by Licensee under this Agreement for or on behalf of the U.S. Government, its agencies and instrumentalities is "commercial software" as defined by the FAR. Use, duplication, and disclosure by the U.S. Government is subject to the restrictions set forth in the license under which the Software was acquired. The manufacturer is Serena Software, Inc., 2755 Campus Drive, San Mateo, CA 94403.

Part Number: MA-COMRTM-003

Publication date: December 2007

Table of Contents

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Book Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Using the Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9What is the Prototype Composer with Dimensions RM Integration? . . . . . 10What Do I Have to Install to Enable the Integration? . . . . . . . . . . . . . . . 10

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10How Does the Prototype Composer with Dimensions RM Integration Work? 10

Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10About Mapping Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Publishing to Dimensions RM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Publishing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Publishing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Publishing Model Items and Scenarios . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Setting Up the Integration . . . . . . . . . . . . . . . . . . . . . . 15Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Dimensions RM Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16What Happens During the Installation?. . . . . . . . . . . . . . . . . . . . . . . . . 16Enabling the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Configuring the Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuring MIME Types and Custom Headers . . . . . . . . . . . . . . . . 17Configuring the rtmBrowser Virtual Directory . . . . . . . . . . . . . . . . . 17

Verifying the Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Testing the Connection in Prototype Composer . . . . . . . . . . . . . . . . . . . 18Disabling the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3 Using the Integration . . . . . . . . . . . . . . . . . . . . . . . . . 19Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Configuring Dimensions RM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 20Creating a Dimensions RM Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About Publishing to Dimensions RM . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Publishing Items to Dimensions RM . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Publishing From Project Requirements View . . . . . . . . . . . . . . . . . . 22Publishing From the RM Publisher Task Pane . . . . . . . . . . . . . . . . . 23

Viewing a Dimensions RM Requirement Attachment . . . . . . . . . . . . . . . . 23Importing Requirements from Dimensions RM. . . . . . . . . . . . . . . . . . . . 24Integration Guide for Serena Dimensions RM 3

Table of ContentsSynchronizing Published Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 25

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Serena Prototype Composer 2.4

WelcomeThe integration of Serena Dimensions RM and Serena Prototype Composer combines the functionality of Prototype Composer as an application prototype and requirement visualization tool with the functionality of Dimension RM as a requirements management solution.

The purpose of the integration is to enable Prototype Composer to publish requirements and associated project model items, scenarios, and documents to Dimensions RM.

These instructions assume that Prototype Composer is installed locally and that you have access to the Dimensions RM server. For information pertaining to system requirements for and the installation of Prototype Composer, see the readme file. For information on installing Dimensions RM, see the Serena Dimensions RM Installation Guide.

Objective

This book describes the process of integrating Dimensions RM and Prototype Composer to manage the exchange of requirements.

Audience

This book has two primary audiences:

Systems integrators, administrators, and those who install and configure the integration between Dimensions RM and Prototype Composer.

End users, such as project managers and developers, who use Prototype Composer to create requirements and associated application model prototypes.

The instructions in this book assume end user and administrative level understanding of Prototype Composer and Dimensions RM. For more information about these products, consult the documentation provided for each product.

Book Organization

The chapters are organized in this book as follows:

Chapter Contents

Overview Description of the installation and installation prerequisites and system requirements

Setting Up the Integration

Integration installation and Web services configuration

Using the Integration Using the integrationIntegration Guide for Serena Dimensions RM 5

Related Documents

For related information, see the following documentation.

Serena Dimensions RM Administrators Guide

Serena Dimensions RM Installation Guide

Serena Dimensions RM Users Guide

Serena Prototype Composer Getting Started Guide

Using the Manuals

The Serena online manuals use the Adobe Portable Document Format (PDF). To view PDF files, use Adobe Reader, which is freely available from www.adobe.com.

This section highlights some of the main Reader features. For more detailed information, see the Adobe Reader online help system.

The online manuals include the following features:

Bookmarks. All of the manuals contain predefined bookmarks that make it easy for you to quickly jump to a specific topic. By default, the bookmarks appear to the left of each online manual.

Links. Cross-reference links within an manual enable you to jump to other sections within the manual and to other manuals with a single mouse click. These links appear in blue.

Printing. While viewing a manual, you can print the current page, a range of pages, or the entire manual.

Advanced search. Starting with version 6, Adobe Reader includes an advanced search feature that enables you to search across multiple PDF files in a specified directory. (This is in addition to using any search index created by Adobe Catalogsee step 3 below.)

To search within multiple PDF documents at once, perform the following steps (requires Adobe Reader version 6 or higher):

1 In Adobe Reader, select Edit | Search (or press CTRL+F).

2 In the text box, enter the word or phrase for which you want to search.

3 Select the All PDF Documents in option, and browse to select the folder in which you want to search.

4 Optionally, select one or more of the additional search options, such as Whole words only and Case-Sensitive.

TIP Be sure to download the full version of Reader. The more basic version does not include the search feature.6 Serena Prototype Composer 2.4

Typographical Conventions5 Click the Search button.

Typographical Conventions

The following typographical conventions are used in the online manuals and online help. These typographical conventions are used to assist you when using the documentation; they are not meant to contradict or change any standard use of typographical conventions in the various product components or the host operating system.

NOTE Optionally, you can click the Use Advanced Search Options link near the lower right corner of the application window to enable additional, more powerful search options. (If this link says Use Basic Search Options instead, the advanced options are already enabled.) For details, see Adobe Reader's online help.

Convention Explanation

italics Introduces new terms that you may not be familiar with and occasionally indicates emphasis.

bold Emphasizes important information and field names.

UPPERCASE Indicates keys or key combinations that you can use. For example, press the ENTER key.

monospace Indicates syntax examples, values that you specify, or results that you receive.

monospaced italics

Indicates names that are placeholders for values you specify; for example, filename.

monospace bold

Indicates the results of an executed command.

vertical rule |or angle bracket >

Separates menus and their associated commands. For example, select File | Copy means to select Copy from the File menu.Also, indicates mutually exclusive choices in a command syntax line.Integration Guide for Serena Dimensions RM 7

8 Serena Prototype Composer 2.4

Chapter 1Overview

This chapter contains the following sections.

What is the Prototype Composer with Dimensions RM Integration? 10

What Do I Have to Install to Enable the Integration? 10

How Does the Prototype Composer with Dimensions RM Integration Work? 10

Publishing to Dimensions RM 12Integration Guide for Serena Dimensions RM 9

Chapter 1 OverviewWhat is the Prototype Composer with Dimensions RM Integration?

This integration of Serena Prototype Composer and Serena Dimensions RM is an environment used to manage and track the exchange of project requirements, model items, scenarios and documents between Prototype Composer and the Dimensions RM repository.

What Do I Have to Install to Enable the Integration?

Requirements

The following main components make up the Prototype Composer with Dimensions RM integration.

Serena Dimensions RM 10.1.1 or later

Serena Prototype Composer 2.4 or later

Microsoft Internet Information Services (IIS)

For details on system requirements for the Prototype Composer with Dimensions RM integration, see the readme file.

See Chapter 2, "Setting Up the Integration" for details on enabling the integration.

See the Serena Dimensions RM Installation Guide for details on installing Dimensions RM.

How Does the Prototype Composer with Dimensions RM Integration Work?

This section describes how Prototype Composer and Dimensions RM work together in the integration.

Connectivity

Communication between Prototype Composer and Dimensions RM is established through Web services enabled by Microsoft Internet Information Services (IIS), which is running on the Dimensions RM server. Web service settings are created automatically by the Dimensions RM installer. See Chapter 2, "Setting Up the Integration" for more information.

A Prototype Composer project is associated with a Dimensions RM project by specifying the Dimensions RM server URL, database, and project in the Project Integrations tab of the Project Information dialog box in Prototype Composer project view. The Dimensions RM server URL must be the address of the Web services endpoint. See Chapter 3, "Using the Integration" for information on specifying these settings. 10 Serena Prototype Composer 2.4

How Does the Prototype Composer with Dimensions RM Integration Work?Connectivity settings entered in Prototype Composer are stored in the project (.bap) file. Because of this, when you share the Prototype Composer project file, the Dimensions RM integration settings are maintained.

About Mapping Requirements

Prototype Composer stores requirements that are instances of requirement types that are defined in Prototype Composer. Dimensions RM stores requirements that are instances of defined Dimensions RM classes. Before you can publish requirements from Prototype Composer to Dimensions RM, you must establish a correlation between the fields in the Prototype Composer requirements and the attributes of the Dimensions RM classes by specifying the fields that correspond (map) to each other. For example, the Prototype Composer requirement ID field can correspond (map) to the Paragraph ID field in a Dimensions RM class.

After mapping is complete, you can publish Prototype Composer requirements to the Dimensions RM database, import Dimensions RM requirements into a Prototype Composer project, and synchronize Prototype Composer requirements with their Dimensions RM requirements.

When planning to map Prototype Composer requirement types to Dimensions RM classes, keep the following concepts in mind.

A requirement is to Prototype Composer what a requirement is to Dimensions RM.

A Prototype Composer requirement type is to a Prototype Composer requirement what a Dimensions RM class is to a Dimensions RM requirement.

A requirement type field in Prototype Composer is to a requirement type what a Dimensions RM class attribute is to a Dimensions RM class.

When documents, model items, or scenarios are published to Dimensions RM, the associated document file (.doc) or reference file (.bapl) is attached to the created Dimensions RM requirement as a file attachment. You specify the file attachment attribute to use for each Dimensions RM class mapped to the document, model item, or scenario type.

The following table illustrates Prototype Composer and Dimensions RM associations.

NOTE See Chapter 3, "Using the Integration" for details on publishing Prototype Composer requirements to Dimensions RM, importing Dimensions RM requirements to Prototype Composer, and synchronizing requirements between the two systems.

Prototype Composer Associated Dimensions RM

Requirement Requirement

Requirement type Class

Requirement type field Class attributeIntegration Guide for Serena Dimensions RM 11

Chapter 1 OverviewPublishing to Dimensions RM

You can publish requirements, documents, model items and scenarios from Prototype Composer to Dimensions RM. This section illustrates how publication occurs.

Publishing Requirements

The following diagram illustrates the relationship between Prototype Composer requirements and Dimensions RM requirements. In the following diagram, Requirement 1 in Prototype Composer is associated with Requirement A in Dimensions RM. The mapping occurs between the requirement type fields of the requirement type (of which Requirement 1 is an instance) and the Dimensions RM class attributes of the Dimensions RM class (of which Requirement A is an instance).

When the Prototype Composer requirement is published to Dimensions RM, the data in the requirement fields are copied to the fields in the Dimensions RM object or requirement.

Although you must explicitly define the mapping between most Prototype Composer requirement type fields and Dimensions RM class attributes, some automatic and permanent associations exist that cannot be changed. The following are the permanent associations between Prototype Composer requirement type fields and Dimensions RM class attributes.

Publishing Documents

The following diagram illustrates the relationship between a document in Prototype Composer and a requirement in Dimensions RM. For example, in the diagram, Document 1 is associated with Requirement A. You must specify the file attachment

Prototype Composer requirement fields

Associated Dimensions RM class attributes

Date Created Time Created

Date Modified Time Modified

Prototype Composer Requirement

Dimensions RM Requirement

Requirement 1

Requirement 2

Requirement A

Requirement B

Type

Date Created

Date ModifiedDescription

ID

Name

Class

Time Created

Time ModifiedText

Paragraph IDParagraph Title12 Serena Prototype Composer 2.4

Publishing to Dimensions RMattribute of the Dimensions RM class under which the attachment should be placed. In this case, the Prototype Composer attachment is the document itself.

When the document is published to Dimensions RM, the document is copied into the file attachment attribute field of the Dimensions RM requirement. You can download and open the document using RM Browser. See "Viewing a Dimensions RM Requirement Attachment" on page 23 for information on opening Dimensions RM requirement attachments.

Publishing Model Items and Scenarios

The following diagram illustrates the relationship between a scenario or model item in Prototype Composer and a requirement in Dimensions RM. For example, in the diagram, Model Item/Scenario 2 is associated with Requirement B. You must specify the file attachment attribute of the Dimensions RM class under which the attachment will be placed. In this case, the Prototype Composer scenario or model item is the scenario or model item reference file (.bapl).

When the Prototype Composer scenario or model item is published to Dimensions RM, the .bapl file is copied into the file attachment attribute of the Dimensions RM requirement. When you download and open the .bapl using RM Browser, Prototype Composer opens and displays the model item or scenario.

Prototype Composer Documents

Dimensions RMClass

File Attachment Attribute.doc

Document 1

Document 2

Requirement A

Requirement B

Prototype Composer Documents

Dimensions RMClass

File Attachment Attribute.bapl

Model Item/Scenario 1

Model Item/Scenario 2

Requirement A

Requirement BIntegration Guide for Serena Dimensions RM 13

Chapter 1 Overview14 Serena Prototype Composer 2.4

Chapter 2Setting Up the Integration

This chapter contains the following sections.

Overview 16

Dimensions RM Prerequisites 16

What Happens During the Installation? 16

Enabling the Integration 17

Configuring the Web Services 17

Verifying the Integration 18

Testing the Connection in Prototype Composer 18

Disabling the Integration 18Integration Guide for Serena Dimensions 15

Chapter 2 Setting Up the IntegrationOverview

After following all the instructions in this chapter for setting up the integration between Serena Prototype Composer and Serena Dimensions RM, you can begin using the integration. See Chapter 1, "Overview" and Chapter 3, "Using the Integration" for details on the requirements management functionality provided by the integration.

Dimensions RM Prerequisites

The following are setup tasks required to prepare Dimensions RM for the integration.

Before enabling the integration, you must define classes in Dimensions RM that will be mapped to Prototype Composer requirement types. You must also define classes for Prototype Composer documents, model items, and scenarios. Each of these classes must contain a file attachment attribute to hold an associated file (.doc or .bapl). Furthermore, you must define relationships (links) between the Dimensions RM classes for Prototype Composer model items and scenarios for each of the classes used for Prototype Composer requirement types. See the Serena Dimensions RM Administrators Guide for information on defining classes in Dimensions RM. See Chapter 1, "Overview" in this guide for more information on mapping requirement types in Prototype Composer.

Because Prototype Composer can send large file attachments to Dimensions RM, you must increase the size of the tablespace for Dimensions RM. See the Serena Dimensions RM Administrators Guide for details on increasing the size of the tablespace.

What Happens During the Installation?

This section describes the changes that occur on the system when you install Dimensions RM. These changes are required to use the Prototype Composer with Dimensions RM integration.

The Dimensions RM installer installs and configures GSOAP on IIS. GSOAP is the Web service module that enables Web communication between Prototype Composer and the Dimensions RM installation. The installer copies mod_gsoap.dll, rtmService.dll, and rtmService.wsdl to the created rtmservice virtual (GSOAP) directory.

The Dimensions RM installer configures custom headers and MIME types for the rtmservices virtual directory.

For IIS version 6.0, the installer creates a new application pool called "GSoapAppPool" and configures the rtmservice virtual directory to run in this application pool.

The Dimensions RM installer adds the following DLL files to the Web Service Extensions list in IIS and allows them to be run on the Dimensions RM Web service:

C:\Program Files\Serena\Dimensions 10.1\RM\bin\mod_gsoap.dllC:\Program Files\Serena\Dimensions 10.1\RM\bin\rtmService.dll16 Serena Prototype Composer 2.4

Enabling the IntegrationEnabling the Integration

To enable the integration, select the Enable Dimensions RM Integration check box on the Project Integrations tab on the Project Information dialog box.

Configuring the Web Services

The Dimensions RM installation configures the Dimensions RM Web services as described in this section. Use the information in this section if you need to reconfigure the Web services.

Configuring MIME Types and Custom Headers

The Dimensions RM installer configures custom headers and MIME types for the rtmservice virtual directory.

Content-Type: text/xml is added to the custom HTTP headers section.

wsdl and xsd are added to the MIME Types section.

To reset these configurations:

1 In the Internet Service Manager, right-click the rtmservice virtual directory and open the rtmservices Properties dialog box.

2 Click the HTTP Headers tab.

3 To configure the custom HTTP headers, add the following header information to the Custom HTTP Headers section:

Content-Type: text/xml

4 Configure the MIME type associations by clicking MIME Type and adding wsdl and xsd to the MIME Types section.

Configuring the rtmBrowser Virtual Directory

The installer configures MIME type associations for the rtmBrowser virtual directory for the following file types:

.bap

.bapl

The .bap and .bapl are file types that Prototype Composer uses. Setting the MIME type associations for these files allows RM Browser to work with Prototype Composer files.

NOTE After configuring the Dimensions RM Web services, commit the changes by restarting the World Wide Web Publishing service.Integration Guide for Serena Dimensions 17

Chapter 2 Setting Up the IntegrationTo reset the MIME type associations for RM Browser:

1 In the Internet Service Manager, right-click rtmBrowser virtual directory and open the rtmBrowser Properties dialog box.

2 Configure the MIME type associations by clicking MIME Type and adding .bap and .bapl to the MIME Types section.

3 Click OK to save the changes.

Verifying the Integration

You can verify the integration using these steps.

1 Open your browser.

2 Enter http:///rtmservices/mod_gsoap.dll?rtmservice (where is the address for the Dimensions RM Web server).

3 Press the ENTER key.

Testing the Connection in Prototype Composer

If your Dimensions RM server has an available project and database with at least one configured class, you can test the connection between Prototype Composer and the Dimensions RM server.

Use the procedure in "Configuring Dimensions RM Settings" on page 20 to test the connection.

Disabling the Integration

To disable the integration, clear the Enable Dimensions RM Integration check box on the Project Integrations tab on the Project Information dialog box.

NOTE When the connection is successful, you get a warning on the browser page indicating that you must use a POST request, not a GET request.18 Serena Prototype Composer 2.4

Chapter 3Using the Integration

This chapter contains the following sections.

Overview 20

Configuring Dimensions RM Settings 20

Creating a Dimensions RM Mapping 21

About Publishing to Dimensions RM 22

Publishing Items to Dimensions RM 22

Viewing a Dimensions RM Requirement Attachment 23

Importing Requirements from Dimensions RM 24

Synchronizing Published Requirements 25Integration Guide for Serena Dimensions RM 19

Chapter 3 Using the IntegrationOverview

This chapter explains how to enter Dimensions RM integration settings in Prototype Composer and use the integration.

Specifying Dimensions RM integration settings enables the Dimensions RM integration functionality in Prototype Composer. Until you provide the Dimensions RM integration settings, no fields or functionality related to the Dimensions RM integration are visible.

Before using the integration, relationships between Prototype Composer requirement types and Dimensions RM classes must be established. This chapter explains how to use Prototype Composer to map requirement types, scenarios, documents, and model items created in Prototype Composer to Dimensions RM classes. See Chapter 1, "Overview" for more information.

Configuring Dimensions RM Settings

This section provides instructions on how to configure Dimensions RM settings. You must provide information for all fields in order for the Dimensions RM integration features to appear in the Prototype Composer user interface.

To configure the Dimensions RM settings:

1 Open the Prototype Composer project that you want to integrate with a Dimensions RM project.

2 In Project view, click Project Information and click the Project Integrations tab.

3 Select the check box next to Enable Dimensions RM Integration.

4 Enter the following Web address into the URL field:

http:///rtmservices/mod_gsoap.dll?rtmservice (where is the host that is running the IIS based Web services).

5 Enter the user name and password for the Dimensions RM server.

6 Select a Dimensions RM database.

7 Select a Dimensions RM project.

8 In the Class & Attachment Association Details section, select a class and attachment attribute for the following items. (You can select any class under which to publish any scenario or model item.)

Scenario Class

Model Item Class

Document Class

NOTE More information on using the integration is available in the Prototype Composer online help and the Serena Prototype Composer Getting Started Guide.20 Serena Prototype Composer 2.4

Creating a Dimensions RM Mapping9 Optionally, select or enter the URL of the RM Browser in which you want to open and edit Dimensions RM requirements.

This option converts the Dimensions RM field labels on the General tab of the Properties Requirements dialog box to active links. Clicking any of these links opens the requirement for editing in Dimensions RM. Check the box next to Default from server URL if you want to set the default to the instance of RM Browser that is associated with the Dimensions RM server URL specified on the Project Integrations tab.

10 Click Test Connection to verify the connection.

Creating a Dimensions RM Mapping

This section explains how to map a Prototype Composer requirement type to a Dimensions RM class. See Chapter 1, "Overview" for background information about mapping Prototype Composer requirement types to Dimensions RM classes.

To map a requirement type to a Dimensions RM class:

1 Click the Display Solution Lists toolbar button.

2 On the Requirement Types tab, double-click a requirement type to open the Requirement Type properties dialog box for the selected requirement type.

3 Click the RM Mapping tab.

4 Select a Dimensions RM class to which to map this requirement type.

5 Select a Dimensions RM attribute for each requirement field that you want to map in the Field Mapping list.

6 If you specified a mapping for the Composer SubType field, select a Dimensions RM attribute value for each requirement subtype in the SubType Mapping list that you want to map.

Requirements that have the given requirement type are now eligible to be published to Dimensions RM, and requirements within Dimensions RM of the mapped Dimensions RM class are now eligible for import into Prototype Composer.

NOTE Use the Refresh Metadata button to update the local cache with any updates made to the project on the Dimensions RM server.

NOTE You can map more than one Prototype Composer requirement type to the same Dimensions RM class.Integration Guide for Serena Dimensions RM 21

Chapter 3 Using the IntegrationAbout Publishing to Dimensions RM

You publish existing requirements, model items, scenarios, and documents as objects to the Dimensions RM repository under the database and project you specify on the Project Integrations tab. Model items, scenarios or other requirements to which requirements are attached are also published. Published requirements become read-only in Prototype Composer; however, any attached model items, scenarios, and associated requirements can still be modified.

For each published requirement attached (associated) to a scenario or model item, a link is created in Dimensions RM between the requirement object and the scenario or model item object. Similarly, for each published requirement associated with another published requirement, a link is created in Dimensions RM between the two published requirements.

To learn how associations are made between requirements and other Prototype Composer items, see the Prototype Composer online Help and read the section on requirements in the Serena Prototype Composer Getting Started Guide.

Each scenario or model item has a reference (.bapl) file attachment that references that particular item within the Prototype Composer project. You can open the reference file from Dimensions RM and view the referenced Prototype Composer item. For more information, see "Viewing a Dimensions RM Requirement Attachment" on page 23.

Publishing Items to Dimensions RM

You publish Prototype Composer project items to Dimensions RM by using either Project Requirements view or the RM Publisher task pane. With some exceptions, both the Project Requirements View and the RM Publisher task pane work the same way.

The following sections explain how to publish requirements, scenarios, model items and documents to Dimensions RM.

Publishing From Project Requirements View

You use the Project Requirements view to select and publish one or more requirements. In Project Requirements view, you can only select requirements for publication; however, upon publication, any attached requirements, model items or scenarios are also published. Documents cannot be published from Project Requirements view.

To publish from Project Requirements View:

1 In Prototype Composer, open the Project Requirements editor.

2 In the Project Requirements view, select one or more requirements to publish.

NOTE Before publishing to Dimensions RM, you must map one or more Prototype Composer requirement types to Dimensions RM classes and create one or more requirements in Prototype Composer using types that were mapped to Dimensions RM classes. See the Serena Prototype Composer Getting Started Guide for information on creating requirements. See the section, "Creating a Dimensions RM Mapping" on page 21 for details on creating a Dimensions RM mapping.22 Serena Prototype Composer 2.4

Viewing a Dimensions RM Requirement Attachment3 Click Publish to RM below the list of requirements.

4 In the Publish to RM dialog box, view the requirements listed for publication. Note any attached model items, scenarios or other requirements, as these will be published in association with the selected requirements.

If you would like to save the current version of the Prototype Composer project as a new version after publication, select the check box next to Save New Project Version.

5 Click OK.

Publishing From the RM Publisher Task Pane

You can publish one or more model items, scenarios, documents and requirements to the Dimensions RM database from the RM Publisher task pane. When publishing model items and scenarios, any attached requirements are automatically included for publication. Similarly, when publishing requirements, any attached model items or scenarios are automatically included for publication. Any requirements associated with requirements that are attached to the model items and scenarios are also included.

PublishingDocuments

You can publish Prototype Composer generated Microsoft Word documents to Dimensions RM. You cannot associate a document with a requirement, model item or scenario. Documents are published separately by selecting and publishing them from the RM Publisher task pane. Published documents contain a single attachment, which is the document itself. When published, it is copied to the attachment attribute field specified for the document class selected on the Project Integrations tab as described in "Configuring Dimensions RM Settings" on page 20.

To publish from the RM Publisher Task pane:

1 In Prototype Composer, open the RM Publisher task pane by selecting Task Pane from the View menu.

2 Select one or more scenarios, model items, requirements or documents in the RM Publisher task pane.

3 Click Publish to RM in the RM Publisher task pane.

4 In the RM Publish Requirements dialog box, view the model items, scenarios, documents, or other requirements listed for publication. Note any attached requirements, because they are published in association with the selected project items.

If you want to save the current version of the Prototype Composer project as a new version after publication, select the check box next to Save New Project Version.

5 Click OK.

Viewing a Dimensions RM Requirement Attachment

In Dimensions RM, you can view the attachment to a Dimensions RM requirement that corresponds to a published scenario, model item, or document from Prototype Composer. Integration Guide for Serena Dimensions RM 23

Chapter 3 Using the IntegrationYou must have Prototype Composer installed locally to view the Dimensions RM requirement attachment.

To view the Dimensions RM requirement attachment, click the .bapl file attachment in the Dimensions RM requirement. See the Dimensions RM documentation for information on opening Dimensions RM requirements.

You can either open the attachment or first save it to the local machine. Prototype Composer downloads and opens the associated Prototype Composer project in read-only mode. If the attachment references a model item, Prototype Composer automatically navigates to that item in the project. If the attachment references a scenario, that scenario is automatically run as a Prototype Composer prototype. If the attachment is a document, that document opens in Microsoft Word.

Importing Requirements from Dimensions RM

You can import existing requirements from the Dimensions RM repository into a Prototype Composer project provided they are instances of Dimensions RM classes that have been mapped to Prototype Composer requirement types. If you specify a Dimensions RM class that has not been previously mapped to a Prototype Composer requirement type, a list of Dimensions RM classes that cannot be imported appears in the Import Requirements Error dialog box. To map the unmapped Dimensions RM classes to Prototype Composer requirement types, click Requirement Types and map the requirement types as described in "Creating a Dimensions RM Mapping" on page 21. When mapping is finished, importation resumes.

To import requirements from Dimensions RM:

1 In the Project Requirements view, click Import from RM.

2 Specify a Dimensions RM class in which to find requirements.

3 Optionally, further refine the requirement search by specifying a search string and whether or not to search descriptions.

4 Click Find.

5 Select one or more of the resulting Dimensions RM requirements.

6 Click OK to import the requirements.

The selected Dimensions RM requirements are imported into the Prototype Composer project. The imported requirements are read-only.

NOTE You can access RM Browser from the linked field labels in the RM Properties area on the General tab of the Requirement Properties dialog box in Prototype Composer and edit the requirement in Dimensions RM. For more information, see "Configuring Dimensions RM Settings" on page 20.24 Serena Prototype Composer 2.4

Synchronizing Published RequirementsSynchronizing Published Requirements

If you have previously published Prototype Composer requirements to Dimensions RM, or imported requirements from Dimensions RM into Prototype Composer, you can synchronize these requirements to update Prototype Composer requirements when their Dimensions RM counterparts have been modified.

To synchronize Prototype Composer requirements, in the Project Requirements view, click Synchronize with RM.

Changes made to the requirements within Dimensions RM are now reflected in the corresponding Prototype Composer requirements.Integration Guide for Serena Dimensions RM 25

Chapter 3 Using the Integration26 Serena Prototype Composer 2.4

Index

Symbols

.bap file 11

.bapl file 13, 24

A

Adobe Acrobat 6application pool 16

C

class attributesmapping 12

classesDimensions RM 11

componentsof the integration 10

configurationDimensions RM integration settings 20Dimensions RM Web services 17rtmBrowser virtual directory 17

connectionbetween Prototype Composer and

Dimensions RM 10testing 18

creatingDimensions RM mapping 21

custom headersconfiguring 17

D

Dimensions RM 5class attributes 12classes 11importing requirements from 24integration settings 10, 20mapping 21

creatingDimensions RM mapping 21

permanent associations 12prerequisites 16publishing requirements to 12requirement attachment 23Web services 17

documentationguide to 6

documentsPrototype Composer 12publishing 12

F

file attachment attributes 13

G

GSOAPinstallation and configuration 16

I

importingrequirements 24

installationintegration 17Prototype Composer 17verifying 18

integrationabout 5components 10Dimensions RM prerequisites 16disabling 18enabling 17, 20how it works 10purpose 10settings 10testing the connection 18

M

manualsinformation about 6

mappingconcepts 11permanent associations 12requirements 11

MIME typeassociations 17configuring 17Integration Guide for Serena Dimensions RM 27

Indexsettings for rtmBrowser virtual directory 17settings for rtmservice virtual directory 16

model itemspublishing 13

O

online documentation 6

P

prerequisitesDimensions RM setup 16

Project Integrations tab 20Dimensions RM integration settings 10

Project Requirements viewsynchronizing requirements 24

Project viewPrototype Composer 20

Prototype Composer 5documents 12Project Integrations tab 20Project view 20requirement type fields 11requirement types 11requirements 11

Prototype Composer requirement fieldsassociated class attributes 12

publishingdocuments 12model items 13requirements 12scenarios 13to Dimensions RM 12

R

requirement type fieldspermanent associations 12

requirementsimporting 24mapping 11Prototype Composer 11publishing 12synchronizing 24

rtmBrowser virtual directoryconfiguration 17custom headers and MIME types 17

rtmservice virtual directory 16configuring MIME types 17custom header configuration 17MIME type settings 16

S

scenariospublishing 13

synchronizingpublished requirements 24

V

viewingDimensions RM requirement attachments 23

W

Web Service ExtensionDLLs added 16

Web servicesused by the integration 1028 Serena Prototype Composer 2.4

Table of ContentsWelcomeObjectiveAudienceBook OrganizationRelated DocumentsUsing the Manuals

Typographical Conventions

OverviewWhat is the Prototype Composer with Dimensions RM Integration?What Do I Have to Install to Enable the Integration?Requirements

How Does the Prototype Composer with Dimensions RM Integration Work?ConnectivityAbout Mapping Requirements

Publishing to Dimensions RMPublishing RequirementsPublishing DocumentsPublishing Model Items and Scenarios

Setting Up the IntegrationOverviewDimensions RM PrerequisitesWhat Happens During the Installation?Enabling the IntegrationConfiguring the Web ServicesConfiguring MIME Types and Custom HeadersConfiguring the rtmBrowser Virtual Directory

Verifying the IntegrationTesting the Connection in Prototype ComposerDisabling the Integration

Using the IntegrationOverviewConfiguring Dimensions RM SettingsCreating a Dimensions RM MappingAbout Publishing to Dimensions RMPublishing Items to Dimensions RMPublishing From Project Requirements ViewPublishing From the RM Publisher Task Pane

Viewing a Dimensions RM Requirement AttachmentImporting Requirements from Dimensions RMSynchronizing Published Requirements

Index

/ColorImageDict > /JPEG2000ColorACSImageDict > /JPEG2000ColorImageDict > /AntiAliasGrayImages false /CropGrayImages true /GrayImageMinResolution 300 /GrayImageMinResolutionPolicy /OK /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 300 /GrayImageDepth -1 /GrayImageMinDownsampleDepth 2 /GrayImageDownsampleThreshold 1.50000 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict > /GrayImageDict > /JPEG2000GrayACSImageDict > /JPEG2000GrayImageDict > /AntiAliasMonoImages false /CropMonoImages true /MonoImageMinResolution 1200 /MonoImageMinResolutionPolicy /OK /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 1200 /MonoImageDepth -1 /MonoImageDownsampleThreshold 1.50000 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict > /AllowPSXObjects false /CheckCompliance [ /None ] /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXOutputIntentProfile () /PDFXOutputConditionIdentifier () /PDFXOutputCondition () /PDFXRegistryName () /PDFXTrapped /False

/Description > /Namespace [ (Adobe) (Common) (1.0) ] /OtherNamespaces [ > /FormElements false /GenerateStructure true /IncludeBookmarks false /IncludeHyperlinks false /IncludeInteractive false /IncludeLayers false /IncludeProfiles true /MultimediaHandling /UseObjectSettings /Namespace [ (Adobe) (CreativeSuite) (2.0) ] /PDFXOutputIntentProfileSelector /NA /PreserveEditing true /UntaggedCMYKHandling /LeaveUntagged /UntaggedRGBHandling /LeaveUntagged /UseDocumentBleed false >> ]>> setdistillerparams> setpagedevice