Serena® Prototype Composer™ Version 2.4
Readme File
Last updated on 20 December 2007

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

This document also describes requirements for integrating Prototype Composer with Serena® Dimensions® RM, Serena® Business Mashups, and Microsoft® Visual Studio® 2005 Team System.

To get help with the product, visit the Serena Connect Community at www.serenaconnect.com.


Table of Contents

1.0 Installation

1.1 Installation Requirements

1.2 Installing Serena Prototype Composer

2.0 Upgrading From a Previous Version of Prototype Composer

3.0 What’s New in Prototype Composer 2.4?

4.0 Composer Integrations

4.1 Composer with Microsoft VSTS Requirements

4.2 Composer with Serena® Business Mashups Integration System Requirements

4.3 Composer with Serena® Dimensions® RM Integration System Requirements

5.0 Known Issues

5.1 Business Mashups (TeamTrack) 6.3 Reviews Require Local Download of Request File

5.2 Document Image Writer Print Driver May Cause Exception Error

5.3 Web Services Execution May Fail

5.4 Dimensions® RM Integration Table Space Error

5.5 Web Capture Limitations for Certain Page Types

5.6 Flow Maps Don’t Scale Fully in Document Publishing

5.7 Business Mashups (TeamTrack) Web Service Does Not Return an Error When Response File Attachment Fails

5.8 Downloaded Prototype Composer Installer Fails to Run When Unable to Download .NET Framework

6.0 Configuring the Process Template for the VSTS Integration

6.1 Installing the Prototpe Composer Ready Process Template

6.2 Creating a New Process Template

6.3 Extending an Existing Process Template

6.4 Creating Projects

 

Return to Contents


1.0 Installation

1.1 Installation Requirements

The minimum system requirements are:

Client Systems - Minimum

Platform

Memory

Screen resolution

System Colors

Windows 2000 or Windows XP

256 MB

1024x768

65,536 colors

The recommended system requirements are:

Client Systems - Recommended

Platform

Memory

Windows 2000 Professional or Windows XP Professional

512 MB

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.

NOTE:
You will not be able to open projects created in Prototype Composer 2.4 in prior versions of Prototype Composer.

To install Serena Prototype Composer:

Follow the instructions until the installation is complete.

Return to Contents


2.0 Upgrading From a Previous Version of Prototype Composer

You can upgrade directly to Prototype Composer 2.4 from Prototype Composer 2.3. Projects are now stored in the \My Documents\Prototype Composer Projects directory. When you open an existing project, you will be prompted whether you want to move the project to the new directory.

Return to Contents


3.0 What’s New in Prototype Composer 2.4?

Prototype Composer 2.4 is a minor maintenance release that fixes an issue which will cause Prototype Composer to stop working on January 3, 2008. Additional branding changes were also made in the product.

Return to Contents


4.0 Prototype Composer Integrations

The requirements for the integrations with Prototype Composer are outlined in this section.

4.1 Prototype Composer with Microsoft VSTS Requirements

The system requirements for the Prototype Composer with Microsoft VSTS integration are as follows:

VSTS Integration

Server

Platform

Operating System

Software

Team Foundation Server

Windows

Windows Server 2003 (Standard or Enterprise)

Prototype Composer/VSTS integration software

Serena Prototype Composer Client

Windows

See Installation Requirements

Serena Prototype Composer 2.4

4.1.1 Installing the Integration Files

See Serena Prototype Composer Integration Guide for Microsoft Visual Studio 2005 Team System for information on installing the integration files onto Team Foundation Server.

4.2 Prototype Composer with Serena® Business Mashups (TeamTrack) Integration System Requirements

The system requirements for the Prototype Composer with Business Mashups integration are as follows:

Business Mashups Integration

Server

Platform

Operating System

Software

Business Mashups Server

Windows or UNIX

All supported Business Mashups servers

Serena® Business Mashups (TeamTrack) 6.3 or 6.5

Business Mashups Web Server

Windows

Windows 2000 Server or Windows 2003 Server

