WRICEF Object Generation via Pre-Defined Rule Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for generating enterprise software objects, such as workflow, report, interface, conversion, enhancement, and forms (WRICEF) objects, are time-consuming, manpower-intensive, and result in objects that cannot be shared or continuously tested, leading to wastage of human and computing resources.
Innovation Solution
A generation system that receives user request data and pre-defined technical object content data to map and generate enterprise objects based on predefined interface format and business rules, allowing for quick and automatic creation of WRICEF objects, conserving resources and enabling sharing and scaling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual methods are used to generate enterprise software objects, then customization and flexibility are improved, but time consumption and manpower requirements increase significantly
Solution Approach 1:
The system performs preliminary actions by pre-defining technical object content, interface formats, and business rules in a library before actual enterprise object generation. This allows rapid assembly and customization of enterprise objects without manual creation from scratch, resolving the contradiction between flexibility and time consumption.
Solution Approach 2:
The system uses copying by retrieving pre-defined technical objects, interface formats, and business rules from a library and assembling them to generate enterprise objects. This eliminates redundant manual work while maintaining customization capability through selective combination and modification of copied elements.
2Adaptability or versatility
If manual generation methods are used, then object uniqueness is improved, but resource wastage and inability to share objects increases
Solution Approach 1:
The system applies universality by creating a shared library of technical objects, interface formats, and business rules that can be reused across multiple enterprise object generations. This eliminates resource wastage from redundant manual creation while maintaining object uniqueness through contextual adaptation and combination of universal building blocks.
Solution Approach 2:
The system enables object sharing through copying by storing generated enterprise objects and their constituent technical objects in a library. These can be copied and reused in future generations, preventing resource wastage while maintaining the ability to create unique objects through selective copying and modification.
3Productivity
If automated generation is implemented, then productivity and resource conservation are improved, but adaptability and sharing capability must be maintained
Solution Approach 1:
The system performs preliminary action by pre-structuring technical objects, interface formats, and business rules in a standardized library format. This enables automated retrieval and assembly processes that maintain high productivity while ensuring generated objects are inherently shareable through their standardized, modular structure.
Solution Approach 2:
The system achieves both productivity and sharing capability through universality by designing the library and generation system to handle multiple object types and purposes. The same infrastructure supports rapid automated generation while simultaneously enabling broad sharing and reuse across different contexts and users.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
In some implementations, a device may receive user request data from a user device associated with a user. The device may retrieve pre-defined technical object content data from an enterprise system. The device may retrieve pre-defined interface format data and a pre-defined business rule from a first data structure and a second data structure, respectively, based on the user request data. The device may determine whether a mapping, for generating an enterprise system object, is stored in a third data structure. The device may map the technical object content data to the pre-defined interface format data, based on the mapping and the pre-defined business rule, to generate mapped data when the mapping is stored in a third data structure. The device may generate the enterprise system object based on the mapped data. The device may perform one or more actions based on the enterprise system object.