Automatic Scenario Pattern Generating Module for E2E Transaction Coverage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for developing and testing software applications struggle to provide an end-to-end (E2E) view spanning multiple components or applications, lacking the capability to articulate requirements and design implementation effectively for complex transactions.

Innovation Solution

An automatic scenario pattern generating module that utilizes processors and memories to generate visualization artifacts, producing scenario patterns in predefined file formats for E2E views, which can be uploaded to application development or testing tools, and deployed on private clouds to create new features or test cases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional deployment and operational engines are used, then some deployment tasks can be addressed, but the deployment and operational focus required may be challenged at times based on other functional delivery priorities and operations experiences

Engineering Contradiction:
Improvedeployment productivityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the complex deployment and testing process into distinct scenario patterns (e.g., happy path, unhappy path, edge case patterns). Each pattern represents a modular unit that can be independently defined, executed, and managed, thereby reducing overall system complexity while maintaining high productivity through systematic coverage of test scenarios.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-defining scenario patterns that capture common transaction flows, error conditions, and edge cases before actual deployment. These pre-configured patterns serve as templates that can be rapidly instantiated and executed, eliminating the need to manually design each test scenario from scratch during deployment operations.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If Specification by example (SbE) is applied to manage requirements and functional tests, then requirements management improves, but SbE focuses on a single input/output and is very one dimensional, thereby lacking the capability of providing a more E2E view spanning multiple applications, state models and events

Engineering Contradiction:
Improverequirements articulationVSAvoidE2E transaction coverage
Core Design Contradiction:
Loss of informationVSAdaptability or versatility

Solution Approach 1:

The patent extends traditional single-input/output specification by adding temporal and contextual dimensions. Scenario patterns incorporate multiple events, state changes, and intermediate steps within a single transaction flow, transforming one-dimensional input/output pairs into multi-dimensional E2E transaction models that span multiple applications and system states.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent merges multiple SbE examples into unified scenario patterns that represent complete E2E transactions. By combining individual input/output specifications with their contextual relationships, state transitions, and cross-application interactions, the system achieves comprehensive E2E coverage while maintaining the clarity and concreteness of example-based specification.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If manual scenario pattern creation is performed, then scenario patterns can be generated, but the process becomes complex and time-consuming for E2E transactions spanning multiple components or applications

Engineering Contradiction:
Improvescenario pattern accuracyVSAvoidpattern generation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements copying by creating reusable scenario pattern templates that can be instantiated multiple times across different transactions. Once a scenario pattern is defined for a particular transaction type, it can be copied and adapted for similar transactions, significantly reducing the time required to create scenario patterns while maintaining consistency and accuracy across the system.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent achieves universality by designing scenario patterns with parameterized structures that can accommodate multiple transaction types and components. A single scenario pattern template can be configured to handle various E2E transactions spanning different applications, state models, and events, eliminating the need to manually create unique patterns for each specific case and thereby reducing overall pattern generation time.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11550706B1System and method for implementing an automatic scenario pattern generating module
Publication Date: 2023.01.10 JPMORGAN CHASE BANK NA
  • US11550706B1 patent drawing
  • US11550706B1 patent drawing
  • US11550706B1 patent drawing

AI summary

A system and method for automatically generating scenario patterns are disclosed. The system includes a processor; and a memory operatively connected to the processor via a communication interface. The processor receives a request to create new features in connection with development and/or testing of one or more applications; automatically generates scenario patterns corresponding to the new features by utilizing an automatic scenario patterns generating tool; outputs the scenario patterns in a predefined file format providing an end-2-end (E2E) view spanning multiple applications, state models and events; uploads the scenario patterns in the predefined file format onto a system different from the automatic scenario patterns generating tool; deploys corresponding application programming interface (API) on a private cloud to request the scenario patterns in the predefined file format from the system; and implements the requested scenario patterns to create the new features.