US6640249B1 Expired / Lapsed US ⏱️ 0.0 years remaining

Presentation services patterns in a netcentric environment

Assignee: Accenture Global Services Ltd

•

Filing: 1999-08-31

•

Granted: 2003-10-28

•

Expires: 2019-08-31

📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A system, method and article of manufacture are provided for implementing presentation services patterns. Non-presentation logic executed on a client is assigned to an activity for allowing reuse of the non-presentation logic across multiple, volatile user interfaces. A view is assigned to the activity. Validation rules are also structured for validating user data across the multiple user interfaces.

Inventors

👤 Michel K. Bowman-Amuah

Bibliographic Details

Application Number —

Jurisdiction US

Data Source google_patents

Last Synchronized 2026-10-24 11:12

CPC Classifications

G; G06; G06F; G06F8/00; G06F8/30; G06F8/38; G06F8/36

Claims Analysis

Total Claims: 18

Claim 1

Independent Claim 223 words

A method for implementing presentation services patterns, comprising the steps of: (a) assigning non-presentation logic executed on a client to an activity for allowing reuse of the non-presentation logic across a plurality of user interfaces corresponding to a plurality of software packages, wherein the activity resides between the plurality of user interfaces, a business model and server components; (b) assigning a view to the activity; (c) providing a plurality of user interface widgets for implementation on the plurality of user interfaces; (d) providing a plurality of validation rules which govern use of the user interface widgets, the plurality of validations rules being encapsulated in a user interface validator; (e) allowing a user to select the validation rules to associate with the user interface widgets of a first user interface by implementing the user interface validator, the user interface validator associating the validation rules with the user interface widgets of the first user interface such that upon invocation of a “validate” method, the plurality of validation rules are sent to the plurality of user interface widgets; and (f) associating the validation rules of the user interface validator across the user interface widgets of the plurality of user interfaces, the user interface validator further linking validation rules associated with the widgets of the first user interface to the widgets of the plurality of user interfaces.

Claim 2

Independent Claim 223 words

Claim 3

Dependent Claim 74 words

A method as recited in claim 1 , wherein the step of assigning non-presentation logic to the activity includes the steps of: interfacing a server and a presentation interface of a client; receiving requests for service from the presentation interface of the client; handling at least a portion of the requests on the client; forwarding another portion of the requests to the server for further handling purposes; and effecting changes in the presentation interface.

Claim 4

Dependent Claim 85 words

A method as recited in claim 1 , wherein the step of assigning the view to the activity includes the steps of: receiving notification that a startup event of an activity has occurred; receiving a reference to a first instance of an object created by the startup event of the activity; determining a view to launch in response to the receipt of the notification and the reference, wherein the view is based on predetermined criteria; associating the view with the activity; and displaying the view.

Claim 5

Dependent Claim 33 words

A method as recited in claim 2 , wherein the step of assigning non-presentation logic to the activity further includes the step of triggering events intended to be received by the presentation interface.

Claim 6

Dependent Claim 19 words

A method as recited in claim 3 , wherein the activity is allowed to run without a corresponding view.

Claim 7

Dependent Claim 251 words

A computer program embodied on a computer readable medium for implementing presentation services patterns, comprising: (a) a code segment that assigns non-presentation logic executed on a client to an activity for allowing reuse of the non-presentation logic across a plurality of user interfaces corresponding to a plurality of software packages, wherein the activity resides between the plurality of user interfaces, a business model and server components; (b) a code segment that assigns a view to the activity; (c) a code segment that provides a plurality of user interface widgets for implementation on the plurality of user interfaces; (d) a code segment that provides a plurality of validation rules which govern use of the user interface widgets, the plurality of validations rules being encapsulated in a user interface validator; (e) a code segment that allows a user to select the validation rules to associate with the user interface widgets of a first user interface by implementing a user interface validator, the user interface validator associating the validation rules with the user interface widgets of the first user interface such that upon invocation of a “validate” method, the plurality of validation rules are sent to the plurality of user interface widgets; and (f) a code segment that associates the validation rules of the user interface validator across the user interface widgets of the plurality of user interfaces, the user interface validator further linking validation rules associated with the widgets of the first user interface to the widgets of the plurality of user interfaces.

Claim 8

Dependent Claim 251 words

Claim 9

Dependent Claim 93 words

A computer program as recited in claim 6 , wherein the code segment that assigns non-presentation logic to the activity includes: a code segment that interfaces a server and a presentation interface of a client; a code segment that receives requests for service from the presentation interface of the client; a code segment that handles at least a portion of the requests on the client; a code segment that forwards another portion of the requests to the server for further handling purposes; and a code segment that effects changes in the presentation interface.

Claim 10

Dependent Claim 100 words

A computer program as recited in claim 6 , wherein the code segment that assigns the view to the activity includes: a code segment that receives notification that a startup event of an activity has occurred; a code segment that receives a reference to a first instance of an object created by the startup event of the activity; a code segment that determines a view to launch in response to the receipt of the notification and the reference, wherein the view is based on predetermined criteria; associating the view with the activity; and a code segment that displays the view.

Claim 11

Dependent Claim 36 words

A computer program as recited in claim 7 , wherein the code segment that assigns non-presentation logic to the activity further includes a code segment that triggers events intended to be received by the presentation interface.

