This tag contain 1 private blog which isn't listed here.

Common or Shared Code in Dimensions CM (Part 1 of 3)

This is part 1 of a 3 part series. 

Best Practice

There is no such thing as best practices. Two different teams approaching the same challenge might succeed with completely different approaches.  What works well for one team may well be irrelevant for the other.  What helped one team might be counter-productive for the other.

So think of the above paragraph as my disclaimer. With that out of the way, let’s proceed. ッ

Overview

Maintaining common or shared files that are used across multiple development efforts can be challenging.  There are many ways to configure Dimensions CM to support this. 

In this 3 part series, I will talk about the pros and cons of two different scenarios so that you can decide which approach to take. Remember that one size does not fit all; hence the reason why Dimensions CM is so adaptable and can support different processes.

At the end of each scenario, I will include how to configure Dimensions CM to support that particular scenario.

Before we get started, let’s cover some terminology and a few ground rules to avoid confusion.

Continue reading
8316 Hits
0 Comments

Common or Shared Code in Dimensions CM (Part 2 of 3)

This is part 2 of 3 part series. See part 1 for an overview.

Scenario 1: Keep a copy of Common with every Application

In this scenario, all applications and the common code are contained in a single Dimensions CM product called Qlarius.  

Each Application will have:

  • Their own design part(s) to control what files belong to a particular application and to facilitate relating common code.
  • Their own streams to isolate development efforts.

The Common will have:

  • Its own design part(s) to control what files belong to a particular common module and to facilitate relating to applications that require/use it.
  • Its own streams to isolate development efforts for updates as it changes over time.

b2ap3_thumbnail_S1_KeepCopyCommonWithApplication.png

Continue reading
10519 Hits
0 Comments

Common or Shared Code in Dimensions CM (Part 3 of 3)

This is part 3 of 3 part series. See part 1 for an overview.

Scenario 2: Reference every Application to Common

In this scenario, all applications are in a single product (Qlarius) and the common code (Common) is contained in a separate Dimensions CM product. 

Each application will have:

  • Their own design part(s) to control what files belong to a particular application and to facilitate relating common code.
  • Their own streams to isolate development efforts.

The Common Code will:

  • Be treated as a ‘vault’
  • Be referenced by the developers for local builds and tests.
  • Require a process to not allow developers to deliver any common code to the application stream

b2ap3_thumbnail_S2_ReferenceCommonWithApplication.png

Continue reading
9312 Hits
0 Comments

Best Practice for Parallel Development using Serena Dimensions

Updated version of the Best Practice for Parallel Development using Serena Dimensions is now available.

When Dimensions CM first introduced stream development capabilities back in 2009, a best practice guide was created. Prior to CM 14.1 you could only merge streams when performing an update operation. In CM 14.1 (and later) the update and merge operations have been separated and there is a new Merge wizard and command.

 

Merging streams and changes is now quicker and easier to accurately identify the source of changes, especially when refactoring has occurred. This updated guide now reflects the new process of merging streams plus more.

 

Best_Practices_Parallel_Development_using_Serena_Dimensions_2015.pdf

 

Continue reading
9530 Hits
0 Comments

Recent Tweets