US 12,430,228 B2
Determining non-functional requirements (NFR) from a run time environment and incorporating into a development cycle
Nitin Tewari, Ghaziabad (IN); Mayank Sharma, Bangalore (IN); Vinay Nair, Hyderabad (IN); Aditi Bhattacharya, Kolkata (IN); and Sandeep Dixit, Bangalore (IN)
Assigned to International Business Machines Corporation, Armonk, NY (US)
Filed by International Business Machines Corporation, Armonk, NY (US)
Filed on Jul. 28, 2023, as Appl. No. 18/227,441.
Prior Publication US 2025/0036548 A1, Jan. 30, 2025
Int. Cl. G06F 11/3604 (2025.01); G06F 11/3668 (2025.01)
CPC G06F 11/3612 (2013.01) [G06F 11/3676 (2013.01); G06F 11/3684 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method, comprising:
in response to a determination, from results of analyzing runtime information associated with an application failure event and/or sub-par runtime performance that occurs during a first operational run cycle of an application, that the failure event and/or sub-par runtime performance is caused by a Non-Functional Requirement (NFR) issue, analyzing application details associated with a plurality of different timestamp intervals;
in response to a determination that a first of the timestamp intervals falls within a predetermined timestamp associated with the application failure event and/or sub-par runtime performance, collecting first pattern information about the application details associated with the first timestamp interval;
applying the first pattern information to a predetermined weightage algorithm; and
in response to a determination, based on an output of the predetermined weightage algorithm, that test coverage gaps exist in a predetermined collection of test cases, causing test cases to be created based on the first pattern information for mitigating the NFR issue during a subsequent operational run cycle of the application.