Information Search and Analysis Skills

(ISAS)
Modeling Integration in ISA

Faculty:
Mr. Hudya

Written By:
Ardian Iqbal Yusmartito
Moch Ramdhani Ali Syahbana

Class:
3SC3

Continuing Education Program on Center for Computing and Information Technology

Faculty of Engineering, Universitas of Indonesia
Kampus Baru UI Depok 16424
 PREFACE

First of all, we want to thanks to Allah SWT because of his bless and grace, the
entitled “Service Oriented Architecture” can be finished on time as ISAS requirements 2021.
The paper is a requirement to fulfill the assignment from Mr. Hudya, as our faculty.
And we also thanks to him for all the guidance to complete it.
We hope this paper can be usefull to all people and increase knowledge for all of us.
We realize that this paper is still far from perfect in the arrangement or in the content of
paper. We hope that the suggestion from all of you can be a support to make us better in the
next ISAS.
Finally, we expect that it can be a medium for the reader to deepen the knowledge
about Modeling Integration in ISA

Bogor, September 19th 2021

Authors

ii | P a g e
 TABLE OF CONTENTS

PREFACE ........................................................................................................................ i
TABLE OF CONTENT .................................................................................................. ii
TABLE OF FIGURE ...................................................................................................... iii
CHAPTER I INTRODUCTION ................................................................................... 1
I.1 Background......................................................................................... 1
I.2. Writing Objective ............................................................................... 1
I.3. Problem Domain ................................................................................. 1
I.4. Writing Methodology .......................................................................... 1
I.5. Writing Framework ............................................................................. 2
CHAPTER II BASIC THEORY .................................................................................... 3
II.1 What is Modeling Integration ............................................................. 3
II.2. Conceptual data integration model ..................................................... 4
II.3. Overview of Information System Architecture ................................... 4
II.4. What Is Modeling Integration in ISA .................................................. 5
CHAPTER III PROBLEM ANALYSIS ......................................................................... 7
III.1. Integration IT Levels .......................................................................... 7
CHAPTER IV CONCLUSION AND SUGESTION ..................................................... 11
IV.1 Conclusion .......................................................................................... 11
IV.2. Sugestion ............................................................................................ 11
BIBLIOGRAPHY .............................................................................................................. 12

iii | P a g e
 TABLE OF FIGURES

Figure 2.1 Bagan SOA ................................................................................................... 3

Figure 2.2 Service Request ............................................................................................ 4
Figure 2.3 Basic Component ......................................................................................... 5
Figure 2.4 SOA and Web Service .................................................................................. 5
Figure 2.4a Implementasi SOA ...................................................................................... 6
Figure 3.1 How to SOA Work ........................................................................................ 7
Figure 3.2 Framewowrk layer SOA ............................................................................... 8
Figure 3.3 Structure SOA ............................................................................................... 9

iv | P a g e
 CHAPTER I
INTRODUCTION

I.1. Background
Integration between software components has always been a fundamental part
of any information system. Recently, its importance has been growing due to the need
of integrating diverse information systems, both within and between organizations.
The move towards ERPs(Enterpriese Resource Planning) in the last 10 years has not
reduced the need for integration, but it has even increased it. And integrating diverse
information systems to react online to external events is a necessary condition for e-
business.
[ CITATION Kal00 \l 1033 ]
A system architecture is the conceptual model that defines the structure,
behavior, and more views of a system. An architecture description is a formal
description and representation of a system, organized in a way that supports reasoning
about the structures and behaviors of the system
Information system architectures (ISAs) have not paid sufficient importance to
integration because they assume that enforcing the existence of a single database
eliminates the need for integration.
I.2. Writing Objective
The purpose of ISAS regarding Modeling Integration in ISA is to understand
what is Meant of Modeling Integration.
I.3. Problem Domain
The ISAS that we created will discuss problems that can be solved with the
Modeling Integration in ISA works, and why this is so .
I.4. Writing Methodology
The writing method that we use is a method of literature study, which is the
collection of materials to be used and then analyzed from trusted sources.

5|Page
I.5. Writing Framework
To facilitate writing of the ISAS, this discussion was organized into systematic
as follows :
 Chapter I Introduction
In chapter I will discuss about background, writing objective, problem
domain, writing methodology used, and writing framework about this ISAS.
 Chapter II Basic Theory
In Chapter II will be discussed about Modeling Integration Information
System Architecture
 Chapter III Problem and Analysis
In chapter III this will discuss about why Modeling Integration in ISA so
important and implementation about Modeling Integration.
 Chapter IV Conclusions and Suggestions