Microsoft Internet Information Service (IIS) 5.0 or 6.0

Prototype Composer Client

Windows

See Installation Requirements

Serena® Prototype Composer™ 2.4

4.2.1 Browser Requirements

For Business Mashups browser support, see the Serena® Business Mashups readme.

4.3 Prototype Composer with Serena® Dimensions® RM Integration System Requirements

The system requirements for the Prototype Composer with Dimensions® RM integration are as follows:

Dimensions® RM Integration

Server

Platform

Operating System

Software

Dimensions® RM Server

Windows

Windows 2000 Server or Windows 2003 Server

- Serena® Dimensions® RM 10.1.1 and later

- Microsoft Internet Information Service (IIS) 5.0 or 6.0

Serena Prototype Composer Client

Windows

See Installation Requirements

Serena® Prototype Composer™ 2.4

4.3.1 Dimensions® RM Version Requirements

The integration between Serena Prototype Composer and Serena Dimensions® RM works only with Dimensions® RM version 10.1.1 and later.

4.3.2 Browser Requirements

For Dimensions® RM Browser support, go to support.serena.com.

Return to Contents


5.0 Known Issues

5.1 Business Mashups 6.3 Reviews Require Local Download of Request File

DEF87416: If you are using Business Mashups version 6.3 to manage Business Mashups based reviews, you must download the request file attached to the Business Mashups task to your local machine and open the request file from there.

5.2 Document Image Writer Print Driver May Cause Exception Error

DEF78077: If you have Microsoft Office Document Image Writer configured as your default printer driver, you may get an unhandled exception error message if you cancel out of the Save As dialog accessed from Print Preview.

5.3 Web Services Execution May Fail

DEF88820: While Prototype Composer can import and execute a wide variety of Web Services as part of an application prototype, some services, such as those containing recursive type definitions, may not execute successfully. Developers who help you populate the set of IT Services for use in application prototypes are advised to test those services for proper execution within Prototype Composer before making them available to you.

5.4 Dimensions® RM Integration Table Space Error

DEF88930: Dimensions® RM must be properly configured for Prototype Composer to successfully publish model items to it. In certain circumstances you may see an error message that indicates the publishing failed. In this case you need to ensure that the Tablespace setting for tables used to store Prototype Composer model items and requirements is sufficient to contain the items published. For example, Microsoft Word documents can be very large and will overflow the available space if it is not reconfigured. You should also ensure that the temporary directories that may be used by both the Dimensions® RM Web service and Dimensions® RM itself are writable by the Web service and Dimensions® RM processes.

5.5 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:

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

5.6 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.

5.7 Business Mashups Web Service Does Not Return an Error When Response File Attachment Fails

DEF93725: Reviewers participating in Business Mashups managed reviews must have the Business Mashups permission, Add Attachments to Any Item, granted in order to enable the attachment of a response file when submitting review responses. If a reviewer attempting to submit a response file does not have this permission set, the response file will not be successfully attached and submitted. The Business Mashups Web services will not return an error message warning of the failed attachment. When the reviewer exits Prototype Composer, the response file will be deleted and the review responses will be lost.

For more information on permissions required for the Business Mashups integration, see Serena Prototype Composer Integration Guide for Serena Business Mashups.

5.8 Downloaded Prototype Composer Installer Fails to Run When Unable to Download .NET Framework

DEF98689: When downloaded the Prototype Composer installer checks the local machine to see if the required .NET Framework version 1.1 (or greater) is present. If it is not present, the Prototype Composer installer attempts to access the InstallShield Web site and download the redistributable .NET Framework program (dotnetfx.exe) to the local machine and install it. If the Prototype Composer installer fails to run, it might be due to an inability to download .NET Framework. Check that you have internet access to the InstallShield Web site. If this site is down or you are otherwise prevented from accessing it, download and install .NET Framework from the Microsoft web site. When .NET Framework is finished installing, run Prototype Composer24.exe located in the installer ZIP file.

Return to Contents


6.0 Configuring the Process Template for the VSTS Integration

