In short
- Definition: The degree to which a system limits its impact on the environment, including energy use, carbon emissions and electronic waste.
- Goal: Reduce the ecological footprint of building and running the system.
- Example S.M.A.R.T. requirement: 20% fewer grams of CO2e per transaction than the previous year, measured with the hosting provider’s carbon report.
1. Definition
As a non-functional requirement, environmental protection describes how much a system limits its impact on the environment: the energy it consumes, the carbon emissions linked to that energy and to the hardware it runs on, and the electronic waste it causes [1], [2].
The greenest server is the one you did not need to run.Key takeaway
Software does not burn fuel itself, but it decides how much hardware is needed, how hard it works and how long devices stay usable. The Green Software Foundation’s Software Carbon Intensity (SCI) specification, published as ISO/IEC 21031:2024, offers a method to express emissions as a rate per functional unit, such as per user or per transaction [3], [4].
Typical levers are efficient code, right-sized infrastructure, low-carbon hosting regions, carbon-aware scheduling of batch jobs and support for older devices.
2. Goal
The goal is to reduce the ecological footprint of building and running the system, and to support the organization’s sustainability commitments and reporting.
Without explicit targets, emissions grow with usage, and teams cannot show progress or compare design options.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Carbon intensity | gCO2e per transaction (SCI score) | ≥ 20% lower than the previous year | SCI method or provider carbon reports |
| Energy use | kWh per month | Within the agreed budget | Provider or data-center reports |
| Low-carbon hosting | % of workloads in low-carbon regions | ≥ 80% | Cloud region inventory |
| Device support | Oldest supported device age | ≥ 5 years | Compatibility matrix |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Cloud service: “The carbon intensity of the service, measured with the SCI method per 1,000 transactions, shall decrease by at least 20% compared with the previous year.”
- Batch processing: “Non-urgent batch jobs shall be scheduled in the hours of lowest grid carbon intensity when the delay is under 12 hours.”
- Mobile app: “The app shall remain fully usable on devices up to 5 years old, to avoid forcing hardware replacement.”
5. Questions to Ask Stakeholders
- Does the organization have sustainability targets or reporting duties?
- Which unit of work best represents the system’s value?
- Which hosting regions and providers are acceptable?
- Can some workloads be delayed or moved to lower-carbon times?
- What is the oldest device we must support?
- Who will measure and report emissions?
6. Common Pitfalls
- Counting only servers. End-user devices and networks also consume energy. Include them where relevant.
- Buying offsets instead of reducing. Measure and reduce first; offsets do not lower the system’s actual intensity.
- No baseline. Without a starting measurement, progress cannot be shown.
7. Related NFRs
- Efficiency — efficient software uses less energy.
- Footprint Reduction — smaller software needs less storage and bandwidth.
- Cost — lower resource use often lowers bills.
- Platform Compatibility — supporting older devices extends their life.
8. FAQ
A rate of carbon emissions per functional unit of a software system, defined by the Green Software Foundation and published as ISO/IEC 21031:2024.
It can be, thanks to higher utilization and renewable energy, but it depends on the region and on how efficiently resources are used.
Running flexible workloads at times or places where electricity has a lower carbon intensity.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
| SCI | Software Carbon Intensity | Green Software Foundation method for measuring the carbon emissions of software per unit of work. | [4] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Bandwidth | Maximum amount of data a connection can carry per second. | [9] |
| Baseline | Approved reference point (scope, schedule, cost or measurement) against which progress is compared. | [10] |
| Batch processing | Processing large groups of records together, often at night, rather than one at a time. | [11] |
| Carbon footprint | Total greenhouse gas emissions caused by an activity, expressed as CO2 equivalent. | [12] |
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
| Transaction | Unit of work, such as a payment or an order, that must complete fully or not at all. | [15] |
10. Sources and Further Reading
- [1] “Green computing.” Wikipedia. https://en.wikipedia.org/wiki/Green_computing (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “Software Carbon Intensity (SCI) Specification.” Green Software Foundation. https://sci.greensoftware.foundation/ (accessed Nov. 18, 2026).
- [4] “SCI, Software Carbon Intensity (ISO/IEC 21031:2024).” Green Software Foundation. https://greensoftware.foundation/standards/sci/ (accessed Nov. 18, 2026).
- [5] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Bandwidth (computing).” Wikipedia. https://en.wikipedia.org/wiki/Bandwidth_(computing) (accessed Nov. 19, 2026).
- [10] “Baseline (configuration management).” Wikipedia. https://en.wikipedia.org/wiki/Baseline_(configuration_management) (accessed Nov. 19, 2026).
- [11] “Batch processing.” Wikipedia. https://en.wikipedia.org/wiki/Batch_processing (accessed Nov. 19, 2026).
- [12] “Carbon footprint.” Wikipedia. https://en.wikipedia.org/wiki/Carbon_footprint (accessed Nov. 19, 2026).
- [13] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [14] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [15] “Database transaction.” Wikipedia. https://en.wikipedia.org/wiki/Database_transaction (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @andrewcoelho; inline photo by @jlag_photos, both on Unsplash.




