<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">CFP: <b>Software Infrastructure as A Crosscutting Concern: Vision for Future (SIaCC)<br></b><span class="Apple-tab-span" style="white-space: pre; "><b> </b></span><b>Workshop at AOSD 2013, March 25/26, Fukuoka, Japan</b><br><br><div>Website URL: <a href="http://lamp-lbi-34.rcs.le.ac.uk/workshop">http://lamp-lbi-34.rcs.le.ac.uk/workshop</a><br> <br><u><b>OVERVIEW:</b> </u><br>Functioning of modern society is deeply dependant on various types of infrastructure, such as water supply, transportation, energy and communication.<br>Each utility infrastructure (such as water or communication) is, in fact, a complex system made up of numerous sub-systems, most of which comprise a critical software element, such as, for control, operation, or security and safety provision.<br>Yet, software itself (along with the physical counterpart for its operation) is an infrastructure. This software infrastructure is already supporting an ever-growing set of services and, gradually, replacing what previously would have been delivered via other forms of infrastructure. For instance, the lion’s share of monetary transactions in developed countries is carried out via ICT infrastructure. Online shopping has become a norm, music, books, and films are becoming almost entirely software products themselves. This in turn has implications on the city planning (many retail shops are closing down!), transportation, and road infrastructure. Even healthcare and socialising are moving from physical into digital world.<br><br>This workshop aims to initiate a discussion on broad topics of software as a crosscutting infrastructure, envision the future with service provision centred around the software infrastructure, identify and discuss the current and future (both software engineering, and broader) issues that either facilitate or prevent this vision.<br><br><b><u>TOPICS</u></b> on software as an infrastructure, including, but not limited to:<br>+ Examples of software as a crosscutting infrastructure:<br><span class="Apple-tab-span" style="white-space: pre; "> </span>++ What are the peculiarities of software infrastructure vs. other forms (e.g., transportation, energy);<br><span class="Apple-tab-span" style="white-space: pre; "> </span>++How can software infrastructure be distinguished from those it crosscuts?<br>+ Problems/issues arising with software becoming a critical infrastructure that crosscuts other utility infrastructures:<br><span class="Apple-tab-span" style="white-space: pre; "> </span>++Will failure in software infrastructure be a “single point of failure”?<br><span class="Apple-tab-span" style="white-space: pre; "> </span>++Will this improve or deteriorate other infrastructure assets?<br></div><div>+ Understanding what requirements a software should fulfil to become a fully formed type of utility (e.g., on par with water and electricity):<br>+ Software Engineering design and implementation ramifications of software moving into a central infrastructure role:</div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>++Do we have adequate development techniques<br><span class="Apple-tab-span" style="white-space: pre; "> </span>++Do we have adequate failure detection/prevention support<br>+Social impact of the transition of software into infrastructure:<br><br>As the first workshop in this space, this even will set up an initial research agenda. Problems for this agenda will be elicited from the workshop submissions, group discussions, and imagination sessions.<br><br><b><u>SUBMISSIONS</u></b><br>We invite submissions of extended abstracts and short papers on the broad set of issues related to software as a crosscutting infrastructure. All submissions must be in standard ACM SIG Proceedings format (see <a href="http://www.acm.org/sigs/publications/proceedings-templates">http://www.acm.org/sigs/publications/proceedings-templates</a>).<br>Extended abstracts should not exceed 2 pages. Short papers should not exceed 4 pages.<br>Each submission will be reviewed by 2 members of the workshop PC.<br>Submissions should be sent to the workshop organisers via email (rc256_at_leicester_dot_ac_dot_uk).<br><br><b><u>PARTICIPATION</u></b><br>Paper/abstract submission is strongly encouraged for workshop participation. However, non-submitting participants will also be welcomed, if space is available.<br><br>All submissions will be posted on the workshop website to initiate discussion before the workshop itself.<br>The workshop itself will comprise of a number of highly interactive discussion and imagination sessions. The workshop will work on preparation of a research agenda on topics of Software as a Crosscutting Infrastructure.<br><br><b><u>IMPORTANT DATES:</u></b><br>+ Workshop Paper submission deadline: 17th January 2013,<br>+ Workshop Paper notification date: 28th January 2013,<br>+ Workshop Paper camera-ready deadline: 18th February 2013.<br><br><b><u>Program Committee:</u></b><br>Mehmet Aksit, University of Twente, The Netherlands<br>Christoph Bockisch, University of Twente, The Netherlands<br>Joby Boxall, University of Sheffield, UK<br>Ruzanna Chitchyan, University of Leicester, UK<br>Robert France, Colorado State University, USA (to be confirmed)<br>Tom Grant, University of Leicester, UK<br>Ana Moreira, New University of Lisboan, Portugal<br>Harold Ossher, BM Thomas J. Watson Research Center, USA<br>Liz Varga, Cranfield Univesity, UK<br><br><b><u>Website URL</u></b>: <a href="http://lamp-lbi-34.rcs.le.ac.uk/workshop">http://lamp-lbi-34.rcs.le.ac.uk/workshop</a><br><br><b><u>PROCEEDINGS:</u></b><br>The workshop proceedings will be included into the ACM digital<br><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-family: Helvetica; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "></span></div></div></div></div><div><br></div></body></html>