Behavior Tags in Source Code for Middleware Technology Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software developers face challenges in selecting the appropriate implementation technology for middleware applications due to similar features across technologies, requiring a method to automatically choose the implementation technology based on desired functionality, and ensuring source code independence across various technologies.
Innovation Solution
A method involving a Configuration Program and a Deployment Program that embeds behavior tags in source code, allowing users to define preferences for implementation technologies, enabling the Deployment Program to automatically select the appropriate technology for execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a developer specifies the desired functionality in a manner specific to the implementation technology, then the application can be executed using that specific implementation technology, but the source code cannot be seamlessly executed by a plurality of different implementation technologies
Solution Approach 1:
The patent creates a universal specification mechanism using behavior tags that can describe functionality independently of any specific implementation technology. The deployment program interprets these tags and maps them to appropriate implementation technologies, allowing the same source code to be executed across multiple platforms without modification.
Solution Approach 2:
The patent introduces a deployment program as an intermediary between the source code and implementation technologies. This mediator reads behavior tags in the source code, determines the appropriate implementation technology based on the tags and a preference list, and facilitates execution without requiring the developer to specify technology-specific details.
2Ease of operation
If a developer is familiar with the various features offered by each implementation technology to make an informed decision, then the appropriate implementation technology can be selected, but the developer must understand how to implement the features in the selected implementation technology
Solution Approach 1:
The patent enables the source code to describe its own requirements through behavior tags embedded within the code itself. The deployment program automatically reads these tags and selects the appropriate implementation technology without requiring the developer to have expert knowledge of multiple technologies' features.
Solution Approach 2:
The deployment program acts as an intermediary that translates behavior tags into implementation technology selections. This eliminates the need for developers to deeply understand implementation technology features, as the mediator handles the mapping automatically based on the tags and configured preferences.
3Adaptability or versatility
If the source code is tailored to a particular implementation technology, then the application can be executed efficiently using that technology, but the developer is locked into that implementation technology
Solution Approach 1:
The patent creates source code that is universally compatible with multiple implementation technologies through the use of behavior tags. The code maintains its efficiency by providing precise behavioral specifications that the deployment program can map to the most appropriate implementation technology for each scenario.
Data Source
AI summary
A method for embedding behavior tags in a source code so that a computer can choose the appropriate implementation technology to execute the source code comprising a Configuration Program (CP) and a Deployment Program (DP). The CP allows a user to define and modify a plurality of behavior tags in the behavior tag definitions. The CP also allows the user to define and modify the preferences as to the implementation technologies in an implementation technology preference list. The user then creates the source code with embedded behavior tags. The DP reads the source code and automatically selects the appropriate implementation technology based on the behavior tags. The DP gives preference to implementation technologies according to the implementation technology preference list. The result is that the user does not have to specify the implementation technology for the source code or configure the behavior tags to a specific implementation technology.