IT Service Architecture Separating Operation and Structural Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Service-Oriented Architecture (SOA) environments face challenges in separating concerns between operational message modeling and structural data modeling, making it difficult to translate user-defined service descriptions and manage IT services independently of service modeling languages.
Innovation Solution
An architecture that separates IT services into an operation model and a structural model, linked by a service model, allowing for language-independent communication and configuration, enabling the operation model to be extended and the structural model to be made opaque, supporting multiple structural modeling languages and simplifying service operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If IT services use a unified model for both operational message modeling and structural data modeling, then it simplifies the architecture, but it makes it difficult to separate concerns and manage services independently of modeling languages
Solution Approach 1:
The patent divides the unified service model into two distinct models: an operational model for message exchange and a structural model for data representation. This segmentation allows independent configuration and management of each model, enabling services to be managed without being tied to specific modeling languages while maintaining architectural clarity through separate concern management.
2Adaptability or versatility
If the architecture tightly couples operational model and structural model, then it simplifies configuration, but it prevents independent extension and makes services dependent on service modeling languages
Solution Approach 1:
The patent introduces a service model as an intermediary layer that connects the operational model and structural model. This mediator enables independent configuration and extension of both models without direct coupling, allowing services to be extended adaptively while the service model manages the relationships between operational and structural aspects.
3Adaptability or versatility
If the structural model is transparent to the operational model, then it enables direct access and simplifies debugging, but it exposes implementation details and reduces flexibility in service operations
Solution Approach 1:
The service model acts as an intermediary that controls the relationship between the operational and structural models, making the structural model opaque to the operational model. This preserves service operation flexibility by preventing direct access to structural details while maintaining necessary functionality through the mediating service model layer.
4Adaptability or versatility
If multiple structural modeling languages are supported, then it increases language independence and versatility, but it complicates the architecture and service management
Solution Approach 1:
The patent designs the service model with universal, language-independent interfaces that can work with multiple structural modeling languages. This multi-functionality allows the architecture to support various languages without increasing complexity, as the service model provides a unified way to manage structural representations regardless of the specific language used.
Data Source
AI summary
Methods, systems, and computer program products are provided for exchanging information between information technology (IT) services. An architecture provides separation of concern between the models by separating the models for IT services into an operation model and a structural model that are linked by a service model. The service model can be configurable to extend the operation model. Configuration of the operation model includes defining messages exchanged between the IT services. Configuration of the structural model includes capturing a structure of the IT services. The service model has an association with the structural model, the association making the structural model opaque to the operation model.