A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2013; you can also visit <a rel="external noopener" href="http://www.sosym.org/editorials/files/FR13a.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
<i title="Springer Nature">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/dfdth37zyfetvchsdjk5e2osrq" style="color: black;">Journal of Software and Systems Modeling</a>
In 2007 ICSE hosted a track called "Future of Software Development" (FOSD). We were invited to write and present a paper on the future of modeling for the track. The resulting paper  described the state of modeling research, identified some major challenges and proposed a research road map. Parts of this road map are currently being explored, and progress has been made in addressing some of the challenges we identified. However, there is still significant research "to be done" with respect<span class="external-identifiers"> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1007/s10270-013-0346-4">doi:10.1007/s10270-013-0346-4</a> <a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/v5hbes5jwzdhdbnbgvfh3e6ygi">fatcat:v5hbes5jwzdhdbnbgvfh3e6ygi</a> </span>
more »... the challenges outlined in that paper. It is not our intent to discuss the progress the community has made with respect to the road map in this editorial (our apologies for deflating expectations in this regard; an editorial is simply not the place for such discussions). Rather, we would like to use this editorial to stimulate discussions around some of the challenges that have arisen since we wrote that paper. Before we get into identifying specific challenges, let us first take a step back and ask "What is the grand challenge addressed by researchers in the SoSyM community?" The answer has typically been "To significantly reduce the time, cost, and effort required to develop complex softwareintensive systems that meet stringent quality requirements through use of models that are fit-for-purpose." This is still the focus of many research programs, but we are also seeing a broadening of the grand challenge to include not only development problems, but problems that occur throughout the lifetime of a complex system, from conception to retirement. For example, in the FOSD paper we made reference to emerging work on the use of models to manage software Rat runtime (now referred to as email@example.com). The grand challenge is thus evolving to encompass a wider range of problems that occur in the life cycle of complex systems, as it should. It is interesting to note that in other disciplines the use of models to manage work on artifacts throughout their life cycles is receiving significant attention. For example, in the construction domain building information modeling (BIM), techniques and standards are being developed to support the management to built environments from conception, to architectural design, to onsite construction, to building occupancy and finally to building demolition. In this case models are the primary means for managing work throughout a building's lifetime. Given this broader view of the role that models can play, we have identified the following research opportunities and challenges: • Systems that integrate mechanical, software and electrical engineering subsystems (e.g., cyber-physical systems (CPS)) will become commonplace, and thus, there is a need for work on how the modeling approaches used by experts in these diverse domains can be integrated. This is a very challenging problem, and thus, there is a need for significant intellectual investment in developing integrated modeling languages and associated tooling. With respect to CPS, there are two core issues that require our attention as researchers: -Mechanical, electrical and software engineering rely on entirely different theories (e.g., theories based on continuous mathematics versus those based on eventbased automata), and thus engineers in these domains use very different approaches. The challenge is to develop good bridges across these theories. 123
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20131109143235/http://www.sosym.org/editorials/files/FR13a.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext"> <button class="ui simple right pointing dropdown compact black labeled icon button serp-button"> <i class="icon ia-icon"></i> Web Archive [PDF] <div class="menu fulltext-thumbnail"> <img src="https://blobs.fatcat.wiki/thumbnail/pdf/55/bb/55bb2147b4a78bd00c0f411d63e37218d3c66312.180px.jpg" alt="fulltext thumbnail" loading="lazy"> </div> </button> </a> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1007/s10270-013-0346-4"> <button class="ui left aligned compact blue labeled icon button serp-button"> <i class="external alternate icon"></i> springer.com </button> </a>