Context-Based Interaction Deliverables via Intermediary Construction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software architectural styles such as Object Oriented Development, Service Oriented Architecture, and Representational State Transfer face limitations in customization due to tight-coupling within and between objects/services, and the inability to utilize server-side context for dynamic interaction customization.
Innovation Solution
A software application that includes work order resources and a construction service resource, which processes interaction requests to dynamically construct custom deliverables by obtaining context information, enabling dynamic context-based construction of interaction deliverables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Object Oriented Development style is used with encapsulated objects and custom interfaces, then rich software applications are supported, but tight-coupling within and between objects limits the practical range of result customization
Solution Approach 1:
The patent introduces an intermediary component that sits between the client and the software application, acting as a mediator to dynamically construct interaction deliverables. This intermediary uses context information to customize responses without requiring changes to the core application architecture, thereby resolving the contradiction between customization adaptability and system coupling complexity.
2Adaptability or versatility
If Service Oriented Architecture is used with loosely-coupled services and meta application layer, then rich software applications are supported, but the black-box nature of services intrinsically limits the practical range of result customization
Solution Approach 1:
The patent performs preliminary actions by collecting and storing context information about user interactions, preferences, and system state before generating interaction deliverables. This pre-gathering of contextual data enables subsequent customization of service responses without requiring changes to the black-box service architecture, thus resolving the contradiction between service encapsulation and customization capability.
3Adaptability or versatility
If Representational State Transfer style is used with standalone resources and standard interface, then rich software applications are supported, but the absence of pre-determined functions and inability to use server-side context results in client driven application that intrinsically limits the practical range of result customization
Solution Approach 1:
The patent introduces an intermediary that acts as a mediator between the RESTful resources and the client, enabling server-side context-based customization of interaction deliverables. This intermediary dynamically constructs responses based on context information while maintaining the loose coupling and standard interfaces of REST architecture, thereby resolving the contradiction between REST principles and customization capability without shifting complexity to the client.
Data Source
AI summary
A software application includes work order resources, each of which defines an atomic operation for the software application, and a construction service resource, which processes the work order resources in response to all interaction requests for the software application. Each interaction request is received from a client and identifies a corresponding work order, which the construction service processes to dynamically construct a set of deliverables, which can include a custom representation of the work order. While processing the interaction request, the construction service, as directed by the work order, can make one or more requests to context resources for context information corresponding to an activity for which the interaction was requested to construct the set of deliverables. The work order resource can comprise a reflective program that enables the construction service to dynamically determine and construct the set of deliverables, including the next appropriate interaction(s) using the context information, thereby directing a set of atomic operations as part of an activity being performed and enabling the dynamic context-based construction of interaction deliverables.