1 / 7

FIspace Review Meeting 1 T250

FIspace Review Meeting 1 T250. Francisco Pérez Atos. Agenda. FIspace Platform Architecture Operational Model and Stakeholders WP Status and Roadmap. Pending:Integrate with rest of the modules. SDI Module – Position in FIspace platform. BCM. EPM. T250: System & Data Integration.

jerod
Télécharger la présentation

FIspace Review Meeting 1 T250

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 1T250 Francisco Pérez Atos

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

  3. SDI Module – Position in FIspace platform BCM EPM

  4. T250: System & Data Integration • ReceiveInformation • Send GPS Position • ReceiveInformation • ReceiveInformation • Deliver Box • NeedTransport • NeedTransport • Send GPS Position • ReceiveInformation • Deliver Box • Deliver Box • NeedTransport • NeedTransport • MovePackage • Send GPS Position • ReceiveInformation • Deliver Box Because we all are different, we have different needs • Objecties • Reception of different types of data from different resources and normalized to FIspace vocabulary in order to process them • Strategic • Towrapmessagesindependly of itnature and transportthem in a normalizewayacrossFIspace • Road blockedissues • To find a pattern design which allows abstraction of data • Definition of interfaces , API and communication channel FIspace Fixed In Progress

  5. T250: System & Data Integration How is the internal mechanish.. • CommandPattern • Represent and encapsulate all the information needed • Makes it easier to construct general components that need to delegate • Centralize communication channel • I/O Channel • Use of RESTfullwebservicesbecause of itlightweightmessage + + +

  6. Task 250 Work Status • Achievements • Implementation of the Command Pattern Design • Definition and Implementation domain model • Definition, implementation and deployment of I/O channels • APIs • Next steps • Support interaction with apps backend by one flexible interfaces • Harmonize message synchronization topics • Control of exception and transaction handling

  7. Questions?

More Related