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

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="DOI">10.5281/zenodo.1445891</identifier>
      <creatorName>Alan Guegan</creatorName>
      <creatorName>Romain Le Néna</creatorName>
      <creatorName>Benoît Rafine</creatorName>
      <creatorName>Laurent Descombes</creatorName>
      <creatorName>Hanane Fadiaw</creatorName>
      <creatorName>Pierre Marty</creatorName>
      <creatorName>Philippe Corrignan</creatorName>
    <title>Compliance matrix model based on ship owners' operational needs</title>
    <subject>compliance matrix; requirements management; operational scenario; system architecture; micro-services</subject>
    <date dateType="Issued">2018-04-16</date>
  <resourceType resourceTypeGeneral="Text">Conference paper</resourceType>
    <alternateIdentifier alternateIdentifierType="url"></alternateIdentifier>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsVersionOf">10.5281/zenodo.1445890</relatedIdentifier>
    <relatedIdentifier relatedIdentifierType="URL" relationType="IsPartOf"></relatedIdentifier>
    <rights rightsURI="">Creative Commons Attribution Non Commercial No Derivatives 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&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;</description>
All versions This version
Views 203203
Downloads 200200
Data volume 135.4 MB135.4 MB
Unique views 195195
Unique downloads 180180


Cite as