Configuration Status Accounting. The traceability of the software configuration is main-
tained throughout the software lifecycle.
We won't get into the details of software configuration management because it is beyond the
scope of this topic. Here, we are interested in using SCM techniques to rationally organize and
manage the deployment process. Naturally, you can avoid using such techniques, but it is like
using your credit card without ever controlling your bank account. Though easier at first, it
may become dangerous in the future.
Though the best way to proceed is through the use of rigorous SCM techniques, for
simple deployment needs some simplified SCM techniques could be used instead—
saving time and producing the desired benefit.
A simple and effective way to keep your software deployment under control is to use the client
A client configuration can be defined as the set of all the items that are meaningful for our
Java software from a deployment perspective.
For example, a client configuration could be composed of the user identity, a given JRE, and a
set of JAR files that compose our application.
Basically, it is a snapshot of what we need to have properly installed on a client computer in
order to run our application. Note that the platform type itself is a part of the client configura-
tion. So, if we plan to provide two platform-dependent versions of our software, we need to
have at least two different client configurations.
A client configuration is the exact description of what minimally has to be installed on the
client platform in order to run the application. One can extend this concept to include in it the
user identity or other client-specific data that are meaningful for deployment.
An application is described by the following client configuration.