PlatformKit is a platform dependency management toolkit. It can be used to support platform-specific configuration in development processes based on the Model Driven Architecture and/or Software Product Lines, where multiple (versions of) software and/or hardware platforms are targeted.
PlatformKit makes its decisions based on platform ontologies. It uses a base vocabulary that explains what a “platform” is. On top of that, platform dependency constraints of a particular software artifact can be defined. Finally, several platform instances can be modelled. If all these are put together, PlatformKit can determine which platform dependency constraints are satisfied by the given platform, and which of the platform dependency constraints is most-specific or least-specific.
PlatformKit currently comes with support for Java ME (MIDP, Personal Profile), and Java SE platforms. Java EE support is under development.
PlatformKit uses Jar2UML to measure platform dependencies of existing Java software. It can then compare these dependencies against a number of supported Java libraries, such as JRE class libraries and several versions of the SWT library.
The following is an introductory presentation:
The instant messenger case study uses PlatformKit. There's no up-to-date documentation on this, but the research principle can still be learned from the following flash presentation/demo that illustrates the use of PlatformKit's predecessor CDDToolkit for the UML 1.4 version of this case study:
- Wagelaar, D., MDE Case Study: Using Model Transformations for UML ands DSLs, presentation/demo for JUGS, Zürich, Switzerland, 30 March 2006.
[ OpenOffice ] [ Adobe PDF ] [ Flash demo (49 min.) ]