Claim 12

Dependent Claim 20 words

A computer program as recited in claim 8 , wherein the activity is allowed to run without a corresponding view.

Claim 13

Independent Claim 232 words

A system for implementing presentation services patterns, comprising: (a) logic that assigns non-presentation logic executed on a client to an activity for allowing reuse of the non-presentation logic across a plurality of user interfaces corresponding to a plurality of software packages, wherein the activity resides between the plurality of user interfaces, a business model and server components; (b) logic that assigns a view to the activity; (c) logic that provides a plurality of user interface widgets for implementation on the plurality of user interfaces; (d) logic that provides a plurality of validation rules which govern use of the user interface widgets, the plurality of validations rules being encapsulated in a user interface validator; (e) logic that allows a user to select the validation rules to associate with the user interface widgets of a first user interface by implementing a user interface validator, the user interface validator associating the validation rules with the user interface widgets of the first user interface such that upon invocation of a “validate” method, the plurality of validation rules are sent to the plurality of user interface widgets; and (f) logic that associates the validation rules of the user interface validator across the user interface widgets of the plurality of user interfaces, the user interface validator further linking validation rules associated with the widgets of the first user interface to the widgets of the plurality of user interfaces.

Claim 14

Independent Claim 232 words

Claim 15

Dependent Claim 81 words

A system as recited in claim 11 , wherein the logic that assigns non-presentation logic to the activity includes: logic that interfaces a server and a presentation interface of a client; logic that receives requests for service from the presentation interface of the client; logic that handles at least a portion of the requests on the client; logic that forwards another portion of the requests to the server for further handling purposes; and logic that effects changes in the presentation interface.

Claim 16

Dependent Claim 90 words

A system as recited in claim 11 , wherein the logic that assigns the view to the activity includes: logic that receives notification that a startup event of an activity has occurred; logic that receives a reference to a first instance of an object created by the startup event of the activity; logic that determines a view to launch in response to the receipt of the notification and the reference, wherein the view is based on predetermined criteria; associating the view with the activity; and logic that displays the view.

Claim 17

Dependent Claim 32 words

A system as recited in claim 12 , wherein the logic that assigns non-presentation logic to the activity further includes logic that triggers events intended to be received by the presentation interface.

Claim 18

Dependent Claim 19 words

A system as recited in claim 13 , wherein the activity is allowed to run without a corresponding view.

References Cited (Backward Citations)

EP0123456B1 Cited

US6041365A Cited

US5047918A Cited

US5133075A Cited

US5471629A Cited

US5187787A Cited

US5187787B1 Cited

US5301270A Cited

US5623418A Cited

US5606664A Cited

US5313636A Cited

US5291593A Cited

US5241580A Cited

US5649139A Cited

US5301320A Cited

US5437038A Cited

US5414812A Cited

US5463686A Cited

US5581758A Cited

US5475844A Cited

US5677997A Cited

US5915115A Cited

US5499371A Cited

US5706506A Cited

US5457797A Cited

US5671386A Cited

US5675748A Cited

US5434978A Cited

US5560005A Cited

US5724575A Cited

US5692107A Cited

US5987501A Cited

US5873086A Cited

US5732270A Cited

US5715397A Cited

US5642511A Cited

US5758351A Cited

US5907704A Cited

US5680602A Cited

US5799310A Cited

US5568644A Cited

US5708828A Cited

US5721908A Cited

US5890133A Cited

US5737607A Cited

US5732263A Cited

US5870746A Cited

US5764955A Cited

US5872973A Cited

US5953707A Cited

US5898870A Cited

US5710901A Cited

US5870742A Cited

US5751965A Cited

US5764235A Cited

US5923736A Cited

US5960200A Cited

US5778368A Cited

US5940594A Cited

US6052711A Cited

US6304893B1 Cited

US6272556B1 Cited

US5768510A Cited

US5761513A Cited

US5958012A Cited

US5787413A Cited

US5774660A Cited

US5892909A Cited

US6057856A Cited

US6018743A Cited

US5867153A Cited

US5987514A Cited

US5933816A Cited

US5995753A Cited

US5909540A Cited

US5878408A Cited

US6023722A Cited

US6081837A Cited

US6006230A Cited

US5905873A Cited

US5920703A Cited

US5966451A Cited

US5905897A Cited

US5946697A Cited

US5896383A Cited

US5987247A Cited

US5987633A Cited

US5995945A Cited

US5999948A Cited

US6016394A Cited

US6125359A Cited

US5946694A Cited

US5940075A Cited

US6223209B1 Cited

US6128279A Cited

US6070191A Cited

US6154212A Cited

US6032153A Cited

US6029177A Cited

US6157940A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage	Window Opens	Payment Deadline	Surcharge Period Until	Estimated Fee	Status
3.5 Years (Year 4)	2006-10-27	2007-04-28	2007-10-28	$2000.00	Window Closed / Lapsed
7.5 Years (Year 8)	2010-10-27	2011-04-28	2011-10-28	$3760.00	Window Closed / Lapsed
11.5 Years (Year 12)	2014-10-27	2015-04-28	2015-10-28	$7700.00	Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag

Select Category

Notes (Optional)