There is a newer version of this record available.

Project deliverable Open Access

D3.3 – Annual Report from TheFSM Software Components Integration and Testing

Danai Vergeti; Dimitris Ntalaperas; Iosif Angelidis


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">food safety</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">big data</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">standards</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">certification</subfield>
  </datafield>
  <controlfield tag="005">20220223073354.0</controlfield>
  <controlfield tag="001">6106865</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">UBITECH</subfield>
    <subfield code="a">Dimitris Ntalaperas</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">UBITECH</subfield>
    <subfield code="a">Iosif Angelidis</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2292465</subfield>
    <subfield code="z">md5:dbe3ac81ecb41cd5a32bf52661a46652</subfield>
    <subfield code="u">https://zenodo.org/record/6106865/files/D3.3 Annual Report from TheFSM software components Integration and Testing_V2.0_M24.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022-01-31</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-thefsm</subfield>
    <subfield code="o">oai:zenodo.org:6106865</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">UBITECH</subfield>
    <subfield code="a">Danai Vergeti</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">D3.3 – Annual Report from TheFSM Software Components Integration and Testing</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-thefsm</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">871703</subfield>
    <subfield code="a">The Food Safety Market: an SME-powered industrial data platform to boost the competitiveness of European food certification</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;In the current document we present the integration strategy of TheFSM Platform which includes the development, testing and deployment strategy for TheFSM technical solution. We focus on the methodology on both component and platform level. Unit testing is utilized to automate testing as much as possible, while we carefully follow well-established industry standards and methodologies in our approach. We provide examples of unit tests which test the internal functionality of components and their compliance with the specifications. Additionally, integration tests are provisioned in order to assure the interoperability between components. As more use cases are covered by the platform, these tests will evolve, adapt and carefully cover the newly added functionality. Moreover, we describe issue tracking and the dockerization process we follow during development.&lt;/p&gt;

&lt;p&gt;The current document provides a) the approach we follow in development regarding both the overall project and within component level, b) the technical verification of our pipeline. We define how verification is guaranteed via unit and integration testing, thoroughly describing the unit testing process and c) the technical evaluation, where we define metrics and KPIs relevant to the project and we provide analytical tables which include our performance against the relevant metrics&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.6106853</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.6106865</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">deliverable</subfield>
  </datafield>
</record>
48
21
views
downloads
All versions This version
Views 4824
Downloads 2111
Data volume 41.1 MB25.2 MB
Unique views 2817
Unique downloads 169

Share

Cite as