Chapter IV contains the conclusions obtained from the analysis of Modeling
Integration and can provide suggestions to readers why we need to apply Modeling
Integration in ISA.

6|Page
 CHAPTER II
BASIC THEORY
II.1. What is Modeling Integration
Modeling Integration or Integrated Modeling  is a term used for a type
of scientific modelling that tries to link main features of society and economy with the
biosphere and atmosphere into one modelling framework.
[ CITATION Cla09 \l 1033 ]

Integrated modeling systems provide support for the definition, manipulation,

and control of mathematical models throughout the entire modeling life cycle. Model
integration is a particularly crucial operation which requires thinking about “modeling
in the large”, and which extends the scope of model management research to include
manipulation as well as definition. Several aspects of model integration are identified
and briefly described with respect to the problems they raise for constructing
integrated modeling environments. Relevant work in these areas is cited. A brief
introduction to each of the papers in this special issue is provided within the context
established.

Different types of graphs are widely used to represent many types of

management science models. Examples include vehicle routing, production planning,
simulation and decision trees. In previous work, the author has developed tools and
techniques based on graph-grammars to provide interfaces for such models. In this
paper, we explore several such models with particular emphasis on integrating
different graph-based models within a single environment. It is shown how the
environment can combine a variety of visual models in different ways.

II.2. Conceptual Data Integration Models

A conceptual data integration model is an implementation-free representation
of the data integration requirements for the proposed system that will serve as a basis
for “scoping” how they are to be satisfied and for project planning purposes in terms
of source systems analysis, tasks and duration, and resources.
At this stage, it is only necessary to identify the major conceptual processes to
fully understand the users’ requirements for data integration and plan the next phase.

7|Page
Figure 2.1 Conceptual data integration model example (Reff:
https://searchdatamanagement.techtarget.com/tutorial/Using-logical-data-models-for-data-
integration-modeling)

II.3. Overview of Information System Architecture

The Information System Architecture (or ISA, for short) represents the
structure of the components, their relationships, principles and directives with the
main purpose of supporting business.
[ CITATION Mae00 \l 1033 ]
In the 80s, a software architecture and ISA were considered synonymous. But
in the 90s emerged the need for manipulating concepts that exceeded the description
of how a system was internally built. The Zachman Framework can be considered the
first important signal that software architectures were not enough.
[ CITATION Zac87 \l 1033 ]
While software architectures represent internal system details (using, for
example, E-R and DFD diagrams) ISA focus on the high-level business processes .
Using the “city” as a metaphor, we can use the concept of “IS urbanization” to
emphasize the need for models to guide the evolution of IS independently of current
technological trends.
[ CITATION Sas98 \l 1033 ]
An ISA can be divided into three levels:
• Informational (or Data) Architecture – represents main data types that support
business;
•Application Architecture – defines applications needed for data management and
business support;
• Technological Architecture – represents the main technologies used in application
implementation and the infrastructures that provide an environment for IS deployment
[ CITATION Spe92 \l 1033 ]

8|Page
II.4. What Is Modeling Integration in ISA
The Modeling Integration in Information System Architecture is referred to
Architecture of Integrated Information System or usually called ARIS.
The ARIS concept (Architecture of Integrated Information Systems) by August-
Wilhelm Scheer aims to ensure that an enterprise information system can completely
meet its requirements.
This framework is based on a division of the model into description views and
levels, which allows a description of the individual elements through specially
designed methods, without having to include the entire model. The methodology
serves as a systems development life cycle for mapping and optimizing business
processes. These processes are mapped for each description view, starting with the
business management question up to the implementation on data processing level.[1]
[ CITATION Dir11 \l 1033 ]

