Service context management for exertion-oriented programming

dc.contributor.committeeChairSobolewski, Michael
dc.contributor.committeeMemberSmith, Philip W.
dc.contributor.committeeMemberZhuang, Yu
dc.creatorMcChesney, Gregory James
dc.date.accessioned2016-11-14T23:16:04Z
dc.date.available2012-06-01T16:54:38Z
dc.date.available2016-11-14T23:16:04Z
dc.date.issued2009-05
dc.degree.departmentComputer Science
dc.description.abstractExertion-oriented programming defines a network centric methodology for programming. Two groups exist in an exertion-oriented system, the providers who offer a service and the requestors who utilize the service. Requestors communicate their request in the form of an exertion; the exertion contains a context which specifies the data and instructions needed for processing. Current exertion-orientated systems do not define a method for providers to communicate the required context to requestors. The provider does not work without the data being sent in the correct format therefore the requestor must inquire with the provider’s developer to obtain the proper data structuring. The lifecycle for context management addresses this problem by providing a series of interfaces that each provider will implement. Using these interfaces requestors can view, edit and delete contexts over the network. The lifecycle also discusses how generic user interfaces can be created to utilize the context management functionality. The lifecycle is defined using UML modeling and then implemented using the SORCER environment. To provide a truly network centric solution for exertion creation the lifecycle includes a sample exertion editor built for the SORCER platform.
dc.format.mimetypeapplication/pdf
dc.identifier.urihttp://hdl.handle.net/2346/13914
dc.language.isoeng
dc.rights.availabilityUnrestricted.
dc.subjectExertion
dc.subjectExertion-oriented
dc.subjectContext
dc.subjectContext management
dc.titleService context management for exertion-oriented programming
dc.typeThesis

Files