With a dependent deployment strategy, some packages are published individually, as standalone units, while others are combined and published as multipackage units. In addition, rather than have a single M-Banking application, each feature is provisioned and installed separately.
In this use case, the goal is to keep the Investment functionality independent and self-contained and so the development and enhancement roadmap can continue without any external dependencies. This separation is desirable, since the availability requirements are most stringent for the Investment application. Conversely, the Account Management application is developed and designed to still depend on the MBOs in the Investment package, without sharing the package directly. For this strategy, the Account Management application now subscribes to MBO data in the Investment package, and is instead assigned only to the Account Management package.
