Product PortabilityProduct Portability

““Optimizing Your Investment in Dimensions CM”Optimizing Your Investment in Dimensions CM”

Presented byPresented by

Lovell & Mercier, Inc.Lovell & Mercier, Inc.

22

Trademarks & CopyrightsTrademarks & Copyrights

• Serena, Dimensions and Serena Dimensions are registered trademarks of Serena Software, Inc. The Serena logo is a trademark of Serena Software, Inc. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

• Lovell & Mercier recognizes Serena Software, Inc. Trademarks and Copyrights. Any use of a Serena Software Inc. Trademark or Copyright in this presentation that is not acknowledged is unintentional and will be corrected as soon as it is brought to our attention.

33

AgendaAgenda

• Introductions– Attendees– Lovell & Mercier– Emagine IT

• Background

• Product Portability

• Demonstration

• Questions

44

Lovell & MercierLovell & Mercier

• Dimensions CM Support– Professional Services

• New Installation/Upgrade• Conversion/Migration• Process Automation• Consulting

– Custom Development• New Interfaces• Triggers

• Custom Dimensions CM Training– Administration– Developers– End Users

55

Emagine ITEmagine IT

Emagine IT is an information technology consulting Services Company that specializes in delivering technology solutions to meet the needs of government and commercial clients. Their mission is to understand and meet the needs of both clients and consultants by delivering quality, value-added solutions. Their solutions are designed and managed to not only reduce costs, but to improve business processes, accelerate response time, improve services to end users, and give clients a competitive edge, now and into the future. As business systems integrators, they align clients’ business processes and information systems to enable them to access the right information at the right time, empowering them to achieve their desired business results and create enterprise value.

Emagine IT’s approach reduces costs and increases productivity by creating collaborative business environments. Their solutions are a carefully selected combination of people, tools, and processes focused on the specific needs of their customers.

Emagine IT is working with Lovell & Mercier to make the Product Portability functionality available to Dimensions CM users. Contact Lucas Aimes from Emagine IT for more information regading Dimensions CM Product Portability.

66

BackgroundBackground

• State of Ohio, Department of Job and Family Services (ODJFS)– Expressed need for Product Portability

• Dimensions Interface developed jointly by L&M and ODJFS– Roger Mercier (L&M)– Bobby Mittra (ODJFS)

• DMPMCLI Function Library developed jointly by L&M and (ODJFS)– Roger Mercier (L&M)– Bobby Mittra (ODJFS)

• Special Thanks– Phil Davis (ODJFS)– Anita Moss (ODJFS)

77

Product PortabilityProduct Portability

• The ability to develop a Dimensions CM Product Control Plan in a Dimensions CM Base Database and migrate that Product Control Plan, in its entirety, to an another EXISTING Dimensions CM Base Database.

88

““Out-of-the-box” Capabilities in Out-of-the-box” Capabilities in Dimensions CMDimensions CM

• Copy Product– Cannot cross Base Databases– Not all information copied

• EXPM– Exports complete Control Plan– Can ONLY be used to create a NEW Base Database

• DMDBA ….. /IMPORT=<EXPM File>

– Cannot be used to create a new product in an existing Base Database

• DMPMCLI– Using “native” DMPMCLI would require hundreds of thousands

of lines of code– Extremely unmanageable for even medium sized products

99

Classical Quality AssumptionsClassical Quality Assumptions

• Faster means you have to sacrifice better, cheaper, or both

• Better means you have to sacrifice faster, cheaper, or both

• Cheaper means you have to sacrifice faster, cheaper, or both

1010

Facts Regarding Product PortabilityFacts Regarding Product Portability

• It is FASTER– Development time– Implementation into a test environment– Implementation into the production environment

• AND, it is BETTER– What was developed in the development environment IS what is

tested in the test environment– What was tested in the test environment IS what is implemented

into the production environment

• AND, it is CHEAPER– Development time– Implementation into a test environment– Implementation into the production environment

1111

Tools RequiredTools Required

