Unified Software Framework for Business and Technical Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software frameworks are limited in scope and primarily designed for a single audience, failing to effectively address both business and technical aspects of software applications, and lack comprehensive interaction and testing capabilities.

Innovation Solution

A software solution framework system that provides an interface for multiple users to interact with and test various business and technical aspects of software applications, mapping user inputs to system capabilities and validating functionality through test cases, while offering output and feedback mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If frameworks are designed for a single audience (end users or developers), then the framework can be simplified and focused, but the scope of aspects covered is limited

Engineering Contradiction:
Improvescope of aspects coveredVSAvoidframework complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework is designed to serve multiple audiences simultaneously - end users, developers, and testers - by providing a unified interface that accommodates different user roles. The framework includes role-based access control and customized views for each audience type, allowing one framework to fulfill multiple functions that previously required separate tools.

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

Solution Approach 2:

The framework is segmented into distinct modules and layers that can be accessed differently by various user roles. Business aspects, technical aspects, and testing capabilities are separated into distinct sections while maintaining unified access through a common interface, allowing each audience to interact with relevant portions without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If frameworks provide comprehensive business and technical aspects, then the framework becomes more versatile, but the ease of operation decreases

Engineering Contradiction:
Improvecompleteness of coverageVSAvoiduser interaction ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

Different portions of the framework are optimized for specific user roles. The interface provides customized navigation, displays, and interaction modes tailored to each audience (end users see business-focused views, developers see technical architecture, testers see testing capabilities). This local optimization maintains ease of operation for each user type while preserving comprehensive coverage overall.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The framework dynamically adapts its interface and available functionality based on the user's role and selection. When users access the framework, their role is detected and the interface automatically configures itself to show relevant aspects first, making comprehensive coverage manageable and intuitive for each user type without requiring them to navigate through all features.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If frameworks allow interaction with multiple aspects, then the framework becomes more versatile, but the device complexity increases

Engineering Contradiction:
Improvemulti-aspect interaction capabilityVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework introduces an intermediary layer - a unified interface that mediates between multiple audiences and the complex underlying system. This interface layer abstracts the complexity by providing standardized, role-appropriate access points to business aspects, technical aspects, and testing capabilities, shielding users from the complexity while maintaining comprehensive interaction capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If frameworks are designed for rapid development, then productivity increases, but the completeness and clarity of the software application may be compromised

Engineering Contradiction:
Improvedevelopment speedVSAvoidsoftware completeness and clarity
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The framework establishes pre-existing relationships and mappings between business aspects, technical aspects, and testing capabilities before development begins. These pre-configured connections enable rapid development by providing ready-to-use templates and structured approaches, while simultaneously ensuring completeness and clarity through enforced traceability between all aspects of the software application.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The framework incorporates feedback mechanisms that continuously validate the software application against predefined business and technical requirements. Testing capabilities provide immediate feedback on completeness and clarity, allowing developers to maintain high precision while working rapidly by automatically identifying gaps or inconsistencies in the software design.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9772933B1Software solution framework system, method, and computer program for allowing interaction with business and technical aspects of a software application and for allowing testing of the software application
Publication Date: 2017.09.26 AMDOCS DEV LTD
  • US9772933B1 patent drawing
  • US9772933B1 patent drawing
  • US9772933B1 patent drawing

AI summary

A software solution framework system, method, and computer program product are provided for allowing interaction with business and technical aspects of a software application, as well as for allowing testing associated with the software application. In use, an interface is provided to a software solution framework accessible to a plurality of users for interacting with information relating to a plurality of different business and technical aspects of a software application. Additionally, input is received from at least one of the users relating to at least one of the business and technical aspects of the software application, utilizing the interface to the software solution framework, the input including at least one requirement for the software application. Further, the at least one requirement is mapped to at least one system capability associated with the at least one of the business and technical aspects of the software application. In addition, one or more test cases are mapped to the at least one system capability such that each test case, when executed, validates whether tested functionality meets the at least one requirement. Moreover, output is provided relating to the at least one of the business and technical aspects of the software application, utilizing the interface to the software solution framework.