Integrated Service Framework Standardization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The inefficiencies in computer programming arise from the lack of a standardized framework, leading to redundant code development and increased time and costs as multiple programmers create similar programs using different algorithms and methods, resulting in varied and non-compatible code structures.

Innovation Solution

An integrated service framework with an abstract class that provides a standardized structure for programming services, allowing developers to create class plug-ins within this framework, reducing redundant programming efforts and enabling efficient code development through a service manager and controller for monitoring and managing services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple programmers create programs from scratch using different algorithms and methods, then each programmer has flexibility in choosing programming approaches, but the development time and costs increase due to redundant code creation and lack of standardization

Engineering Contradiction:
Improveprogramming flexibilityVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the programming process into modular components through the abstract class structure. The abstract class divides common service functionality into standardized methods that can be independently developed, tested, and reused across multiple services. This segmentation allows programmers to focus only on service-specific logic while sharing common infrastructure, thereby maintaining flexibility while improving development efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The abstract class serves as a universal template that can be applied to multiple different services across various programming languages and operating systems. By defining common methods and structures at the abstract level, the framework enables a single implementation to serve multiple purposes and services, eliminating redundant programming while maintaining adaptability to different service requirements.

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

2Adaptability or versatility

If programmers write code without a standardized framework, then each program can be customized to specific needs, but the time to interface with and maintain multiple different code structures increases

Engineering Contradiction:
Improveprogram customizationVSAvoidinterface time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The abstract class acts as an intermediary layer between the operating system and service-specific implementations. It provides a standardized interface that all services must implement, allowing programmers to interact with diverse services through a common structure. This intermediary approach maintains program customization capabilities while significantly reducing the time required to interface with different services, as developers work with a consistent API regardless of the underlying service implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If no abstract class structure is provided, then programmers have complete freedom in code organization, but redundant programming of common tasks increases development costs

Engineering Contradiction:
Improveprogramming freedomVSAvoidcode reusability
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-defining the abstract class structure with common service methods, patterns, and best practices before actual service development begins. This upfront preparation establishes a reusable framework that guides programmers in creating services, eliminating the need to reinvent common patterns for each service while preserving freedom in implementing service-specific logic within the established structure.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8850387B2Integrated service framework
Publication Date: 2014.09.30 BANK OF AMERICA CORP
  • US8850387B2 patent drawing
  • US8850387B2 patent drawing
  • US8850387B2 patent drawing

AI summary

Embodiments of the invention provide for methods, systems and computer program products for an integrated service framework with a suite of products that provide a development environment and common framework for programming within an operating system. The programmers write code to develop class plug-ins within that structure of the abstract class in order to perform services. The abstract class provides a standardized structure that may be utilized by all of programmers working within the integrated service framework to reduce redundant programs. The integrated framework also provides a service manager that identifies the class plug-ins, runs the services, logs information about the services, sends notifications to users about the services, configures itself to monitor the services, and provides communication between the services. Furthermore, the integrated service framework also provides a controller service that allows a programmer or an administrator to control, monitor, or query any issues that occur with the services.