June 1, 2022 Conference paper Open Access

Bussemaker, J.H.; Boggero, L.

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">System Architectures, optimization, surrogate modeling</subfield>
  </datafield>
  <controlfield tag="005">20220607135040.0</controlfield>
  <controlfield tag="001">6619019</controlfield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">1-3 June 2022</subfield>
    <subfield code="g">ODAS</subfield>
    <subfield code="a">ONERA-DLR Aerospace Symposium</subfield>
    <subfield code="c">Hamburg, Germany</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">German Aerospace Center (DLR), Institute of System Architectures in Aeronautics, Hamburg, Germany</subfield>
    <subfield code="a">Boggero, L.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1069822</subfield>
    <subfield code="z">md5:d3121556dd862ad097e0cf292478b327</subfield>
    <subfield code="u">https://zenodo.org/record/6619019/files/ODAS_2022_Technologies_for_Enabling_System_Architecture_Optimization.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022-06-01</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-agile4</subfield>
    <subfield code="o">oai:zenodo.org:6619019</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">German Aerospace Center (DLR), Institute of System Architectures in Aeronautics, Hamburg, Germany</subfield>
    <subfield code="a">Bussemaker, J.H.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Technologies for Enabling System Architecture Optimization</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-agile4</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">815122</subfield>
    <subfield code="a">AGILE 4.0: Towards cyber-physical collaborative aircraft development</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;Optimization of complex system architectures can support the non-biased search for novel architectures in the early design phase. Four aspects needed to enable architecture optimization and the author&amp;rsquo;s views on how to solve them are discussed: formalization of the architecture design space, systematic exploration of the design space, conversion from architecture model to simulation model, and flexible simulation of architecture performance. Modeling the design space is done using the Architecture Design Space Graph (ADSG) implemented in ADORE. Systematic exploration can be done using evolutionary or surrogate-based optimization algorithms. Architecture to simulation model conversion can be done using an object-oriented approach using class factories, or using the MultiLinQ tool to synchronize a central data repository. Finally, simulation environments should expose a flexible and modular interface to be used in architecture optimization. A jet engine architecting problem is presented that demonstrates various aspects of system architecture optimization.&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.6619018</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.6619019</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
</record>