Product Portability “Optimizing Your Investment in Dimensions CM” Presented by Lovell & Mercier, Inc.

2 Trademarks & 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.

3 Agenda Introductions –Attendees –Lovell & Mercier –Emagine IT Background Product Portability Demonstration Questions

4 Lovell & 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

5 Emagine 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.

6 Background 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)

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

8 “Out-of-the-box” Capabilities in Dimensions 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= –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

9 Classical 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

10 Facts 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

11 Tools 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 ***

12 Skills 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

13 Technical 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

14 Considerations Order of execution is MOST important Verification is VERY important MOST IMPORTANTLY – NO ORACLE TABLE UPDATES –DMPMCLI –DMCLI

15 Objects 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 Subscriptions

16 Details

17 PRODUCT 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

18 ROLES Role Name –Cannot exist in Target Base Database Role Description –From Role in Source Base Database

19 LIFECYCLES 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

20 LIFECYCLE 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

21 LIFECYCLE 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

22 VALID 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

23 VALID 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

24 DESIGN 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

25 BASELINE 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

26 BASELINE 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

27 BASELINE 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

28 RELEASE 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

29 RELEASE 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

30 REQUEST 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

31 REQUEST 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

32 REQUEST 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

33 REQUEST 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

34 REQUEST 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

35 REQUEST 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

36 REQUEST 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

37 REQUEST VALID SET RELATIONSHIPS 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

38 REQUEST 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

39 REQUEST 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

40 ITEM 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

41 ITEM 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

42 ITEM 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

43 ITEM TEMPLATES Item Templates are not ported at this time

44 ITEM 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

45 ITEM 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

46 ITEM VALID SET RELATIONSHIPS 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

47 ITEM 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

48 ITEM 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

49 RELATIONSHIPS All Relationships are ported from the Source Base Database to the Target Base Database Dimensions CM will resolve any attempt to create duplicate relationships.

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

51 PROJECTS 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.

52 STREAMS 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.

53 USER 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

54 ROLE 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

55 PRIVILEGE 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

56 SUBSCRIPTIONS 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

57 Demonstration

58 Source Product Base Database – DEMO_SRCDB Two Products –$GENERIC –DEMO_PROD Product – DEMO_PROD –7 Request Types –7 Item Types –Etc.

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

60 Demonstration 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

61 L&M Function Library

62 Comparisons 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

63 Answers For Your Questions

64 Lovell & Mercier, Inc. PO Box 1296 Warrenton, VA