Serena^® Prototype Composer™ PRO Edition, Version 3.2.1
Readme File
Last updated on 7 April 2011

This file contains information about installing and using the current release of Serena® Prototype Composer™ PRO Edition.

This document also describes requirements for integrating Prototype Composer with Serena® Dimensions® RM.

To get help with the product, visit http://community.serena.com.

Table of Contents

1.0 Installation

1.1 Installation Requirements

1.2 Installing Serena Prototype Composer

2.0 What’s New in Prototype Composer 3.2.1?

2.1 RM Login Password Prompt During Connection Timeout

2.2 Changes in Model Items now Synchronized even when Requirements have not changed

2.3 Requirements can be Published to Selected RM Category

2.4 Model Items can be Published to Selected RM Category

2.5 Model Items now Replaced during Synchronization

2.6 MS .Net Framework Upgraded to Version 4.0

2.7 Images Only Created for High-level Model Items

3.0 Prototype Composer Integrations

3.1 Prototype Composer with Serena Dimensions RM Integration System Requirements

4.0 Known Issues

4.1 Web Capture Limitations for Certain Page Types

4.2 Flow Maps Don’t Scale Fully in Document Publishing

4.3 New Background Color for a Button is not Displayed

4.4 Requirement Description Field in Prototype Composer Does Not Support HTML Formatted Text

4.5 Synchronization Does Not Update Links from Dimensions RM

4.6 Model Items not Sent as File Attachments to IIS Enabled RM Servers

1.0 Installation

1.1 Installation Requirements

For the system requirements for Prototype Composer see the Serena Release Plan page for Prototype Composer at:

http://support.serena.com/Roadmap/Product.aspx?sel=COMPOSER

and click on the name of the release. This also describes which versions are compatible for upgrade.

The minimum system requirements are:

The recommended system requirements are:

• The full version of .NET Framework 4.0 must also be installed on the system. To install this, see Installing Serena Prototype Composer below.
• Microsoft® Word 2003 (either the standalone version or the version supplied with Microsoft Office Professional Edition 2003) or Microsoft Office Word 2007 is required to generate documents in the Document Publisher. The XML support supplied with these specific versions is needed to generate documents.

1.2 Installing Serena Prototype Composer

This section explains how to install Serena Prototype Composer. You must perform the following installation procedures on all client machines where necessary.

If you do not have the full version of Microsoft .NET 4.0 installed, download and install it from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7

To install Serena Prototype Composer PRO Edition:

1. Download Serena Prototype Composer PRO Edition and run the executable (.exe) file.
2. Follow the instructions until the installation is complete. 

Return to Contents

2.0 What’s New in Prototype Composer 3.2.1?

2.1 RM Login Password Prompt During Connection Timeout

The Dimensions RM login password is no longer stored in Prototype Composer. When there is a connection timeout during RM integration activities such as synchronization, publishing, or importing, the user is prompted with a login dialog box requiring them to re-enter their password. The current timeout default is 30 minutes.

This dialog box is also presented when completing the Project Integrations tab after entering the server URL and username and testing the connection.

When first creating a project, the Dimensions RM Settings tab will no longer be present for a project that does not store the password.

2.2 Changes in Model Items now Synchronized even when Requirements have not changed

In previous versions of Prototype Composer, changes in model items would only be synchronized with Dimensions RM when there had been changes in their associated Requirements. Now model items are synchronized even when the requirements have not changed.

2.3 Requirements can be Published to Selected RM Category

You can now select an RM category to which to publish a requirement. Previously you could only publish requirements to the root category.

2.4 Model Items can be Published to Selected RM Category

You can now select an RM category to which to publish a model item. Previously you could only publish model items to the root category.

2.5 Model Items now Replaced during Synchronization

When a Requirement is published to RM, and there are changes to associated model items, they are replaced with a requirement with the new model items attached.

2.6 MS .Net Framework Upgraded to Version 4.0

This version of Prototype Composer has been upgraded to MS .Net Framework Version 4.0 compared with Version 1.1 in the previous release.

2.7 Images Only Created for High-level Model Items

In the previous release, when publishing and synchronizing Prototype Composer Requirements that have associated processes, activities, and interfaces, their images could be stored in Dimensions RM. This is now only true for high-level model items alone.

Return to Contents

3.0 Prototype Composer Integrations

3.1 Prototype Composer with Serena Dimensions RM Integration System Requirements

The system requirements for the Prototype Composer with Dimensions RM integration are described on the Serena Integrations tab of the Prototype Composer 3.2.1 page at:

http://support.serena.com/roadmap/product.aspx?sel=COMPOSER_3.2.1

Return to Contents

4.0 Known Issues

4.1 Web Capture Limitations for Certain Page Types

DEF86108, DEF84168: While in most cases the Web Capture utility in Prototype Composer will import and convert simple Web pages with high fidelity, pages with dynamic content or complex HTML elements may result in less than optimal capture results. Examples include:

