Expense Reimbursement Software Architecture Service Interfaces

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large and complex enterprise software systems require a scalable and cost-effective architecture for expense reimbursement processes, with existing solutions often failing to efficiently manage interactions between distributed components across different hardware platforms.

Innovation Solution

A software architecture design for an expense reimbursement system structured as multiple process components interacting through service operations, including Expense and Reimbursement Management, Due Item Processing, Payment Processing, Payroll Processing, and Accounting components, allowing for deployment on separate hardware platforms and scalable interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enterprise software systems are structured as distributed components across multiple hardware platforms, then the system can achieve better scalability and platform independence, but the complexity of managing interactions between components increases

Engineering Contradiction:
Improveplatform independenceVSAvoidinteraction management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces service interfaces as intermediary components that mediate interactions between distributed process components. These service interfaces provide standardized communication protocols and data exchange formats, enabling components across different hardware platforms to interact without direct point-to-point connections, thus reducing interaction management complexity while maintaining platform independence

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If the software architecture uses multiple process components for different expense reimbursement functions, then the system achieves better modularity and reusability, but the number of service operations and interfaces increases

Engineering Contradiction:
Improvesoftware reusabilityVSAvoidnumber of service operations
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent designs service interfaces with universal data structures and communication protocols that can be reused across multiple process components. The standardized service operation framework allows the same interface patterns to be applied to Expense Management, Payment Processing, Payroll Processing, and Accounting components, reducing the effective complexity despite the presence of multiple components

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If deployment units are separated onto different hardware platforms, then the system achieves better scalability and independent deployment, but the reliability of interactions between distributed components becomes more challenging to ensure

Engineering Contradiction:
Improvedeployment scalabilityVSAvoidinteraction reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements error handling, transaction management, and data validation mechanisms within the service interface layer that prepare for and cushion against potential failures in distributed interactions. These pre-established reliability mechanisms ensure that interactions between deployment units on different hardware platforms maintain consistency and reliability despite the distributed nature of the system

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS8401936B2Architectural design for expense reimbursement application software
Publication Date: 2013.03.19 SAP SE
  • US8401936B2 patent drawing
  • US8401936B2 patent drawing
  • US8401936B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing expense reimbursement. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include an Expense and Reimbursement Management process component, a Due Item Processing process component, a Payment Processing process component, a Payroll Processing process component, and an Accounting process component.