Dynamic Models and Static Models of the Enterprise
The primary objective for technical analysis is to produce a technical design that can be used for the implementation of a system. The technical design should clearly outline to the implementers the exact tasks that need to be undertaken to produce a working system. The technical analysis should make implementation choices, and make assumptions about vendors and infrastructure. Even at this stage, a technical design can be vendor and deployment independent. If required, it is possible to make a layered technical design, that separates an implementation model from a vendor realization. For instance, it is possible to make a database model that can be realized with any RDBMS, or an object model that can be deployed to any Application Server. The vendor specific implementation details can be placed in a separate model, such as a deployment model that explains the changes necessary to make an implementation function in a vendor- specific environment.
The key artefacts produced through technical analysis should be the following:
Dynamic model
- Services model
- System interaction model
Static model
- Domain model
- Data model
Your technical analysis should be closely aligned to the system and business models, and your implementation scope should be governed by the system models.