The integration of Prototype Composer with Microsoft Visual Studio 2005 Team System (VSTS) requires the installation and implementation of any VSTS process template on Team Foundation Server (TFS). A Serena specific ("Prototype Composer ready") process template is available that you can import into VSTS and use immediately in the integration. The Prototype Composer ready process template is a collection of XML files that defines processes and artifacts for use in VSTS, including Prototype Composer model items, scenarios, requirements and work item types. The Prototype Composer ready process template simplifies the process of mapping Prototype Composer items to items in VSTS.

The other options that are available for configuring a process template are to extend an existing process template or create a new one. All options are implemented using the VSTS Process Template Manager. Using the Process Template Manager requires administrative rights to VSTS.

The following sections provide details on the options available for configuring the process template.

NOTE:
For information and instructions on how to use the VSTS Process Template Manager to configure a process template, see the Microsoft documentation.

6.1 Installing the Prototype Composer Ready Process Template

To get you up and running quickly with the Prototype Composer/VSTS integration, it is suggested that you install a Prototype Composer ready process template and create a new project based on it. To install the Prototype Composer ready process template, upload (import) the Serena specific process template from the \ Composer CMMI Process Improvement sub-directory of the VSTS integration installation directory on TFS.

6.2 Creating a New Process Template

You can create a new process template to work with the Prototype Composer/VSTS integration. If you choose to create your own process template (or extend an existing one), you must incorporate the modifications described in the section, Extending an Existing Process Template. See the Microsoft documentation for information on creating and importing process templates in VSTS.

6.3 Extending an Existing Process Template

You can extend an existing process template by incorporating the following suggested changes to the files that make up the process template. These modifications apply to process templates that are based on the Microsoft CMMI Process Improvement. These suggestions are provided as a general guide. To further assist you in making these modifications, see the corresponding fields in the Prototype Composer ready process template provided.

To extend (modify) an existing process template, download (export) an existing process template, for example, MSF for CMMI Process Improvement - v4.0, save it, and make the following suggested changes to your process template XML files. When you are finished making the modifications, upload (import) the process template to make it available for use by a VSTS project.

To complete the update of your process template, you’ll need to copy some files from the Prototype Composer ready process template to your process template directory. The Prototype Composer ready process template files are located in the \Composer CMMI Process Improvement sub-directory of the VSTS integration installation directory on TFS.

6.3.1 .\ProcessTemplate.xml

Update the ProcessTemplate.xml file by adding appropriate information for the <name> and <description> tags as in the following examples.

Update the process template name as follows:

<ProcessTemplate>
...
<metadata>
...
<name>MyProcessImprovement</name>
...
</metadata>
...
</ProcessTemplate>

Update the process template description as follows:

<ProcessTemplate>
...
<metadata>
...
<description>Description of MyProcessImprovement</description>
...
</metadata>
...
</ProcessTemplate>
6.3.2 .\WorkItem Tracking\WorkItems.xml

Update the WorkItems.xml file by adding new workitemtypes and queries.

Add the following new workitemtypes exactly as typed in the following example.

<tasks>

<task id="WITs" name="WorkItemType definitions" plugin="Microsoft.ProjectCreationWizard.WorkItemTracking" completionMessage="WorkItemTypes created">

...

<taskXml>
...
<WORKITEMTYPES>
...
<WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\Model.xml"/>
<WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\Prototype.xml"/> 
...
</WORKITEMTYPES>
...
</taskXml>
...
</task>
...
</tasks>

To add new queries, add the following new queries under the <QUERIES> tag exactly as typed as follows.

<tasks>
<task id="Queries" name="Stored Query Definitions" plugin="Microsoft.ProjectCreationWizard.WorkItemTracking" completionMessage="Queries uploaded">
...
<taskXml>
...
<QUERIES>
...
<Query name="Models" fileName="WorkItem Tracking\Queries\Models.wiq" />
<Query name="Prototypes" fileName="WorkItem Tracking\Queries\Prototypes.wiq" />
...
</QUERIES>
...
</taskXml>
...
</task>
...
</tasks>
6.3.3 .\WorkItem Tracking\Queries\CustomerRequirements.wiq

