Service-Level Maturity Assessment: A Gap Analysis

Maturity and quality assessment frameworks have guided software and IT management since the Capability Maturity Model of the early 1990s. Their dominant premise is that organisations progress along a universal ladder toward a single ideal of "good," and that premise fits awkwardly with modern service-oriented architectures, where the individual software service is the unit of deployment, operation, and investment. This paper presents a structured review of the maturity-assessment literature organised around two axes: the unit of assessment (organisation, process, or service) and the calibration basis of the thresholds against which maturity is judged (a single universal standard, or differentiated expectations set through some mechanism). Mapping the literature onto these axes shows three densely populated regions and one sparsely occupied corner. To examine that corner precisely, we define a strong target construct: strategically grounded, multi-domain, service-level maturity assessment, where "strategically grounded" names the theoretically preferred instantiation while the inclusion criteria test the more general reproducible-calibration construct. We operationalise the construct through four inclusion criteria and find that, across the peer-reviewed corpus assembled here, no framework fully occupies it. Several approaches partially enter the space. Site-reliability-engineering error budgets supply service-level, context-sensitive reliability thresholds; developer-portal scorecards supply practitioner-level service tiering; and process-assessment models supply configurable capability profiles, but above the service level, so they are adjacent analogues rather than occupants of the corner. None combines service-level granularity, differentiated target profiles, a reproducible context-to-threshold calibration mechanism, and multi-domain maturity coverage. We interpret this gap as a translation problem. The field has produced sophisticated measurement instruments and sophisticated strategic-positioning tools, but no connective mechanism that derives differentiated, service-level operational thresholds from stated contextual variables. From the review we derive four core design requirements for an artefact that would occupy the construct, together with two adoption principles grounded in practitioner evidence, and we position the contribution relative to situational maturity models, architectural fitness functions, and IT portfolio management. The review follows a concept-centric methodology, triangulated against an independent literature corpus to guard against single-database bias.