Service Meta Model for Enterprise Architecture Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software development processes lack efficient methods for modeling and reusing software modules across applications, making it difficult for non-technical users to combine service-providing components into full applications and business processes.
Innovation Solution
A service meta model that includes an object node class, association class, and object class, with a core service interface class and service interface class, allowing for the creation of reusable interface patterns for business object operations, enabling non-programmers to construct service-based application architectures and automate tasks typically performed by programmers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional software development processes are used, then software modules can be developed, but it is difficult for non-technical users to combine service-providing components into full applications and business processes
Solution Approach 1:
The patent introduces a service meta model as an intermediary layer between non-technical users and complex service architectures. This meta model provides simplified abstractions including service interface patterns, object node classes, and association classes that enable users to compose services without needing to understand the underlying complexity. The meta model acts as a mediator that translates high-level business process requirements into service composition specifications.
Solution Approach 2:
The patent segments the service architecture into distinct conceptual components: service interface patterns, object node classes, association classes, and core service interfaces. This segmentation allows non-technical users to work with individual, well-defined building blocks rather than the entire complex system at once. Each segment has a specific purpose and can be independently understood and combined.
2Adaptability or versatility
If service-based application architecture is implemented, then software modules can be reused across applications, but the modeling process becomes more complex
Solution Approach 1:
The patent creates universal, multi-functional abstractions in the service meta model that can be applied across different applications. Service interface patterns and object node classes serve as universal templates that can be instantiated in multiple contexts. The association classes provide universal relationship definitions that work across different service compositions, enabling reuse without requiring application-specific modeling for each use case.
Solution Approach 2:
The patent enables parameterization of service interfaces and object nodes, allowing the same meta model structures to be instantiated with different parameters for different applications. Service interface patterns can be parameterized to create specific service implementations, and object node classes can be parameterized to represent different business objects. This parameterization maintains reusability while adapting to specific application requirements.
3Extent of automation
If detailed service descriptions with interface patterns are provided, then tools can automatically perform tasks, but the amount of information to be managed increases
Solution Approach 1:
The patent performs preliminary action by pre-defining service interface patterns, object node classes, and association classes in the meta model before actual service implementation. These pre-defined structures include templates for service interfaces, core service interfaces with standard operations, and association relationships. This preliminary modeling enables automated tools to generate code by simply instantiating these pre-defined patterns rather than requiring detailed manual specification of every interaction.
Data Source
AI summary
Methods and apparatus, including computer program products, for defining and using a service meta model operate on a meta model that includes an object node class, an association class, and an object class. The object node class includes a key identifier and represents data types. The association class is associated with the object node class and represents an association between instances of the object node class. The object class is associated with an object composition. The object composition is defined by a data structure of instances of the object node class and associations between the instances of the object node class represented by the association class.