5.1 Causes of Design Deterioration
The previous sections outline the main problems of the direction
taken by the implementation following the Pre-ID, which is not
always towards improvement. Intuitively, as the project
progresses understanding of the solution to be implemented
should be improving, shared mental models of the team should be
more accurate, and design should be maturing. While trials and
errors may explain some temporary deterioration, in an efficient
process, they should correct themselves before Post-ID, which is
not what is observed.
Observations show that opportunism played an important role in
design erosion. In many cases, developers preferred to add the
new features in existing designed classes instead of creating new
classes to hold these features. This behavior may be explained by
the perception of design artifacts as being a gold standard; it
introduces a reluctance to change and adjust Pre-ID. This is
corroborated by the fact that classes created from scratch do not
suffer from the type of bad implementation likely to be found in
implemented Pre-ID classes. It is found that all 22 created classes
have been implemented correctly.
This does not mean that design artifacts should be cast aside.
Design artifacts are still useful to facilitate the sharing of mental
models and understanding between team members. Blind
opportunism during implementation may constitute an increased
risk, at least for future maintenance. Therefore, taking the Pre-ID
as a gold standard to abide to, or discarding it completely as junk
is to consider cautiously.
5.1 Causes of Design Deterioration The previous sections outline the main problems of the direction taken by the implementation following the Pre-ID, which is not always towards improvement. Intuitively, as the project progresses understanding of the solution to be implemented should be improving, shared mental models of the team should be more accurate, and design should be maturing. While trials and errors may explain some temporary deterioration, in an efficient process, they should correct themselves before Post-ID, which is not what is observed. Observations show that opportunism played an important role in design erosion. In many cases, developers preferred to add the new features in existing designed classes instead of creating new classes to hold these features. This behavior may be explained by the perception of design artifacts as being a gold standard; it introduces a reluctance to change and adjust Pre-ID. This is corroborated by the fact that classes created from scratch do not suffer from the type of bad implementation likely to be found in implemented Pre-ID classes. It is found that all 22 created classes have been implemented correctly. This does not mean that design artifacts should be cast aside. Design artifacts are still useful to facilitate the sharing of mental models and understanding between team members. Blind opportunism during implementation may constitute an increased risk, at least for future maintenance. Therefore, taking the Pre-ID as a gold standard to abide to, or discarding it completely as junk is to consider cautiously.
การแปล กรุณารอสักครู่..
