Integration of Zachman Framework and TOGAF ADM on Academic Information Systems Modeling

Zachman Framework (ZF) and The Open Group Architecture Framework (TOGAF) are Architecture Frameworks often used in Architecture Enterprise's implementation. Each side of the two architecture Frameworks has advantages and disadvantages. Sekolah Tinggi Manajemen Informatika dan Komputer Muhammadiyah Paguyangan Brebes (STMIK MPB) is a new university established on April 28, 2017; STMIK MPB as a new university has no plans in building an information system. The research will select the parts that exist in the ZF and TOGAF methodologies. The two methods will be combined and compiled to be applied to the Academic Information System modeling or blended methods. These research results are architectural blueprints that can be used as a reference in the development of academic information systems. Keyword—Zachman Framework, TOGAF, ADM, Architecture, Enterprise Abstrak—Zachman framework (ZF) dan The Open Group Architecture Framework (TOGAF) merupakan Architecture Framework yang sering digunakan dalam penerapan Architecure Enterprise, masing-masing sisi dari kedua architecture Framework tersebut memiliki kelebihan dan kekurangan. Sekolah Tinggi Manajemen Informatika dan Komputer Muhammadiyah Paguyangan Brebes (STMIK MPB) merupakan perguruan tinggi baru yang berdiri pada 28 april 2017, dan STMIK MPB sebagai perguruan tinggi baru belum memiliki perencanaan dalam membangun sistem informasi. Penelitian ini akan memilih bagian-bagian yang ada pada metodologi ZF dan TOGAF, kedua metode tersebut akan digabungkan dan disusun untuk diterapkan pada pemodelan Sistem Informasi Akademik atau bisa disebut blended methodology. Hasil dari penelitian ini berupa blueprint Arsitektur yang dapat digunakan sebagai acuan dalam pembangunan sistem informasi akademik. Kata Kunci—Zachman Framework, TOGAF, ADM, Architecture, Enterprise INTENSIF, Vol.5 No.1 February 2021 ISSN: 2580-409X (Print) / 2549-6824 (Online) DOI: https://doi.org/10.29407/intensif.v5i1.14678 INTENSIF: Jurnal Ilmiah Penelitian dan Penerapan Teknologi Sistem Informasi 73


I. INTRODUCTION
The increasing need for business functions is one factor that encourages organizations to take advantage of information systems [1]. Today, many organizations, enterprises, and industries that implement information systems without planning to pay attention to momentary needs, the impact of all that information systems that are implemented are not running well, and there is overlap between systems that are not integrated. [2]. Such information system conditions cause the information system to not meet the organization's needs from the highest level to the lowest organizational needs, namely operational needs [3]. Today's use of information systems is part of strategic investment for organizations, enterprises, and industries [4]. Architectural Framework (DoDAF), and Zachman. Framework [5]. According to Wartika [6], The point of view of some of these methodologies has in common, namely :

Business Architecture
Business plan development, application utilization, technology, and implementation require a Business Architecture, which is needed as a foundation for other enterprise architecture components.
2. Data/Information Architecture An application system needs to manage data entities or manage information shows from the data/information architecture. It is an essential capital in supporting the business.

Application Architecture
Application architecture is deemed necessary to define what applications are needed to manage data and business support.

Technology Architecture
The technology architecture works to determine the application's technology platform, including hardware and software in managing data and business support.
Universities must own a reliable information system. Information systems are used to manage and improve the quality of academic programs and services [7]. Higher education must have an information system that can collect data, process data, analyze data, store data, retrieve data, and report data. It can be used as a means of communicating with interested parties. [8]. optimal. To optimize services, STMIK MPB is developing an information system. Building and developing information systems will be more comfortable if you follow a framework of thought with the term Enterprise Architecture (EA) framework [9]. In this case, it will be discussed how to integrate the Zachman Framework with TOGAF ADM in the STMIK MPB Academic Information System modeling.
According to Rully Pramudita [10], the perspective/layer from several developer points of view has not been seen in TOGAF ADM as in Table 1.  Phase A (vision architecture), 3 Phase B (business architecture), 4 Phase C (information architecture), Designer 1 Phase A (vision architecture), 2 Phase B (business architecture), 3 Phase C (information architecture), 4 Phase D (technology architecture) The relationship between the phases in the TOGAF ADM with the current perspectives in the Zachman framework, namely:

Planner
In the initial phase, vision architecture, business architecture, information architecture, and technology architecture required a planner's perspective to determine enterprise business objectives at the start.

Owner
The Zachman Framework Model, related to product requirements, service needs, and business needs, is described from the owner's perspective. So that in TOGAF ADM, determining the needs from vision, business, data, and enterprise applications require the owner's point of view.

