Sustainability requirement patterns
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
In light of the looming threats of global climate change and environmental degradation, the software research community has begun to recognize the need to transition toward environmental sustainability. However, the process of detecting, specifying and evaluating requirements related to environmental sustainability within industry is often neglected or at best performed after the system is built. Most software engineering teams do not include any environmental sustainability expertise to account for the broad range of sustainability concerns related to software systems. To overcome the barriers of incorporating environmental sustainability into the requirements engineering process, this paper suggests the use of sustainability requirement patterns (SRPs), which will provide software engineers with guidance on how to write specific types of sustainability requirements. SRPs contain information on the situations in which the pattern should be used, a starting point for developing sustainability requirements, and any other information needed to develop requirements of a specific type. This research is part of an overarching research project on Software Engineering for Sustainability.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Towards a definition of sustainability in and for software engineering
Penzenstadler, B. (2013) · Proceedings of the 28th Annual ACM Symposium on Applied Computing · doi:10.1145/2480362.2480585 · Cited by 82 · cited 1×
“Developers of these systems, however, generally lack a comprehensive understanding of how to integrate sustainability into their software development processes [1].”
Background
Cited by
Duboc, L., Penzenstadler, B., Porras, J., Akinli Kocak, S., Betz, S., Chitchyan, R., Leifler, O., Seyff, N., & Venters, C. C. (2020) · Requirements Engineering · doi:10.1007/s00766-020-00336-y · Cited by 88
Duboc, L., Betz, S., Penzenstadler, B., Akinli Kocak, S., Chitchyan, R., Leifler, O., Porras, J., Seyff, N., & Venters, C. C. (2019) · 2019 IEEE 27th International Requirements Engineering Conference (RE) · doi:10.1109/re.2019.00013 · Cited by 69
Characterising Sustainability Requirements: A New Species Red Herring or Just an Odd Fish?
Venters, C. C., Seyff, N., Becker, C., Betz, S., Chitchyan, R., Duboc, L., Mcintyre, D., & Penzenstadler, B. (2017) · 2017 IEEE/ACM 39th International Conference on Software Engineering: Software Engineering in Society Track (ICSE-SEIS) · doi:10.1109/icse-seis.2017.2 · Cited by 44
Betz, S., Penzenstadler, B., Duboc, L., Chitchyan, R., Kocak, S. A., Brooks, I., Oyedeji, S., Porras, J., Seyff, N., & Venters, C. C. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3649597 · Cited by 23
“…into the SE process [97], the application of a sustainability requirement pattern to guide the specification of sustainability requirements [98], an economics-driven architectural evaluation method which extends the CBAM (Cost Benefits Analysis Method) and integrates principles of modern…”
Metadata
- Authors
- Roher, K., & Richardson, D.
- Venue
- 2013 3rd International Workshop on Requirements Patterns (RePa)
- Publisher
- IEEE
- Published
- 2013-07
- Pages
- 8-11
- OpenAlex
- W2128730087
- Cited by
- 37
- References
- 1
- FWCI
- 1.88
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Sustainability requirement patterns. https://app.cochat.ai/papers/10.1109/repa.2013.6602665
- The paper
- Roher, K., & Richardson, D. (2013). Sustainability requirement patterns. 2013 3rd International Workshop on Requirements Patterns (RePa). https://doi.org/10.1109/repa.2013.6602665
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.