Conference paper Open Access

Compliance matrix model based on ship owners' operational needs

Alan Guegan; Romain Le Néna; Benoît Rafine; Laurent Descombes; Hanane Fadiaw; Pierre Marty; Philippe Corrignan


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="653" ind1=" " ind2=" ">
    <subfield code="a">compliance matrix; requirements management; operational scenario; system architecture; micro-services</subfield>
  </datafield>
  <controlfield tag="005">20210111151202.0</controlfield>
  <controlfield tag="001">1445891</controlfield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">16-19 April 2018</subfield>
    <subfield code="g">TRA2018</subfield>
    <subfield code="a">7th Transport Research Arena TRA 2018 (TRA 2018)</subfield>
    <subfield code="c">Vienna</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Romain Le Néna</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Benoît Rafine</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Laurent Descombes</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Hanane Fadiaw</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Pierre Marty</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Philippe Corrignan</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">677171</subfield>
    <subfield code="z">md5:36175a65d210324563c7c2376c015fec</subfield>
    <subfield code="u">https://zenodo.org/record/1445891/files/Contribution_10363_fullpaper.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="y">Conference website</subfield>
    <subfield code="u">https://2018.traconference.eu/</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2018-04-16</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-tra2018</subfield>
    <subfield code="o">oai:zenodo.org:1445891</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Alan Guegan</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Compliance matrix model based on ship owners' operational needs</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-tra2018</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution Non Commercial No Derivatives 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;Automation, embedded software, stringent regulation and customer expectations have increased the complexity of ship design and requirements management. The requirements management approach described here brings two innovations with respect to existing tools used in the shipbuilding industry. First, requirements are assigned to operational scenarios rather than physical components to emphasize the focus on customer needs rather than subsystem optimization. Second, a tool based on a microservices architecture is introduced to manage scenario-centered &amp;ldquo;communities of interest&amp;rdquo; to which system architecture blocks and requirements subscribe depending on their involvement in the scenario. System architecture, operational scenarios, customer requirements are designed and managed in separate tools and the overall consistency of the design &amp;ndash; reflected in the compliance matrix model - is preserved within each &amp;ldquo;community&amp;rdquo; they belong to. Collaborative ship design where partners provide diverse contributions to the design of a single vessel could benefit from such an approach.&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.1445890</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.1445891</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
</record>
203
200
views
downloads
All versions This version
Views 203203
Downloads 200200
Data volume 135.4 MB135.4 MB
Unique views 195195
Unique downloads 180180

Share

Cite as