classified for an addressed comparison, allowing the identification
of the differences in the same procedure of the development
phase. Figure 3 illustrates the structuring of CDM.
The first step in CDM is to develop a model, a formal
description of each software methods compared. Considering that
most of the technologies have the same development
characteristics [10, 7, 11], similar components are identified and
later described informally and in high level.
To apply CDM it is necessary to use a formal language to
describe the activities of the compared [12]. This formalism is
necessary to consistently represent the details of each activity,
extracting the common characteristics to compare. Two
formalisms are usually used: HFSP described by Katayama [4],
and used in [12], and SLANG described by Bandinelli et al. and
used by Podorozhny [6].