Codeless SCM Application Framework With Layered Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise applications face challenges in customization due to reliance on relational databases, leading to inefficiencies and complexity, especially in managing diverse operational requirements and data abstractions, which are not adequately addressed by current codeless development architectures.
Innovation Solution
A layered platform architecture with configurable components that include a data layer, foundation layer, shared framework layer, application layer, and customization layer, utilizing machine learning and AI-based process orchestrator to enable codeless development of SCM applications, allowing for secure and efficient execution of complex operations without affecting neighboring functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a relational database (RDBMS) is used to build enterprise applications with stored procedures and database triggers, then transactional support is provided, but the system becomes a big monolith at the storage level with inherent technical issues resulting in inefficient functioning of complex application functions
Solution Approach 1:
The patent segments the monolithic RDBMS architecture into separate microservices that can be independently deployed and managed. Each microservice handles specific business functions, eliminating the need for complex stored procedures and triggers while maintaining transactional integrity through distributed transaction protocols.
Solution Approach 2:
The patent extracts the storage and computation functions from the RDBMS, separating data persistence from business logic execution. This allows the use of lightweight key-value stores or document databases while running application logic in containerized microservices, thereby reducing architectural complexity and improving scalability.
2Adaptability or versatility
If a developer modifies the underlying code of the enterprise application to accommodate operational requirements, then new features or operations can be introduced, but other functions of the enterprise application may be broken and the change consumes a lot of time requiring halting of multiple processes
Solution Approach 1:
The patent implements dynamic configuration capabilities that allow operational requirements to be adjusted without modifying underlying code. Configuration parameters, business rules, and process flows can be changed at runtime through configuration files or administrative interfaces, enabling customization while maintaining system stability and avoiding downtime.
Solution Approach 2:
The patent uses configuration templates and blueprints that can be copied and modified to create new features. Instead of writing custom code for each new operation, developers can replicate existing functional patterns through configuration, reducing the risk of introducing bugs and minimizing impact on existing functions.
3Adaptability or versatility
If the basic structure of the enterprise application is changed to meet operational requirements, then the application can be customized, but it requires a skilled developer to make changes to complex enterprise application scenarios at system backend which is extremely tedious
Solution Approach 1:
The patent introduces configuration interfaces and abstraction layers that mediate between user requirements and system implementation. These intermediaries provide high-level configuration options that hide complex backend scenarios from developers, allowing customization through simplified parameter settings rather than direct code modification.
Solution Approach 2:
The patent implements universal configuration mechanisms that can handle multiple types of customizations through a common interface. A single configuration framework supports various operational requirements across different modules, reducing the need for specialized development knowledge and making the system easier to adapt to new scenarios.
4Productivity
If codeless development is used to overcome customization problems, then development time is reduced, but the architecture remains unsupportive in working with different data abstractions and integrating multiple functions while dealing with distinct data abstractions is cumbersome
Solution Approach 1:
The patent adds an abstraction dimension by introducing multiple layers of data access interfaces. The codeless development platform operates at the application logic layer while underlying data access can utilize different data abstractions (relational, document, key-value) through adapter patterns. This allows codeless development to maintain high productivity while the system architecture supports diverse data abstractions through standardized interface layers.
Data Source
AI summary
The present invention provides a platform architecture, a development application framework and a method for codeless development of one or more Supply chain management (SCM) enterprise application. The invention includes a layered platform architecture for supporting and executing development of SCM applications. The platform and method provide interaction of an SCM application user, a citizen developer user and a platform developer user with one or more layers of the platform architecture for codeless development of the SCM applications.