AI & ML
Requirements Nobody Wrote Down: Emergence in a Public-Sector ML Pipeline
arXiv cs.SE0 views
arXiv:2611.07951v1 Announce Type: new Abstract: Governments increasingly use machine learning (ML) to handle data volumes beyond their analytical capacity, yet little is known about how requirements arise and evolve as an ML experiment moves toward operational use. Requirements Engineering (RE) for ML often assumes that requirements can be elicited upfront; in the public sector, however, demands arrive vague, stakeholders speak different professional languages, and what counts as a ``good'' result is unknown in advance. We report a 15-month case study of a thematic classification pipeline for Brazil's national digital participation platform, which holds over 60,000 citizen proposals, triangulating 43 project artifacts with interviews of six project participants. Institutional demands arrived as broad goals, endorsed but not sponsored, and only 40\% of the 95 reconstructed requirements and criteria were ever formalized. The pipeline's key requirements emerged largely from experiments, model outputs, and integration work, shaped by technical decisions and institutional constraints; the central one, the classification categories, was settled by a government taxonomy chosen for its institutional legitimacy. Acceptance relied on technical metrics, domain judgment, and political assessment, without shared thresholds or validation of usefulness in practice. In public-sector ML, technical and institutional artifacts thus act as elicitation instruments, and experimentation and integration belong to the requirements process.
Source:https://arxiv.org/abs/2611.07951PreviousA Low Similarity Score Does Not Show Independence after Source-Conditioned Repository RewritingNextReducing Representational Interference in Retrieval Embeddings with Trainable Prefix Tokens
Related posts
A detective game where LLM suspects lie: what it taught me about trusting AI at work
0dev.to AI
Axi Lets Retail Traders Bet On OpenAI And Anthropic Prices
0dev.to AI
My Claude Code token log, week of Nov 02
0dev.to AI
Jev Shows $0 Bill After 1M Tokens, Orosz Says
0dev.to AI
B2b Website Redesign Agency
0dev.to WebDev
Google SecOps Added Case Wall Tags. One Untagged Result Can Change the Handoff.
0dev.to DevOps