• Microsoft Visual Basic (VB6.0 Pro)

• Dimensions CM DMPMCLI

• Dimensions CM DMCLI

• Access to Dimensions CM Published Views AND Dimensions CM Tables (Read Only)

• L&M Function Library ***

1212

Skills RequiredSkills Required

• Intimate familiarity with the Dimensions CM Administration functions

• Intimate familiarity with the Dimensions CM Database structure

• Intimate familiarity with the Dimensions CM DMCLI

• Intimate familiarity with the Dimensions CM DMPMCLI ***

• Intimate familiarity with Visual Basic• Intimate familiarity with SqlPlus

1313

Technical DetailsTechnical Details

• Must have access to both the Source Base Database and Target Base Database AT THE SAME TIME

• Must have READ ONLY access to both the Source Base Database and Target Base Database tables and Published Views

• Must have Dimensions CM Admin rights on both the Source Base Database and Target Base Database

1414

ConsiderationsConsiderations

• Order of execution is MOST important

• Verification is VERY important

• MOST IMPORTANTLY – NO ORACLE TABLE UPDATES– DMPMCLI– DMCLI

1515

Objects PortedObjects Ported• Product• Roles• Lifecycles• Lifecycle Images• Lifecycle Transitions• Valid Sets• Valid Set Values• Design Part Types• Baseline Types• Baseline Templates• Baseline Template Rules• Release Templates• Release Template Rules• Request Types• Request Type Options• Request Templates• Request CM Rules• Request Attributes• Request Priming• Request Valid Set Relationships

• Request Attribute Rules• Request Block Attributes• Item Types• Item Type Options• Item Libraries• Item CM Rules• Item Attributes• Item Valid Set Relationships• Item Attribute Rules• Item Block Attributes• Relationships• Design Parts• Projects• Streams• User Accounts• Role Assignments• Privilege Assignments• eMail Subscriptions

1616

DetailsDetails

1717

PRODUCTPRODUCT

• Product Name– Cannot exist in target Base Database– Will be deleted in Target Base Database

• Product Description– Uses Source Product description

• Product Manager– Defaults to Tool Manager

• Based On– Defaults to $GENERIC

• Copy Structure– Default FALSE

1818

ROLESROLES

• Role Name– Cannot exist in Target Base Database

• Role Description– From Role in Source Base Database

1919

LIFECYCLESLIFECYCLES

• If Lifecycles exist in the Target Base Database they WILL BE USED, AS IS

• If Lifecycles do not exist in the Target Base Database they WILL BE CREATED

• Lifecycles in the Target Base Database WILL NOT BE MODIFIED

2020

LIFECYCLE IMAGESLIFECYCLE IMAGES

• If Lifecycle existed in the Target Base Database it’s images will not be modified

• If Lifecycle did not exist in the Target Base Database all revisions of it’s images in the Source Base Database will be ported to the lifecycle in the Target Base Database

2121

LIFECYCLE TRANSITIONSLIFECYCLE TRANSITIONS

• If Lifecycle existed in the Target Base Database it’s transitions will not be modified

• If Lifecycle did not exist in the Target Base Database all of it’s transitions in the Source Base Database will be ported to the lifecycle in the Target Base Database

2222

VALID SETSVALID SETS

• If the Valid Set exists in the Target Base Database it will not be ported from the Source Base Database

• If the Valid Set does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

2323

VALID SET VALUESVALID SET VALUES

• If the Valid Set exists in the Target Base Database its values will not be ported from the Source Base Database

• If the Valid Set does not exist in the Target Base Database its values will be ported from the Source Base Database to the Target Base Database

2424

DESIGN PART TYPESDESIGN PART TYPES

• If the Design Part Type exists in the Target Base Database it will not be ported from the Source Base Database

• If the Design Part Type does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

2525

BASELINE TYPESBASELINE TYPES

• If the Baseline Type exists in the Target Base Database it will not be ported from the Source Base Database

• If the Baseline Type does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

2626

