US6158044A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Proposal based architecture system
Assignee: ePropose Inc
•
Filing: 1998-05-20
•
Granted: 2000-12-05
•
Expires: 2018-05-20
Abstract
Abstract A proposal based architecture system that converts a transaction submission process into a generic object in a computer environment. A preferred embodiment of the invention provides a tool set which allows the user to create a set of Proposal Specifications which define the structure of the possible components of a Proposal. The user defines the complete characteristics (meta-data) for any kind of Proposal which define the hierarchy of domain relationships, interaction modes, validation references, and assumptions. The actual Proposal instance is formed using the definitions in the Proposal Specifications. A Proposal allows a user to add, change, and annotate data, is self aware and navigates between pages and skips to appropriate fields automatically and supports n-level undo/redo. It also tracks all versions of data updates and the user that is responsible for each data update, recognizes and corrects stale data, and enables long-lived transactions, off-line transaction processing, and collaborative transactions. A Proposal is accessed via multiple User Interfaces (UI), breaking the close coupling between the front-end and the back-end and allowing the user to add a Web or Graphical User Interface (GUI) front-end without having to rewrite the back-end application. A UI coordinator maps user input fields to components of the Proposal and communicates with different user interfaces such as: Internet; Graphical User Interface (GUI); Object Oriented User Interface (OOUI); proprietary interface; and devices such as bar code readers or keypads. The invention also provides a default UI and components. A set of Transaction Processing/Data Processing (TP/DP) interfaces are provided to communicate with back-end transactional interfaces such as Database Management Systems (DBMS), Transactional Processing (TP) Monitors, and Object Oriented Databases.
Inventors
- 👤 John J. Tibbetts
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-29 22:14
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/465; G06F9/44; G06F9/451; G06F9/466; Y; Y10; Y10S; Y10S707/00; Y10S707/99931
Claims Analysis
Total Claims: 78
Claim 1
Independent Claim
110 words
A process for converting a transaction submission process into a reusable, generic transaction-formation object, said object mediating between a front-end and a back-end of a transactional application in a computer environment, and said object including a plurality of components defined by metadata, said process comprising the steps of: defining a set of specifications for each of the components; creating said object by using a combination of said specifications to instantiate the transaction submission process; and providing a back-end interface, wherein said object transmits data to at least one of a plurality of back-end resources through said back-end interface, said specifications defining a hierarchy of domain relationships, interaction modes, and assumptions.
Claim 2
Dependent Claim
110 words
A process for converting a transaction submission process into a reusable, generic transaction-formation object, said object mediating between a front-end and a back-end of a transactional application in a computer environment, and said object including a plurality of components defined by metadata, said process comprising the steps of: defining a set of specifications for each of the components; creating said object by using a combination of said specifications to instantiate the transaction submission process; and providing a back-end interface, wherein said object transmits data to at least one of a plurality of back-end resources through said back-end interface, said specifications defining a hierarchy of domain relationships, interaction modes, and assumptions.
Claim 3
Dependent Claim
27 words
The process of claim 1, further comprising the step of providing said user interfaces and said components by default, wherein said coordinator communicates with said user interfaces.
Claim 4
Dependent Claim
25 words
The process of claim 1, further comprising the step of providing said user interfaces that are user-defined, wherein said coordinator communicates with said user interfaces.
Claim 5
Dependent Claim
41 words
The process of claim 1, further comprising the step of said coordinator communicating with user interfaces selected from a group consisting of an Internet Interface, Graphical User Interface (GUI), Object Oriented User Interface (OOUI), proprietary interface, bar code readers and keypads.
Claim 6
Dependent Claim
19 words
The process of claim 1, further comprising the step of providing a specification builder tool to create said specifications.
Claim 7
Dependent Claim
34 words
The process of claim 1, further comprising the step of said back-end interface communicating with said back-end resources selected from a group consisting of Database Management Systems, Transaction Processing Monitors, and Object Oriented Databases.
Claim 8
Dependent Claim
49 words
The process of claim 1, further comprising the step of selectively coupling said back-end interface to any of said back-end resources to thereby allow said object to be interrupted, temporarily pended, routed to another party, worked on overtime, and accessed for resumption of processing of the transaction submission process.
Claim 9
Dependent Claim
49 words
The process of claim 1, further comprising the step of selectively coupling said object to any of said user interfaces to thereby allow said object to be interrupted, temporarily pended, routed to another party, worked on over time, and accessed for resumption of processing of the transaction submission process.
Claim 10
Dependent Claim
21 words
The process of claim 1, wherein said object is self aware and navigates between pages and skips to appropriate fields automatically.
Claim 11
Dependent Claim
22 words
The process of claim 1, further comprising the step of said object supporting n-level undo/redo of versions of any of said data.
Claim 12
Dependent Claim
24 words
The process of claim 1, further comprising the step of said object allowing a user to add, change, and annotate any of said data.
Claim 13
Dependent Claim
34 words
The process of claim 1, further comprising the step of said object tracking versions of updates made to any of said data in said object, and an identity of a user providing said updates.
Claim 14
Dependent Claim
26 words
The process of claim 1, further comprising the step of said object including data security selected from a group consisting of authorization, authentication, and digital signatures.
Claim 15
Dependent Claim
47 words
The process of claim 1, further comprising the steps of said object: accepting and recording messages originating external to the object relating to errors in the object; tracking said errors for resolution thereof; and managing and resolving said errors prior to said transaction submission process being completed.
Claim 16
Dependent Claim
50 words
The process of claim 1, further comprising the steps of said object: recognizing any of said data that has become stale data; and providing user options for responding to said stale data, said user options being selected from a group consisting of user correction, rule based correction, and error flagging.
Claim 17
Dependent Claim
20 words
The process of claim 1, further comprising the step of structuring said object as a quantified hierarchy tree with cardinality.
Claim 18
Dependent Claim
23 words
The process of claim 1, further comprising the step of providing a simple component-based assembly process for creating and customizing said user interfaces.
Claim 19
Dependent Claim
19 words
The process of claim 1, further comprising the step of providing a standard default visual editor for said object.
Claim 20
Independent Claim
114 words
An apparatus for converting a transaction submission process into a reusable, generic transaction-formation object, said object mediating between a front-end and a back-end of a transactional application in a computer environment, and said object including a plurality of components defined by metadata, comprising: a module for defining a set of specifications for each of the components; a module for creating said object by using a combination of said specifications to instantiate the transaction submission process; and a module for providing a back-end interface, wherein said object transmits data to at least one of a plurality of back-end resources through said back-end interface, said specifications defining a hierarchy of domain relationships, interaction modes, and assumptions.
Claim 21
Independent Claim
114 words
An apparatus for converting a transaction submission process into a reusable, generic transaction-formation object, said object mediating between a front-end and a back-end of a transactional application in a computer environment, and said object including a plurality of components defined by metadata, comprising: a module for defining a set of specifications for each of the components; a module for creating said object by using a combination of said specifications to instantiate the transaction submission process; and a module for providing a back-end interface, wherein said object transmits data to at least one of a plurality of back-end resources through said back-end interface, said specifications defining a hierarchy of domain relationships, interaction modes, and assumptions.
Claim 22
Dependent Claim
31 words
The apparatus of claim 19, further comprising a module for providing said user interfaces and said components by default, wherein said module for coordinating user interfaces communicates with said user interfaces.
Claim 23
Dependent Claim
29 words
The apparatus of claim 19, further comprising a module for providing said user interfaces that are user-defined, wherein said module for coordinating user interfaces communicates with said user interfaces.
Claim 24
Dependent Claim
41 words
The apparatus of claim 19, wherein said module for coordinating user interfaces communicates with user interfaces selected from a group consisting of an Internet Interface, Graphical User Interface (GUI), Object Oriented User Interface (OOUI), proprietary interface, bar code readers and keypads.
Claim 25
Dependent Claim
19 words
The apparatus of claim 19, further comprising a module for providing a specification builder tool to create said specifications.
Claim 26
Dependent Claim
30 words
The apparatus of claim 19, wherein said back-end interface communicates with said back-end resources selected from a group consisting of Database Management Systems, Transaction Processing Monitors, and Object Oriented Databases.
Claim 27
Dependent Claim
46 words
The apparatus of claim 19, wherein said back-end interface is selectively coupled to any of said back-end resources to thereby allow said object to be interrupted, temporarily pended, routed to another party, worked on overtime, and accessed for resumption of processing of the transaction submission process.
Claim 28
Dependent Claim
46 words
The apparatus of claim 19, wherein said object is selectively coupled to any of said user interfaces to thereby allow said object to be interrupted, temporarily pended, routed to another party, worked on over time, and accessed for resumption of processing of the transaction submission process.
Claim 29
Dependent Claim
21 words
The apparatus of claim 19, wherein said object is self aware and navigates between pages and skips to appropriate fields automatically.
Claim 30
Dependent Claim
18 words
The apparatus of claim 19, wherein said object supports n-level undo/redo of versions of any of said data.
Claim 31
Dependent Claim
20 words
The apparatus of claim 19, wherein said object allows a user to add, change, and annotate any of said data.
Claim 32
Dependent Claim
30 words
The apparatus of claim 19, wherein said object tracks versions of updates made to any of said data in said object, and an identity of a user providing said updates.
Claim 33
Dependent Claim
22 words
The apparatus of claim 19, wherein said object includes data security selected from a group consisting of authorization, authentication, and digital signatures.
Claim 34
Dependent Claim
43 words
The apparatus of claim 19, wherein said object accepts and records messages originating external to the object relating to errors in the object, tracks said errors for resolution thereof, and manages and resolves said errors prior to said transaction submission process being completed.
Claim 35
Dependent Claim
46 words
The apparatus of claim 19, wherein said object recognizes any of said data that has become stale data, and provides user options for responding to said stale data, said user options being selected from a group consisting of user correction, rule based correction, and error flagging.
Claim 36
Dependent Claim
17 words
The apparatus of claim 19, wherein said object is structured as a quantified hierarchy tree with cardinality.
Claim 37
Dependent Claim
23 words
The apparatus of claim 19, further comprising a module for providing a simple component-based assembly process for creating and customizing said user interfaces.
Claim 38
Dependent Claim
19 words
The apparatus of claim 19, further comprising a module for providing a standard default visual editor for said object.
Claim 39
Dependent Claim
128 words
A program storage medium readable by a computer, tangibly embodying a program of instructions executable by the computer to perform method steps for converting a transaction submission process into a reusable, generic transaction-formation object, said object mediating between a front-end and a back-end of a transactional application in a computer environment, and said object including a plurality of components defined by metadata, said method steps comprising: defining a set of specifications for each of the components; creating said object by using a combination of said specifications to instantiate the transaction submission process; and providing a back-end interface, wherein said object transmits data to at least one of a plurality of back-end resources through said back-end interface, said specifications defining a hierarchy of domain relationships, interaction modes, and assumptions.
Claim 40
Dependent Claim
128 words
A program storage medium readable by a computer, tangibly embodying a program of instructions executable by the computer to perform method steps for converting a transaction submission process into a reusable, generic transaction-formation object, said object mediating between a front-end and a back-end of a transactional application in a computer environment, and said object including a plurality of components defined by metadata, said method steps comprising: defining a set of specifications for each of the components; creating said object by using a combination of said specifications to instantiate the transaction submission process; and providing a back-end interface, wherein said object transmits data to at least one of a plurality of back-end resources through said back-end interface, said specifications defining a hierarchy of domain relationships, interaction modes, and assumptions.
Claim 41
Dependent Claim
27 words
The method of claim 37, further comprising the step of providing said user interfaces and said components by default, wherein said coordinator communicates with said user interfaces.
Claim 42
Dependent Claim
25 words
The method of claim 37, further comprising the step of providing said user interfaces that are user-defined, wherein said coordinator communicates with said user interfaces.
Claim 43
Dependent Claim
41 words
The method of claim 37, further comprising the step of said coordinator communicating with user interfaces selected from a group consisting of an Internet Interface, Graphical User Interface (GUI), Object Oriented User interface (OOUI), proprietary interface, bar code readers and keypads.
Claim 44
Dependent Claim
19 words
The method of claim 37, further comprising the step of providing a specification builder tool to create said specifications.
Claim 45
Dependent Claim
34 words
The method of claim 37, further comprising the step of said back-end interface communicating with said back-end resources selected from a group consisting of Database Management Systems, Transaction Processing Monitors, and Object Oriented Databases.
Claim 46
Dependent Claim
50 words
The method of claim 37, further comprising the step of selectively coupling said back-end interface to any of said back-end resources to thereby allow said object to be interrupted, temporarily pended, routed to another party, worked on over time, and accessed for resumption of processing of the transaction submission process.
Claim 47
Dependent Claim
49 words
The method of claim 37, further comprising the step of selectively coupling said object to any of said user interfaces to thereby allow said object to be interrupted, temporarily pended, routed to another party, worked on over time, and accessed for resumption of processing of the transaction submission process.
Claim 48
Dependent Claim
21 words
The method of claim 37, wherein said object is self aware and navigates between pages and skips to appropriate fields automatically.
Claim 49
Dependent Claim
22 words
The method of claim 37, further comprising the step of said object supporting n-level undo/redo of versions of any of said data.
Claim 50
Dependent Claim
24 words
The method of claim 37, further comprising the step of said object allowing a user to add, change, and annotate any of said data.
Claim 51
Dependent Claim
34 words
The method of claim 37, further comprising the step of said object tracking versions of updates made to any of said data in said object, and an identity of a user providing said updates.
Claim 52
Dependent Claim
26 words
The method of claim 37, further comprising the step of said object including data security selected from a group consisting of authorization, authentication, and digital signatures.
Claim 53
Dependent Claim
47 words
The method of claim 37, further comprising the steps of said object: accepting and recording messages originating external to the object relating to errors in the object, tracking said errors for resolution thereof; and managing and resolving said errors prior to said transaction submission process being completed.
Claim 54
Dependent Claim
20 words
The method of claim 37, further comprising the step of structuring said object as a quantified hierarchy tree with cardinality.
Claim 55
Dependent Claim
23 words
The method of claim 1, further comprising the step of providing a simple component-based assembly process for creating and customizing said user interfaces.
Claim 56
Dependent Claim
19 words
The method of claim 37, further comprising the step of providing a standard default visual editor for said object.
Claim 57
Dependent Claim
75 words
The process of claim 1, further comprising the step of using a coordinator for coordinating user interfaces with said object by mapping user input fields to said components associated therewith, accepting data in the user input fields, said data originating from users at the front end, converting the data in said input fields to said components associated therewith, said user interfaces for viewing contents of the transaction submission process, and outputting data from said object.
Claim 58
Dependent Claim
29 words
The process of claim 54, further comprising the step of organizing said data into a group consisting of user input fields, field groups, and additional reusable, generic transaction-formation objects.
Claim 59
Dependent Claim
186 words
The process of claim 1, wherein each of said back-end resources corresponds to a resource coordinator, said process further comprising the steps of organizing data into fields and grouping these fields into field groups, each said field group operating to exchange said data with at least one of said back-end resources through said back-end interface by determining from the object a first operation that governs the exchange of data with at least one of the back-end resources, determining from each of said field groups an interaction mode by which that field group exchanges data with at least one of the back-end resources, determining a second operation to be implemented by a resource coordinator, said second operation being a function of said first operation and said interaction mode, identifying from said second operation a particular back-end resource which exchanges said data with the field group, implementing the first operation so that the particular resource coordinator associated with said particular back-end resource exchanges said data with the field group, and implementing the second operation so that said particular back-end resource exchanges said data with said particular resource coordinator.
Claim 60
Dependent Claim
25 words
The process of claim 56, further comprising the step of selecting said first operation from a group consisting of Populate, Commit, Verify, and Check Assumptions.
Claim 61
Dependent Claim
15 words
The process of claim 1, further comprising the step of said specifications defining validation references.
Claim 62
Dependent Claim
71 words
The apparatus of claim 19, further comprising a module for coordinating user interfaces with said object by mapping user input fields to said components associated therewith, accepting data in the user input fields, said data originating from users at the front end, converting the data in said input fields to said components associated therewith, said user interfaces for viewing contents of the transaction submission process, and outputting data from said object.
Claim 63
Dependent Claim
26 words
The apparatus of claim 59, wherein said data is organized into a group consisting of user input fields, field groups, and additional reusable, generic transaction-formation objects.
Claim 64
Dependent Claim
181 words
The apparatus of claim 19, wherein each of said back-end resources corresponds to a resource coordinator, said apparatus organizing data into fields and grouping these fields into field groups, each said field group operating to exchange said data with at least one of said back-end resources through said back-end interface by determining from the object a first operation that governs the exchange of data with at least one of the back-end resources, determining from each of said field groups an interaction mode by which that field group exchanges data with at least one of the back-end resources, determining a second operation to be implemented by a resource coordinator, said second operation being a function of said first operation and said interaction mode, identifying from said second operation a particular back-end resource which exchanges said data with the field group, implementing the first operation so that the particular resource coordinator associated with said particular back-end resource exchanges said data with the field group, and implementing the second operation so that said particular back-end resource exchanges said data with said particular resource coordinator.
Claim 65
Dependent Claim
22 words
The apparatus of claim 61, wherein said first operation is selected from a group consisting of Populate, Commit, Verify, and Check Assumptions.
Claim 66
Dependent Claim
12 words
The apparatus of claim 19, wherein said specifications further define validation references.
Claim 67
Dependent Claim
75 words
The method of claim 37, further comprising the step of using a coordinator for coordinating user interfaces with said object by mapping user input fields to said components associated therewith, accepting data in the user input fields, said data originating from users at the front end, converting the data in said input fields to said components associated therewith, said user interfaces for viewing contents of the transaction submission process, and outputting data from said object.
Claim 68
Dependent Claim
29 words
The method of claim 64, further comprising the step of organizing said data into a group consisting of user input fields, field groups, and additional reusable, generic transaction-formation objects.
Claim 69
Dependent Claim
186 words
The method of claim 37, wherein each of said back-end resources corresponds to a resource coordinator, said method further comprising the steps of organizing data into fields and grouping these fields into field groups, each said field group operating to exchange said data with at least one of said back-end resources through said back-end interface by determining from the object a first operation that governs the exchange of data with at least one of the back-end resources, determining from each of said field groups an interaction mode by which that field group exchanges data with at least one of the back-end resources, determining a second operation to be implemented by a resource coordinator, said second operation being a function of said first operation and said interaction mode, identifying from said second operation a particular back-end resource which exchanges said data with the field group, implementing the first operation so that the particular resource coordinator associated with said particular back-end resource exchanges said data with the field group, and implementing the second operation so that said particular back-end resource exchanges said data with said particular resource coordinator.
Claim 70
Dependent Claim
25 words
The method of claim 66, further comprising the step of selecting said first operation from a group consisting of Populate, Commit, Verify, and Check Assumptions.
Claim 71
Dependent Claim
15 words
The method of claim 37, further comprising the step of said specifications defining validation references.
Claim 72
Dependent Claim
50 words
The method of claim 37, further comprising the steps of said object: recognizing any of said data that has become stale data; and providing user options for responding to said stale data, said user options being selected from a group consisting of user correction, rule based correction and error flagging.
Claim 73
Dependent Claim
36 words
The process of claim 55, further comprising the step of providing introspective control for automatically determining characteristics of said metadata, making decisions based on said characteristics, and navigating among said input fields, field groups and objects.
Claim 74
Dependent Claim
33 words
The apparatus of claim 60, further comprising providing introspective control for automatically determining characteristics of said metadata, making decisions based on said characteristics, and navigating among said input fields, field groups and objects.
Claim 75
Dependent Claim
36 words
The method of claim 65, further comprising the step of providing introspective control for automatically determining characteristics of said components, making decisions based on said characteristics, and navigating among said input fields, field groups and objects.
Claim 76
Dependent Claim
22 words
The process of claim 1, further comprising the step of said object transmitting the data to asset managers through the back-end interface.
Claim 77
Dependent Claim
18 words
The apparatus of claim 19, wherein said object transmits the data to asset managers through the back-end interface.
Claim 78
Dependent Claim
22 words
The method of claim 37, further comprising the step of said object transmitting the data to asset managers through the back-end interface.
References Cited (Backward Citations)
US5084816A
Cited
US5539909A
Cited
US5522079A
Cited
US5457797A
Cited
US5627979A
Cited
US5706500A
Cited
US6009266A
Cited
US5991823A
Cited
US6009405A
Cited
US6016490A
Cited
US6016394A
Cited
US6018627A
Cited
US5924097A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-12-05 | 2004-06-05 | 2004-12-05 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-12-05 | 2008-06-05 | 2008-12-05 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-12-05 | 2012-06-05 | 2012-12-05 | $7700.00 | Window Closed / Lapsed |