Figure 2.2 ARIS_Model (Reff: https://en.wikipedia.org/wiki/File:ARIS_Model_EN.svg)

ARIS relies mainly on its own five-view architecture (ARIS house). These five views are the
organizational, data, service, functional and process views of a process. The classification is
made to break down the complexity of the model into five facets and thus make business
process modeling simpler.
Each view of the ARIS concept represents the model of a business process under a specific
aspect:

 Function view: The activities and the groupings and hierarchical relationships that
exist between them are described in the function view, for example in a function
tree.[2] Since functions support goals and are controlled by them, goals are also
assigned to the function view
 Organization view: It provides an overview of the organizational structure of a
company, including human resources, machines, hardware and their relationships,
see also Organizational chart
 Data view: All events (that generate data) and environmental data, such as
correspondence, documents, etc., i.e. all company-relevant information objects,
see also Entity Relationship Model

9|Page
 Product/Service view: Provides an overview of the entire product/service
portfolio (incl. services, products, financial)
 Process view: The process view connects all other views into a time-logical
schedule, for example in an event-driven process chain or BPMN

10 | P a g e
 CHAPTER III
PROBLEM ANALYSIS
III.1. Integration IT Level
The integration process can be divided into three parts (represented bellow in
Figure 3.1): a source (the system that calls the service or sends the message), a target
and the integration port itself representing the relation between source and target. At
the IT level we propose to split the characteristics associated exclusively to the
source, target, and those associated to the relation.

Figure 3.1 Integration Process(Reff:www.google.com)

Considering only the characteristics associated exclusively to the system

(source or target), the integration can be described along two dimensions:
• Automation Level – the integration services executed in the source or target
system are accomplished Automatically (no human interference) or Manually
(implies human interaction);
• Role Type – the system may be the source or the target of data. For example, in a
web service, the source is the client; in a messaging product, the source is the IS
sending the message.
we propose that IT integration should be adopted as a novel concept to
encapsulate both the platform (e.g., J2EE, .Net, CORBA, etc.) and/or the IT
Application. Figure 4 presents our proposed

11 | P a g e
Figure 3.2 Proposed UML extension for modeling integration concepts in ISA
(Reff:www.google.com)

Figure 3.3 presents the attributes proposed above for the IT Integration Block UML
stereotype (in detail).

Figure 3.3 IT Integration Block in detail

The IT Integration Block is not further specialized to accommodate the large

diversity of concepts and the continuously progression in this area. However,
depending on the objectives and the target audience, the IT Integration Block can be
specialized to model integration specific concepts such as message broker,
WebServices, and so on. The case study, presented in the next section, exemplifies
these issues.
The IT Integration Service can be used to model the relation port of the
integration process as presented in Figure 3.1. We propose this component be
characterized in terms of:
• Technological Level –if integration takes place inside a computer, inside an Intranet,
inside an Extranet, or on the public Internet.

12 | P a g e
 • Synchronism Level – integration between IT Blocks may occur synchronously (as in
RPC, for example), or asynchronously (usually with no reply, scalable and with
higher performance).
• Organizational Level – distinguishes integration between a department, inside an
enterprise, inside an holding, inside a value chain, or between two (or more) unrelated
organizations.

Figure 3.4 presents the proposed UML extensions in detail

Figure 3.4 IT Integration Service (Reff:www.google.com)

13 | P a g e
 CHAPTER IV
CONCLUSION AND SUGGESTION

IV.1. Conclusion
A system architecture is the conceptual model that defines the structure,
behavior, and more views of a system. An architecture description is a formal
description and representation of a system, organized in a way that supports reasoning
about the structures and behaviors of the system.
System integration brings together component sub-systems into one functional
system. It ensures that all components work together in harmony to preserve
productivity and accurate data analysis.

IV.2. Suggestion
Modeling Integration is a mandatory thing that needs to be made to take into
account a business framework in a company, especially a pioneering company that
builds from scratch. In addition, building an integration model can make the design
steps for the future clearer in the development process.

In the information system architecture, this modeling integration can be a

guideline to make this architectural system more relevant with the aim of saving
company costs by removing unnecessary things and knowing the performance of the
product made is very good.

14 | P a g e
 Bibliografi

https://en.wikipedia.org/wiki/Integrated_assessment_modelling#cite_note-clarke-etal-
2014-1

https://en.wikipedia.org/wiki/Architecture_of_Integrated_Information_Systems

https://www.researchgate.net/figure/Model-based-Integration-
Framework_fig6_228350945

Maes, Rik, Daan Rijsenbrij, Onno Truijens, and Hans Goedvolk, Redefining Business – IT
Alignment Through a Unified Framework, White Paper, May 2000.
http://www.cs.vu.nl/~daan/

Zachman, John, A Framework for Information System Architecture, IBM System Journal
Vol.26 Nº 3, 1987, p.276 – 292.

Sassoon, Urbanisation des systèmes d’information, 1998 (in French).

Spewak, Steven, and Steven Hill, Enterprise Architecture Planning: Developing a Blueprint
for Data, Applications and Technology, Wiley-QED, ISBN 0-471-599859, 1992.

Kalakota, Ravi and Marcia Robinson, E-Business 2.0, Addison-Wesley Longman,

Incorporated, 2000

https://searchdatamanagement.techtarget.com/tutorial/Using-logical-data-models-for-data-
integration-modeling

15 | P a g e