FIspace Review Meeting 1 T280 Francisco Pérez Atos

FIspace Platform Architecture Operational Model and Stakeholders WP Status and Roadmap perezdf2 Agenda Pending:Integrate with rest of the modules

SDK Module – Position in FIspace platform BCM EPM

perezdf T280: FIspace Studio SDK Objecties Ease developing work during the implementation of the apps, providing some specific tools and hiding the complexity of the platform Strategic Reuse a wirely well known SDK based on Eclipse platform Road blocked issues Autogeneration of artifacts applying the constraints of Eclipse plugin Fully integration with Maven built engine Aligned approach to the similar Eclipse distribution hosting in Eclipse.org Fixed In Progress Fixed Tools are not silver bullets but make life easier

perezdf5 T280: FIspace Studio SDK Community Open Source Promotes the idea of universal access and redistribution Make easy the “howto” in order to get focus on “what” develop Tooling Eclipse JDT (for example, classpath container) Fully integration of specific models and APIs Specific facilities to deploy and app storage Runtime Preconfigure framework provide standard and specific libraries What behind the shell egg is… + Backend Widget FISpace library JDT FIspace Community FIspace Deployment +

Achievements Integration with Maven built engine in order to reuse preimplemented plugins and archetypes Implementation of Wizard plugin in order to start spreading out Fispace Studio distribution as first starting point in the Fispace app development Next steps – Enrich set of plugins including some related to specific Fispace vocabulary as I/O channels and API message handling – Integration with FIspace components for development activities as auto deployment of apps in FIspace Task 280 Work Status

Questions?