Module Baselines within a Service Component Architecture

[article]

with this is that the SCA module has behaviours that have to be supported in away that can be traced but at the same are treated as a software change which would created a new version of SCA modules which is not what you want.

The idea to support this is a very old idea which I have used many years ago but which fits the build exactly this is the use of information notes. The type of behaviour we are trying to control is the change of business rules, which will change every so often as the business gets the used to the service. As each new information note is issued then the behaviour changes and usually comes thorough the Configuration Manager. This will show the previous and new behaviour that the service has to use, however the information of the
change comes from the Senior business Analyst. The change is as usual is tested in an environment before it goes in to the Production environment and when it is tested to make sure the production environment has change has taken affect.

The information note has work in conjunction with the existing systems as this will provide extra information to the /change request record.

To get his baselining in we have approached this is an two stage method so people can get used to this new method and allow for the main baseline to get in and then look at how we adjust the overall method for the second baseline to put into place and this has to tie up with existing systems.

While this article gives a favour of the problems SOA gives to traditional methods of baselines and how many of the existing systems need to be adapted to the new ways of working.

Another aspect of this work how hard I have had to work on the senior management to make sure that they on board for the changes to the existing systems and making sure I have the budget to make this happen. This has require a great deal of explaining to them and they have been very response and supportive we has made my life a great deal easier.

As it can be seen the considerations that I come across during the construction of the baseline for the project and that as Configuration managers we have to deal with. While information notes are not consider as baseline in the true sense of the Configuration management. It is a type of baseline because it is identifying a controlling artefact of the SCA module

About the Author
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

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!