Enterprise Accounting Services Architecture via Segmented Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large and complex enterprise software systems require a scalable and cost-effective architecture for providing enterprise-level accounting functionality, with existing solutions struggling to efficiently manage distributed components and ensure reliable, pair-wise interaction between process components across different deployment units.
Innovation Solution
A services architecture design that includes service operations, process components, deployment units, and suitable business objects, allowing for scalable and cost-effective implementation by defining service interfaces for pair-wise interaction between process components across different deployment units, enabling business processes and business-to-business communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If enterprise software systems are designed as large and complex integrated systems, then accounting functionality can be provided at the enterprise level, but the architecture becomes difficult to manage and scale across distributed hardware platforms
Solution Approach 1:
The patent divides the enterprise software system into separate deployment units, each containing process components that can be independently deployed on different hardware platforms. This segmentation reduces overall architecture complexity while maintaining enterprise-level functionality through standardized interfaces between units.
Solution Approach 2:
The patent creates a universal architecture where process components can be deployed on any hardware platform through standardized service interfaces. This multi-functionality allows the same accounting functionality to operate across diverse hardware environments without requiring platform-specific implementations.
2Adaptability or versatility
If process components are distributed across multiple deployment units on different hardware platforms, then system scalability is improved, but ensuring reliable pair-wise interaction between components becomes more difficult
Solution Approach 1:
The patent introduces service interfaces as intermediaries between process components in different deployment units. These standardized interfaces act as mediators that ensure reliable pair-wise interactions by defining clear contracts for communication, eliminating the need for direct point-to-point connections between distributed components.
3Ease of manufacture
If a services architecture design with process components and deployment units is implemented, then cost-effective and scalable deployment is achieved, but the system requires careful management of service interfaces and component interactions
Solution Approach 1:
The patent standardizes service interfaces with well-defined parameters and data formats, allowing process components to interact reliably across deployment units. This parameter standardization simplifies interface management by establishing consistent communication protocols that reduce the complexity of managing distributed component interactions.
Data Source
AI summary
Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having accounting 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.