Download Improving software configuration management across multiple

50
Improving SCM across multiple Microsoft Dynamics AX 2009 applications
In relation to the releases, both companies describe a time consuming activity of
putting different parts together, ensuring that documentation, training material,
included components, etc. are all in order. This work could be interpreted as being
part of the configuration audit, even though it is more of a collecting and putting
parts together than it is a review activity. However, many of the activities lack
support from the system and rely on manual labour. Also, proper and structured
testing activities are not clearly visible or traceable with the way the companies work.
Configuration audit can be improved.
Both companies describe similar structures in the way they work. To communicate
with the customers, a separate web application is used. This involves transferring the
issues reported in the web application to Development Center, and later updating
the same web application again. The many applications each have a separate
installation of the tool Development Center for maintaining tasks. This makes each
development environment a separate repository, with no possibility of sharing data.
This is a major drawback with the current tool and setup since the environments are
interdependent. According to Royce (1998), one key practice to improve overall
software quality is providing integrated life-cycle environments that support early
and continuous configuration control. The tools used are per environment and are
therefore not providing the well needed integration.
In summary:
•
Missing software configuration management routines, no plan
•
Lack of system support for development and project management
•
Many products to develop, maintain and support
•
One installation per product, version, and service pack resulting in a vast
number of environments
•
Dependencies between products and/or componentized development
4.2 The SCM plan
I would suggest a proper SCM plan is created with basis from the theories in Chapter
2 Software Configuration Management. The SCM organization has to be described
and the level of configuration management for each involved product/component
should be stated. This is important since the level differs between products; the
certified solutions require more ceremony and better control than the smaller
components. The existing support and test organizations should also be described
and how they interact with the development. This addresses the SCM Organization
Pattern.