[ecoop-info] CFP: IEEE Software Special Issue on Green Software

[Ayse Bener]

*IEEE Software** Call for Articles: Green Software*

* *

*Submission deadline: 25 June 2013*

*Publication: January/February 2014*

* *

Information technologies (IT) requiring vast amount of energy and other
resources are used in almost every field and process. Green IT is the study
and practice of using computing resources efficiently to reduce negative
impacts on the environment. Green IT is applicable to various high-tech
domains, such as data centers, mobile computing, and embedded systems.
Recently, global carbon dioxide emissions reached 9.1 billion tons, the
highest level in human history—49% higher than in 1990 (the Kyoto reference
year). At least 2% of global carbon dioxide emissions can be attributed to
IT systems; and further increases are expected with new IT systems being
deployed daily. Therefore, reducing the energy consumption and related
carbon dioxide emission of IT systems is a crucial requirement. Reducing
energy consumption also leads to reduced maintenance expenses and costs of
ownership, giving manufacturers a competitive advantage.



Change is therefore inevitable. Companies must implement energy-efficient
and technology services around the globe. This, along with regulations and
standards for measuring energy efficiency, will continue to drive the
development of energy-efficient pathways. In this context, green IT is an
ideal way for companies to achieve environmental sustainability and reduce
the cost of system and product maintenance. Most studies and regulatory
controls focus on hardware related measurement, analysis, and control for
energy consumption. However, all forms of hardware include significant
software components.



Although software systems do not consume energy directly, they affect
hardware utilization, leading to indirect energy consumption. Therefore, it
is important to engineer software with optimized energy consumption in
mind.



As software continues to affect all aspects of our lives in ever-changing
forms, leveraging existing systems is a challenging task for many
companies. Keeping software available on demand with a high quality of
service (in respect to end-users’ requirements) creates a conflict in terms
of software energy consumption. Moreover, each integrated quality feature
is accompanied by increasing levels of energy consumption. Therefore, it is
challenging to maintain environmentally friendly software.



On the other hand, software systems can play a proactive role in saving
energy by providing feedback about the way they consume resources. Such
proactive feedback can lead to changes in people’s behavior and help make
processes greener. Building green software systems has implications for
environmental awareness, behavioral changes, and can contribute to the
building of smart communities and cities.

* *

Possible topics include but are not limited to:

·         Green software: definition, reality and vision.

·         Green software in different computing contexts (data centers,
mobile devices, sensor networks, and embedded systems).

·         Software engineering of green software: requirements engineering,
architecting and designing.

·         Trade-offs during analysis and prioritization of green IT-related
requirements (for example, those related to energy consumption) versus
others.

·         Quality assurance of green software (for example, quality models
for greenness and metrics to measure them).

·         Making the world greener via software.

·         “Greening” legacy systems.

·         Energy as a hidden cost of computing.

·         Business models associated with green computing (for example,
aggregation of workloads in cloud environments).

·         Cost/benefit analyses of green software efforts.

·         Tools enabling green software engineering.

·         Case studies and industry experience reports.

·         Incentives to invest in greener software.

·         Energy-aware programming languages.



*Questions?*

For more information about the focus, contact the Guest Editors:

●      Ayse Basar Bener, professor, Ryerson University:
ayse.bener at ryerson.ca

●      Maurizio Morisio, professor, Politecnico di Torino:
maurizio.morisio at polito.it

●      Andriy Miranskyy, software engineer, IBM Toronto Software Lab:
andriy at ca.ibm.com



*Submission Guidelines*

Manuscripts must not exceed 4,700 words including figures and tables, which
count for 200 words each. Submissions in excess of these limits may be
rejected without refereeing. The articles we deem 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 or special issue
you are submitting for.



Articles should have a practical orientation and be written in a style
accessible to practitioners. Overly complex, purely research-oriented or
theoretical treatments are not appropriate. Articles should be novel. *IEEE
Software* does not republish material published previously in other venues,
including other periodicals and formal conference/workshop proceedings,
whether previous publication was in print or in electronic form.

For general author guidelines: www.computer.org/software/author.htm

For submission details: software at computer.org

To submit an article: https://mc.manuscriptcentral.com/sw-cs




-- 
Ayse Bener, PhD
Professor
Department of Mechanical and Industrial Engineering
Ryerson University
350 Victoria Street, Toronto, ON Canada M5B 2K3
Tel: 1 416 979 5000, X- 3155
Web: http://www.ryerson.ca/~abener/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://web.satd.uma.es/pipermail/ecoop-info/attachments/20130313/8350d7f5/attachment.html