UNIFYING DOMAIN MODEL FOR INTERNET BUSINESS SYSTEMS

• US 20120271779A1
• Filed: 04/19/2011
• Published: 10/25/2012
• Est. Priority Date: 04/19/2011
• Status: Abandoned Application

• Current Assignee: Ascentium Inc.
• Original Assignee: Cactus Commerce, Inc.
• Inventors: Remillard, Donna J., Stevenson, Cameron P., Donovan, Ryan R.
• Application Number:
  US13/090,085
• Publication Number:
  US 20120271779A1
• Time in Patent Office: Days
• US Class Current: 705/348
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A unifying domain model for Internet business systems is described that includes an authoritative definition of logical objects that make up a modern Internet business system, a canonical list of attributes associated with such objects, a specification of how such objects may be composed and may relate to one another, and what operations or actions may be taken on or provided by them. A middleware framework is also described that brokers communication between end-user applications that are designed to consume the aforementioned objects and various integrated systems that are not so designed, such as LOB systems and partner systems, wherein brokering communication may include performing a translation between a representation of the data and operations utilized by an integrated system and the unifying domain model utilized by the end-user applications during runtime of the end-user applications.

Claims

1. An Internet business system, comprising:

a plurality of integrated systems, each of which represents and operates on data maintained thereby in a manner specified by a corresponding unique integrated system data model;

one or more end-user applications that represent and operate on data in a manner specified by a unifying domain data model;

a translation layer that processes data interaction requests received from the end-user application(s) during runtime thereof, wherein processing a data interaction request includes at least determining that data to be interacted with comprises data maintained by one of the integrated systems and translating between an integrated system data or service model representation of the data to be interacted with and a unifying domain data model representation of the data to be interacted with.

2. The Internet business system of claim 1, wherein the plurality of integrated systems includes at least one of:

a line of business (LOB) system;

a transactional e-commerce system;

a personalization and analytics system;

a social media system; and

a Web content management system.

3. The Internet business system of claim 1, wherein the one or more end-user applications includes at least one of:

a business management application; and

a consumer application.

4. The Internet business system of claim 1, wherein processing a data interaction request further includes translating between an integrated system data model operation and a unifying domain data model operation.

5. The Internet business system of claim 1, wherein each end-user application interacts with the translation layer using a common application programming interface.

6. The Internet business system of claim 1, wherein the unifying domain data model comprises a plurality of Internet business object definitions, each Internet business object definition specifying one or more required attributes associated with an Internet business object and optionally specifying one or more optional attributes associated with the Internet business object.

7. The Internet business system of claim 6, wherein each required attribute is designated as concrete and wherein each optional attribute may be designated as concrete or non-concrete, wherein a concrete attribute is an attribute having a defined semantic behavior.

8. The Internet business system of claim 6, wherein each Internet business object definition specifies one or more operations that support the use of a corresponding Internet business object in a user interface.

9. The Internet business system of claim 1, wherein the translation layer is configured to store data retrieved from the integrated systems in a runtime cache for servicing subsequent data interaction requests received from the end-user application(s).

10. The Internet business system of claim 1, wherein the translation layer records information concerning data interactions initiated by the end-user application(s), the system further comprising:

at least one of an analytics system and an auditing system that processes the recorded information.

11. A method of operating of an Internet business system, comprising:

receiving data interaction requests from one or more end-user applications during runtime thereof, wherein each of the end-user applications represents and operates on data in a manner specified by a unifying domain data model;

determining that data to be interacted with by a particular data interaction request comprises data maintained by one of a plurality of integrated systems, wherein each of the integrated systems represents and operates on data maintained thereby in a manner specified by a corresponding unique integrated system data or service model; and

responsive to the determining step, processing the particular data interaction request by at least translating between an integrated system data or service model representation of the data to be interacted with and a unifying domain data model representation of the data to be interacted with.

12. The method of claim 11, wherein determining that the data to be interacted with by the particular data interaction request comprises data maintained by one of the plurality of integrated systems comprises determining that the data to be interacted with by the particular data interaction request comprises data maintained by one of:

a line of business (LOB) system;

a transactional e-commerce system;

a personalization and analytics system;

a social media system; and

a Web content management system.

13. The method of claim 11, wherein receiving the data interaction requests from the one or more end-user applications comprises receiving data interaction requests from one or more of:

a business management application; and

a consumer application.

14. The method of claim 11, wherein processing the particular data interaction request further comprises:

translating between an integrated system data model operation and a unifying domain data model operation.

15. The method of claim 11, wherein receiving the data interaction requests from the one or more end-user applications during runtime thereof comprises receiving the data interaction requests via a common application programming interface.

16. The method of claim 11, wherein the unifying domain data model comprises a plurality of Internet business object definitions, each Internet business object definition specifying one or more required attributes associated with an Internet business object and optionally specifying one or more optional attributes associated with the Internet business object.

17. The method of claim 16, wherein each required attribute is designated as concrete and wherein each optional attribute may be designated as concrete or non-concrete, wherein a concrete attribute is an attribute having a defined semantic behavior.

18. The method of claim 16, wherein each Internet business object definition specifies one or more operations that support the use of a corresponding Internet business object in a user interface.

19. The method of claim 11, further comprising:

storing data retrieved from the integrated systems in a runtime cache for servicing data interaction requests subsequently received from the end-user application(s).

20. The method of claim 11, further comprising:

recording information relating to data interactions initiated by the end-user application(s); and

providing the recorded information to at least one of an analytics system and an auditing system.

21. A computer program product comprising a computer-readable storage medium having computer program logic recorded thereon, the computer program logic comprising:

first means for enabling a processing unit to receive data interaction requests from one or more end-user applications during runtime thereof, wherein each of the end-user applications represent and operate on data in a manner specified by a unifying domain data model;

second means for enabling the processing unit to determine that data to be interacted with by a particular data interaction request comprises data maintained by one of a plurality of integrated systems, wherein each of the integrated systems represents and operates on data maintained thereby in a manner specified by a corresponding unique integrated system data model; and

third means for enabling the processing unit to process the particular data interaction request responsive to the determination by at least translating between an integrated system data model representation of the data to be interacted with and a unifying domain data model representation of the data to be interacted with.

22. An Internet business system, comprising:

one or more clients configured to generate data interaction requests; and

a software architecture configured to receive the data interaction requests over the Internet and to process the received data interaction requests by performing one or more of a predefined set of operations specified by an Internet business domain model upon one or more Internet business objects defined in accordance with the Internet business domain model, wherein each Internet business object specifies one or more required attributes and optionally specifies one or more optional attributes, and wherein each required attribute is designated as concrete and each optional attribute may be designated as concrete or non-concrete, wherein a concrete attribute is an attribute having a defined semantic behavior.