News Column

Researchers Submit Patent Application, "Resource Processing Using an Intermediary for Context-Based Customization of Interaction Deliverables", for...

January 30, 2014



Researchers Submit Patent Application, "Resource Processing Using an Intermediary for Context-Based Customization of Interaction Deliverables", for Approval

By a News Reporter-Staff News Editor at Computer Weekly News -- From Washington, D.C., VerticalNews journalists report that a patent application by the inventors Duggal, Dave M. (Glens Falls, NY); Malyk, William J. (Guelph, CA), filed on September 9, 2013, was made available online on January 16, 2014.

The patent's assignee is EnterpriseWeb LLC.

News editors obtained the following quote from the background information supplied by the inventors: "Organized software development generally follows well-defined styles that provide recognizable and repeatable structures, much like other disciplines (e.g., civil engineering, culinary arts, graphic design, etc.). Structure enables the consistent implementation of constraints to achieve specific desired properties. Three leading software architectural styles are Object Oriented Development, Service Oriented Architecture, and Representational State Transfer.

"In the Object Oriented Development (OOD) style, an object is a set of dependent data and functions. Each encapsulated object is an artifact that has a custom interface providing for its manipulation. Objects can be loosely-coupled, but are not individually addressable by a remote system without extension (e.g., common object request broker architecture, CORBA). In the context of an application, object bindings are often prescribed as fixed components of the system. The use of any interaction context to customize system responses is left to the software developer in defining an object. Overall, the OOD style supports rich software applications, but the tight-coupling within, and often between objects, limits the practical range of result customization.

"In the Service Oriented Architecture (SOA) style, a service is a set of dependent data and functions. Each encapsulated service is a black-box artifact that has a custom interface defining the fixed range of its manipulation. Services are loosely-coupled and can be individually addressable components in a distributed system. In the context of an application, the SOA style requires a meta application layer for messaging, translation, and binding. This layer is typically supported by discrete middleware components (e.g. enterprise service bus (ESB), business process execution language (BPEL), business process management (BPM), etc.). The use of any interaction context to customize system responses is left to the software developer in defining a service interface. Overall, the SOA style supports rich software applications, but the tight-coupling within services and the black-box nature of services intrinsically limits the practical range of result customization.

"In the Representational State Transfer (REST) style, a resource is any discrete element of information (e.g. document, database record, temporal service, etc.), independent of any pre-determined function, that can be referenced with a unique address (e.g., Uniform Resource Indicator, URI). Each resource is a standalone artifact that has a standard interface (e.g., the Uniform Interface) providing for its manipulation, however manipulation is done through representations, which isolate a resource from direct interaction. Resources are loosely-coupled and addressable components in a distributed system. In the context of an application, every resource is a potential state addressable by a client, therefore each client request results in a representation and a new application state. The use of any interaction context to customize system responses is constrained to in-band context provided with the client request, the software developer is prohibited from using any out-of-band context that may reside on the server. Overall, the REST style supports rich software applications, but the absence of pre-determined functions, and the inability to use server-side context, results in a client driven application that intrinsically limits the practical range of result customization."

As a supplement to the background information on this patent application, VerticalNews correspondents also obtained the inventors' summary information for this patent application: "Aspects of the invention provide a software application, which includes work order resources, each of which defines an atomic operation for the software application, and a construction service resource, which processes the work order resources in response to all interaction requests for the software application. Each interaction request is received from a client and identifies a corresponding work order, which the construction service processes to dynamically construct a set of deliverables, which can include a custom representation of the work order. While processing the interaction request, the construction service, as directed by the work order, can make one or more requests to context resources for context information corresponding to an activity for which the interaction was requested to construct the set of deliverables. The work order resource can comprise a reflective program that enables the construction service to dynamically determine and construct the set of deliverables, including the next appropriate interaction(s) using the context information, thereby directing a set of atomic operations as part of an activity being performed and enabling the dynamic context-based construction of interaction deliverables.

"A first aspect of the invention provides a software application comprising program code embodied in at least one computer-readable medium, the software application comprising: a plurality of work order resources, wherein each work order resource defines an atomic operation for the software application and has a corresponding unique work order resource identifier; a construction service resource configured to process all interaction requests for the software application, wherein each interaction request includes a work order resource identifier, and wherein each interaction request is made as part of an activity being performed using the software application, wherein the construction service resource is configured to process each interaction request by: processing a representation of a work order resource corresponding to the work order resource identifier in the interaction request, wherein the processing includes constructing a set of deliverables as directed by the representation of the work order resource and context information for an activity corresponding to the requested interaction; and providing the set of deliverables in response to the interaction request.

