9.3. Checklist for using subproducts

Linus Tolke

In the ArgoUML project we use several subproducts to solve parts of the problem for us. These subproducts are an important part of the ArgoUML tool and must be handled in a good way if ArgoUML is going to be successful.

When this is written (March 2004) we have had problems with the discontinuance of one of the subproducts (NSUML) and will continue to have it for well some time in the future, until we have managed to replace it. The problem with NSUML could probably not have been foreseen or avoided if this checklist would have been in place when NSUML was taken into the project but some more appearant risks with subproduct candidates might be.

Here is the list of things to check in the subproduct and to discuss with yourself and maybe with the ArgoUML development team before considering to use it in the ArgoUML project.

Notice that we should not and don't need to do this in a passive way. We should explain to the subproduct team what we want and why. Especially for subproducts that we have already in ArgoUML but also for project that we consider taking in. This is to increase the likelyhood that they will have us in mind when planning and evolving.

Here are the steps to go through and the recommended order once the decision is taken to use the subproduct in ArgoUML:

See Section 12.8, “How to relate issues to problems in subproducts” for a discussion on how to handle bugs found in subproducts and updates of the version of a subproduct.