Papers
Topics
Authors
Recent
Search
2000 character limit reached

REConnect Framework for Participatory RE

Updated 25 May 2026
  • REConnect Framework is a participatory requirements engineering method that re-centers the process on trust, co-design, and empowerment to ensure socially grounded software requirements.
  • It integrates actionable practices across elicitation, analysis, and validation phases, exemplified by stakeholder mapping, iterative prototyping, and capacity building.
  • The framework supports generative AI integration with human-in-the-loop oversight and has been validated through case studies demonstrating measurable improvements.

The REConnect Framework is a participatory requirements engineering (RE) methodology that re-centers the requirements process on sustained, relational human connection. It operationalizes a set of principles and actionable practices to ensure that software requirements are not only technically robust but are socially grounded, culturally legitimate, and empowering to all stakeholders involved. REConnect is architected to support continuous stakeholder engagement across all classical RE phases—elicitation, analysis, and validation—and natively accommodates integration with emerging Generative AI tools, while maintaining human agency and contextual integrity (Damian et al., 31 Aug 2025).

1. Formal Definition and Objectives

REConnect is defined as a methodological tuple: REConnect=(S, P, A, phase, impl)\mathrm{REConnect} = (S,\,P,\,A,\,\text{phase},\,\text{impl}) where:

  • SS: the set of formal (e.g., institutional) and informal (e.g., community leaders, end-users) stakeholders;
  • P={Trust,CoDesign,Empower}P = \{\mathit{Trust}, \mathit{CoDesign}, \mathit{Empower}\}: the three core guiding principles;
  • AA: the set of actionable RE practices ("REActions");
  • phase ⁣:A→{Elicitation,Analysis,Validation}\text{phase}\colon A\to \{\mathit{Elicitation},\mathit{Analysis},\mathit{Validation}\}: RE phase of each practice;
  • impl ⁣:A→P\text{impl}\colon A\to P: mapping from practices to operative principle.

The principal objectives are to:

  • Embed deep contextual understanding in requirements, ensuring cultural and social legitimacy;
  • Sustain engagement with all stakeholders throughout all RE phases;
  • Explicitly surface and embed human values such as dignity, fairness, and inclusion in system requirements;
  • Foster and amplify stakeholder agency, leading to requirements that are sustainable and extensible beyond system deployment.

2. Core Principles and Enablers

REConnect is structured around three interdependent principles:

2.1 Trust

Establishing strong, mutual trust among all stakeholders is foundational. Trust is operationalized through a dynamic trust-strength function T:S×S→[0,1]T: S\times S \to [0,1], mapping every pair of stakeholders to their current trust metric. This is driven by structured relational activities such as contextual stakeholder mapping and immersive field presence.

Enablers:

  • Joint construction of stakeholder role maps (formal/informal roles);
  • Ethnographic fieldwork to surface latent socio-political dynamics;
  • Story circles and open-ended workshops to reveal hidden concerns or historical mistrust.

2.2 Co-Design

This principle repositions stakeholders from passive sources of information to active co-creators of requirements and designs, formalized as a surjective function φ:S×X→R\varphi: S \times X \to R, mapping stakeholder-artifact pairs to requirements.

Enablers:

  • Iterative, participatory prototyping ("Wizard of Oz" simulations);
  • Decomposition workshops for scenario-driven requirement mapping;
  • Socio-culturally situated artifacts (e.g., low-literacy iconography).

2.3 Empower

Stakeholder empowerment is formalized as E:S→{0,1}E: S\to\{0,1\}, with actionable practices designed to move E(s)E(s) to 1. It aims to transform users from passive subjects to co-owners and agents of change with lasting impact on system evolution.

Enablers:

  • Motivation mapping aligned to both requirements and stakeholder goals;
  • Engagement in real deployments and operational roles;
  • Train-the-trainer programs that transfer governance and technical maintenance to the community.

3. Actionable RE Practices ("REActions")

REConnect specifies nine context-sensitive, phase-aligned practices, each mapped to an operative principle:

Phase Practice Principle
Elicitation Contextual Stakeholder Mapping Trust
Elicitation Immersive Field Presence Trust
Elicitation Community-Engaging Workshops Trust
Analysis Iterative Prototyping & Simulation CoDesign
Analysis Community-Engaged Requirement Mapping CoDesign/Trust
Analysis Co-Design Socioeconomic Artifacts CoDesign
Validation Motivation Mapping Empower
Validation Engage Empowered Stakeholders Empower
Validation Capacity Building & Training Empower

Each practice consists of explicit steps to formalize relationality, contextual validation, and cyclical feedback. For example, Contextual Stakeholder Mapping includes convening initial meetings, mapping influence circles, and identifying community gatekeepers and informal leaders; Iterative Prototyping combines low-fidelity design with scenario-driven role play; Motivation Mapping explicitly aligns stakeholders' intrinsic motivations to technical capabilities.

4. Integration with Generative AI

REConnect offers a principled mechanism for incorporating Generative AI (GenAI) into participatory RE, while maintaining human-centric control:

  • Step 1: Groundwork via stakeholder mapping and ethical boundary setting (humans as value guardians);
  • Step 2: Knowledge discovery—curation of raw AI-generated summaries (LLMs) as initial thematic artifacts;
  • Step 3: Human-in-the-loop sense-making, ensuring AI outputs are validated, contextualized, and reinterpreted;
  • Step 4: Alignment of stakeholder motivations with capabilities identified in previous steps;
  • Step 5: AI-supported co-design for rapid prototyping, subject to immediate stakeholder review and adjustment.

At each stage, the artifact-generation process is formalized as a collaboration SS0 with subsequent stakeholder validation, promoting AI accountability to the values established by the human participants.

5. Empirical Validation: Case Studies

REConnect was piloted in three socio-technical contexts:

  • BloodSync (Nepal): Building trust with local officials, iterative workflow redesign via co-design, empowerment through local ownership (blood committees). Measurable outcome: ≈ 40% increase in donor turnout within six months.
  • Herluma (Canada): Trust cultivated with homeless women, direct stakeholder-led decision to abandon mobile-first in favor of web-based tools, and empowerment by giving staff control over privacy. Outcome: 70% reduction in search time for shelter beds, increased staff morale.
  • BridgingRoots (Inuit Arctic): Trust via multi-year relational investment and engagement with Elders, co-design of game-authoring for youths, youth-led content curation. Outcomes: increase in classroom attendance (45%→85%), enhanced intergenerational engagement.

These cases demonstrate the replicability of REConnect's principles and practices in adverse, low-resource, or historically underserved environments.

6. Distinguishing Features and Significance

REConnect marks a methodological shift in RE by:

  • Rejecting extractive or document-centric approaches in favor of dialogic, evolving, and participatory processes;
  • Systematically mapping each RE action to a contextual principle and phase—supporting both practical implementation and rigorous study;
  • Providing a resilient pattern for inclusion of automated and AI-driven tools, with explicitly defined guardrails that ensure continuing stakeholder agency and iterative human oversight.

The framework is positioned as a blueprint for developing requirements that anticipate not just technical feasibility but long-term social embedding, legitimacy, and adaptability (Damian et al., 31 Aug 2025).

Definition Search Book Streamline Icon: https://streamlinehq.com
References (1)

Topic to Video (Beta)

No one has generated a video about this topic yet.

Whiteboard

No one has generated a whiteboard explanation for this topic yet.

Follow Topic

Get notified by email when new papers are published related to REConnect Framework.