Customers often ask the best way to model application and component dependencies. The most common use of this feature is to ensure that the system checks any application and version dependencies before deployment. For example if application A has a dependency with Application B - perhaps at the component level with a shared library or artifact, the customer generally wants to know about that link before deploying application A to an environment. 

Release Control supports a number of ways to model such a scenario, from third party system integration (think CMDB or asset register), to the use of the inbuilt relationship service, but the most commonly used approach is via simple application, component and version matching, based upon the status of the application and component. 

This is very easy to configure using the Composer interface. Use the following steps to implement this approach: