Main Page

From Green software

(Difference between revisions)
Jump to: navigation, search
Line 26: Line 26:
Indirect savings are done by influencing artifacts that on their own influence the energy consumption of an IT artifact. [[Best practices to indirect savings|Ways to save energy indirectly]] include raising awareness or adding regulating and information gathering tools to a system added with the sole purpose to help accomplish direct savings.
Indirect savings are done by influencing artifacts that on their own influence the energy consumption of an IT artifact. [[Best practices to indirect savings|Ways to save energy indirectly]] include raising awareness or adding regulating and information gathering tools to a system added with the sole purpose to help accomplish direct savings.
 +
 +
== Green software metrics ==
 +
 +
Ways to measure greenness in design and implementation are non-existent. Measuring energy consumption during operation is possible, but always with some error-margin. For energy measurements of software different [[Green metrics | tools]] are available.
== Using a wiki ==
== Using a wiki ==

Revision as of 11:12, 15 September 2010

Welcome to the green software wiki

Green software refers to environmentally sustainable software. This wiki covers (all) different aspects of green software.

Contents

Green software

In [1] the definition for green software is introduced as "Computer software that can be developed and used efficiently and effectively with minimal or no impact to the environment". This definition has been derived from the definition of green IT as provided by Murugesan in Harnessing Green IT: Principles and Practices.

There are different reasons to create green IT, and is often stimulated (or enforced) by a sustainability strategy. In this strategy sometimes a special section on environmental strategies or green strategy is included.

The development of software is done in several different stages. <more>

Green design

<under construction>

Green implementation

For a product to be considered green, its production process has to keep its emission of greenhouses gases and consumption of non-renewable resources to a minimum.

Green operation

Different ways for IT to decrease its own operation carbon footprint is by direct and indirect savings.

In direct savings the goal is to reduce the carbon footprint an IT artifact causes. Systems that consume as little energy as possible during production and operation are said to be energy efficient. Direct savings can increase the energy efficiency of a software system. For ways to increase the energy efficiency of software, see the best practices for energy efficient software.

Indirect savings are done by influencing artifacts that on their own influence the energy consumption of an IT artifact. Ways to save energy indirectly include raising awareness or adding regulating and information gathering tools to a system added with the sole purpose to help accomplish direct savings.

Green software metrics

Ways to measure greenness in design and implementation are non-existent. Measuring energy consumption during operation is possible, but always with some error-margin. For energy measurements of software different tools are available.

Using a wiki

Consult the User's Guide for information on using the wiki software.

References

[1]. Gude, S. 2010. Energy efficient software

Personal tools