Update the CustomerRequirements.wiq by adding a new OR clause to the query to include additional workitemtypes. Refer to the following example.

<WorkItemQuery Version="1">
 <Wiql>
SELECT [System.Id], [System.IterationId], [System.State], [Microsoft.VSTS.Common.Priority], [System.Title]
FROM WorkItems WHERE [System.TeamProject] = @project  AND  [System.WorkItemType] = 'Requirement'
  AND ([Microsoft.VSTS.CMMI.RequirementType] = 'Scenario'  OR  [Microsoft.VSTS.CMMI.RequirementType] = 'Quality of Service'
  OR  [Microsoft.VSTS.CMMI.RequirementType] = 'Business' OR  [Microsoft.VSTS.CMMI.RequirementType] = 'User'
  ) 
  ...
ORDER BY [System.Id]
 </Wiql>
</WorkItemQuery>
6.3.4 .\WorkItem Tracking\Queries\Models.wiq

Locate this file in the directory of the Prototype Composer ready process template provided and copy it to the same location in your process template directory.

6.3.5 .\WorkItem Tracking\Queries\Prototypes.wiq

Locate this file in the directory of the Prototype Composer ready process template provided and copy it to the same location in your process template directory.

6.3.6 .\WorkItem Tracking\TypeDefinitions\Requirement.xml

Update the Requirement.xml file by adding new requirement types, a new field to hold the ID of the related Prototype Composer requirement and a new control for the Prototype Composer ID field.

Add a new requirement type field as in the following example.

<WITD>
...
<WORKITEMTYPE>
...
<FIELDS>
...
<FIELD name="Requirement Type">
...
<ALLOWEDVALUES>
...
<LISTITEM value="Business"/>
<LISTITEM value="User"/>
...
</ALLOWEDVALUES>
...
</FIELD>
...
</FIELDS>
...
</WORKITEMTYPE>
...
</WITD>

Add a new field to hold the Prototype Composer ID as in the following example. Add this field to the bottom of the list of field elements.

<WITD>
...
<WORKITEMTYPE>
...
<FIELDS>
...
<FIELD name="Composer Id"refname="Serena.VSTS.CMMI.ComposerId" type="String">
<HELPTEXT>Id of the related Prototype Composer requirement
</HELPTEXT>
</FIELD>
...
</FIELDS>
...
</WORKITEMTYPE>
...
</WITD>

Add a new control for the Prototype Composer ID field as follows:

<WITD>
...
<WORKITEMTYPE>
...
<FORM>
...
<Layout>
...
<Group name="Status">
...
<Column PercentWidth='50'>
...
</Column>
<Column PercentWidth='50'>
...
<Control Type="FieldControl" FieldName="Serena.VSTS.CMMI.ComposerId" Label="&amp;Composer Id:" LabelPosition="Left"/>
...
</Column>
...
</Group>
...
</Layout>
...
</FORM>
...
</WORKITEMTYPE>
...
</WITD>
6.3.7 .\WorkItem Tracking\TypeDefinitions\Model.xml

Locate this file in the directory of the Prototype Composer ready template provided and copy it to the same location in your process template directory.

6.3.8 .\WorkItem Tracking\TypeDefinitions\Prototype.xml

Locate this file in the directory of the Prototype Composer ready template provided and copy it to the same location in your process template directory.

6.4 Creating Projects

Create a new VSTS team project that uses the new Prototype Composer ready process template and create a project on Prototype Composer. In Prototype Composer, enable the VSTS integration and configure mappings.

For complete information on enabling the integration, creating mappings, and using the integration, see the Serena Prototype Composer online help, Serena Prototype Composer Getting Started Guide, and Serena Prototype Composer Integration Guide for Microsoft Visual Studio 2005 Team System.

Return to Contents


End Readme
Copyright © 2003-2008 Serena Software, Inc. All rights reserved.