Composite Software Program Integrating Callable Libraries

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional software development approaches require separate installation, compilation, and execution of individual packages, which can be cumbersome and inefficient, often requiring permissions and additional storage space, and may not be ideal for embedding packages directly into the software program.

Innovation Solution

A composite software program is generated that incorporates the functionality of individual packages by rewriting their source code as callable libraries and using invocation mechanisms, allowing the packages to run in a separate process without affecting the main program, thus eliminating the need for separate executables and permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate standalone executable packages are used for software development tools, then each package can be independently executed with its own functionality, but the process becomes cumbersome and inefficient requiring separate installation, compilation and execution

Engineering Contradiction:

Improveindependent package functionalityVSAvoidseparate installation and execution process

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent combines multiple separate standalone executable packages into a single integrated executable file. The system rewrites package source code as callable libraries and generates a composite software program that can invoke these libraries, merging the functionality of multiple packages while eliminating the need for separate installation and execution processes.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The composite software program serves multiple functions by incorporating callable libraries from different packages. A single executable file can perform tasks that previously required multiple separate tools, making the system more versatile while simplifying the user workflow.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If separate standalone executable packages are used, then each package maintains its own execution environment, but additional storage space is required and permission issues may arise

Engineering Contradiction:

Improveseparate execution environmentVSAvoidstorage space requirement

Core Design Contradiction:

ReliabilityVSWeight of stationary object

Solution Approach 1:

The patent embeds callable libraries within the composite software program's execution environment. The composite program contains or references the rewritten package code, allowing nested execution where smaller library functions are invoked within the larger composite executable context, reducing the need for separate stored executable files.

Inventive Principle:

Principle #7Nested doll (Nesting)

Solution Approach 2:

The system rewrites package source code as callable libraries that can be embedded or linked into the composite program. Instead of storing multiple separate executable files, the system creates a single composite executable that incorporates the necessary library code, reducing overall storage requirements while maintaining execution capabilities.

Inventive Principle:

Principle #26Copying

3Device complexity

If packages are embedded directly into the software program, then integration is achieved, but the packages may affect the main program execution and conflict with other packages

Engineering Contradiction:

Improveintegration levelVSAvoidmain program execution stability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent segments the software system into a composite software program that coordinates multiple callable libraries. Each package's functionality is divided into callable library units that can be independently invoked by the composite program, allowing modular execution that prevents conflicts between packages while maintaining integration.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The composite software program acts as an intermediary between the user and the individual package functionalities. It manages the invocation of callable libraries, handling execution control and coordination, thereby preventing direct conflicts between packages while maintaining their standalone capabilities through standardized invocation mechanisms.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11256483B2Approaches for amalgamating disparate software tools

Publication Date: 2022.02.22 PALANTIR TECHNOLOGIES INC

AI summary

Systems and methods are provided for obtaining one or more source code files that correspond to a software program. At least one first software package that is separately executable from the software program is obtained, the first software package including one or more source code files. At least one first callable library for the first software package and at least one first invocation mechanism for calling the first callable library are generated. A composite software program that is capable of invoking at least the software program and the first callable library for the first software package using the first invocation mechanism is generated.