Extensible Storage Abstraction for Declarative Model Packaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems lack an extensible intermediate file system representation to package declarative source code and its transformed artifacts together, leading to inefficiencies in data management and deployment.

Innovation Solution

A modern declarative model-driven development environment that transforms declarative models into various artifacts during their lifetime, using an extensible storage abstraction to preserve the declarative format of source code and metadata, packaged as image files conforming to ECMA Open Packaging Conventions, with tools for synchronization, deployment, and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional systems use traditional file storage for declarative source code and transformed artifacts, then storage simplicity is maintained, but data integrity, security, and manageability deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoidpackaging system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges declarative source code, transformed artifacts, and metadata into a single packaged file format. This integration ensures that all components are stored together with consistent integrity constraints, while the packaging system provides unified security and management mechanisms for the entire artifact set rather than handling individual files separately.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a packaging system as an intermediary layer between the declarative development environment and the file system. This intermediary structure organizes artifacts into a standardized format with embedded metadata, providing a controlled interface that enhances data integrity and security without requiring direct manipulation of individual source files.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If declarative source code is transformed through multiple tools into various artifacts, then functionality is enhanced, but tracking and managing transformed artifacts becomes difficult

Engineering Contradiction:
Improveartifact transformation capabilityVSAvoidtraceability of transformed artifacts
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms through metadata that tracks the transformation process. The packaging system records information about source code inputs, transformation tools applied, and resulting artifacts, creating a traceable chain that provides feedback on the transformation process. This enables verification and tracking of artifact origins without limiting transformation capabilities.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent creates a universal packaging format that can accommodate various transformed artifacts from different tools and languages within a single standardized structure. This multi-functional packaging system handles diverse artifact types (object code, libraries, configuration files) while maintaining consistent metadata tracking, enabling unified management of heterogeneous transformed outputs.

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

3Reliability

If declarative models are packaged with all transformed artifacts, then deployment completeness is improved, but file size and storage requirements increase

Engineering Contradiction:
Improvedeployment completenessVSAvoidpackaged file size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the packaged file into distinct components: declarative source code, transformed artifacts, and metadata. This segmentation allows for organized storage where each component serves a specific purpose. The structured segmentation enables efficient indexing and retrieval, reducing the overhead of managing large packaged files while ensuring all necessary deployment components are included.

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If metadata describing attributes of contents is defined and stored, then data management is enhanced, but processing overhead increases

Engineering Contradiction:
Improvedata management efficiencyVSAvoidmetadata processing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by generating and storing metadata during the packaging process itself, rather than creating metadata on-demand during operations. Transformation tools and the packaging system pre-compute attribute information about contained artifacts and store it in the metadata section. This preliminary preparation eliminates the need for time-consuming analysis during deployment or management operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10019243B2Packaging system to facilitate declarative model-driven development
Publication Date: 2018.07.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10019243B2 patent drawing
  • US10019243B2 patent drawing
  • US10019243B2 patent drawing

AI summary

The subject disclosure relates to a method and system for packaging a post-processed definition of a programming module. Contents of a constraint-based and/or order-independent execution model are received, in which the contents include a declarative source code. The contents are stored into an extensible storage abstraction such that the source code is stored in a declarative format. Metadata describing attributes of the contents stored in the extensible storage abstraction is also defined. A file is then created, which includes the extensible storage abstraction and the metadata.