Mining Minds Platform Open Source Presentation Service Orchestrator - PowerPoint PPT Presentation

SCL Service Orchestrator Mining Minds Platform Open Source Presentation Service Orchestrator is released as a part of Recommendation Builder ( RB ) and Recommendation Interpreter ( RI ). The open source 10 step process can be observed in the RB and RI open source presentations.

Open Source Release Process - Roadmap 2 / 1 2 3 4 Library Code Code S Unit Testing Functions Review Refactoring 5 6 Integration API Design Testing 9 8 7 Build Demo Harness API Documentation Creation 10 Open Source E Release

Open Source Release Process - Roadmap 3 / • Service Orchestrator is released as a part of Recommendation Builder ( RB ) and Recommendation Interpreter ( RI ). • The open source 10 step process can be observed in the RB and RI open source presentations. • In following slides, an overview of the packages, classes, and code of overall SCL particularly the service orchestrator is provided.

SCL Communication- Service Orchestrator 4 / User App Uid 13 Uid, Request 10 Uid, Context, preferences 1 Uid, Situation Event Recommendation Recommendation Service 2 Uid, Recommendations Builder Interpreter Uid, Data Request Orchestrator 5 Rule-based Reasoner Interpretation 9 Event Input/output 8 Handler Adapter 12 Pattern Conflict Result Context Content Explanation Matcher Uid, Data Resolver Generator Interpreter Interpreter Generator Uid, Context Uid, Data Request 7 1 Set of Rules Situation Event 3 5 14 Uid, Situation Event Uid, Data 11 6 Uid, Personalized Recommendation Uid, Context RESTful Web Services RESTful Web Services Index- RESTful Web Services based Reasoning KCL SL (UI/UX) DCL Rule Index RESTful Web Services Rule-base base

SCL Package Distribution 5 / 3 17 Service Orchestrator 22 16 Packages 7 12 2 8 Recommendation 9 Builder 7 10 6 10 4 Recommendation 2 Interpreter 112 Classes 1 3 2 2 6

SCL Logical Structure 6 / SCL Service Communication Logic Modules Utilities Service Recommendation Recommendation Orchestrator Builder Interpreter

class kr.ac.khu.uclab.mm.scl.logicmodules T : Class SCL Logic Module Design T : Class «interface» / U : Class «singleton» V : Class RecommendationLogicModuleInterface RuleBaseReasoner «abstract» + execute(T) :T + getPhysicalActivityReasoner(LogicModuleReasonerEnum) :void RecommendationFactsPacket + interprateRecommendation(T) :T + getRuleBaseReasoner() :RuleBaseReasoner # factsOutput :V # recommendationInput :T # recommendationOutput :U SCL logic modules implements two-level bridging + getFactsOutput() :V < T->RecommendationFactsPacket > + getRecommendationInput() :T T : Class > «abstract»RecommendationFactsPacket + getRecommendationOuput() :U + setFactsOutput(V) :void + setRecommendationInput(T) :void «abstract» + setRecommendationOutput(U) :void AbstractRecommendationBuilder + execute(T) :T Recommendation Level 1 bridging + interprateRecommendation(T) :T Interface < T->RecommendationIngredients, U->PhyActivityRecommendations, V->PhyActivityFacts > PhysicalActivityRMLRecommendationFactsPacket < T->PhysicalActivityRMLRecommendationFactsPacket > + getFactsOutput() :V + getRecommendationInput() :T + getRecommendationOuput() :U + setFactsOutput(V) :void Level 2 bridging Abstract RB Abstract RI PhysicalActivityRML + setRecommendationInput(T) :void + setRecommendationOutput(U) :void + execute(T) :T Implementation T : Class Implementation V : Class RI RB «abstract» < T->ExceptionPacket > ExceptionPacket # exceptionOutPut :V T : Class > «abstract»ExceptionPacket # interpretationIngredients :T + getExceptionOutPut() :V AbstractRecommendationInterprater + getInterpretationIngredients() :T + setExceptionOutPut(V) :void + execute(T) :T + setInterpretationIngredients(T) :void + interprateRecommendation(T) :T Abstract Packet Design Pattern Packet < T->InterpretationIngredients, V->PhyActivityException > - An example of Observer < T->PhysicalActivityIMLExceptionPacket > design pattern PhysicalActivityIMLExceptionPacket - It separate the logical module PhysicalActivityInterpretationManager + getExceptionOutPut() :V Implementation to know the semantics of the + getInterpretationIngredients() :T + interprateRecommendation(T) :T + setExceptionOutPut(V) :void Packet data + setInterpretationIngredients(T) :void

Service Orchestrator: Communication Design / Communication structure is based on three design patterns Bridge Pattern • For flexibility of adding new clients Factory pattern • For object instantiation control Facade pattern • For outer world communication Singleton pattern • For ensuring single instantiation of an object

Service Orchestrator: Sample Package/Classes 9 / Package org.uclab.scl.communication.dcl This is an implementation class of This class provides the abstraction abstract DCL client that implements to communication of SCL with DCL current context client

Service Orchestrator: Sample Package/Classes 10 / Package org.uclab.scl.communication.dcl Code Excerpt

Service Orchestrator: Sample Package/Classes 11 / Two way communication through restful service/ clients. GetData PostData

12 / Thanks