System and method for interpreting a specification language file to implement a business system

• US 8,578,350 B2
• Filed: 11/30/2006
• Issued: 11/05/2013
• Est. Priority Date: 11/30/2006
• Status: Active Grant

• Current Assignee: NCR Voyix Corporation
• Original Assignee: NCR Corporation
• Inventors: Miller, David D.
• Primary Examiner(s): Vu, Tuan A
• Application Number:
  US11/606,683
• Publication Number:
  US 20080134155A1
• Time in Patent Office: 2,532 Days
• Field of Search: 717105-106, 717/108, 717/114, 717/120, 717/124, 717139-143, 709/203, 709/204, 709217-227, 709/250, 709/201, 716/103, 715/205, 715/239, 715/709, 715/202, 715/234, 715/513, 718/102, 235/375, 235/432, 705/3, 705/7.27, 705/1.1, 705/16, 705/43, 719/328, 707/103.Y
• US Class Current: 717/139
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 9/4498 Finite state machines

Abstract

A system controls operation of a business system having a processor, memory, and a hard drive. The system comprises a specification language file stored on a hard drive, the file containing specification language statements defining a state machine implementation of a business system, a parser for extracting specification language statements from the specification language file and interpreting the extracted specification language statements, a business logic application program comprised of business logic modules, the business logic modules including executable compiled program statements, and the parser calls at least one of the business logic modules to process a message extracted by the parser from the specification language file.

Claims

1. A checkout business system controlling the operation of a checkout station that implements a plurality of the state machines each implementing a different method of operating the checkout business system, the system comprising:

a memory including computer instructions;

a processor coupled to the memory and adapted to execute the computer instructions;

a plurality of specification language files stored in a permanent memory on the checkout station, each specification language file containing a plurality of specification language statements defining a state machine implementation of a different checkout business system where each state machine defines all the operations of the checkout station and where the checkout station is operable to generate an instance of the state machine during a system initialization process for the checkout station;

a parser operable to extract specification language statements from each of the specification language files and validate the structure of the specification language statements during the generation of the instance of each of the state machines and interpret the extracted specification language statements in the instance of each of the state machines;

a business logic application program comprised of business logic modules, the business logic modules including executable compiled program statements that when executed by the processor perform a checkout station action;

a focus variable operable to identify from the plurality of specification language files the specification language file for the state machine currently being interpreted where multiple state machines can be running simultaneously; and

where the parser is operable to call at least one of the business logic modules to process a message extracted by the parser from a specification language statement and to change the status of the focus variable to another specification language statement file when the current specification language statement file being interpreted fails to have a method to process the message.

2. The system of claim 1, the parser comprising:

an expression interpreter for locating expression tags in the specification language statements and interpreting the specification language statements between corresponding tags in accordance with the located expression tags;

a method invoker for calling business logic modules, the invoker using messages extracted by the parser from the specification language statements to support the business logic module calls.

3. The system of claim 2 further comprising:

a Java support interface in a Java application for generating a state machine and invoking actions implemented in one of a Java class and a C++ object.

4. The system of claim 1, the business logic modules being programming language objects.

5. The system of claim 4, the programming language objects being one of a C++ object and a Java object.

6. The system of claim 1 further comprising:

a plurality of specification files, each of which contains specification language statements defining a state machine implementation of a checkout business system; and

the parser maintaining a focus variable identifying the specification file currently being parsed.

7. The system of claim 6, wherein the parser changes focus status in response to the state machine implementation defined by the specification language statements in the specification language file being parsed failing to have a method for processing a message.

8. The system of claim 1, the specification language statements being written in Extensible Markup Language (XML) statements.

9. The system of claim 4, the parser being an application program executed by the processor of the checkout station.

10. The system of claim 1, the checkout station action including reading a bar code.

11. A computer implemented method that controls the operation of a checkout station and implements a plurality of state machines each implementing a different method of operating the checkout business system, the method comprising:

receiving a plurality of specification language files wherein each specification language file contains specification language statements that define a state machine implementation of a different checkout business system where the state machine defines all the operations of the checkout station and wherein the plurality of specification language files are stored in a permanent memory on the checkout station;

extracting, using a parser, specification language statements from each of the plurality of specification language files and validating the structure of each state machine defined by the plurality of specification language statements in each of the plurality of specification language files;

generating an instance of each state machine by interpreting one of the plurality of specification language statements from each of the plurality of specification language statements files during a system initialization process for the checkout station;

setting a focus variable to identify one of the plurality of specification language files being used to interpret the current state machine wherein multiple state machines can be running simultaneously;

interpreting one of the plurality of specification language statements from the one of the plurality of specification language files identified by the focus variable;

calling a business logic module identified in the interpreted specification language statement where the business logic module contains executable compiled program statements that process a message extracted from the interpreted specification language statement and where the business logic module performs a checkout station action; and

changing the focus variable to another of the specification language files when the current specification language file being interpreted fails to have a method to process the message.

12. The method of claim 11, the interpreting one of the plurality of specification language statements further comprising:

locating expression tags in the specification language statement;

interpreting the specification language statement between corresponding tags in accordance with the located expression tags;

calling a business logic module using a message extracted from the specification language statement.

13. The method of claim 12 further comprising:

calling Java action classes through a Java support interface included in a definition of a state machine implementation.

14. The method of claim 11, the calling of a business logic module further comprising:

invoking a method in a programming language object.

15. The method of claim 11, the interpretation of specification language statements further comprising:

interpreting Extensible Markup Language (XML) statements.

16. The method of claim 11 wherein the specification language statement interpretation includes:

executing an application program with a processor of the checkout business system.

17. The method of claim 11, the calling of a business logic module including:

invoking a programming language object.

18. The method of claim 17, the invocation of a programming language object including:

invoking one of a C++ object and a Java object.

19. The method of claim 11, the checkout station action including reading a bar code.