1. Definition of the SDK for FIspace Augusto Morales & Hector Bedón UPM

2. SDK Definition What does the SDK do? What doesn’t the SDK do? Apps created by the SDK SDK look and feel and features Apps life cycle

3. What does the SDK do? The SDK : The software development kit for App developers basically is Eclipse plus the required libraries Allowed to subscribe to information (require information in order to operate) App developer need to indicate which information they need to operate - Has NOT to configure the metadata/msg format that ST250 to be able to receive msgs from backend systems ○ Handled by the Business Architecture (Configurator) Whenever there is an interaction between at least 2 people or business partners than the business architect will have to define the BE and the App will need to indicate what are its requirements to support this collaboration Develop the App components according to the characteristics of Apps -- Subroutine called and that provide a service (e.g., App backend has a service that will be invoke by the BE of the collaborative process) – App that subscribe to an information (Pub/Sub App) – Not allowed to build this kind of characteristic for now -> Only UI functionality, e.g., wetter forecast, clock, etc Taken from: Clarissa’s and Andreas email, Andreas Key Agreement Essen,Oct’13 doc

4. What doesn’t the SDK do ? Not allowed to create or extend BEs - (In the future) Not aware of BEs in the future (but for now we will be in contact and aware of the existence of BEs) Taken from: Clarissa’s and Andreas email, Andreas Key Agreement Essen,Oct’13 doc

5. Apps created by the SDK App Internal Logic Which language to use for defining this How to define and to use this Interface Is the UI built in the App? SDK How to relate UI with App internal logic How to use the three types of App components (subroutines, subscribe to an information, only UI functionality) What is the APP lifecycle? Taken from Key aggrements actions Essen, Oct 2013 Business Architect Platform Developers

6. SDK Look and feel and features UPM provides a mock-up in order to fix concepts before programming: – SDK User Interface – SDK supporting libraries – App structure of the generated App Internal Components Interfaces Apps – SDK Integration with B2B platform – App development model

7. SDK Mock-up  To present the mock-up developed by UPM.

8. SDK Mock-up  To present the mock-up developed by UPM.

9. SDK Mockup  To present the mock-up developed by UPM.

10. SDK FIspace Editor  To present the mock-up developed by UPM.

11. SDK Design approach 1 App Internal Logic GUI SDK CSB Business architects define business rules Platform Developers API Widgets Templates? Like Android templates? Javascript

12. SDK Design approach 2 GUI SDK CSB Business architects define business rules Platform Developers API GUI Interactions App Internal Logic API

13. SDK developed as one Plug-in for Eclipse Introduction is a small program which acts as a plug-in loader. functionality is located in different plug-ins. is surrounded by hundreds of plug-ins. Eclipse: are structured bundles of code and/or data that contribute functionality to another program. Plug-ins can consume functionality provided by other plug-ins. and it can extend another plug-ins by providing its functionality to them will not be activated unless it has been requested according to the user's activity. Eclipse plug-in

14. SDK developed as one Plug-in for Eclipse Introduction (II) JAR file A plug-in contains the code and resources that it needs to run. It can be delivered as a JAR file. Self-contained It describes in its manifest files who it is, which plug-ins it contributes and which plug-ins it needs to work. Self-describing Functionality that can be added to other plug-ins (e.g. views, buttons, editors). Extension Well-defined places where other plug-ins can add functionality. Extension point

15. Eclipse SDK: Structure Standard Widget Toolkit (SWT): is a low-level operating system independent toolkit to develop the UI. JFace UI framework: provides higher-level application constructs for supporting the development of the UI. Workbench UI plug-in: defines a number of extension points that allow other plug-ins to contribute menu and toolbar actions, dialogs, etc. UI (User Interface) Java development tools (JDT) plug-in: extend the platform workbench by providing specialized features for developing Java code. Plug-in Development Environment (PDE): supplies tools that automate the development of plug- ins. Business Business layers View layers