Java Reference
In-Depth Information
11.2
I
ntegrating antipatterns with process
We can indeed make a significant impact by studying and applying the theory
of antipatterns. While individual pockets of value can make a difference, we
can do much more by integrating them into our processes and organizations.
Figure 11.1 illustrates the six stages in which we can improve our process with
antipattern-related activity.
Figure 11.1 shows a common iterative development process that we
reviewed in chapter 2. The eight-ball symbols identify the likely places that a
development process can be modified to include protection from antipatterns.
Some deal with prevention or early detection of antipatterns, and some deal
with capturing and refactoring them.
C
Plan
Design
Code
Assess
Plan
Design
Code
Assess
D
Plan
Design
Code
Assess
Plan
Design
Code
Assess
F
Plan
Design
Code
Assess
Plan
Design
Code
Assess
E
Prototypes Designs
Beta Release
Production
G
B
Figure 11.1 An antipattern can be addressed in at least six stages in the development process.
At initialization, we can research antipatterns in our chosen domain. At design and code time, we
can use annotations and inspections to prevent them. At testing time, we can establish patterns.
Between cycles, we can refactor. At the end of the cycle, postmortems help to identify
antipatterns.
B
In the project initialization.
We can identify antipatterns related to a technology or
approach. By aggressively seeking out likely problems, we can short-circuit many
of them before they start. This is a highly recommended practice that helps pre-
vent antipatterns.
c
In the design stage.
In our design documentation, we can provide a place in our
design artifacts to capture likely antipatterns. We should also capture annotations
