This document discusses system integration options for the Higher Education Management Information System (HEMIS) in Afghanistan. It provides an overview of HEMIS, noting that it currently has two functional modules. It then discusses the challenges of integrating the 10 new HEMIS modules being developed, as well as other related systems. The document explores two common integration architectures - hub-and-spoke and bus - and four levels of integration - data, application interface, method, and user interface. It aims to determine the most feasible integration approach for HEMIS given its modular development.

1. System Integration for HEMIS
(EAI)
Ghezal Ahmad Zia
Technical University of Berlin
August 11, 2016
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 1 / 43

2. Outline
1 HEMIS
Problem
2 What is System Integration?
The Integration Problem (i.e. Opportunity)
3 EAI Architecture
Hub/Spoke
BUS
4 EAI Types
Data Level
User Interface Level
Method Level
Application Interface Level
5 Conclusions
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 2 / 43

3. Forward
This presentation, represent the current situation of HEMIS,
Development of 10 Modules of HEMIS by ITCC, System
Integration of HEMIS which mostly focus on which architecture
and type of integration is feasible for HEMIS.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 3 / 43

4. HEMIS
The HEMIS (Higher Education Management Information
Systems) was established in 2008.[IT Conference]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 4 / 43

5. HEMIS
The HEMIS (Higher Education Management Information
Systems) was established in 2008.[IT Conference]
The goal of HEMIS is to improve management, data collection,
and analysis.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 4 / 43

6. HEMIS
The HEMIS (Higher Education Management Information
Systems) was established in 2008.[IT Conference]
The goal of HEMIS is to improve management, data collection,
and analysis.
Currently, two modules of HEMIS are functional.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 4 / 43

7. 11th IT Conference
On the 11th IT Conference, the concept of Module-based
distributed HEMIS was presented.[IT Conference]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 5 / 43

8. ACADEMIC
KANKOR
HEMIS
LMS
SMIS
Admtn
HR
Private
Universities
…
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 6 / 43

9. ACADEMIC
KANKOR
HEMIS
LMS
SMIS
Admtn
HR
Private
Universities
… extended
.
.
.
.
.
.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 7 / 43

10. ACADEMIC
KANKOR
HEMIS
LMS
SMIS
Admtn
HR
Private
Universities
… extended
.
.
.
.
.
.
Scholarship
Management
System
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 8 / 43

11. Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 9 / 43

12. 11th IT Conference
The ITCC (IT Competence Center of Afghanistan) started
developing 10 modules of HEMIS recently.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 10 / 43

13. Problem ...?
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 11 / 43

14. System development over the last 20 years has been tended to
emphasize core functionality as opposed to integration [iConexio]
Many systems are highly stovepiped and difficult to integrate with
other similar systems.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 12 / 43

15. ACADEMIC
KANKOR
HEMIS
LMS
SMIS
Admtn
HR
Private
Universities
…
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 13 / 43

16. What is System Integration?
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 14 / 43

17. What is System Integration?
Definition
It is the combination of processes, software, standards and hardware
resulting in the seamless integration of two or more enterprise systems
allowing them to operate as one. [EAI]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 15 / 43

18. The Problem
”70% of all code written today consists of interfaces, protocols,
and other procedures to establish linkages among various systems”
[IBM]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 16 / 43

19. The Problem
”70% of all code written today consists of interfaces, protocols,
and other procedures to establish linkages among various systems”
[IBM]
”30% of entire IT budget is spent on building, maintaining, and
supporting application integration” [FORRESTER]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 16 / 43

20. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

21. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Multiple platforms
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

22. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Multiple platforms
Multiple databases
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

23. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Multiple platforms
Multiple databases
Multiple transaction processors
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

24. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Multiple platforms
Multiple databases
Multiple transaction processors
Multiple data entry points
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

25. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Multiple platforms
Multiple databases
Multiple transaction processors
Multiple data entry points
Multiple versions of the same data
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

26. The Integration Problem (i.e. Opportunity)
Definition
Multiple, disparate applications
Custom
Legacy
Packaged
Multiple platforms
Multiple databases
Multiple transaction processors
Multiple data entry points
Multiple versions of the same data
Incompatible business data
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 17 / 43

27. EAI
Enterprise Application Integration or EAI, is a technical term
since the early 2000.
EAI is an approach, or more accurately, a general category of
approaches, to providing interoperability between the multiple
disparate systems.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 18 / 43

28. EAI Architecture
There are two basic architectures to achieve this.
[EAI-Architecture]
HUB/SPOKE
BUS
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 19 / 43

29. Hub/Spoke
Uses a centralized broker (Hub) and adapters (Spoke)
Spoke connect to application and convert application data format
to a format which Hub understands and vice versa.
Hub on the other hand brokers all messages and takes care of
content transformation/translation of the incoming message.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 20 / 43

30. Hub/Spoke
SMIS
AMIS DMIS
LMIS
PUMIS
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 21 / 43

31. Hub/Spoke
SMIS
AMIS DMIS
LMIS
PUMIS
Hub
Message
Broker and
Central
Integra:on
Engine
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 22 / 43

