Serena Prototype Composer Integration Guide For Serena Dimensions RM
Serena Prototype Composer Integration Guide for Serena Dimensions RM SERENA PROPRIETARY AND CONFIDENTIAL INFORMATION
Copyright 2001–2007 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. Trademarks Serena, 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 Rights Any 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objective . . . . . . . . . . . . Audience. . . . . . . . . . . . . Book Organization . . . . . . Related Documents . . . . . Using the Manuals . . . Typographical Conventions Chapter 1 Chapter 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 5 6 6 7 9 What 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? Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Mapping Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing to Dimensions RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing Model Items and Scenarios . . . . . . . . . . . . . . . . . . . . . . 10 10 10 10 10 11 12 12 12 13 Setting Up the Integration . . . . . . . . . . . . . . . . . . . . . . 15 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensions RM Prerequisites. . . . . . . . . . . . . . . . What Happens During the Installation?. . . . . . . . . Enabling the Integration . . . . . . . . . . . . . . . . . . . Configuring the Web Services . . . . . . . . . . . . . . . Configuring MIME Types and Custom Headers Configuring the rtmBrowser Virtual Directory . Verifying the Integration. . . . . . . . . . . . . . . . . . . Testing the Connection in Prototype Composer . . . Disabling the Integration . . . . . . . . . . . . . . . . . . Chapter 3 . . . . . . 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Integration . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Dimensions RM Settings . . . . . . . . . . . Creating a Dimensions RM Mapping . . . . . . . . . . . . About Publishing to Dimensions RM . . . . . . . . . . . . Publishing Items to Dimensions RM . . . . . . . . . . . . Publishing From Project Requirements View . . . Publishing From the RM Publisher Task Pane . . Viewing a Dimensions RM Requirement Attachment . Importing Requirements from Dimensions RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration Guide for Serena Dimensions RM . . . . . . . . . 16 16 16 17 17 17 17 18 18 18 19 . . . . . . . . . 20 20 21 22 22 22 23 23 24 3
Table of Contents 4 Synchronizing Published Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 25 Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Serena Prototype Composer 2.4
Welcome The 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 integration Integration Guide for Serena Dimensions RM 5
Related Documents For related information, see the following documentation. Serena Dimensions RM Administrator’s Guide Serena Dimensions RM Installation Guide Serena Dimensions RM User’s 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. TIP Be sure to download the full version of Reader. The more basic version does not include the search feature. 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 Catalog—see step 3 below.) To search within multiple PDF documents at once, perform the following steps (requires Adobe Reader version 6 or higher): 6 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. Serena Prototype Composer 2.4
Typographical Conventions 5 Click the Search button. 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. 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. 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 1 Overview 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 12 Integration Guide for Serena Dimensions RM 9
Chapter 1 Overview What 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. 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. 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. Prototype Composer Associated Dimensions RM Requirement Requirement Requirement type Class Requirement type field Class attribute Integration Guide for Serena Dimensions RM 11
Chapter 1 Overview Publishing 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. Requirement 1 Requirement A Requirement 2 Requirement B Prototype Composer Requirement Dimensions RM Requirement Type Class Date Created Time Created Date Modified Description Time Modified Text Paragraph ID Paragraph Title ID Name 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. Prototype Composer requirement fields Associated Dimensions RM class attributes Date Created Time Created Date Modified Time Modified 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 12 Serena Prototype Composer 2.4
Publishing to Dimensions RM attribute 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. Document 1 Requirement A Document 2 Requirement B Prototype Composer Documents Dimensions RM Class .doc Attachment File Attachment Attribute 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. Model Item/Scenario 1 Requirement A Model Item/Scenario 2 Requirement B Prototype Composer Documents Dimensions RM Class .bapl Attachment File Attachment Attribute Integration Guide for Serena Dimensions RM 13
Chapter 1 Overview 14 Serena Prototype Composer 2.4
Chapter 2 Setting 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 18 Integration Guide for Serena Dimensions 15
Chapter 2 Setting Up the Integration Overview 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 Administrator’s 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 Administrator’s 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.dll C:\Program Files\Serena\Dimensions 10.1\RM\bin\rtmService.dll 16 Serena Prototype Composer 2.4
Enabling the Integration Enabling 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. NOTE After configuring the Dimensions RM Web services, commit the changes by restarting the World Wide Web Publishing service. 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. Integration Guide for Serena Dimensions 17
Chapter 2 Setting Up the Integration To 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:// servername /rtmservices/mod gsoap.dll?rtmservice (where servername is the address for the Dimensions RM Web server). 3 Press the ENTER key. 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. 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. 18 Serena Prototype Composer 2.4
Chapter 3 Using 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 25 Integration Guide for Serena Dimensions RM 19
Chapter 3 Using the Integration Overview 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. NOTE More information on using the integration is available in the Prototype Composer online help and the Serena Prototype Composer Getting Started Guide. 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:// hostname /rtmservices/mod gsoap.dll?rtmservice (where hostname 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 20 Serena Prototype Composer 2.4
Creating a Dimensions RM Mapping 9 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. NOTE Use the Refresh Metadata button to update the local cache with any updates made to the project on the Dimensions RM server. 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 th
Serena Prototype Composer Integration Guide for Serena Dimensions RM SERENA PROPRIETARY AND CONFIDENTIAL INFORMATION
Serena Requirements Manager is an orchestration of Serena Dimensions RM and Serena Business Manager. As part of Serena ALM, Requirements Manager fits into an orchestrated workflow with Serena Development Manager. Optionally, it can leverage the rich reporting capabilities of Serena Dashboard. It also includes Serena Prototype Composer as a .
Third party programs included with the Dimensions product are subject to a restricted use license and can only be used in conjunction with Dimensions. Trademarks Serena, TeamTrack, StarTool, PVCS, Collage, Comparex, Dimensions, Serena Dimensions, Mashup Composer, Mashup Exchange, Prototype Composer, Mariner and ChangeMan are
SERENA SERENA DASHBOARD Installation and Configuration Guide Serena Proprietary and Confidential Information
The Developer's Toolkit includes functions that implement the functionality of Serena ChangeMan Version Manager and Serena Configuration Builder. You can use Developer's Toolkit to build applications that use Serena ChangeMan Professional Suite services on various platforms. Components of the Toolkit DLLs, libraries, and header files
6 Install the IBI WebFOCUS Server, which powers the Serena ALM Dashboard. 7 Install the Serena ALM Dashboard, which provides reporting features for Serena Development Manager. 8 Install the IBI WebFOCUS Developer Studio, which enables you to manage and edit metrics for the Serena ALM Dashboard. Preparing for the Installation .
Serena Dashboard presents data on your most essential key performance indicators (KPIs) with a fully configurable set of graphical charts, tabular data, and more. What Is Included Out-of-the-Box Right out-of-the-box, Serena Dashboard includes a number of KPI metrics designed to present
1-2 IBM Maximo Integration Adapter for Tivoli Application Dependency Discovery Manager: Implementation Guide Integration Composer Components This section provides an overview of the Integration Composer components. For more detailed info rmation, refer to the IBM Maximo Integration Composer System Administrator s Guide. The Integration .
ALEX RIDER www.anthonyhorowitz.com. Never Say Die Exclusive Extract The start of another day. Alex went into the bathroom, showered and cleaned his teeth. Then he got dressed. He had started school a week ago, arriving at the start of the fall semester – the autumn term, he would have called it back in London. There was no uniform at the Elmer E. Robinson High School. Today, Alex threw on .
