1 / 8

FIspace Review Meeting 1 T280

FIspace Review Meeting 1 T280. Francisco Pérez Atos. Agenda. FIspace Platform Architecture Operational Model and Stakeholders WP Status and Roadmap. Pending:Integrate with rest of the modules. T280: FIspace Studio SDK. BCM. EPM. T280: FIspace Studio SDK.

alden-barrera
Télécharger la présentation

FIspace Review Meeting 1 T280

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIspaceReview Meeting 1T280 Francisco Pérez Atos

  2. Agenda • FIspace Platform Architecture • Operational Model and Stakeholders • WP Status and Roadmap Pending:Integratewithrest of the modules

  3. T280: FIspace Studio SDK BCM EPM

  4. T280: FIspace Studio SDK Tools are not silver bullets but make life easier • Objecties • Make ease their work during the implementation of the apps, providing some specific tools and hiding the complexity of the platform • Strategic • Reuse a wirelywellknown SDK basedon Eclipse platform • Road blockedissues • 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 Fixed In Progress

  5. T280: FIspace Studio SDK What behind the shell egg is… • 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) • Fullyintegration of specificmodels and APIs • Specificfacilitiestodeploy and appstorage • Runtime • Preconfigure framework provide standard and specific libraries + + FISpace library + JDT Backend + + Widget + FIspaceCommunity + FIspace Deployment +

  6. Task 280 Work Status So far • Achievements • Integration with Maven runtime 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 • Adaptation and Using Scrum methodology. • Next steps (What’s the next?) • Enrich set of plugins including some related to specific FIspacevocabulary as I/O channels and API message handling • Integration with FIspace components for development activities as auto deployment of apps in FIspace • FIspace Studio Release 1.0. and New features.

  7. Known issues • Typical time overhead in using an open source frameworks. • Improve understanding and cooperation among people from different cultures. • TEAM T 280 • Dimitris (Greece) • Paco (Spain) • Augusto (Panama) • Pablo (Spain) • Hector (Peru) • Castulo (Colombia)

  8. Questions?

More Related