Runtime Connector for Abstract Business Object Classes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software applications face challenges in accessing different components for person management without requiring extensive interface adaptations and the need for multiple interfaces for each component, limiting flexibility and increasing maintenance costs.
Innovation Solution
A method that uses a connector with an identifier for an abstract business object class to determine and connect to concrete business object classes at runtime, reducing the need for multiple interfaces and allowing access to a hierarchy of business objects through a single interface, enabling flexible access to various software components and applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a monolithic software system is used where functional elements are combined in a single software application, then the system structure is simple and easy to implement, but the maintainability and flexibility of the software components deteriorate
Solution Approach 1:
The patent divides the monolithic software system into separate software components (e.g., activity recording component and person management component). Each component can be independently developed, maintained, and replaced. The connector mechanism enables these segmented components to communicate through standardized interfaces, resolving the contradiction by providing both structural simplicity (through standardized connections) and operational flexibility (through independent component replacement).
Solution Approach 2:
The connector is designed as a universal interface mechanism that can connect the software application to multiple different person management components through a single standardized interface. This allows the same connector to work with various concrete business object classes (e.g., Person, Employee, Customer) without requiring separate interface implementations, thus providing both ease of implementation and adaptability.
2Adaptability or versatility
If separate software components are used with client-server architecture, then the maintainability and flexibility of software components improve, but the complexity of interface adaptation increases
Solution Approach 1:
The connector serves as a universal interface that can connect to multiple different person management components through a single standardized interface. The connector contains an identifier for an abstract business object class and can determine concrete business object classes at runtime, eliminating the need for separate interface implementations for each component type and reducing interface complexity while maintaining flexibility.
Solution Approach 2:
The connector acts as an intermediary between the software application and various person management components. It handles the complexity of interface adaptation internally by determining the appropriate concrete business object class based on the abstract class identifier and establishing connections accordingly, thus shielding the main software application from interface complexity while maintaining flexible component replacement capability.
3Adaptability or versatility
If individual interfaces are implemented for each person management component, then the access to different components is enabled, but the number of interfaces increases and maintenance costs increase
Solution Approach 1:
The connector is designed as a single universal interface that can access multiple different person management components through one standardized interface rather than requiring separate interfaces for each component. The connector determines the appropriate concrete business object class at runtime based on the abstract class identifier and establishes connections dynamically, enabling access to various components (Person, Employee, Customer, etc.) without increasing the number of interfaces, thus reducing maintenance costs while preserving access capability.
Data Source
AI summary
A computer-implemented method and a correspondingly adapted computer program product or software application for connecting business objects in a software application (SA), wherein the software application comprises a connector (K), wherein the connector comprises a code identifying an abstract business object class (ABO1 to ABOn), the software application identifies the abstract business object class specified in the connector at runtime in a hierarchy of abstract business object classes, and the software application, at runtime, proceeding from the identified abstract business object class, identifies at least one concrete business object class (KBO1 to KBOn), directly or indirectly derived therefrom, and establishes a connection (V) in at least one instance (I1 to In) of the at least one identified concrete business object class, via which connection the software application accesses attributes and methods of the instance of the concrete business object class.