| Term | Description |
| Energy efficiency | Generally, the amount of “useful work” divided by the amount of energy it requires. In the context of this document, “useful work” is operationalized as the successful execution of standard usage scenarios. |
| Hardware | The material goods required to run programs or to store or transport data. |
| Hardware capacity | Quantifiable characteristic of a hardware system which represents its performance limit on a given dimension of performance (e.g., working memory capacity, computing power, bandwidth). |
| Hardware system | Delimitable unit of hardware that performs defined functions. |
| Indicator | An empirically determinable quantity that provides insight into a matter that cannot be measured directly. The indicators proposed in this document have different levels of measurement. In some cases, researchers will have to settle for an ordinal scale (e.g., “insufficient”, “sufficient”, “good”, “very good”, or even merely “fulfilled”, “not fulfilled”) to avoid giving the false impression of non-existent precision arising from a cardinal scale. |
| Reference system | A hardware system that is defined as generally customary in terms of its most important capacities (e.g., working memory, processor performance) during a defined period of time (e.g., one year). The purpose of the reference system is to be able to express indicators such as “minimum local memory” in relation to a reference value (currently “customary” memory). |
| Resource | In the context of this document, a natural resource, in particular a raw material, a form of energy, or also the capacity of an environmental medium to absorb emissions. To differentiate natural resources from technical ones, especially hardware resources, the more precise term “hardware capacities” is used here for the latter. Since using hardware capacities always results in using natural resources, this distinction (which ultimately amounts to a definitionally difficult differentiation between the ecosphere and the technosphere) is not of decisive importance here. |
| Resource efficiency | Generally, the amount of “useful work” divided by the amount of resources it requires. In the context of this document, “useful work” is operationalized as the successful execution of standard usage scenarios. |
| Software | Programs and data in digital form. |
| Software product | A delimitable unit of programs and data for which a license is available. |
| Standard configuration | A set of conditions, defined as a reference, under which a given software product is run; it includes the parameter settings selected during installation or operation, the system software provided, potentially additional software products required for operation, as well as the reference system at the hardware level. |
| Standard usage scenario | A usage scenario that is used for testing a software product and is supposed to be as representative as possible for the customary use case. |
| Usage pattern | Abstracted form of a sequence of interactions with a given software product. |
| Usage scenario | Description of a usage pattern which is generally machine executable. |
You are leaving the official website of Trier University of Applied Sciences
![[Translate to Englisch:] Facebook](/fileadmin/Beispiel-Dateien/SociaMedia-Icons/facebook-f.svg){kind=icon}
![[Translate to Englisch:] Youtube](/fileadmin/Beispiel-Dateien/SociaMedia-Icons/youtube.svg){kind=icon}
![[Translate to Englisch:] Instagram](/fileadmin/Beispiel-Dateien/SociaMedia-Icons/instagram.svg){kind=icon}