![]() |
Real world scenarios presents experiences from actual systems that reveal the pain and cost of deploying highly |
| configurable systems based on components. |
![]() |
Hidden dependencies are a large problem in understanding and deploying systems. |
![]() |
Configuration files: Configuration files allow developers, testers, deplorers, operators (any user of the system) to |
![]() |
dynamically configure it. Software components then use these values to configure and tune themselves. |
![]() |
Versions of Components: |
![]() |
While component dependencies are not well documented, dependencies between versions are even less | |
| documented. |
![]() |
Deployment problems with component versions can also appear when two components in a system depend | |
| on different versions of the same component. Problems arise when the component space is cluttered with | ||
| multiple versions of the same component. |
![]() |
Example of versioning components - HTML |
![]() |
Developers and testers must consider the different types and different versions of browsers found in their | |
| user base. |
![]() |
Browser variants can differ dramatically with variants in HTML, different JavaScript language support, and | |
| supported plugins. |
![]() |
The problem is compounded when considering the variable WAP devices and their different form factors. |