Service Context Management for Exertion-oriented Programming Session #, Speaker Name Service Context Management for Exertion-oriented Programming Greg McChesney Thesis Proposal Presentation Computer Science, TTU Greg.mcchesney@ttu.edu 4/4/2019

Overall Presentation Goal or Primary Purpose Create a life-cycle for context management in Exertion-Oriented Programming Greg McChesney Beginning

Session #, Speaker Name 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 Greg McChesney Beginning 4/4/2019

Speaker’s Qualifications Session #, Speaker Name 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 Greg McChesney Beginning 4/4/2019

Session #, Speaker Name Did you know? There is no network-centric methodology for creating service contexts in the SORCER environment. Contexts can be created in code but there is not currently a way to create them using network applications Greg McChesney Beginning 4/4/2019

Presentation Agenda Background knowledge What is a service context? Session #, Speaker Name 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 Greg McChesney Beginning 4/4/2019

Background Knowledge Many different Exertion-Oriented (EO) Systems Session #, Speaker Name 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 McChesney 4/4/2019

All About Contexts A service context is a basic data structure in SOOA Session #, Speaker Name 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 SOOA-Service Object-oriented Architecture. Greg McChesney 4/4/2019

Sample Context Session #, Speaker Name Greg McChesney Image courtesy of Dr. Sobolewski 4/4/2019

Need for a Life-Cycle Two roles Provider Requestor Session #, Speaker Name 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 Two roles in SORCER environment, the providers who provide a service the requestors who use it. The providers have the following issues The requestor has the following issues: Greg McChesney 4/4/2019

Need for a Life-Cycle Requestor Session #, Speaker Name 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 The requestor side will be handled by the newly created Context Cataloger. DISCUSS SCALABLITY IN SORCER! Greg McChesney 4/4/2019

Session #, Speaker Name 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 Discuss interactive editing of these contexts as part of new context catalog Greg McChesney 4/4/2019

Life-Cycle Explained Context must be: Changes must be Session #, Speaker Name 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 McChesney 4/4/2019

Use Case Diagram Context Cataloger Session #, Speaker Name Use Case Diagram Context Cataloger USE CASES!! Not METHODS! Greg McChesney 4/4/2019

Component Diagram Context Cataloger Session #, Speaker Name Component Diagram Context Cataloger Component diagram shows the interaction between the various layers. Greg McChesney 4/4/2019

Cataloger UI Component Diagram Session #, Speaker Name Cataloger UI Component Diagram Describe model-view-controller Separates business logic from user interface. Model represents the data View is the user interface and client facing end Controller is the logic that handles events from the view and processes them to determine which data from the model should be selected and which views need to be updated. Controller handles user interaction Greg McChesney 4/4/2019

Need for a Context Creation Panel Session #, Speaker Name 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 Greg McChesney Middle 4/4/2019

Session #, Speaker Name 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 McChesney 4/4/2019

Use Case-Context Creation Panel Session #, Speaker Name Use Case-Context Creation Panel Greg McChesney 4/4/2019

Component Diagram-Context Creation Panel Session #, Speaker Name Component Diagram-Context Creation Panel Greg McChesney 4/4/2019

Context Creation Panel UI Component Diagram Session #, Speaker Name Context Creation Panel UI Component Diagram Greg McChesney 4/4/2019

Session #, Speaker Name 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 McChesney 4/4/2019

Session #, Speaker Name Feasibility Study Greg McChesney 4/4/2019

Session #, Speaker Name Feasibility Study Greg McChesney 4/4/2019

Session #, Speaker Name Feasibility Study Greg McChesney 4/4/2019

Session #, Speaker Name Feasibility Study Greg McChesney 4/4/2019

Session #, Speaker Name Feasibility Study Greg McChesney 4/4/2019

Session #, Speaker Name Feasibility Study Greg McChesney 4/4/2019

Summary Benefits of Context Creation Panel Session #, Speaker Name 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 Greg McChesney End 4/4/2019

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 McChesney

Session #, Speaker Name Greg McChesney 4/4/2019