The use of Baselines in a SOA Environment


SCA module and shared components, which will need their own tags.



This shows where we have shared components
such as interfaces that they will have their own tag.

Shared libraries or components in a SCA


An SCA module may be up of a number of shared libraries or components. Those components which are shared will the number as the SCA module that is being released. The shared components will have there own tag because other SCA Modules will reference these.

The tag sequence will look like this

SCA Module 1.1

            C1.1 (reflecting this is non shared component)

The non-shared tag will also be referenced first in the list that makes up the SCA module.

Movement of baselines
If one of the process baselines, then the service baseline will change and depending on the change will determine how the baselines will change.  In these examples it is assumed that Process B and C are shared libraries, so therefore have their own tags.

  • Customer_Alterations _1.0.0
    • ProcessA_1.0.0
    • ProcessB_1.0.0
    • ProcessC_1.0.0

This will always be the initial starting baseline for both the service and the process

  • Customer_Alterations _1.0.1
    • ProcessA_1.0.0
    • ProcessB_1.0.1
    • ProcessC_1.0.0

This shows that ProcessB has had a patch change; therefore the service baseline has change by 0.0.1

  • Customer_Alterations _1.0.2
    • ProcessA_1.0.1
    • ProcessB_1.0.1
    • ProcessC_1.0.0

This shows that ProcessA has had a patch change; therefore the service baseline has change by 0.0.2

  • Customer_Alterations _1.1.2
    • ProcessA_1.1.2
    • ProcessB_1.0.1
    • ProcessC_1.0.0

This shows that Customer Alterations LLP had a minor change and therefore ProcessA has also changed number, as this needs to be same as the LLP number.

  • Customer_Alterations _2.0.0
    • ProcessA_2.0.0
    • ProcessB_1.0.1
    • ProcessC_1.1.0

This shows that there has been major change in ProcessA and this will result in the Service baseline having the baseline 2.0.0 even though ProcessA and ProcessB are still which patch and minor releases respectively.

  • Customer_Alterations _2.0.1
    • ProcessA_2.0.0
    • ProcessB_1.0.1
    • ProcessC_1.1.1

This shows there has been patch change to ProcessC

  • Customer_Alterations _3.0.0
    • ProcessA_2.0.0
    • ProcessB_1.0.1
    • ProcessC_1.1.1
    • ProcessD_1.0.0

This shows there has been a new process (ProcessD) being added to the service, so the follow the convention the major number will have to change and in the case it moves from 2 to 3.  It also shows there has been a patch releases in ProcessC and the Service baseline has moved as well.

Co-existence of Baselines
There will be the possibility of many baselines existing on the environment at any one time the release note will reflect which baselines are currently on the environment. This will help if there is a problem occurs on the environment that the person carrying out the
resolution of the defect has a complete of the set up as regarding to SOA delivery.

Alan Rogers has been working as a Configuration Manager for the last 13 years and been in the IT industry for 17.  He has worked on many projects both designing the Configuration Management infrastructure as well implementing it for many large companies for particular projects. A lot of these processes and standards that he developed for the project have in many cases been adopted as corporate standards. He also has an MBA from Henley Management College, which has been very useful when trying to explain Configuration Management to Senior Management, and is also a chartered Manager holding a MCIM.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.