4.2. Quantifying modularity of change scenarios
After producing an overview of the modularity attributes in the base versions, we
proceeded with the analysis regarding the stability of modularity attributes in the
presence of change scenarios. Generally, any variation to their values is considered
undesirable and indicate instability. However, variations are unavoidable, particularly
when a certain module is the focus of an implementation change. Hence, variation in
the values can be unavoidable or negative. Unavoidable variations occur when a
component that is directly related to the a®ected concern is modified. For example, if a
scenario targets the DbC concern (which is the focus of this work), then variations in
the metric for the related modules are generally expected and unavoidable. Since, the
DbC concern crosscuts the entire layer of the HW system among several modules, let
us say that in a particular development phase we are interested on the contracted
modules of the GUI concern. Hence, the change propagation of adding, removing, or
changing a contract in the view related modules are expected and also unavoidable.
However, if unrelated modules are a®ected, these changes should be considered as
being a negative variation. In summary, the approach with most stable design is the
one which minimizes the number of negative variations.
4.2. Quantifying modularity of change scenariosAfter producing an overview of the modularity attributes in the base versions, weproceeded with the analysis regarding the stability of modularity attributes in thepresence of change scenarios. Generally, any variation to their values is consideredundesirable and indicate instability. However, variations are unavoidable, particularlywhen a certain module is the focus of an implementation change. Hence, variation inthe values can be unavoidable or negative. Unavoidable variations occur when acomponent that is directly related to the a®ected concern is modified. For example, if ascenario targets the DbC concern (which is the focus of this work), then variations inthe metric for the related modules are generally expected and unavoidable. Since, theDbC concern crosscuts the entire layer of the HW system among several modules, letus say that in a particular development phase we are interested on the contractedmodules of the GUI concern. Hence, the change propagation of adding, removing, orchanging a contract in the view related modules are expected and also unavoidable.However, if unrelated modules are a®ected, these changes should be considered asbeing a negative variation. In summary, the approach with most stable design is theone which minimizes the number of negative variations.
การแปล กรุณารอสักครู่..
