On the JI-RADAR: Uncovering Sustainability Tool Support for Requirements Engineering

· Source: cs.SE updates on arXiv.org · Field: Technology & Digital — Software Development & Engineering, Project & Product Management · Depth: Intermediate, long

Summary

JI-RADAR is a new Jira plugin designed to integrate sustainability considerations directly into agile Requirements Engineering (RE) processes. Built on the widely adopted Atlassian Jira platform, it extends existing features like User Stories and Issues to systematically capture, assess, and trace sustainability impacts. The tool incorporates the Sustainability Management Model (SuMM), a weighted decision matrix based on the five sustainability dimensions from the Sustainability Awareness Framework (SuSAF): Environment, Technical, Social, Economic, and Individual. JI-RADAR enables the creation of "Sustainability Stories" and generates Sprint and Product KPI Reports. A pilot user study with N=4 participants indicated significant improvements in capturing and assessing sustainability information, with both aspects scoring a median of 4.5 out of 5 for usability. This tool aims to bridge the gap between regulatory requirements like the EU's CSRD and daily development workflows.

Key takeaway

For Requirements Engineers and Project Managers integrating sustainability into software development, JI-RADAR offers a practical solution to embed these concerns directly within established Jira workflows. You can customize sustainability dimensions and weights, create traceable "Sustainability Stories," and generate KPI reports, streamlining compliance with regulations like the CSRD. This integration avoids cumbersome standalone tools, ensuring sustainability is a core part of your agile process rather than an afterthought.

Key insights

JI-RADAR integrates sustainability requirements into Jira's agile workflow, enabling systematic assessment and reporting.

Principles

Method

JI-RADAR extends Jira by adding SuMM configuration, allowing users to define "Sustainability Stories", assess artifacts using a Likert scale, and generate Sprint and Product KPI Reports.

In practice

Topics

Code references

Best for: Product Manager, Software Engineer, Research Scientist

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.SE updates on arXiv.org.