Common Quality Criteria and Metrics relate to quality criteria and metrics well known from the standard quality models for software e.g. ISO 25000 (SQuaRE). These are then interpret-ed on the background of their contribution to sustainable development.
Reusability, which is the ability of software components to be reused in other software systems, reduces efforts to develop other software systems and thus reduces environmental impacts of the development phase .
Modifiability, the ability to implement changes of software quickly, reduces environmental impacts that result from developing and main-taining a software system .
Usability and Accessibility of software contrib-ute to social aspects, as they make software easier to learn, more accessible to users with disabilities, or more accessible to people with-out access to computers with sufficient per-formance or screen sizes .
Predictability, which refers to the development process itself, is the ability of the developers to accurately estimate person-days for required features. This contributes to social aspects, as it improves the developers’ conditions of work by reducing the probability of overtime work .
Directly Related Quality Criteria and Metrics relate to quality properties known from standard quality models, but also introduce new aspects and a new quality property.
The property Efficiency considers aspects like runtime efficiency and usage of computer resources. Appropriate metrics to measure efficiency are CPU-intensity, memory usage, peripheral intensity and idleness. Runtime efficiency directly relates to the property Performance, as runtime efficient programs minimize energy consumption through less computer usage . Hence, it is possible to define energy efficiency metrics for software , which relate the work done to the energy consumption of the IT system or components of it. By comparing the measured system with a reference system, it is possible to determine which system is more energy efficient .
An aspect newly introduced into the property Portability is hardware obsolescence. It considers the amount of hardware that must be replaced before it has reached the end of its useful lifetime in order to use the new soft-ware [1,3].
The property Feasibility  considers how the software engineering process follows and manages sustainability issues during its execution. Main aspects are carbon footprint , travel, energy, and waste , according to our life cycle of software products.
Indirectly Related Criteria and Metrics subsume quality properties and their supporting metrics that regard how software indirectly affects its usage domain and how software supports sustainable development in its application domain. The first is addressed by the property Reflectivity whereas the latter is addressed by the property Sustainability.
Currently, the property Reflectivity  re-quires more research to get easy-to-use and reliable metrics.
The property Sustainability  is supported by the aspects fit for purpose, reduction, and beauty. Fit for purpose describes how software helps its application domain to reach its objectives. Reduction considers how the software supports its application domain in waste reduction. Beauty assesses the contribution of the software to sustainable development. To measure the property Sustainability, it is necessary to define a reference software system and to calculate metrics that can then be compared with the same metrics of the system currently under development.
At first, it covers common metrics and criteria for the measurement of software quality and relates these to their effects on sustainable development. Secondary, it covers directly related criteria and metrics, which regard first-order effects of ICTs on sustainable development, as well as indirectly related criteria and metrics, which regard the more advanced second- and third-order effects. The identified properties and metrics form a quality model for green and sustainable software.