<div dir="ltr"><b><span id="gmail-m_-7760122779055478994gmail-m_5689034437624025804gmail-m_806736369643065987gmail-m_-6670370838578867643gmail-m_6959837570064564918inbox-inbox-docs-internal-guid-1ab5142d-a9c2-7237-025f-8bec46092a9f"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-weight:normal"><span style="font-size:10pt;font-family:Arial;color:rgb(34,34,34);font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><span class="gmail-m_-7760122779055478994gmail-m_5689034437624025804gmail-m_806736369643065987gmail-il">[Apologies</span> for <span class="gmail-m_-7760122779055478994gmail-m_5689034437624025804gmail-m_806736369643065987gmail-il">cross</span>-<span class="gmail-m_-7760122779055478994gmail-m_5689034437624025804gmail-m_806736369643065987gmail-il">posting</span>]</span></span></p></span></b><div dir="ltr"><div><b><span id="gmail-m_-7760122779055478994gmail-m_5689034437624025804gmail-m_806736369643065987gmail-m_-6670370838578867643gmail-m_6959837570064564918inbox-inbox-docs-internal-guid-1ab5142d-a9c2-7237-025f-8bec46092a9f"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-weight:normal"><span style="font-size:10pt;font-family:Arial;color:rgb(34,34,34);font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">-----------------------------------------------------------------------------------------</span></span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(34,34,34);font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><br></span></p></span></b></div><div><b>IEEE Software Theme Issue on <br></b></div><div><b>Sentiment and Emotion in Software Engineering: <b>Call for Papers</b></b></div><div><a href="https://publications.computer.org/software-magazine/2018/07/18/sentiment-emotion-software-engineering-call-papers/" target="_blank">https://publications.computer.org/software-magazine/2018/07/18/sentiment-emotion-software-engineering-call-papers/</a><b><br></b></div><div><b><br></b></div><div><b>Submission deadline: 1 Feb. 2019</b></div><b>Publication: Sept./Oct. 2019</b><br><br><div>Over
the past decade, research has shown the affective states’ impact on
work performance and team collaboration. This also applies to software
engineering, which involves people in a broad range of activities in
which personality, moods, and emotions play a crucial role. Software
development is a mainly intellectual activity requiring creativity and
problem-solving skills, which are known to be influenced by affective
states.</div>For successful software engineering projects, stakeholders
need to experience positive emotions, agree on emotion display rules,
and be mutually committed to the project goals. Conversely, negative
affective states (such as resentment or frustration) might be an
obstacle when stakeholders react to undesirable facts (for example,
negative customer feedback). Such states can also impact the cognitive
processes involved in learning a new language, solving tasks with high
reasoning complexity, and performing the usual programming and code
comprehension tasks.</div><div dir="ltr">Finally, software engineering
involves numerous social interactions, as programmers often need to
cooperate with others, whether directly or indirectly. Developers’
awareness of the project mood and of how their communication style
reflects their affective state might help them become wise in teamwork,
thus improving the outcome of collaborative development.<br>So,
researchers have recently started studying the role of affective
computing and affective states in software engineering. This theme issue
of IEEE Software aims to share with practitioners the current trends
and recent advances in research and practice and the latest tools and
frameworks for supporting and enhancing emotion awareness in software
development.<br><br><div>We invite <b><i>practice-oriented papers</i></b>
covering any aspect of sentiment and emotion awareness in software
engineering. We aim to cover a rich variety of topics, focusing on
issues, challenges, methods, and practices related to the role of
emotions in software development. Topics of interest include, but are
not limited to,</div><ul><li>the impact of affective states (emotions, moods, attitudes, and personality traits) on individual and group performance;</li><li>the role of emotions in collaborative software development;</li><li>leveraging stakeholders’ affective feedback to improve software, tools, and processes;</li><li>design, development, and evaluation of tools and datasets for supporting emotion awareness in software engineering;</li><li>reusable software frameworks, APIs, and patterns for affect-aware systems;</li><li>ethnographic approaches to affect monitoring in software development;</li><li>mining sentiment and emotion from developers’ communication traces;</li><li>sentiment and emotion detection from biometrics;</li><li>methodologies and tools for large-scale emotion mining;</li><li>emotion awareness in requirements engineering, software design, and software management;</li><li>emotion awareness in software design philosophies, development practices, and tools;</li><li>emotion awareness in cross-cultural teams in global software development; and</li><li>methodologies and standards.</li></ul><div>In
addition to regular-length articles, we seek short experience reports.
These reports don’t need to make a research contribution. Instead, they
should present the experiences of practitioners or tool developers,
sharing their practical experience and insights and focusing on the
challenges faced, solutions attempted, and results obtained.<br><br><i>Questions?</i><br><div>For more information about the theme issue, contact the guest editors:</div><div>- Nicole Novielli, Università degli Studi di Bari Aldo Moro, <a href="mailto:nicole.novielli@uniba.it" target="_blank">nicole.novielli@uniba.it</a></div><div>- Per Lenberg, Saab, <a href="mailto:per.lenberg@saabgroup.com" target="_blank">per.lenberg@saabgroup.com</a></div><div>- Alexander Serebrenik, Eindhoven University of Technology, <a href="mailto:a.serebrenik@tue.nl" target="_blank">a.serebrenik@tue.nl</a></div><br><i>Submission Guidelines</i><br>Manuscripts
must not exceed 3,000 words including figures and tables, which count
for 250 words each. Submissions exceeding these limits might be rejected
without refereeing. Articles deemed within the theme and scope will be
peer-reviewed and are subject to editing for magazine style, clarity,
organization, and space. We reserve the right to edit the title of all
submissions. Be sure to include the name of the theme for which you’re
submitting.<br>Articles should have a practical orientation and be
written in a style accessible to practitioners. Overly complex, purely
research-oriented or theoretical treatments aren’t appropriate. Articles
should be novel. IEEE Software doesn’t republish material published
previously in other venues, including other periodicals and formal
conference or workshop proceedings, whether previous publication was in
print or electronic form.<br><br>For general author guidelines:<a href="http://www.computer.org/software/author.htm" target="_blank"> http://www.computer.org/software/author.htm</a> <br>For submission details: <a href="mailto:software@computer.org" target="_blank">software@computer.org</a><br>To submit an article: <a href="https://mc.manuscriptcentral.com/sw-cs" target="_blank">https://mc.manuscriptcentral.com/sw-cs</a></div></div></div>