Isolate Abstraction Weakness
The Analyst detects and isolates an abstraction weakness. To avoid overcomplexity, the analyst does not research for a solution and implement it.
Generalized Construct Request
The Analyst passes a Generalized Construct Request to the Domain Experts.
Specific Construct
The Domain Experts (e.g. language masters, existent project members) detect based on the generalized construct request the Specific Construct within their domain (e.g. constructs of the programming language, project details, etc.).
Requirements Audit
The suggested constructs are validated against an existent Complex Requirements Set (e.g. Requirements of a Consistent Software Production System) and the final construct is selected.
Change Management
Depending on the project organization and on the complexity of the change, several preparation steps are necessary, e.g.:
- affects of the change must be verified
- people must be convinced
Implementation
The Implementation (= code level results) should happen by the domain experts or by other participants, prefered the original author of the code. This has the additional benefit to keep the copyright/authorship status of the code (see Licensing Process).
Important to Realize
This is a give and take situation.
An abstractly thinking mind must be free of specific constructs. This results in a reduced ability to operate concretely*.
An concretely thinking mind must be full of specific constructs. This results in a reduced ability to operate abstractly (at least within the domain).