International Journal of Multidisciplinary Research and Growth Evaluation

From Ambiguity to AI-Ready Requirements: A Business Analysis Framework for Structuring Business Problems for Intelligent Process Automation

Joseph Idanesi Alieme1, Aumbur Sule2, Valentina Ochuko Obukadata3

  1. 1
  2. 2
  3. 3
Version of record

This is an author-deposited copy. The version of record was originally published elsewhere: Originally published in International Journal of Multidisciplinary Research and Growth Evaluation, Volume 5, Issue 6, 2024. DOI 10.54660/.IJMRGE.2024.5.6.2088-2117 . Original source: https://www.allmultidisciplinaryjournal.com/archives/year-2024.vol-5.issue-6.

Abstract

This paper argues that intelligent process automation fails at specification more often than at implementation. Requirements engineering offers a mature account of ambiguity as a defect to be removed and a mature account of the quality characteristics of a well-formed requirement, but neither transfers cleanly to processes whose automation depends on judgement and on probabilistic components. This paper develops the Ambiguity-to-Specification (A2S) pipeline, a five-gate business analysis framework; problem framing, decision decomposition, data grounding, behavioural specification, and oversight and acceptance, that converts an ambiguously stated business problem into a specification an intelligent automation can be built and governed against. The framework rests on three arguments: that the unit of specification shifts from system behaviour to the decision; that ambiguity is not uniformly a defect but a resource whose resolution should be routed to the gate at which it is cheapest and most informative, leaving a residue that must be specified rather than resolved; and that probabilistic components break the correctness contract on which classical quality criteria rest. A second contribution extends the requirement quality characteristics of ISO/IEC/IEEE 29148 with six AI-readiness characteristics; decidability, data-groundedness, error-tolerance specification, escalation specification, observability and drift sensitivity, each with a test question, an evidencing artefact and a corresponding requirement smell. The framework is illustrated on a hypothetical mid-sized services organisation performing document-heavy casework, and eight propositions are stated for empirical evaluation. The paper is conceptual: no primary data were collected and the framework has not been validated.

Keywords: business analysisrequirements engineeringambiguityintelligent process automationdecision modellingrequirements qualityAI governance

How to cite

Licensed under CC BY 4.0.