Method and system for creating reusable software components through a uniform interface

• US 20040205692A1
• Filed: 01/14/2002
• Published: 10/14/2004
• Est. Priority Date: 01/12/2001
• Status: Abandoned Application

• Current Assignee: Marck R. Robinson
• Original Assignee: Marck R. Robinson
• Inventors: Robinson, Marck R.
• Application Number:
  US10/047,457
• Publication Number:
  US 20040205692A1
• Time in Patent Office: Days
• US Class Current: 717/100
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A method for designing software components for integration into any system without additional coding is provided. The method includes adopting a uniform application programming interface that breaks down external objects to include the characteristics of object, attribute, and method. Ideally, the characteristics include create object, delete object, read attributes, write attributes, and invoke behavior. A software tool is provided for communication between an API and a data source, the tool including a join engine adapted to provide communication between at least one view and at least one base source associated with the data source, the join engine further adapted to update the at least one base source in response to updates to the view. Ideally, the tool is further configured to support on the at least one base source operations of create object and delete object on the at least one view. The software tool is also configured to map events in the at least one base source to the at least one view, and can be configured to create virtual attributes based on the view through operations or expressions performed on the view, including, but not limited to algebraic expressions, names, strings, and functions.

Claims

1. A method for designing software components for integration into any system without additional coding, the method comprising:

adopting a uniform application programming interface that breaks down external objects to include the characteristics of object, attribute, and method. Ideally, the characteristics include create object, delete object, read attributes, write attributes, and invoke behavior.

2. A software tool for providing communication between an API and a data source, the tool comprising:

a join engine adapted to provide communication between at least one view and at least one base source associated with the data source, the join engine further adapted to update the at least one base source in response to updates to the view.

3. The tool of claim 2, wherein the join engine is configured to support on the at least one base source operations of create object and delete object on the at least one view.

4. The tool of claim 2, wherein the join engine is configured to map events in the at least one base source to the at least one view.

5. The tool of claim 2, wherein the join engine is configured to create virtual attributes based on the view through expressions performed on the view.

6. The tool of claim 5, wherein the expressions comprise algebraic expressions, names, strings, and functions.