"A second aspect of the invention provides a computer-implemented method of processing interactions for a software application, the method comprising: receiving a work order resource identifier corresponding to an interaction request at a representation of a construction service resource of the software application executing on a computer system, wherein the representation of the construction service resource processes the interaction request by: obtaining a representation of a work order resource corresponding to the work order resource identifier in response to the receiving; processing the representation of the work order resource, wherein the processing includes constructing a set of deliverables as directed by the representation of the work order resource and context information for an activity corresponding to the requested interaction; and providing the set of deliverables in response to the interaction request.

"A third aspect of the invention provides a computer system including: a processing component; and a storage component, wherein the storage component includes at least one computer-readable medium comprising a software application including: a plurality of work order resources, wherein each work order resource defines an atomic operation for the software application and has a corresponding unique work order resource identifier; and a construction service resource configured to process all interaction requests for the software application, wherein each interaction request includes a work order resource identifier, and wherein each interaction request is made as part of an activity being performed using the software application, wherein the construction service resource is configured to process each interaction request by: processing a representation of a work order resource corresponding to the work order resource identifier in the interaction request, wherein the processing includes constructing a set of deliverables as directed by the representation of the work order resource and context information for an activity corresponding to the requested interaction; and providing the set of deliverables in response to the interaction request.

"A fourth aspect of the invention provides a method of performing an activity, the method comprising: providing a request for an atomic operation of the activity for processing by a system controller, the request including an identifier of a work order resource defining the atomic operation, wherein the system controller is configured to provide the identifier of the work order resource to a construction service for processing; and receiving a custom representation of the work order in response to the request from the construction service.

"Other aspects of the invention provide methods, systems, program products, and methods of using and generating each, which include and/or implement some or all of the actions described herein. The illustrative aspects of the invention are designed to solve one or more of the problems herein described and/or one or more other problems not discussed.

BRIEF DESCRIPTION OF THE DRAWINGS

"These and other features of the disclosure will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings that depict various aspects of the invention.

"FIG. 1 shows an illustrative high level data flow diagram for performing an atomic operation using a software application according to an embodiment.

"FIG. 2 shows a more detailed illustrative data flow diagram for performing an atomic operation using the software application of FIG. 1 according to an embodiment.

"FIG. 3 shows an illustrative method of pre-processing a request using the application of FIG. 2 according to an embodiment.

"FIG. 4 shows an illustrative method of processing a request using the application of FIG. 2 according to an embodiment.

"FIG. 5 shows an illustrative environment for executing the application of FIG. 2 in order to perform a task according to an embodiment.

"FIG. 6 shows an illustrative software development method for developing the software application of FIG. 1 according to an embodiment.

"FIG. 7 shows an illustrative flow diagram for performing a task using the software application of FIG. 1 according to an embodiment.

"FIG. 8 shows an illustrative flow diagram for performing an activity using the software application of FIG. 1 according to an embodiment.

"FIG. 9 shows illustrative activity relationships between activities being performed using the software application of FIG. 1 according to an embodiment.

"FIG. 10 shows a conceptual architecture of an illustrative SOA-style implementation of the software application of FIG. 1 according to an embodiment.

"FIGS. 11A-11M show illustrative flowcharts for an illustrative set of tasks for managing the lifecycle of a grant according to an embodiment.

"FIGS. 12A-12E show illustrative views of a grant during various portions of the lifecycle of the grant according to an embodiment.

"It is noted that the drawings may not be to scale. The drawings are intended to depict only typical aspects of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements between the drawings."

For additional information on this patent application, see: Duggal, Dave M.; Malyk, William J. Resource Processing Using an Intermediary for Context-Based Customization of Interaction Deliverables. Filed September 9, 2013 and posted January 16, 2014. Patent URL: http://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=%2Fnetahtml%2FPTO%2Fsearch-adv.html&r=176&p=4&f=G&l=50&d=PG01&S1=20140109.PD.&OS=PD/20140109&RS=PD/20140109

Keywords for this news article include: Software, EnterpriseWeb LLC.

Our reports deliver fact-based news of research and discoveries from around the world. Copyright 2014, NewsRx LLC


For more stories covering the world of technology, please see HispanicBusiness' Tech Channel



Source: Computer Weekly News


Story Tools