Example of Strategic Pattern:
Visualization
Brief Description:
Wanting to see a flow chart representation of complicated data relationships or complex software code.
Benefits Analysis:
- As a tactical move, team members realize that a complicated component relationship and workflow may be better understood through a flowchart or a block diagram of some sort. In many projects, even though it may not be part of the original strategic plan, the advantage of having a visual representation of the existing system or the system to be built is realized and ad-hoc demands for such forms of visual representation are made.
- Sometimes, just the process of making the visualization artifact is good enough to lend understanding of the system, in addition to the finished artifact serving as a means to enhance understanding.
- As a tactical move in increasing the understanding of the system to be built, the demand for visual representations is usually a fruitful move, provided the visual representation produced is effective.
- All members can potentially have different, even conflicting views of the design, which may not be evident from the written or verbal form of design representation.
- This type of visual representation helps in bridging any disparities or gap in understanding and brings everyone involved to effectively the same level of understanding.
Risks:
- If the visual representation is too vague however, it may confuse some folks, or generate discussion and an opportunity for things to become clear.
- Some team members may believe generating multiple visualizations of the system may be a waste of time and resources, specially if they already understand the system.
Example:
Both CS team members and client wanted to see that in Seabase I and the client wanted to see that again in Seabase II.