Presentation services patterns in a netcentric environment

• US 6,640,249 B1
• Filed: 08/31/1999
• Issued: 10/28/2003
• Est. Priority Date: 08/31/1999
• Status: Expired due to Term

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Bowman-Amuah, Michel K.
• Primary Examiner(s): Lim, Krisna
• Assistant Examiner(s): Kupstas, Tod
• Application Number:
  US09/387,072
• Time in Patent Office: 1,519 Days
• Field of Search: 709/219, 709/203, 709/227, 709/237, 709/201, 709/228, 709/315, 345/717, 345/797
• US Class Current: 709/228
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/38 for implementing user interfaces

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.

Claims

1. 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.

2. 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.

3. 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.

4. 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.

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

6. 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.

7. 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.

8. 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.

9. 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.

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

11. 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.

12. 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.

13. 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.

14. 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.

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