Main Page

From Green software

(Difference between revisions)
Jump to: navigation, search
Current revision (11:50, 5 December 2015) (edit) (undo)
 
(14 intermediate revisions not shown.)
Line 1: Line 1:
<big>'''Welcome to the green software wiki'''</big>
<big>'''Welcome to the green software wiki'''</big>
-
Green software refers to environmentally sustainable software. This wiki covers all different aspects of green software.
+
Green software commonly refers to environmentally sustainable software. This wiki is a guide for practitioners and researchers on different aspects of green software.
== Green software ==
== Green software ==
-
In ''Harnessing Green IT: Principles and Practices'' a [[definition of green IT]] as provided by Murugesan is ''the study and practice of designing, manufacturing, using and disposing of computers, servers, and associated subsystems—such as monitors, printers, storage devices, and networking and communications systems—efficiently and effectively with minimal or no impact on the environment''.
+
In [[Energy efficient software (Master Thesis)|''Energy efficient software'']] the [[green software (definition) | 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 [[green IT (definition) | definition of green IT]] as provided by Murugesan in ''Harnessing Green IT: Principles and Practices''.
-
In ''<reference naar eigen paper>'' the definition for green software is introduced as being ''Computer software that can be developed and used efficiently and effectively with minimal or no impact to the environment''
+
-
There are different [[reasons for green IT|reasons to create green IT]], but is often part of a sustainability strategy. In this strategy can be a special section on environmental strategies or [[green strategy]].
+
There are different [[reasons for green IT|reasons to achieve greener IT]], and a [[green strategy|sustainability strategy]] is necessary.
-
<explain different stages of software development>
+
Green Software must encompass multiple phases of the software lifecycle: hereby we describe how to address Design, Implementation and Usage.
=== Green design ===
=== Green design ===
-
<include Patricia's definition of intent during design>
+
Energy efficiency is a quality concern of software systems, and as such it must be addressed already at the early stages (design and architecture). In [[Energy efficient software (Master Thesis)|''Energy efficient software'']] we present a number of architectural tactics to address energy efficiency.
 +
<under construction>
=== Green implementation ===
=== 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.
+
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. Software makes no exception.
 +
<under construction>
=== Green operation ===
=== Green operation ===
Line 24: Line 25:
Different ways for IT to decrease its own operation carbon footprint is by direct and indirect savings.
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]].
+
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.
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.
-
== Using a wiki ==
+
== Green software metrics ==
-
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.
+
-
* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
+
Ways to measure greenness in design and implementation are non-existent. [[Measuring green operation | Measuring energy consumption during operation]] is possible using different tools, but always with some error-margin.
-
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
+
 
-
* [http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
+
== Green software practices ==
 +
Software energy efficiency can be increased by following [[best practices for energy efficient software]]. We extracted our list of practices from both industry and academic literature. We are currently empirically evaluating our practices, but we are already able to estimate the impact of some of them.

Current revision

Welcome to the green software wiki

Green software commonly refers to environmentally sustainable software. This wiki is a guide for practitioners and researchers on different aspects of green software.

Contents

Green software

In Energy efficient software 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 achieve greener IT, and a sustainability strategy is necessary.

Green Software must encompass multiple phases of the software lifecycle: hereby we describe how to address Design, Implementation and Usage.

Green design

Energy efficiency is a quality concern of software systems, and as such it must be addressed already at the early stages (design and architecture). In Energy efficient software we present a number of architectural tactics to address energy efficiency. <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. Software makes no exception. <under construction>

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.

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 using different tools, but always with some error-margin.

Green software practices

Software energy efficiency can be increased by following best practices for energy efficient software. We extracted our list of practices from both industry and academic literature. We are currently empirically evaluating our practices, but we are already able to estimate the impact of some of them.

Personal tools