Greg McChesneyThesis Proposal PresentationComputer Science, TTUGreg.mcchesney@ttu.edu

Service Context Management for Exertion-oriented Programming

Greg McChesney2

Overall Presentation Goal or Primary Purpose

Beginning

• Create a life-cycle for context management in Exertion-Oriented Programming

Greg McChesney3

Proposal Objectives

• As a result of this presentation, you will be able to:– Understand the purpose of service contexts– Understand why a life-cycle is required– Utilize the life-cycle for your SORCER projects– Create a context in SORCER– Modify a context in SORCER– Execute an exertion in SORCER– View a returned exertion context from the

federation

Beginning

Greg McChesney4

Speaker’s Qualifications

• Greg McChesney is a graduate student at TTU

• Greg McChesney is planning to graduate in May of 2009 with a Master’s in Computer Science

• Completed a related project as a feasibility study in Communication Networks

Beginning

Greg McChesney5

Did you know?

There is no network-centric methodology for creating service contexts in the SORCER environment.

Beginning

Greg McChesney6

Presentation Agenda

• Background knowledge

• What is a service context?

• Discuss why a life-cycle is required

• Overview of life-cycle

• Discuss Context Creation Panel

• Feasibility Study

• Schedule

Beginning

Background Knowledge

• Many different Exertion-Oriented (EO) Systems

• Implementation based on SORCER– Developed by Texas Tech SORCER Lab– Based on Jini network technology– Framework constantly evolving– Interoperability with existing providers a concern

for new development

Greg McChesney7

All About Contexts

• A service context is a basic data structure in SOOA

• Used for communication between provider and requestor (a data exchange contract)

• A service context depends on the provider and the method being executed

• Data specification of hierarchical attributes the method will require

• Stored in a tree like format of path/value

Greg McChesney8

Sample Context

Greg McChesney9 Image courtesy of Dr. Sobolewski

Need for a Life-Cycle

• Two roles– Provider

• No methodology to obtain a service context from a provider

• No methodology to interactively create network centric contexts

• No method of updating or removing a context from a provider

– Requestor

Greg McChesney10

Need for a Life-Cycle

– Requestor• Exertion-oriented programming cannot be

network centric without context management• A new service provider - Context Catalog will

provide more accessibility• Need service context editing operations for

EO programming

Greg McChesney11

Proposed Life-Cycle

• Implement service context editing operations into provider classes– New operations will be remotely invokeable

• Get- Requestor• Save -Admin• Delete -Admin

• Create Context Catalog Service UI to utilize the methods

Greg McChesney12

Life-Cycle Explained

• Context must be:– Stored locally by provider– Reloaded on provider restart– Saved on update/create– Return undefined service context on error

• Changes must be– Compliant with existing providers– Provide backup file in case of bad context

Greg McChesney13

Use Case Diagram Context Cataloger

Greg McChesney14

Component Diagram Context Cataloger

Greg McChesney15

Cataloger UI Component Diagram

Greg McChesney16

Greg McChesney17

Need for a Context Creation Panel

• No network-centric method for creating context for exertions

• No network-centric method for reusing a context for exertions

• No common graphical method of creating exertions with context directly from providers in SORCER– Each provider must have own GUI interface– Users must learn each providers interface

• Provide easier network-centric development of new services

Middle

Edit the Context?

• Why would we want to edit a service context before we launch the exertion?– The service context can often describe input

variables that are not static, editing it allows us to change them.

– Example: The AccountTester would be useless if you could not specify how much you were depositing or withdrawing.

Greg McChesney18

Use Case-Context Creation Panel

Greg McChesney19

Component Diagram-Context Creation Panel

Greg McChesney20

Context Creation Panel UI Component Diagram

Greg McChesney21

Feasibility Study

• Create the Context Cataloger provider to test Life-Cycle methods– Get Context– Add Context– Update Context– Delete Context

• Utilize provider from Air Force Research Center (Mealstrom) to validate context creation panel works as intended

Greg McChesney22

Feasibility Study

Greg McChesney23

Feasibility Study

Greg McChesney24

Feasibility Study

Greg McChesney25

Feasibility Study

Greg McChesney26

Feasibility Study

Greg McChesney27

Feasibility Study

Greg McChesney28

Greg McChesney29

Summary

• Benefits of Context Creation Panel– Simplified user interface– Less work for new provider creators

• In combination with a new Context Cataloger service will provide:– Complete Context Management– Exertion initiation

End

Schedule

• Literature Review

• System Requirements

• Life-Cycle context management model

• Architecture and detailed design

• LCSM prototype

• Thesis proposal presentation

• Framework Implementation End Of February

• Validation of Use Cases and deployment Early March

• Thesis Defense Mid March

Greg McChesney30

Greg McChesney