- supports-1
- supported by-1
- has alternative-1
- assumed for-1
- contains knowledge about-1
| arguments |
This solution isn’t extensible, because it is fitted to the current infrastructure of the organization. When a new data source is introduced, it has to be fitted to the application as well.
The current fit-solution is not complex , relative to the other solutions, because there aren’t any abstractions. The implementations are tightly coupled in the system which makes the application pretty simple.
If we look at the first solution, we see that it is easy to deploy . Only the initial configuration is needed to fit it to the systems within the organization, and no other configuration is needed.
|
| assumes | |
| description |
This scenario describes a current fit – Fitted on the current source systems, without chance of flexibility.
Within this scenario, the application is fitted to the current system. This means that the application is tightly coupled to the current infrastructure of the organization.
For instance, the organization currently uses Mercurial for version control . In this scenario the application is tightly fitted to this version control system. If a new version control system is going to be used by the organization, the internal structure of the application needs to be modified .
|
| knowledge is located in | |
| name |
Current fit data sources
|
| status |
Rejected
|
| supported by | |
| Class |
|
| Name |
Current fit data sources
|