32. Hub/Spoke
SMIS
AMIS DMIS
LMIS
PUMIS
Hub
Message
Broker and
Central
Integra:on
Engine
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 23 / 43

33. BUS
Bus architecture uses a central messaging backbone (bus) for
message propagation.
Applications would publish messages to bus using adapters.
These messages would flow to subscribing applications using
message bus.
Subscribing applications will have adapters which would take
message from bus and transform the message into a format
required for the application.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 24 / 43

34. BUS
SMIS
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 25 / 43

35. BUS
SMIS
Adapter-1
+ Integra1on Engine
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 26 / 43

36. BUS
SMIS
Adapter-1
+ Integra1on Engine
PUMIS
Adapter-2
+ Integra1on Engine
LMIS
Adapter-3
+ Integra1on Engine
AMIS
Adapter-4
+ Integra1on Engine
SMIS
Adapter-5
+ Integra1on Engine
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 27 / 43

37. BUS
Bus – Messaging Backbone
SMIS
Adapter-1
+ Integra:on Engine
PUMIS
Adapter-2
+ Integra:on Engine
LMIS
Adapter-3
+ Integra:on Engine
AMIS
Adapter-4
+ Integra:on Engine
SMIS
Adapter-5
+ Integra:on Engine
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 28 / 43

38. BUS
Bus – Messaging Backbone
SMIS
Adapter-1
+ Integra:on Engine
PUMIS
Adapter-2
+ Integra:on Engine
LMIS
Adapter-3
+ Integra:on Engine
AMIS
Adapter-4
+ Integra:on Engine
SMIS
Adapter-5
+ Integra:on Engine
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 29 / 43

39. EAI Types
EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 30 / 43

40. EAI Types
• Data Level
01EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 31 / 43

41. EAI Types
+ The data is moved
from one data
store to another
and processes the
informa2on if
required.
+ There is no code
change which
saves the cost of
redevelopment.
• Data Level
01EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 32 / 43

42. EAI Types
+ The data is moved
from one data
store to another
and processes the
informa2on if
required.
+ There is no code
change which
saves the cost of
redevelopment.
• Data Level • Applica-on
Interface
Level
01 02EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 33 / 43

43. EAI Types
+ The business
process and data
is accessed
through the
interfaces with
this approach.
+ This approach is
mostly used with
the packaged
applica9ons.
+ Message brokers
are used as
preferred solu9on
+ The data is moved
from one data
store to another
and processes the
informa9on if
required.
+ There is no code
change which
saves the cost of
redevelopment.
• Data Level • Applica-on
Interface
Level
• Method
Level
01 02 03EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 34 / 43

44. EAI Types
+ The business
process and data
is accessed
through the
interfaces with
this approach.
+ This approach is
mostly used with
the packaged
applica9ons.
+ Message brokers
are used as
preferred solu9on
+ A method can be
accessed by many
applica9ons.
+ In this approach
we reuse the
business logic,
means reusing the
exis9ng
applica9on.
+ The data is moved
from one data
store to another
and processes the
informa9on if
required.
+ There is no code
change which
saves the cost of
redevelopment.
• Data Level • Applica-on
Interface
Level
• Method
Level
• User
Interface
Level
01 02 03 04EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 35 / 43

45. EAI Types
+ The business
process and data
is accessed
through the
interfaces with
this approach.
+ This approach is
mostly used with
the packaged
applica9ons.
+ Message brokers
are used as
preferred solu9on
+ A method can be
accessed by many
applica9ons.
+ In this approach
we reuse the
business logic,
means reusing the
exis9ng
applica9on.
+ Bundles the
applica9ons use
their user
interfaces
+ The mainframe
applica9ons can
be accessed
through this
approach.
+ Not preferred
approach.
+ The data is moved
from one data
store to another
and processes the
informa9on if
required.
+ There is no code
change which
saves the cost of
redevelopment.
• Data Level • Applica-on
Interface
Level
• Method
Level
• User
Interface
Level
01 02 03 04EAI Types
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 36 / 43

46. Integration on the Data Source Level [AI]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 37 / 43

47. Integration on the Business Logic Level [AI]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 38 / 43

48. Integration on the User Interface Level [AI]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 39 / 43

49. Level of Integration [AI]
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 40 / 43

50. Conclusions
The current developed modules of HEMIS has been explained.
The integration architectures and levels defined.
The role of adapter and its complexity
The easy and suitable integration level are proposed for HEMIS.
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 41 / 43

51. References
IBM
FORRESTER
https://go.forrester.com/
EAI
Tariq Rahim Soomro & Abrar Hasnain Awan
Challenges and Future of Enterprise Application Integration
11th IT Conference
ZiiK-Report Nr. 41
, Page 20 - 21
8th IT Conference
ZiiK-Report Nr. 31
, Page 23 - 24
Heiko Paulheim & Florian Probst
Application Integration on the User-Interface Level
Atul Apte
Adapters and EAI
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 42 / 43

52. Thank You
Ghezal Ahmad Zia (Technical University of Berlin) EAI August 11, 2016 43 / 43