Pluging and unpluging
Modularity gives plenty of options and flexibility when developing, backing up, sharing, updating, customizing, populating, training, installing, etc.
– Developing: When having more than a development on the same environment, being able to separate each artifact into modules makes developments much more structured. You can package a module and plug or unplug it.
– Managing: If you want to manage and supervise your developers work, is easy to do it plug in the modules, verifying and unplug in.
– Backing up: Is enough to execute ant package.module to have a backup of whatever you are developing. If you get on the wrong way, you can unplug the module and plug in your backup.
– Sharing: Sending developments from one developer to other is easy. Sharing developments with de community using the central repository is very easy too.
– Updating: Jumping from one maintenance pack to other is easy using modules. Plug in the .obx file is enough.
– Customizing: It is possible to customize in a development environment (once customization flag is set to true), hide some fields, show other owns, change properties (read only, mandatory, drop down, length, etc.), etc. Then, you can export this parametrization and move it to production environment easily. If other developers of the project need to include some more parametrizations, can install same module, generate a new version, make changes and apply it in production environment.
– Populating: Using reference data populating parametrization tables is very easy.
– Training: Having needed sample data in order to build a demo or a training with not to much effort is simple using modularity.
– Installing: Once you have developed all the modules by different developers, it is easy to plug in all the new modules into production environment. You can build a production environment from scratch and adapt it using already developed modules. Plug in the modules and it’s ready.
And for sure, there are many more utilizations for modularity.
Do you have some more?