BASELINE TEMPLATESBASELINE TEMPLATES

• If the Baseline Template exists in the Target Base Database it will not be ported from the Source Base Database

• If the Baseline Template does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

2727

BASELINE TEMPLATE RULESBASELINE TEMPLATE RULES

• If the Baseline Template exists in the Target Base Database its Template Rules will not be ported from the Source Base Database

• If the Baseline Template does not exist in the Target Base Database its Template Rules will be ported from the Source Base Database to the Target Base Database

2828

RELEASE TEMPLATESRELEASE TEMPLATES

• If the Release Template exists in the Target Base Database it will not be ported from the Source Base Database

• If the Release Template does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

2929

RELEASE TEMPLATE RULESRELEASE TEMPLATE RULES

• If the Release Template exists in the Target Base Database its Template Rules will not be ported from the Source Base Database

• If the Release Template does not exist in the Target Base Database its Template Rules will be ported from the Source Base Database to the Target Base Database

3030

REQUEST TYPESREQUEST TYPES

• If the Request Type exists in the Target Base Database it will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

3131

REQUEST TYPESREQUEST TYPES

• If the Request Type exists in the Target Base Database it will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

3232

REQUEST TYPE OPTIONSREQUEST TYPE OPTIONS

• If the Request Type exists in the Target Base Database the Request Type Options will not be ported from the Source Base Database

• If they are to be ported, LOOK IN THE OBJ_TYPES table, TEMPALATE2 column to determine the options that are relevant

3333

REQUEST TEMPLATESREQUEST TEMPLATES

• If the Request Type exists in the Target Base Database its Request Templates will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its Request Templates (all revisions) will be ported from the Source Base Database to the Target Base Database

3434

REQUEST CM RULESREQUEST CM RULES

• If the Request Type exists in the Target Base Database its CM Rules will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its CM Rules will be ported from the Source Base Database to the Target Base Database

3535

REQUEST ATTRIBUTESREQUEST ATTRIBUTES

• If the Request Type exists in the Target Base Database its Attributes will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its Attributes will be ported from the Source Base Database to the Target Base Database

3636

REQUEST PRIMING RULESREQUEST PRIMING RULES

• If the Request Type exists in the Target Base Database its Priming Rules will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its Priming Rules will be ported from the Source Base Database to the Target Base Database

3737

REQUEST VALID SET REQUEST VALID SET RELATIONSHIPSRELATIONSHIPS

• If the Request Type exists in the Target Base Database its Valid Set Relationships will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its Valid Set Relationships will be ported from the Source Base Database to the Target Base Database

3838

REQUEST ATTRIBUTE RULESREQUEST ATTRIBUTE RULES

• If the Request Type exists in the Target Base Database its Attribute Rules will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its Attribute Rules will be ported from the Source Base Database to the Target Base Database

3939

REQUEST BLOCK ATTRIBUTESREQUEST BLOCK ATTRIBUTES

• If the Request Type exists in the Target Base Database its Block Attributes will not be ported from the Source Base Database

• If the Request Type does not exist in the Target Base Database its Block Attributes will be ported from the Source Base Database to the Target Base Database

4040

ITEM TYPESITEM TYPES

• If the Item Type exists in the Target Base Database it will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database it will be ported from the Source Base Database to the Target Base Database

4141

ITEM TYPE OPTIONSITEM TYPE OPTIONS

• If the Item Type exists in the Target Base Database the Item Type Options will not be ported from the Source Base Database

• If they are to be ported, LOOK IN THE OBJ_TYPES table, TEMPALATE2 column to determine the options that are relevant

4242

ITEM TYPE LIBRARIESITEM TYPE LIBRARIES

• If the Item Type exists in the Target Base Database its associated Item Library definition will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database its associated Item Library definition will be ported from the Source Base Database to the Target Base Database

4343

ITEM TEMPLATESITEM TEMPLATES

• Item Templates are not ported at this time

4444

ITEM CM RULESITEM CM RULES

