UML Workflow Engine for Mobile App Development Complexity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing and maintaining software applications for mobile devices is challenging due to restricted resources and the need for expertise in programming languages like Java and C++ for native applications, as well as complex data management and maintenance operations.
Innovation Solution
A component-based application development environment that uses metadata descriptors in structured definition languages and scripted instructions to facilitate interaction with schema-defined services, including a workflow extractor and generator to associate processing components, enabling interaction with Web Services without requiring extensive programming knowledge.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If native applications are developed using programming languages like Java and C++, then application functionality and performance are improved, but development complexity and barrier to entry increase
Solution Approach 1:
The patent introduces a workflow engine as an intermediary layer between the UML model and the native application code. The workflow engine automatically generates platform-specific code from high-level workflow definitions, eliminating the need for developers to write complex Java or C++ code directly. This mediator translates business logic into executable applications while maintaining platform independence.
Solution Approach 2:
The patent replaces manual mechanical coding processes with automated code generation. Instead of developers manually writing and compiling native code, the system automatically generates application code from UML models through the workflow engine, substituting the mechanical coding task with an automated transformation process that produces platform-specific implementations.
2Reliability
If compiled native applications are used, then execution performance is improved, but maintenance operations and updates become difficult
Solution Approach 1:
The patent introduces dynamic reconfiguration capabilities where applications can be updated without complete recompilation. The workflow engine enables dynamic generation of platform-specific code from updated UML models, allowing maintenance operations to be performed by modifying high-level workflows rather than manipulating compiled binaries. This dynamic approach maintains execution performance while enabling easier updates and patches.
Solution Approach 2:
The patent segments the application into platform-independent workflow definitions and platform-specific generated code. This segmentation allows maintenance operations to be performed at the high-level workflow definition stage, while the generated code is automatically updated. The separation of concerns enables independent modification of business logic without affecting the execution performance of the generated native code.
3Use of energy by moving object
If platform-specific native applications are developed, then device resource utilization is optimized, but adaptability across different platforms decreases
Solution Approach 1:
The patent creates a universal workflow engine that serves multiple platforms simultaneously. The same UML model and workflow definition can be used to generate applications for different platforms (mobile, desktop, web) by configuring the workflow engine to produce platform-specific code. This multi-functional approach maintains platform adaptability while generating optimized native code for each target platform, resolving the contradiction between universality and platform-specific optimization.
Data Source
AI summary
An application development system for developing an application with application components is described. The system application development includes a modeling tool. The modeling tool imports the application components in a comparable component definition format, and defines a data relation between data, screens, and operations embodied in the application components in an application model. The application model has a static structural characteristic, a dynamic behavioral characteristic and an implementation characteristic. The static structural characteristic defines parts of the application. The dynamic behavioral characteristic defines responsiveness of the application to events or actions, and the implementation characteristic describes elements required for deploying the application. The modeling tool updates the cross-component mapping. The modeling tool further includes a mapping analyzer for analyzing message components and data components in the application components, and generating a cross-component mapping.