Service-Oriented Architecture for Scalable Supplier Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise software systems, particularly those with supplier relationship management functionality, face challenges in scalability and cost-effectiveness due to their complex and distributed nature, requiring a robust architecture that allows for independent deployment of components across multiple hardware platforms.
Innovation Solution
A services architecture design that includes service operations, process components, and deployment units, enabling scalable and cost-effective implementation by defining service interfaces for interaction between process components across different deployment units, and utilizing business objects and process agents for efficient business processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If enterprise software systems are designed with distributed components across multiple hardware platforms, then adaptability and versatility are improved, but device complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the enterprise software system into independent process components, each capable of being deployed on separate hardware platforms. These components are organized into deployment units that can be independently distributed across multiple platforms, enabling adaptability while managing complexity through modular architecture.
Solution Approach 2:
The patent implements universality through standardized service interfaces that allow process components to interact across different hardware platforms using common protocols. The service-oriented architecture enables components to function universally across diverse platforms while maintaining platform-specific implementations where needed.
2Productivity
If process components are deployed independently on separate hardware platforms, then scalability is improved, but device complexity increases
Solution Approach 1:
The patent segments the system into independently deployable process components that can be scaled by deploying additional instances of components on separate hardware platforms. This segmentation enables linear scalability while the standardized interfaces prevent complexity from increasing proportionally with scale.
Solution Approach 2:
The patent introduces service interfaces as intermediaries between process components, providing standardized communication protocols that simplify interactions across distributed platforms. These interfaces act as mediators that handle complexity centrally while keeping individual component implementations simple and scalable.
3Ease of operation
If service interfaces define pairwise interaction between process components, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The patent uses service interfaces as intermediary layers that abstract the complexity of component interactions. These interfaces provide standardized, simplified interaction protocols between process components, making the system easier to operate while the interface definitions manage the underlying complexity through standardized contracts.
Solution Approach 2:
The patent applies parameter changes by transforming complex direct component interactions into standardized service interface calls with defined parameters. This transformation simplifies operation by providing clear interface contracts while managing complexity through parameterized communication protocols that can be consistently implemented across platforms.
Data Source
AI summary
Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.