Stacked-Layer Source Code Framework for Platform Porting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In modern digital environments, porting a project in a code management system to a different platform architecture is challenging due to constraints on functional modules that work in parallel, making it difficult to split and compile efficiently.

Innovation Solution

A stacked-layer framework is introduced, comprising a code layer, a label layer, and a mask layer, which allows for efficient partitioning of source code by features or functions, enabling automatic micro-compiling and improved collaboration among developers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If source code is managed as a complete unit without partitioning, then code integrity is maintained, but porting to different platform architectures becomes inefficient and time-consuming

Engineering Contradiction:
Improveporting efficiencyVSAvoidcode management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the source code into modular functional units with defined interfaces. Each functional unit can be independently managed, labeled, and ported to different platform architectures. This segmentation enables parallel processing and reduces the complexity of managing large codebases during porting operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of organization by implementing a stacked-layer framework that adds hierarchical structure to code management. This framework organizes code into multiple layers (functional units, modules, subsystems) that can be selectively compiled and ported, transforming the traditional flat code structure into a multi-dimensional organization system.

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

2Adaptability or versatility

If the entire source code base is compiled and distributed, then all features are available, but load and dependency increase unnecessarily

Engineering Contradiction:
Improvefeature selection flexibilityVSAvoidcode volume
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent applies the extraction principle by enabling selective removal of unwanted functional units from the codebase. Users can extract only the specific features and functions they need through the label layer and mask layer mechanisms, eliminating unnecessary code volume while maintaining adaptability to choose different feature combinations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements local quality by allowing different portions of the codebase to have different levels of visibility and accessibility. The label layer assigns specific characteristics to different code regions, enabling fine-grained control over which features are exposed to users based on their specific needs, rather than distributing the entire codebase uniformly.

Inventive Principle:
Principle #3Local quality

3Ease of manufacture

If functional modules are constrained to work in parallel without proper partitioning, then system integration is simplified, but splitting and compiling becomes difficult

Engineering Contradiction:
Improvecompilation easeVSAvoidmodule dependency structure
Core Design Contradiction:
Ease of manufactureVSStability of the object's composition

Solution Approach 1:

The patent applies preliminary action by pre-defining interfaces and dependency relationships between functional units during the code organization phase. This preliminary structuring establishes clear compilation boundaries and interface contracts before actual compilation occurs, making it easier to split and compile modules independently while maintaining stable dependency relationships.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12008363B1Delivering portions of source code based on a stacked-layer framework
Publication Date: 2024.06.11 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12008363B1 patent drawing
  • US12008363B1 patent drawing
  • US12008363B1 patent drawing

AI summary

Various embodiments of the present invention provide a method, system, and program product that perform the following operations: organizing a project having source code into a stacked-layer framework, the stacked-layer framework having: (i) a code layer including the source code of the project, (ii) a label layer including one or more label pages labelling the source code according to respective features of the source code, and (iii) a mask layer including one or more mask pages concealing portions of the source code according to labels of the label layer; receiving a request from a user to utilize a portion of the project, wherein the request includes a user requirement identifying one or more desired features; identifying a mask page of the one or more mask pages corresponding to the one or more desired features identified by the user requirement; and communicating the identified mask page to the user.