Enterprise Meta Model for Service Architecture Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business software applications face challenges in separating front-end and back-end components effectively, leading to inconsistencies and difficulties in data management and scalability, especially in large-scale systems.
Innovation Solution
A meta model for an enterprise service architecture is introduced, which includes classes for data organization, field identification, action identification, and service provider identification, enabling a separation between the front-end and back-end components and providing a platform-independent, scalable solution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If front-end and back-end components are tightly integrated in traditional business software applications, then data management and business logic processing can be performed within a single system, but the system becomes difficult to scale, maintain, and adapt to different platforms
Solution Approach 1:
The patent segments the business software application into distinct front-end and back-end components with clearly defined interfaces. The back-end is further divided into data storage layer and business logic layer, allowing independent development, deployment, and scaling of each component across different platforms without increasing overall system complexity
Solution Approach 2:
The patent introduces service interfaces and data models as intermediary layers between the front-end and back-end components. These intermediaries enable platform-independent communication and data exchange, allowing the system to adapt to different platforms while maintaining a consistent architecture
2Productivity
If a meta model with multiple classes for data organization, field identification, action identification, and service provider identification is implemented, then platform independence and scalability are achieved, but the initial system design and implementation become more complex
Solution Approach 1:
The patent creates a universal meta model where classes such as Aspect, Structure, Aspect Action, and Relation serve multiple functions. For example, the Aspect class not only represents data types but also serves as a container for structures, actions, and relations, reducing the need for separate specialized classes and simplifying the overall model while maintaining scalability
Solution Approach 2:
The patent implements a nested structure where structures are contained within aspects, actions are contained within aspects, and relations connect aspects. This nesting allows the meta model to represent complex business logic and data relationships in a hierarchical manner that is both scalable and manageable, avoiding the need for a flat, overly complex structure
Data Source
AI summary
Methods and apparatus, including computer program products, for using a meta model for an enterprise service architecture. The meta model includes a first class to represent data organization in a back end data store. The first class includes a data type identifier attribute to permit meta data to identify a data type. The meta model also includes a second class associated with the first class. The second class includes a field identifier attribute to permit meta data to identify fields for a particular data type. The meta model also includes a third class associated with the first class. The third class includes an action identifier attribute to permit meta data to identify an action. In some examples, there is a service provider identifier to permit meta data to identify a service provider class that can effect the action.