https://www.scipedia.com/wd/index.php?action=history&feed=atom&title=Guegan_et_al_2018a 2026-05-06T09:31:37Z Revision history for this page on the wiki MediaWiki 1.27.0-wmf.10 https://www.scipedia.com/wd/index.php?title=Guegan_et_al_2018a&diff=205998&oldid=prev 2021-02-03T17:00:46Z

<p>Scipediacontent moved page <a href="/public/Draft_Content_486470241" class="mw-redirect" title="Draft Content 486470241">Draft Content 486470241</a> to <a href="/public/Guegan_et_al_2018a" title="Guegan et al 2018a">Guegan et al 2018a</a></p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr style='vertical-align: top;' lang='en'> <td colspan='1' style="background-color: white; color:black; text-align: center;">← Older revision</td> <td colspan='1' style="background-color: white; color:black; text-align: center;">Revision as of 17:00, 3 February 2021</td> </tr><tr><td colspan='2' style='text-align: center;' lang='en'><div class="mw-diff-empty">(No difference)</div> </td></tr></table>

Scipediacontent https://www.scipedia.com/wd/index.php?title=Guegan_et_al_2018a&diff=205997&oldid=prev 2021-02-03T17:00:43Z

<p>Created page with &quot; == Abstract == International audience; Automation, embedded software, stringent regulation and customer expectations have increased the complexity of ship design and require...&quot;</p> <p><b>New page</b></p><div><br /> == Abstract ==<br /> <br /> International audience; 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 &quot; communities of interest &quot; 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 – reflected in the compliance matrix model-is preserved within each &quot; community &quot; they belong to. Collaborative ship design where partners provide diverse contributions to the design of a single vessel could benefit from such an approach.<br /> <br /> Document type: Conference object<br /> <br /> == Full document ==<br /> &lt;pdf&gt;Media:Draft_Content_486470241-beopen5782-9632-document.pdf&lt;/pdf&gt;<br /> <br /> <br /> == Original document ==<br /> <br /> The different versions of the original document can be found in:<br /> <br /> * [https://zenodo.org/record/1445891 https://zenodo.org/record/1445891] under the license http://creativecommons.org/licenses/by-nc-nd/4.0/legalcode<br /> <br /> * [https://hal.archives-ouvertes.fr/hal-01813601 https://hal.archives-ouvertes.fr/hal-01813601],<br /> : [https://hal.archives-ouvertes.fr/hal-01813601/document https://hal.archives-ouvertes.fr/hal-01813601/document],<br /> : [https://hal.archives-ouvertes.fr/hal-01813601/file/TRA2018.pdf https://hal.archives-ouvertes.fr/hal-01813601/file/TRA2018.pdf]<br /> <br /> * [https://zenodo.org/record/1445891 https://zenodo.org/record/1445891],<br /> : [http://dx.doi.org/10.5281/zenodo.1445890 http://dx.doi.org/10.5281/zenodo.1445890] under the license http://creativecommons.org/licenses/by-nc-nd/4.0/legalcode<br /> <br /> * [https://zenodo.org/record/1445891 https://zenodo.org/record/1445891],<br /> : [http://dx.doi.org/10.5281/zenodo.1445891 http://dx.doi.org/10.5281/zenodo.1445891] under the license http://creativecommons.org/licenses/by-nc-nd/4.0/legalcode<br /> <br /> <br /> <br /> DOIS: 10.5281/zenodo.1445890 10.5281/zenodo.1445891</div>

Scipediacontent