• If the Item Type exists in the Target Base Database its CM Rules will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database its CM Rules will be ported from the Source Base Database to the Target Base Database

4545

ITEM ATTRIBUTESITEM ATTRIBUTES

• If the Item Type exists in the Target Base Database its Attributes will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database its Attributes will be ported from the Source Base Database to the Target Base Database

4646

ITEM VALID SET ITEM VALID SET RELATIONSHIPSRELATIONSHIPS

• If the Item Type exists in the Target Base Database its Valid Set Relationships will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database its Valid Set Relationships will be ported from the Source Base Database to the Target Base Database

4747

ITEM ATTRIBUTE RULESITEM ATTRIBUTE RULES

• If the Item Type exists in the Target Base Database its Attribute Rules will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database its Attribute Rules will be ported from the Source Base Database to the Target Base Database

4848

ITEM BLOCK ATTRIBUTESITEM BLOCK ATTRIBUTES

• If the Item Type exists in the Target Base Database its Block Attributes will not be ported from the Source Base Database

• If the Item Type does not exist in the Target Base Database its Block Attributes will be ported from the Source Base Database to the Target Base Database

4949

RELATIONSHIPSRELATIONSHIPS

• All Relationships are ported from the Source Base Database to the Target Base Database

• Dimensions CM will resolve any attempt to create duplicate relationships.

5050

RELATIONSHIPSRELATIONSHIPS

• All Design Parts in the Source Product will be ported to the new Product in the Target Base Database

5151

PROJECTSPROJECTS

• All Projects in the Source Product will be ported to the new Product in the Target Base Database, along with their entire directory structure.

• Actual Items in the Source Base Database Projects will not be ported.

5252

STREAMSSTREAMS

• All Streams in the Source Product will be ported to the new Product in the Target Base Database, along with their entire directory structure.

• Actual Items in the Source Base Database Streams will not be ported.

5353

USER ACCOUNTSUSER ACCOUNTS

• User Accounts that exist in the Source Base Database that DO NOT exist in the Target Base Database will be ported to the Target Base Database

5454

ROLE ASSIGNMENTSROLE ASSIGNMENTS

• Role Assignments that exist in the Source Base Database that DO NOT exist in the Target Base Database will be ported to the Target Base Database

5555

PRIVILEGE ASSIGNMENTSPRIVILEGE ASSIGNMENTS

• Privilege Assignments that exist in the Source Base Database that DO NOT exist in the Target Base Database will be ported to the Target Base Database

5656

EMAIL SUBSCRIPTIONSEMAIL SUBSCRIPTIONS

• Email Subscriptions that exist in the Source Base Database that DO NOT exist in the Target Base Database will be ported to the Target Base Database

5757

DemonstrationDemonstration

5858

Source ProductSource Product

• Base Database – DEMO_SRCDB

• Two Products– $GENERIC– DEMO_PROD

• Product – DEMO_PROD– 7 Request Types– 7 Item Types– Etc.

5959

Target ProductTarget Product

• Base Database – DEMO_TGTDB– One Product ($GENERIC)– No Request Types– No Item Types– etc,.

6060

DemonstrationDemonstration

• Verify DEMO_SRCDB• Verify DEMO_TGTDB• Run ProductPortability

– Select DEMO_PROD as source product– Source code is GENERATED (No Coding)

• Approximately 15 seconds

– Product is ported• Approximately 2 minutes

• Verified by RPCP DEMO_PROD in both Base Databases

6161

L&M Function LibraryL&M Function Library

6262

ComparisonsComparisons

• Native DMPMCLI– Lines of code needed to be developed to port

a typical product – >700,000 lines of code– Level of Java Scripting experience needed –

VERY experienced

• L&M Function Library– Lines of code needed to be developed to port

a typical product – <1,500 lines of code– Level of Java Scripting experience needed –

mimimal

6363

Answers For Your Questions

6464

Lovell & Mercier, Inc.

PO Box 1296

Warrenton, VA 20188

www.lovellmercier.com

540-347-7274