Designer
The phases of vision architecture, business architecture, information architecture, and technology architecture require a designer's perspective to model the business context and business processes in detail. In this perspective, a technical design model is described, which is the basis for implementing information systems to the required computer network infrastructure.

Builder
The information architecture and technology architecture phase requires a builder's perspective to build an overall information system and computer network infrastructure by enterprise requirements. Because from the builder's point of view, it is related to the development of information systems architecture and technology based on predetermined design models.
The TOGAF ADM phases used in this study are the vision phase, the business phase, the information phase, and the technology phase. In contrast, the Zachman framework perspective used is a Planner, Owner, and Designer.

A. Data Collection
The data collection method was done qualitatively, namely, by conducting observations and interviews.
1. Observation is a process of observation to produce facts from human activities in a continuous and natural activity [11]. This method is done by coming directly to the research object to make observations and collect the necessary data related to the current academic system conditions.  [12], The FGD technique aims to obtain respondents' perceptions of a theme by the research objectives. Interviews were conducted with related parties with the academic section of STMIK MPB and the leaders of STMIK MPB. This method is used to ensure that the data obtained is by the facts.

B. Characteristics of Respondents
Determination of respondents in this study using a purposive sampling method. According to Ayu Sri Mahatma Dewi [13], purposive sampling takes samples based on predetermined considerations. Respondents consisted of 2 academic staff, two information system management units, two heads of study programs, and two leaders. The data was collected using a question and answer polling process to the eight respondents who had been determined.

A. Preliminary
The preliminary phase is from the perspective of the Planner and Owner in the Zachman  Main activities consist of: 1. Student admission: student admission is a process of new student registration activities, unique student selection, and new student data collection.
2. Academic Operations: A process of academic administration management activities from being accepted as a student until the student graduates from college.
3. Graduation or discharge of students is an activity related to the process of academic end or academic release.
Supporting activities consist of: 1. Human Resource Management: is a process that supports activities to determine the needs of higher education operational human resources.
2. Asset and infrastructure management: is the process of managing infrastructure activities starting from planning, maintenance, and disposal.  [15]. Figure 4 is a business process for conducting lectures; this business process is assisted by an information system based on the standard Business Process Modeling Notation (BPMN), a graphic notation that describes the steps in a business process. Business processes that are created should be evaluated to describe the current business process conditions and expected business processes.  One of the enterprise architecture stages is the data architecture in the information architecture, which is in the first column of the Zachman framework matrix and is part of the Information system Architecture phase in the TOGAF ADM phase. The first thing that must be done to define data architecture is to determine candidate data entities; entities are defined as places, concepts, people, objects, or events that have meaning (information) related to college academic business processes. Table 3 is an example of a candidate for lecture data entities.
After the candidate entity is defined, the entity is made a data architecture modeling described by the Entity-Relationship Diagram (ERD). According to Brady & Loonam [16], ERD is a model created and consists of collecting necessary objects called entities and describing relationships between entities used in the system. ERD models data structures and relationships between data. Realized entities have cardinality and participation. Cardinality (or degree of relationship) is the number of entities involved in the relationship.  The next step is to create a process vs. data entity metric; the Entity Matrix links the business processes data. Each part of the "CUR" in the matrix has the meaning C (created), which means a function to determine the created data entities, U (update), which means the part of updating and repairing, R (reference), which means the role can access data or use. The process that performs "C" implies "U" and "R." In contrast, the performing process "U" implies "R." This data architecture will show the data sharing by business functions. Then define the scope of future information systems and link applications to tasks that can create a sequence of application implementations. Table 4 is an example of process metrics vs. course data entities. is an area or data with strong linkages with the business process or functional area. Besides, some of the information that is out of parts in shading is the data that is irregular due to the distribution process using data that are not clumped part relationship thick outside the box shows the level of data sharing on business.  Then the System/Function Matrix stage aims to connect applications with defined business functions. This stage seeks to identify business functions that are directly supported or performed by the application. With data orientation, cross-mapping between applications against data entities takes precedence. It can be done using a process vs data entity matrix.
The grouping of matrix cells for application identification is applied by prioritizing cells that contain lots of "CUR", then with "UR" and "R" cells as the last priority. This priority is based on the essential applications that are used to support business processes in generating data. The sample results from the application vs. business function matrix are listed in Table   5.    The resulting technology architecture is only conceptual. It cannot be used as a measure of needs but only provides an overview that needs to be reviewed when implemented.

IV. CONCLUSION
The resulting Enterprise architecture results from integrating the Zachman framework and TOGAF ADM by paying attention to the relationship between each perspective in the Zachman