 |
|
Assisting platform development
|
|
|
|
| eBinder's "platform packaging (PLP) feature" assists in platform development. A platform here means the verified boot image including RTOS, BIOS, and basic middleware and the related configurations. |
|
|
| Where and when the platform packaging feature works best |
|
|
| * |
Distributed development |
| |
In large-scale software development with a number of people involved, it is common to divide the target software into sections and have developers work on the sections separately. In this case, some developers work first on the platform, which is the base of the whole system, including RTOS and BIOS. Then, using the standardized platform, other developers proceed with each part of the application. |
| * |
Developing a product series or product line |
| |
If each new product release requires verification of many common platform elements, a common platform for all products may help avoid duplicate work. |
Typically, a platform, including source code which can be modified, is passed to application developers. Without protection, a naive application developer may modify the platform code or configurations accidentally. Or, if he changes build settings, some modules may not be linked properly. The PLP feature minimizes this type of risk.
For small-scale development, the conventional method is still effective. |
|
|
| Benefits of the platform packaging feature |
|
|
| Platform developers and platform users are explicitly separated |
|
| The concept behind this feature is to allow platform developers to focus on already-verified and reliable platform development. Updates can be made using eBinder's iterative development cycle. At the same time, platform users can concentrate on application development using a stable platform. |
|
|
| Simplifying platform development and distribution |
|
| Using the PLP feature, platform developers can create a platform package (PLP) from an already-verified and configured platform to distribute to platform users. A PLP consists of source files, object files, configuration information, and documentation. Normally, a platform also contains a verified boot image including the RTOS, BIOS, and basic middleware and related settings. |
|
| Control the usage environment of a platform |
|
| A PLP can be used to control the usage environment. Files may be restricted from rebuilding by making them binary-only. This will avoid the unintentional modification of platform modules or settings. Limitations can also be placed on items for building or configuration. Platform users cannot edit a PLP. They are only allowed to add middleware to a distributed PLP and delete the added middleware. |
|
| Version control on a platform |
|
| A PLP can make version control easier. |
|
|
|
