Business Software Kiosk for Low-Code Process Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional business software platforms face issues such as complex and confusing user interfaces, platform dependence, lack of mobile functionality, miscommunication between process managers and developers, difficulty in customizing and maintaining systems, and inadequate reporting and auditing capabilities, leading to inefficiencies and high costs.
Innovation Solution
A cloud-based business software system that allows for customizable data collection graphical user interfaces (GUIs) with metadata tags, a business assembly language (BA) for easy customization and documentation, and a kiosk user interface (KUI) for streamlined process execution, enabling users to define and enforce processes and controls without extensive programming knowledge.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional business software is made more customizable, then it can better meet diverse business needs, but the complexity of the system increases and maintenance becomes more difficult
Solution Approach 1:
The system segments customization into discrete metadata tags and configurable parameters that can be independently modified. The low-code platform divides complex software functionality into modular components that business users can adjust without affecting the entire system architecture.
Solution Approach 2:
The patent introduces an intermediary layer between business users and core system code through metadata tags and a low-code framework. This intermediary allows users to customize functionality by configuring metadata rather than modifying code, reducing system complexity while maintaining adaptability.
2Ease of operation
If the user interface is simplified to improve ease of use, then usability increases, but the system's functionality and power may be reduced
Solution Approach 1:
The user interface dynamically adapts its complexity based on user role and context. Business users see simplified configurations through metadata tags, while system administrators access full functionality through the low-code platform. The interface transitions between simple and powerful modes as needed.
Solution Approach 2:
The system creates simplified visual representations of complex functionality through metadata tags and graphical interfaces. These copies allow users to interact with and customize system behavior without seeing or needing to understand the underlying code complexity.
3Adaptability or versatility
If developers introduce new functionality to meet technical needs, then system capability improves, but miscommunication with process managers increases and requirements change
Solution Approach 1:
The system allows different parts of the organization to define and customize functionality locally through metadata tags. Each business process can be configured independently with specific tags that reflect local needs, reducing the need for broad system changes and improving communication alignment.
Solution Approach 2:
The low-code platform provides continuous feedback loops where process managers can review and validate functionality before deployment. Configuration changes are visible and testable, allowing real-time alignment between technical development and business process needs.
4Reliability
If existing software platforms are made more expensive to provide better functionality, then quality improves, but businesses must choose between needed features and budget constraints
Solution Approach 1:
The platform changes the parameter of value delivery by allowing businesses to pay only for the functionality they configure and use. Through metadata tags and selective module deployment, organizations can scale functionality up or down based on actual needs and budget constraints.
Data Source
AI summary
A system includes a controller, a database controlled by the controller, and a memory including an end-user executable code and a business software management code. The controller receives a user update to modify the end-user executable code, converts the user update to a machine language input, and, in response to the machine language input, modifies one or more of the end-user executable code, the database structure, and a documentation of the end-user executable code. In response to executing the program instructions associated with the modified end-user executable code on the end-user device, the controller generates a data collection GUI according to the modified end-user executable code and stores data in the database structure according to the modified end-user executable code.