Application Bundle Onboarding Dashboard With Automated Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The onboarding process for newly developed software applications is cumbersome, involving manual communication, multiple vendors, and lack of automation, leading to inefficiencies, increased costs, and compromised quality due to a lack of automated testing and security standardization.

Innovation Solution

A dashboard user interface is provided for managing end-to-end onboarding of application bundles, allowing users to select and create components through a graphical user interface with drag-and-drop features, enabling automated distribution and email notifications for approval, and supporting Type 1 and Type 2 bundles with detailed intake UIs for configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual processes are used for onboarding application bundles, then flexibility and customization are maintained, but productivity and time efficiency deteriorate

Engineering Contradiction:
Improveonboarding speedVSAvoidprocess complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The onboarding process is segmented into distinct phases: application bundle creation, quality testing, verification, certification, and deployment. Each phase is handled by dedicated automated components within the multi-tenant system, allowing parallel processing and improving overall productivity while maintaining manageable complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Manual mechanical processes (manual testing, manual verification, manual deployment) are replaced with automated electronic systems. The system uses automated quality testing engines, electronic verification workflows, and programmatic deployment mechanisms to eliminate manual intervention, dramatically improving onboarding speed while the automated nature keeps complexity contained.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If multiple vendors and services are involved in the onboarding process, then comprehensive quality control is achieved, but device complexity and coordination overhead increase

Engineering Contradiction:
Improvequality assuranceVSAvoidsystem integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Multiple vendor services and quality control functions are merged into a single multi-tenant onboarding system. The system consolidates quality testing, verification, and certification capabilities from multiple vendors into one unified platform, maintaining comprehensive quality control while reducing coordination overhead and simplifying the overall system architecture.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The onboarding system is designed with universal multi-tenant capabilities that can accommodate multiple vendors and services through a common interface. The system provides universal quality testing, verification, and certification functions that work across different application bundles and vendors, reducing integration complexity while maintaining comprehensive quality assurance.

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

3Productivity

If manual communication and coordination occur between multiple teams, then flexibility in handling diverse requirements is maintained, but loss of time and productivity deteriorate

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidcoordination time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

Manual communication between Cloud, Network, Security, and Infrastructure teams is replaced with automated electronic communication within the onboarding system. The system uses programmatic interfaces, automated notifications, and electronic workflow coordination to replace manual meetings and communications, dramatically reducing coordination time while improving deployment efficiency.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The multi-tenant onboarding system acts as an intermediary between multiple teams (Cloud, Network, Security, Infrastructure). It consolidates coordination requirements and provides a single point of interaction, eliminating the need for direct communication between all teams. The system mediates all coordination activities, reducing coordination time while maintaining flexibility in handling diverse team requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If automated testing and security standardization are implemented, then quality and reliability improve, but device complexity and initial setup time increase

Engineering Contradiction:
Improvesoftware qualityVSAvoidautomation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Automated testing and security standardization are segmented into distinct modules within the onboarding system. Quality testing, security verification, and compliance checking are separated into independent automated components that can be executed in sequence or parallel. This segmentation improves software quality through comprehensive automated testing while keeping the automation system complexity manageable through modular design.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12373184B2Managing end-to-end onboarding of application bundles
Publication Date: 2025.07.29 RAKUTEN MOBILE INC
  • US12373184B2 patent drawing
  • US12373184B2 patent drawing
  • US12373184B2 patent drawing

AI summary

Management of end-to-end onboarding of application bundles is described. A dashboard user interface is presented for displaying information associated with at least one application bundle component and presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to create. A selection of the at least one application bundle component to create is received via the dashboard menu. Based on the selection, a creation user interface including a selectable control component to initiate creation of the at least one application bundle component is displayed. In response to receiving selection of the selectable control component, the at least one application bundle component is created.