We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Materializing Applications/Services Ecosystem and Delivery Framework in FI-WARE - FIWARE Forge Wiki

Materializing Applications/Services Ecosystem and Delivery Framework in FI-WARE

From FIWARE Forge Wiki

Jump to: navigation, search

Introduction

Contents

Following is a description of the assets that have been adopted as baseline for building a reference implementations of the GEs in the Apps/Services Ecosystem and Delivery chapter of FI-WARE. The reference implementation of a Generic Enabler is typically based on the evolution and integration of a number of assets, some being open source, therefore publicly available, while others being provided by partners of the FI-WARE project. A Backlog of Themes, Epics, Features and User-Stories followed for the evolution and integration of assets linked to the reference implementation of a Generic Enabler is also included.

Finally, a list of topics still being addressed at a high level follows the description of assets in this chapter. They are mapped into Themes and Epics in the Chapter Backlog. Features and User-Stories, derived from refined of these Theme and Epics will be allocated to Backlogs linked to GEs in the future.

For a comprehensive vision on the Apps/Services Ecosystem and Delivery chapter architecture, you can go here. We highly recommend you to read it before analyzing how reference implementations of GEs are being materialized.

The Roadmap of Applications/Services Ecosystem and Delivery Framework presents a description of the Technical Roadmap planned for the chapter, which will be developed through subsequent Releases of the FI-WARE Platform. Please also check the Releases and Sprints numbering, with mapping to calendar dates.

Generic Themes

The following themes are cross different enablers:


USDL Service Descriptions

Baseline Specifications

  • USDL 3.0 Specifications M5 - A set of service description schemas that are used to describe the various aspects of services accross the service life-cycle. USDL has a focus on describing business aspects but links also to technical aspects described elsewhere. USDL can be used as a common unified description format that enables sharing information about services among the various components of the FI-Ware platform.

Epics

Features


Service Repository

Baseline Assets

Epics

Features


Unit Testing Plan

Product guides

Registry

Baseline Assets

Epics

Features


Unit Testing Plan

Product guides

Marketplace

Baseline Assets

Epics

Features


Unit Testing Plan

Product guides

Store

Baseline Assets

Epics

Features


Unit Testing Plan

Product Guides

Business Elements & Business Models

Baseline Assets

No baseline asset available, it was addressed under the scope of a FI-WARE open call.

Following is the compilation of entries in the Backlog followed for materialization of this Generic Enabler.

Epics

Features



Unit Testing Plan

Product Guides

Revenue Sharing

Baseline Assets

This asset is based on the Settlement Engine product developed by Telefónica I+D as part of the Payment Enabler initiative.


Following is the compilation of entries in the Backlog followed for materialization of this Generic Enabler.

Epics

Features


Unit Testing Plan

Product Guides

Business API Ecosystem

This asset is based on the FIWARE Business Framework released in FIWARE R4 jointly with TMForum API Ecosystem.

Following is the compilation of entries in the Backlog followed for materialization of this Generic Enabler.

Epics

Features

Data Visualization

Epics

Features

Composition Editor and Execution Engine

Baseline Assets

Following is a list of the main assets that have been adopted as baseline for the reference implementation of the generic enablers offering composition:

  • EricssonCommonCompositionCore is a tool set to create and execute composed services and applications. It implements the "Service Composition" generic enabler. It contains a constraint-based graphical Composition Editor and a dynamic late-binding Composition Engine.
  • WebConnectivityEnabler is an application level communication protocol providing it's own addressing and messaging semantics. In composition it can be used for enabling communication (wiring) among web gadgets in different web contexts.
  • Wirecloud Mashup Platform is a framework that allows end-users to mashup/compose and execute service front-ends (also known as gadgets/widgets). It consists of an application mashup editor, a mashup execution engine and a widget/operator catalogue.
  • Mashup Factory is a toolset to compose own services and applications. A graphical editor supports the combination of services in a data flow oriented mash-up style, later to be deployed on an appropriate orchestration engine.
  • LighSemantic-enabled Design Time Semi-automatic Service Composition is a suite for creating processes as service compositions at design time using standard modelling languages and light semantic descriptions and annotations.

Epics


Features






Unit Testing Plan

Product Guides




Mediation

Baseline Assets

Epics

Features


Unit Testing Plan

Product guides


Business Framework (Package)

The Business Framework package provides a set of GEris packaged together that can be installed as a whole:

Product guides

Business Framework Consumption (bundle)

The bundle Business Framework Consumption provides the necessary assets to allow the automatic deployment of a set of GEris in the FIWARE Lab Cloud:

Service Business Frameworks (SBFs) represent one of the cornerstones of service ecosystems. The key objective of a SBF is to build and support an ecosystem of applications and services that is sustainable and fosters innovation as well as cross-fertilization. In particular, it consists of a number of interrelated components that support managing services in the business framework across the whole service lifecycle: from creation and composition of services to monetization and revenue sharing.

The Business Framework Consumption Bundle offers an environment where service providers can meet potential customers bringing together offering and demand while supporting the complete offering live cycle, from the creation and publication of service and application offerings under flexible and complex pricing models, to the acquisition and charging of those offerings including the revenue sharing between the involved stakeholders.

Bundle guides

Wirecloud Monetization (bundle)

The bundle Wirecloud Monetization provides an installable set of GEris packaged together:

The Wirecloud (App Mashup) Monetization Bundle represents one of the uses cases of the Service Business Framework and intends to show the potential of the SBF features provided by FIWARE in a concrete use case. This use case is based on the use of the SBF to monetize the mashable application components used in Wirecloud.

Bundle guides

Issues for the Open Calls


Personal tools
Create a book