Design Patterns in Enterprise Application Integration for e Learning Arena

Transcription

1 Design Patterns in Enterprise Application Integration for e Learning Arena

2 Outline Key Terms Introduction Learning Management System Challenges / Motivation Proposed Solution Enterprise Application Integration Model View Controller Imitating MVC Enhancing Controller to form ESB Dependency Injection Enhancing DI Pattern to form ESB Conclusion Future Scope References 2

3 Key Terms Learning objects in open scalable architecture Design Patterns e Learning Learning Management System Enterprise Application Integration Service Oriented Architecture Model View Controller Dependency Injection Enterprise Service Bus Aspect Oriented Programming 3

4 e Learning Introduction Web based products and services designed to support individual teams and organizational learning [1] Advanced over the years Improving technologies Cloud Computing and Web technologies High speed computing devices Social Networking Generations 1 st : Structured learning (Instructor driven) 2 nd : Free flow (Learner driven) 4

5 Learning Management System Classroom oriented learning to LMS Facilitates exchange of tools, functionality, semantics, and learning workflow No restriction on physical time and location Customization of content Managing course and knowledge effectively Handling resources Assessment/Grading of users/students 5

6 Challenges / Motivation Increase in demand of e Learning Managing learning objects in open and scalable architecture Scalable technologies with support of multiple users Personalized and customized learning environment Avoid expensive process of reinventing, rediscovering, and revalidating software Proposed Solution Design based approach Imitating MVC design Extending controller(mvc) to form an ESB Enhancing DI pattern in controller to form an ESB 6

7 Enterprise Application Integration Lack of communication for sharing data between SCM, CRM, etc., in an enterprise, leading to inefficiency, redundancy and no automation in process EAI: Process of linking such applications to simplify and automate business processes Composed of collection of technologies to form a middleware to enable integration of system and application 7

8 Model View Controller Software design for interactive computer user interface Separates representation from user interaction Application data and business rules Closed Loop. View Updates from Model Output Represen tation Original MVC Design Pattern [1] Mediates input. Converts commands for model and view 8

9 Imitating Model View Controller Collaborates reusable services in model wrapped inside the controller Removes direct link between Model and View. Reorganizes the controller Acts as a single point of contact Acts as centralized container (Invoke service) DAO: Transfer state of data from DBL and BLL Redefined MVC Design Pattern [1] 9

10 Enhancing Controller to form ESB Software architecture model, used for designing and implementing interaction and communication between mutually interacting software applications in SOA iii viii i ix vi vii v iv ii Enterprise Service Bus Collaboration in MVC design pattern[1] 10

11 Enhancing Controller to form ESB View: Issues a high level request Solve Taylor Equation (i) View: Provide input data (i) ESB: Contains service mapping information for solving in Service Registry and Repository (vi) Model: Services are deployed and maintained (ii) ESB: Composes end point services required to execute Advantage: No need of Universal Description Discovery and Integration (UDDI) registries. View: Does not need to know endpoint services Increases service interoperability and reusability 11

12 Dependency Injection Hides implementation from interface Enables client to consume service without knowing origin External mechanism to pass dependent objects (Injection) Removes dependency from implementation of BL Formula Engine that sets and processes any Mathematical Formulae Dependency Injection Pattern[1] 12

13 Enhancing DI pattern to form ESB Implemented in SOE Integration components (Client): Transformations and service virtualization are registered in SOE Integration components declares dependencies (interface) implemented by implementer component present in SOE Integration Component Mapping Table [1] Composite Key Dependency Implementer Mapping Table [1] 13

14 Enhancing DI pattern to form ESB i ii iii iiia iiib iiic iiid iiie Algorithm for DI implementation in Controller SOE[1] 14

15 Enhancing DI pattern to form ESB Converts from one type to other Acts as Assembler Example of Dependency Injection in Java for Data Transformation [1] 15

16 Conclusions Integration logic becomes independent DI pattern benefits software development Integration components can be developed, deployed, tested, and replaced independently DI enables ESB to grow/shrink DI as plug points of application framework ESB can be used for effective EAI e learning Future Scope Introduce AOP methodologies in ESB on top of DI Pattern 16

17 References [1] Rajam, S., Cortez, R., Vazhenin, A., Bhalla, S. Dec Design Patterns in Enterprise Application Integration for e Learning Arena. In Proceedings of the 13 th International Conference on Humans and Computers.UniversityofAizuPress Fukushima ken, Japan Thank You 17