Abstract: A system comprises a set of databases in communication with a processor, and a requirements validation AI engine hosted by the processor. The databases comprise software requirements, regulatory guidelines, historical requirements defects, requirements review checklist, and prompts. The AI engine communicates with the databases, and a fine-tuned LLM communicates with the AI engine. A user interface communicates with the AI engine, and a configuration management repository communicates with the user interface. The user interface sends new requirements, from the configuration management repository, with corresponding check instructions to the AI engine, which selects prompts for review, based on types of new requirements and the check instructions. The AI engine sends the prompts and the new requirements to the LLM to review for any defects in the new requirements. The LLM sends a response to the user interface, to report on validity of and any defects in the new requirements.

Abstract: Techniques are generating a test plan, based on test requirements, using artificial intelligence (AI) whilst avoiding hallucinations. Hallucinations in the AI generated test plan may be reduced by utilizing generative AI and providing the generative AI with pre-defined custom templates, test plan guidelines, and/or information for selecting a test environment based on test type. Additionally or alternatively, a similarity between the test plan and a similar test plan may be determined to avoid hallucinations.

Abstract: A method for verifying data and control couplings of software under test comprises obtaining software architecture and design information for the software; extracting expected control coupling information based on an order in which software component calls are in the software architecture; extracting expected data coupling information from one software component to another software component in a sequence diagram; updating the expected control and data coupling information in an expected control and data coupling sequencing table; deriving actual control coupling information from execution trace data obtained from a requirements based test execution; deriving actual data coupling information from data trace information; and updating the actual control and data coupling information in an actual control and data coupling sequencing table.

Abstract: A system includes processor(s) configured to: receive natural language text describing software requirements for software program; analyze natural language text describing software requirements to identify relationships between different software requirements at least in part by: analyzing how data flows between different software requirements; analyzing how different software requirements influence path and decision points to achieve functionality identified by software requirements; and identifying dependencies between different software requirements; establish sequence for different software requirements based on relationships identified between different software requirements; group plurality of different software requirements together into logical group(s) of software requirements based on sequence for different software requirements and relationships between different software requirements; generate test cases based on logical group(s) of software requirements; execute software program using test cases;

Abstract: A method for verifying data and control couplings of software under test comprises obtaining software architecture and design information for the software; extracting expected control coupling information based on an order in which software component calls are in the software architecture; extracting expected data coupling information from one software component to another software component in a sequence diagram; updating the expected control and data coupling information in an expected control and data coupling sequencing table; deriving actual control coupling information from execution trace data obtained from a requirements based test execution; deriving actual data coupling information from data trace information; and updating the actual control and data coupling information in an actual control and data coupling sequencing table.