Architecture by Implication

This anti-pattern is about architect's overconfidence, forgetting to document the specifications and documentation during development stage.

Symptoms and Consequences

• Lack / missing documentation for future enhancement and references.
• Hidden risk caused by scale, domain knowledge, technology, and complexity, all of which emerge as the project progresses.
• Impeding project failure or unsuccessful system due to inadequate performance, excess complexity, misunderstood requirements and all no documentation related issues.
• Ignorance of new technologies.
• Absent of technical backup.

Causes

• No risk management.
• Overconfidence of manager, architect, or developers.
• Over-reliance on previous experience.
• Implicit or unresolved architecture issues caused by gaps in system engineering.

Refactor Recipes

• Define the architectural goal.
• Define the problem it is solving, and the architecture purpose.
• Select the view perspectives.
• Analyze each view perspectives.
• Integrate the blueprints.
• Track the view perspectives to needs.
• Iterate the blueprints development.
• Promote the architecture.
• Validate the implementation.