Overview of NESSI Projects Portfolio Stefano De Panfilis

download Overview of NESSI Projects Portfolio  Stefano De Panfilis

of 12

  • date post

    15-Jan-2016
  • Category

    Documents

  • view

    30
  • download

    0

Embed Size (px)

description

Overview of NESSI Projects Portfolio Stefano De Panfilis Engineering Ingegneria Informatica S.p.A. How it all started. NESSI Open Service Framework (NEXOF) Open Reference Model  Concept and Principles Open Reference Architecture  Standards Open Reference Implementation - PowerPoint PPT Presentation

Transcript of Overview of NESSI Projects Portfolio Stefano De Panfilis

  • Overview of NESSI Projects Portfolio

    Stefano De PanfilisEngineering Ingegneria Informatica S.p.A.

    NESSI Projects Summit

  • How it all started...Valencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • NEXOF main conceptsNESSI Open Service Framework (NEXOF)Open Reference Model Concept and PrinciplesOpen Reference Architecture StandardsOpen Reference ImplementationConformance Test SuiteValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • NEXOF layered Functional ViewValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • The role of NSPs and NCPsNESSI Strategic Projects (NSP) have the primary commitment to work in tight collaboration to build common artefacts which are in direct support of the NESSI Mission and Vision:Direct contributions to NEXOF in all its forms (Reference Architecture, Reference Implementation, Tests Suite, and Deployment/Test Beds)Cover extensively a research area, crosscutting several areasNSPs must allocate significant resources to the execution of these common actionsNSPs implement specific actions to animate the NESSI community, focusing on the themes tackled by the projectThe status of NSP is granted after a validation by the NESSI Steering Committee, which includes an analysis of research topics and commitments. NSPs receive a specific endorsement from the NESSI Board, which reflects the industrial commitment in support of these initiativesNSP are the pillars contributing to the overall coherence, consistence and integration of NEXOFValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • The role of NSPs and NCPsNESSI Compliant Projects are projects arising from the NESSI Community which focus on themes and approaches aligned with the priorities of NESSI, as defined in the Mission, the Vision, and the SRANCPs do not have the strong provisions for direct collaboration which are the characteristics of NSPs, but nonetheless commit to contribute to NESSI in general and in particular to NEXOF, for example through crosscommunity mechanisms like Investigation TeamsThe status of NCP is granted through selfassessment followed by a formal applicationNCP embody the opportunity to link research interests with NESII and NEXOFNSPs and NCPs are granted the right to use the Contributing to NESSI logoValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • Contributing to NEXOFValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • NESSI Strategic Projects Functional CoverageValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • NEXOF-RANESSI Open Service Framework

    Open Reference Model Concept and PrinciplesOpen Reference Architecture StandardsOpen Reference ImplementationConformance Test SuiteValidation of NEXOF instances in real scenarios *

    NESSI Projects Summit

  • JJWorking together JRRRRRIIIIIDCSValencia, 12 and 13 April 2010NESSI Projects Summit

    NESSI Projects Summit

  • We thank our Sponsors

    NESSI Projects Summit

  • NESSI Projects Summit

    ****The purpose of this slide is to list the main results which will be left by the project as starting points for others, either to build upon or simply use. When writing it, think about the LEGACY FOR THE FUTURE left by your project. Focus ONLY on the main contributions, what you want to be remembered for. DO NOT REDUCE FONT SIZE unless you absolutely must. Describe higher level abstractions if too many things to capture at the detailed level.***