<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div id="divRpF432911" style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 16px; direction: ltr;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 16px;">
</div>
<div>
<div style="direction: ltr;">
<div>
<div>
<div style="direction: ltr;">
<div>
<div>
<div style="direction: ltr;">
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>Call for Papers</b></span></font><font face="Times New Roman,serif" size="3"><span lang="en-US"><b> </b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b> </b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>Minitrack for</b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b> </b></span></font></div>
<div align="center" style="text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<font face="Times New Roman, serif" size="3"><b>Software Product Lines: Engineering, Services, and Management</b></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>at</b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>48th Annual Hawaii International Conference on System Sciences</b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>January 5-8, 2015 (Monday through Thursday)</b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>Grand Hyatt, Kauai, U.S.A.</b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<a href="http://www.hicss.hawaii.edu/" target="_blank"><font size="3"><font face="Times New Roman,serif"><span lang="en-US"><b>http://www.hicss.hawaii.edu</b></span></font></font></a></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>by</b></span></font></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>Timo Käkölä </b></span></font><span style="font-family: 'Times New Roman', serif; font-size: 12pt;"><b>Andrea Leitner</b></span></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"><b>University of Jyväskylä, Finland </b></span></font><span style="font-family: 'Times New Roman', serif; font-size: 12pt;"><b>Graz University of Technology, Austria</b></span></div>
<div align="center" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-align: center; margin-top: 14pt; margin-bottom: 14pt;">
<span style="font-family:'Times New Roman',serif; font-size:medium; text-align:justify"> timokk@jyu.fi andrea.leitner@tugraz.at</span></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; margin-top: 14pt; margin-bottom: 14pt;">
<font face="Times New Roman,serif" size="3"><span lang="en-US"> </span></font></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; margin-top: 14pt; margin-bottom: 14pt;">
<p class="MsoNormal" style="margin-bottom: 0.0001pt;"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:
Batang;mso-fareast-language:KO">Software has become the key asset for competitive products and services
in all industries. Thus, competitiveness in software development, maintenance, and related services has become a concern for organizations. Competitiveness can be increased through (1) internal strategies such as the strategic creation and reuse of software
assets and (2) external strategies such as outsourcing software development, maintenance, and/or services from third party service providers and acquiring off-the-shelf components from providers and open source communities. A viable third strategy is to develop
both strategies in parallel. This minitrack focuses on the first and third strategy.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt;"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:
Batang;mso-fareast-language:KO"><br>
</span></p>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;text-indent:
17.85pt;mso-pagination:none;mso-layout-grid-align:none;text-autospace:none">
<span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman","serif";
mso-fareast-font-family:Batang;mso-fareast-language:KO">Software product line engineering (SPL) is an industrially-validated methodology for developing software-intensive
systems and services faster, at lower costs, and with better quality and higher end-user satisfaction. It differs from single system development, as:
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 17.85pt; text-indent: -17.85pt;">
<!--[if !supportLists]--><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman","serif";
mso-fareast-font-family:"Times New Roman";mso-fareast-language:KO">1.<span style="font-size: 7pt; font-family: 'Times New Roman';">
</span></span><!--[endif]--><span lang="EN-GB" style="font-size:12.0pt;
font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-fareast-language:KO">It needs two development processes to work optimally: domain engineering and application
engineering. Domain engineering defines and realizes the common and variable features of the product line by establishing a common software platform. Application engineering derives applications by exploiting the commonality and binding variability
built into the platform.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 17.85pt; text-indent: -17.85pt;">
<!--[if !supportLists]--><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman","serif";
mso-fareast-font-family:"Times New Roman";mso-fareast-language:KO">2.<span style="font-size: 7pt; font-family: 'Times New Roman';">
</span></span><!--[endif]--><span lang="EN-GB" style="font-size:12.0pt;
font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-fareast-language:KO">It needs to explicitly define and manage variability. During domain engineering, variability
is introduced in all assets such as requirements, architectural models, components, and test cases. It is used during application engineering to mass-customize applications to the needs of customers.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-size: 12pt; font-family: 'Times New Roman', serif;"><br>
</span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-size: 12pt; font-family: 'Times New Roman', serif;">The software product line engineering body of knowledge has mainly been created to enable industrialized software
production. </span><span style="font-family: 'Times New Roman', serif; font-size: 12pt; text-indent: 18pt;">However, the extant software product line body of knowledge has not yet been integrated well enough with other relevant bodies. For example, substantial
and long-term product portfolio planning, organizational learning, and investments are typically needed in corporations to fully adopt and leverage the product line strategy by establishing the common set of product line assets, building products from it,
and having supportive processes and organizational structures in place. The product line strategy also tends to involve geographically distributed work in multiple sites and projects by a network of internal organizational units, external service providers,
and open source communities. The work is knowledge-intensive and the assets to be created and reused involve types of knowledge such as business process models which are far more versatile than the software components that have been the focus of earlier reuse
efforts. The network needs to be carefully orchestrated and the relevant knowledge needs to be identified, stored, and shared amongst the appropriate stakeholders. When open source communities take substantial responsibility for platform development, the
leadership of the network becomes increasingly distributed and emergent. The control of any one stakeholder over the network and the produced assets will thus diminish, making product line planning and management ever more challenging. Finally, the products
need to be serviced throughout their life-cycles and comprehensive service systems need to be built to increase customer satisfaction, generate new revenue streams, and to ensure that the feedback from the customers is effectively leveraged in improving the
product lines.</span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-family: 'Times New Roman', serif; font-size: 12pt; text-indent: 18pt;"><br>
</span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:
Batang;mso-ansi-language:EN-US;mso-fareast-language:KO">The business, leadership, economic,
organizational, process, service, and knowledge management related issues have not been systematically and comprehensively investigated from the viewpoint of software product lines. For example, product lines are seldom viewed in the literature as services
to customers that require the design of dedicated service systems. Organizations may fail in leveraging the product line strategy partly because the extant body of knowledge provides them with limited and fragmented guidance for adopting and enacting the strategy.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:
Batang;mso-ansi-language:EN-US;mso-fareast-language:KO"><br>
</span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-size: 12pt; font-family: 'Times New Roman', serif;">This minitrack welcomes contributions to the mainstream product line body of knowledge.
</span><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">To help integrate new bodies of knowledge in product line research and practice, the minitrack also
welcomes contributions including but not limited to<o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Business models and s<span style="font-family: 'Times New Roman', serif;">ocio-technical
ecosystem </span>strategies for producing product lines</span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Economic valuation of product lines<o:p></o:p></span>
</li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Ecosystem, organizational, and process designs
for product lines<o:p></o:p></span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Distributed leadership in developing open
source platforms and product lines<o:p></o:p></span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Knowledge management practices and systems
for product lines<o:p></o:p></span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Service systems and their implications for
product lines<o:p></o:p></span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">International standardization initiatives
related to product lines<o:p></o:p></span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">Theory building and/or validation from the
viewpoints of design and behavioral science<o:p></o:p></span> </li></ul>
<p class="MsoNormal" style="margin-bottom: 0.0001pt; text-indent: 18pt;"><span style="font-size: 12pt; font-family: 'Times New Roman', serif;">The minitrack is also interested in industrial experiences in product line engineering if they can be used
<o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">to support academic and/or industrial courses
on software product line engineering and/or<o:p></o:p></span> </li><li class="MsoNormal" style="margin-bottom: 0.0001pt;"><span style="font-size:
12.0pt;font-family:"Times New Roman","serif";mso-fareast-font-family:Batang;
mso-ansi-language:EN-US;mso-fareast-language:KO">to validate or challenge existing theories
and/or create new theories relevant to the software product line engineering body of knowledge.<o:p></o:p></span>
</li></ul>
</div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3"><b>Deadlines for Authors</b></font></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-indent: -18pt; margin-top: 14pt; margin-bottom: 0px;">
<font face="Symbol" size="3"><span lang="en-US">·</span></font><font face="Times New Roman" size="3"><span lang="en-US"> Before </span></font><span style="font-family:'Times New Roman',serif; font-size:medium">June 15: A one page abstract as an indication
of interest is encouraged</span></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-indent: -18pt; margin-top: 14pt; margin-bottom: 0px;">
<font face="Times New Roman,serif" size="3" style="text-indent:-18pt"><span lang="en-US"><span class="Apple-tab-span" style="white-space:pre"></span><span class="Apple-tab-span" style="white-space:pre"></span> <span class="Apple-tab-span" style="white-space:pre">
</span> June 15: </span></font><font face="Times New Roman,serif" size="3" style="text-indent:-18pt"><span lang="en-US">Submit full manuscripts for review as instructed. The review is double-blind; therefore, this initial submission must be without author
names.</span></font></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-indent: -18pt; margin-top: 14pt; margin-bottom: 0px;">
<font face="Symbol" size="3"><span lang="en-US">·</span></font><font face="Times New Roman" size="3"><span lang="en-US"> </span></font><font face="Times New Roman,serif" size="3"><span lang="en-US">August 15: </span></font><font face="Times New Roman,serif" size="3"><span lang="en-US">Acceptance/Rejection
Notices to authors. It is very important that at least one author of each accepted paper register and attend the conference.</span></font></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-indent: -18pt; margin-top: 14pt; margin-bottom: 0px;">
<font face="Symbol" size="3"><span lang="en-US">·</span></font><font face="Times New Roman" size="3"><span lang="en-US"> </span></font><font face="Times New Roman,serif" size="3"><span lang="en-US">September 15: Submit final paper.</span></font></div>
<div align="justify" style="color: rgb(0, 0, 0); font-family: Tahoma; font-size: 10pt; text-indent: -18pt; margin-top: 14pt; margin-bottom: 0px;">
<font face="Symbol" size="3"><span lang="en-US">·</span></font><font face="Times New Roman" size="3"><span lang="en-US"> </span></font><font face="Times New Roman,serif" size="3"><span lang="en-US">October 1: </span></font><font face="Times New Roman,serif" size="3"><span lang="en-US">Early
Registration fee deadline. At least one author of each paper should register by this date to secure publication in the Proceedings.</span></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>