• Web pages with data tables converted to bitmaps with text objects representing the data records.
• Web pages with scrolling panels vertically truncated and the panels converted to bitmaps.

You are advised to perform test captures and adjust the capture controls to maximize the quality of imported Web content.

4.2 Flow Maps Don’t Scale Fully in Document Publishing

DEF88549: Images of process or activity flow maps included in published documents may not scale to the full extent possible depending upon the aspect ratio of the image. These images can be selected and scaled manually following the generation of the document.

4.3 New Background Color for a Button is not Displayed

DEF152533: If a user changes the background color for a button, the new color is not displayed when the user runs a simulation.

4.4 Requirement Description Field in Prototype Composer Does Not Support HTML Formatted Text

The Requirement Description field in Prototype Composer does not support HTML formatted text, but Dimensions RM does support HTML formatted text. Therefore, when a user overwrites a description field from Dimensions RM that is HTML formatted, Prototype Composer removes the HTML formatting and stores the description as plain text.

4.5 Synchronization Does Not Update Links from Dimensions RM

In the following scenario, the Synchronize function does not update links from Dimensions RM:

1. In Dimensions RM, create a Business Requirement (BRx) and a User Requirement (URy).
2. In Dimensions RM, link BRx and URy.
3. In Prototype Composer, import BRx.
4. In Prototype Composer, import URy.
5. In Prototype Composer, the Synchronize function does not update the links from Dimensions RM to Prototype Composer.

Perform the following steps as a workaround to this issue:

1. Clear the checkbox for the RM integration on the Project Integrations tab.
2. Delete the parent requirements (BRx) and child requirements (URy) in Prototype Composer.
3. Select the check box for the RM integration on the Project Integrations tab.
4. Import child requirements (URy) and then import parent requirements (BRx) in Prototype Composer.

4.6 Model Items not Sent as File Attachments to IIS Enabled RM Servers

DEF186325: Model Items are not automatically being sent as file attachments to IIS enabled Dimensions RM Servers. It is necessary to provide Anonymous Authentication for the specific user for this function to work. The instructions below will explain how to set the Anonymous Authentication, and how to add the MIME type to open the Scenario, Model item and Document class which is integrated as a file Attachment in Dimensions RM for IIS7 and IIS6. For a fuller description, see the Appendix Enabling Model Items to be Sent as File attachments to IIS Enabled RM Servers in the User's Guide.

Procedures for IIS7

To Set the Anonymous Authentication

In Internet Information Services (IIS) Manager:

1. Click on the Default Web Site in the Connections pane. A Default Web Site Home pane will be displayed.
2. On the Default Web Site Home, in the Features view, double-click on Authentication. A new window for Authentication will be opened.
3. In the Authentication Window, right-click on Anonymous Authentication and select the Edit option. You can also select the Edit option in the Action Pane of the Authentication Window.
4. On clicking on the Edit option, the Edit Anonymous Authentication Credentials dialog will be opened.
5. Set the Specific user by clicking on the Set button. The format for the user name field is:
• For a domain user: <domain name>\<User Name>
• For Workgroup user: <user name>

To Set the MIME Types

In Internet Information Services (IIS) Manager:

1. Click on the Default Web Site in the Connections pane, a Default Web Site Home pane will be displayed.
2. On the Default Web Site Home, in the Features view, double-click MIME Types. A new window for MIME Types will be opened.
3. Select Add by right-clicking or from the Action Pane of the MIME Types Window.
4. On clicking the Add option, a new Add MIME Type dialog will be opened.
5. In the textbox under File name Extension enter “bapl” and in the Textbox under MIME types enter “text/bapl”. Click OK.
6. Similarly for bap files, in the textbox under File name extension enter bap and in the Textbox under MIME types enter text/bap. Click OK.

Procedures for IIS6

To Set the Anonymous Authentication

In Internet Information Services (IIS) Manager:

1. Right-click on the Default Web Site and select Properties.
2. Select the Directory Security tab from the opened Default Web Site Properties dialog.
3. On the Default Web Site Properties dialog, click on the Edit button of Authentication and access Control.
4. On clicking the Edit button of Authentication and access Control, an Authentication Methods dialog will be opened.
5. Select Enable anonymous access by selecting the check box.
6. Select the required user by clicking the Browse button, or by directly entering the user details in the Username/password fields. The format for the user name field is:
• For a domain user: <domain name>\<User Name>
• For Workgroup user: <user name>

To Set the MIME Types

In Internet Information Services (IIS) Manager:

1. On the Default Web Site properties dialog, select the HTTP Headers tab, and then click the MIME Types Button.
2. On the MIME Types dialog, click the New button. Another MIME Type Dialog will be opened.
3. In the Extension textbox enter bap and in the MIME types text box enter text/bap. Click OK.
4. Similarly for bapl files enter bapl in the Extension text box, and enter text/bapl in the MIME types text box. Click O

Return to Contents

End Readme
Copyright © 2007-2011 Serena Software, Inc. All rights reserved.