Assessing Application Stability – The Application Stability Index (ASI)

Read full text Summarise with VIRAT
Authors: Abhinav Srivastava, Jasleen Kaur Multani
Cited by: 0

Summary

No summary yet. VIRAT can read this paper and write a plain-language summary of its aim, methods, key findings and limitations.

Summarise with VIRAT Free to try with your Science Catalogs account.

Abstract

Modern DevOps teams track many fragmented release indicators—failed tests, open defects, downtime, repair time—yet lack a unified stability measure to guide “ship or hold” decisions. We propose the Application Stability Index (ASI), a single score (0–999) combining six factors: BrokenIndex, AverageFixTime, Downtime, FailedTestCases, FailedSuites, and ApprovedVariances. Computed automatically from CI/CD and incident data, ASI produces an interpretable trend line across releases. We evaluated ASI on five releases of a medium-scale MIS system. Results showed strong correlation between ASI and post-release incidents: the highest-scoring release (ASI = 679) had the fewest incidents, while the lowest (ASI = 115) required multiple emergency patches. This paper contributes: (1) a conceptual model of ASI, including rationale for the 0–999 scale and weighting of stability factors; (2) a methodology and reference workflow for extracting and computing ASI from DevOps telemetry; (3) a case study demonstrating ASI detects regressions earlier than traditional metrics; and (4) practical guidelines for integrating ASI into release gates and dashboards. We conclude that ASI is a lightweight, actionable metric that supports go/no-go decisions and data-driven dialogue between engineering and stakeholders.

Fields of Study & Subjects

Software Engineering Techniques and Practices Software System Performance and Reliability Software Engineering Research

Publication details

Journal / source
International Journal Of Engineering And Computer Science
Volume
15
Issue
03
Pages
28337–28347
Publication date
1 January 2026
Language
EN