Project workpackage

Workpackage 1 - From M1 to M12

PaaSport Architecture and Conceptualization

  • - To identify the requirements of the participating software and Cloud PaaS platform vendors SMEs, which represent all different types of stakeholders identified in the value chain of a Cloud platforms marketplace;
  • - To collect requirements, needs and priorities of the Software SMEs at pan-European level regarding the realization of Cloud platforms marketplaces through the large-scale involvement of the members participating SME Associations;
  • - To homogenize and analyze the identified requirements of the European Software SMEs and to create and maintain a prioritized list of the requirements that the PaaSport project will address;
  • - To review the state-of-the-art in the fields of Cloud Computing with special focus on platform-as-a-service, examining the extend that current state-of-the-art affects the identified interoperability and portability requirements;
  • - To design the open, generic PaaSport Reference Architecture for realizing a thin Cloud platforms broker; and
  • - To design and implement the lightweight PaaSport semantic models, which will provide the modeling artefacts and the vocabularies for the creation of the semantic representation of the available Cloud Platform-as-a-Service offerings, the applications to be deployed on top of the proposed Cloud marketplace and the SLAs to be established among the offerings providers and the applications owners.

Workpackage 2 - From M7 to M24

PaaSport Offerings Recommendation Layer

  • - To define a Cloud PaaS offerings discovery, short-listing and recommendation algorithm and model for providing the user with the most suitable and appropriate Cloud platform offering; and
  • - To design, specify and develop the software components of the Offerings Recommendation layer of the PaaSport Reference Architecture which will facilitate the user to select the most appropriate PaaS offering published at the PaaSport marketplace – based on the semantic description and deployment profile of the business applications that the user wishes to put on top of the Cloud.

Workpackage 3 - From M7 to M24

PaaSport Monitoring and Accounting Layer

  • - To take into consideration current state-of-the-art and developments in the fields of Cloud Computing SLAs, billing and accounting, in order to define the innovative PaaSport Service Level Agreement Policy Model for the available PaaS offerings;
  • - To design, specify and develop the mechanisms of the Offerings Monitoring and Accounting layer of the PaaSport Reference Architecture which will implement, enforce and monitor the service level agreement policy and accounting models of the PaaS offerings published on the PaaSport marketplace infrastructure.

Workpackage 4 - From M7 to M24

PaaSport Persistence and Execution Layer

  • - To define a common Cloud platforms interface model and a standardised API that will allow the cross-platform deployment of business applications transparent to the user, re-using the work of CAMP and Cloud4SOA;
  • - To specify and implement a tunnelling and execution mechanism for the deployment and migration of applications on the available PaaS offerings of the PaaSport Marketplace Infrastructure; and
  • - To design and develop a data repository infrastructure accompanied with the respective search and discovery interfaces, allowing the creation, storage and management of three types of data entities: a) PaaS Offerings Profiles, b) Deployed Applications Profiles, and c) User Profiles.

Workpackage 5 - From M13 to M27

PaaSport Platform Integration and Testing

  • - To (pro-) actively handle software components integration issues through the design of a detailed, overall technical architecture, and the software integration and testing planning;
  • - To integrate the different software components that will be developed in the technical work-packages WP2, WP3 and WP4 into a flexible, service-based software framework that will support the implementation and operation of an interoperable Cloud platforms marketplace;
  • - To technically evaluate the integrated system according to predefined testing criteria, ensuring the quality of the produced software system; and
  • - To provide significant, valuable feedback from the first software layers implementation, platform integration and testing cycle to the second development cycle of work-packages WP2-WP4.

Workpackage 6 - From M19 to M36

Business Demonstrators and Overall Performance Evaluation

  • - To define and organize the four PaaSport demonstration scenarios that focuses in the applicability and usability of the PaaSport project results in pragmatic conditions;
  • - To deploy, operate and support the PaaSport marketplace demonstration infrastructure that is going to be utilized for the organization, realization and execution of the four PaaSport demonstration scenarios;
  • - To execute the predefined, organized PaaSport demonstration scenarios on top of the deployed marketplace demonstration infrastructure;
  • - To test and monitor the performance of the PaaSport demonstrator in the given demonstration scenarios;
  • - To define and validate the evaluation strategy of the performance of the PaaSport demonstration infrastructure;
  • - To identify and collect feedback from end-users and system engineers while experiencing the PaaSport marketplace infrastructure in realistic scenarios, and assess the performance of the deployed demonstrator through the analysis of the testing results; and
  • - To generate the lessons learnt (from the development, deployment and execution of the demonstration scenarios) and formulate them as a step-by-step cookbook and methodological adoption guidelines for interoperable Cloud Platforms marketplaces.

Workpackage 7 - From M1 to M36

IPR Handling, Dissemination and Training

  • - To handle the innovative results produced within the project and the relative IPRs, taking into account the collective interest of the participating Software SMEs Associations and the individual contribution of each partner to the project resources;
  • - To ensure proper know-how exchange among the PaaSport consortium and other related European initiatives, through a set of clustering activities;
  • - To present the project progress, technologies and results outside the scope of the PaaSport consortium and project reviewers, ensuring large awareness of the academic community as well as to the software and Cloud industry through scientific and business publications (in journals and magazines) and participation to relative events (conferences, workshops, symposiums, exhibitions);
  • - To analyze the market for the PaaSport solution, and define a viable exploitation model and business plan and taking into account the Software SMEs and SME Cloud Vendors needs and priorities at pan-European level;
  • - To provide internal training during the early stages of project among the consortium partners (from the RTD performers towards the SMEs and the SMEs Associations staff) & towards the end of the project to the PaaSport engineers (from the RTD performers and the SMEs Associations) towards the staff of the associations members;
  • - To establish, operate and maintain the PaaSport Industrial Focus Group (IFG), open to Software SMEs and SME Cloud vendors across the enlarged Europe;
  • - To organize and deliver a set of promotional, dissemination events and workshops; and
  • - To develop and maintain the official project’s website throughout the project lifecycle.

Workpackage 8 - From M1 to M36

Consortium and Project Management

  • - To ensure efficient communication within the PaaSport Consortium and reassure effective liaison with the REA, other projects and other bodies as required;
  • - To ensure strategic and everyday management of the project, with three main levels of responsibility from the top to the bottom: project manager, work-package leaders, task leaders; and
  • - To ensure efficient scientific and technical coordination among the project’s participants;
  • - To identify, assess and manage the technological development and project administration related risks; and
  • - To ensure the quality of the final results and deliverables (reports and prototypes).