Software Architecture for Product Catalog Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large and complex enterprise software systems require a scalable and cost-effective architecture for product catalog management, particularly in handling agreements between purchasers and suppliers, creating and publishing product catalogs, and interacting with external systems, while existing solutions often lack efficient reuse and deployment flexibility.

Innovation Solution

A software architecture design comprising multiple process components interacting through service interfaces, including Purchasing Contract Processing, Product Catalogue Authoring, and Product Catalogue Publishing components, allowing for scalable deployment across different hardware platforms and interaction with external systems, leveraging service operations and deployment units for efficient reuse and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a large and complex enterprise software system is implemented, then comprehensive product catalog management functionality is achieved, but system complexity and deployment difficulty increase

Engineering Contradiction:
Improveproduct catalog management functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The software system is divided into separate deployment units (authoring unit, publishing unit, contract processing unit) that can be independently deployed and managed. Each unit handles specific functionality, reducing overall system complexity while maintaining comprehensive product catalog management capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The architecture uses service interfaces and operations that enable deployment units to interact through standardized mechanisms. This universal interface approach allows the same architectural pattern to serve multiple functions across different deployment units, reducing complexity through consistency.

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

2Adaptability or versatility

If software components are distributed across multiple hardware platforms, then deployment flexibility is improved, but integration complexity increases

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Service interfaces act as intermediaries between distributed deployment units, providing standardized communication mechanisms that simplify integration across multiple hardware platforms. The service interface layer abstracts the complexity of inter-platform communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If process components are reused across deployment units, then development cost is reduced, but component interaction complexity increases

Engineering Contradiction:
Improvedevelopment costVSAvoidcomponent interaction complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

Process components are designed with universal service interfaces that enable them to be reused across different deployment units. The standardized interface pattern reduces development cost through reuse while the consistent interaction model manages complexity.

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

4Productivity

If service interfaces are used for component interaction, then system scalability is improved, but interface management complexity increases

Engineering Contradiction:
Improvesystem scalabilityVSAvoidinterface management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Service interfaces are designed as universal communication mechanisms that support multiple deployment units and scenarios. This universality enables scalability while the standardized patterns reduce interface management complexity through consistency.

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

Data Source

PatentUS8326703B2Architectural design for product catalog management application software
Publication Date: 2012.12.04 SAP SE
  • US8326703B2 patent drawing
  • US8326703B2 patent drawing
  • US8326703B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing catalog management useful to create or update published catalogs based on product master data changes or external supplier catalogs. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include a Purchasing Contract Processing process component that handles agreements between a purchaser and a supplier; a Product Catalogue Authoring process component that creates and edits product catalogs by collecting product information from relevant sources, controls the quality of the product catalogs' contents, and controls when and to what extent Product Catalogues can be published; and a Product Catalogue Publishing process component that makes published product catalogs available to a large number of users electronically for use in other business processes.