Systems Architecture and

Technology Integration -
IT8x19
ASSIGNMENT 1
Systems Architecture and Technology Integration - IT8x19

TABLE OF CONTENTS
TOPICS PAGE
NO.

Introduction ……………………………………………………………………………………………………….02
Types of Enterprise Architecture Methodologies
Zachman Framework.………………………………………………………………….………. 03
TOGAF………………………………..………………………………………………………………… 04
FEA Framework ……………………………………………………………………………………………… 05
CASE STUIDY
Introduction………………………………………………………………………………………………………. 06
Objective ………………………………………………………………………………………………. 07
Enterprise Integration Using Zachman Framework .……………………………………………
07
Integration of communication process……………………………………………………..07
Mapping data into Zachman Model………………………………………………………. 08
Conclusion ………………………………………………………………………………………………….……. 09
References ………………………………………………………………………………………………………… 10
10

Student No. 2200005 Page 2

Systems Architecture and Technology Integration - IT8x19

INTRODUCTION

Enterprise architecture is a practice that has been around for almost 20 years EA sets out a
blueprint for a successful IT strategy and directs IT's controlled evolution in a way that provides
cost-efficient business benefits. (Sousa et al., 2007).
EA defines the key business, information, application, and technology strategies and their impact
on business functions. It also integrates each of these strategies into a coherent framework.

ENTERPRISE ARCHITECTURE

Business Architecture

Information System Architechture

Information Application
Architechture Architechture

Technical Architechture
Product Architechture

Figure1. Architecture Relationship (Pereira & Sousa, 2004)

Business architecture is the source for determining requirements for IS which help business
activities. Application architecture offers a structure based on designing and executing business
specifications applications and achieving the quality necessary to meet business needs. The Data
Architecture discusses both the physical and conceptual dimensions of the data and the data
resource management. This is the result of developing the knowledge required to sustain the
enterprise's processes and functions.
The technological architecture defines and prepares the computing resources which form the
business' technical infrastructure. Technical architecture offers a structure to support other 3
architectural levels. Product Architecture is a subclass of Technical Architecture which defines
requirements and configurations for enabling technical architecture technology and products.

TYPES OF ENTERPRISE ARCHITECTURE METHODOLOGIES

The EA frameworks of today fall into a few types:

1. Zachman Framework

Student No. 2200005 Page 3

Systems Architecture and Technology Integration - IT8x19

The Zachman Framework is a structure and not a methodology that how various theoretical
concepts from different viewpoints are presented. Its 2D matrix comprises of 6 rows
(perspectives) and columns (foundational concerns), its interwoven cells illustrating in a detailed
and organized manner manifestation of the organization. The approach allows for the distillation
of complex subjects in the column headers into hierarchical categories, using these six simple
questions (known as 5WH). These questions will be answered differently, depending on the
viewpoints (represented in the rows).

Figure2. The Zachman Framework (Zachman, n.d.)

Benefits and Challenges

The benefits of the Zachman Framework Approach provide an efficient classification matrix that
offers broad coverage to all stakeholders interested in enterprise architecture. The drawbacks of
the approach include a lack of accuracy and a large requirement for the generating document.

2. TOGAF - The Open Group Architecture Framework

The TOGAF approach has a broad terminology and is intended to support multiple stages of
architecture for smaller as well as larger firms. It is developed for the rapid development of
architecture (Architecture Development Method or ADM) is a one-by-one process describing ten
phases organized in a loop. Requirements Management at the heart of the method-a stage that

Student No. 2200005 Page 4

Systems Architecture and Technology Integration - IT8x19

illustrates the gradual process of associating changes and specifications with each step.

Figure3. TOGAF Architecture Framework(TOGAF | The Open Group, n.d.)

Benefits and Challenges

It helps in planning and establishing accurate and refined development strategies. It also provides
a clear methodology for enterprises and organizations to reach from point A to point B
effectively. However, the repository structure within TOGAF is not well defined. Referring to
the TOGAF Enterprise Continuum and Architecture Repository segments, such areas are not
really effective because of the lack of depth and practical uses. TOGAF has defined 75 +
artifacts (deliverables, matrixes, catalogs, and diagrams) that do not include a single template
about any of them(TOGAF Strength and Weaknesses, n.d.).

3. FEAF- Federal Enterprise Architecture Framework

Federal Enterprise Architecture Framework (FEAF) – an architectural framework intended by
the Federal Council of the United States of America in 1999 for practical use within the
Government of the United States(AbuZail, 2015). It offers a standard approach to combine
strategic, financial, and technology management as way of organizational design and improving
performance.

Student No. 2200005 Page 5

Systems Architecture and Technology Integration - IT8x19

They aim at encouraging cross-department cooperation and identifying duplicative spending,

differences and shared opportunities within and between agencies. Architecture can be
subdivided into architectures below:
 Business Architecture: what, how, when, why and by whom
 Data Architecture: Data that the Organization uses to do business.
 Application architecture: Applications/software that manages data as per specified
business rules.
 Technology Architecture: technology that supports the above three levels.

Figure4. Federal Enterprise Architecture Framework (FEAF - Enterprise Architecture, n.d.).

Such interlinked "reference models" that define the domains of the Framework like Enterprise,
Information, Applications, Infrastructure and Security. Moreover, by adopting reference models,
entities can build a peripheral vision from the objectives at the highest official level to the
software and hardware systems to permit such goals.

Benefits and Challenges

FEA had been the backbone of a high-end government's major transformation, so the framework
is a good core to follow when creating a strong base for a potential business. However, it does
not explain how to formulate an EA transition plan and best practices.

CASE STUIDY: USING ZACHMAN FRAMWORK

Introduction
KITA is a leading company in tailored Products and services in Indonesia. the HR Department in
kita was receiving more no of job availability which had made the process a lot more tedious and
time-consuming(Journal & Ranggadara, n.d.). Company to find the best potential employee has
to go through the huge number of applicants to find a suitable candidate. HR staff seeking
assistance that will enable them to streamline and speed up the process while at the same time
helping them to recruit talent(nitmansub, 2014). This resulted the HR person in charge to
develop an online recruitment system solution for recruitment.

Student No. 2200005 Page 6

Systems Architecture and Technology Integration - IT8x19

Objective
Designing the recruitment system module in the HRIS application with the Zachman framework
work and mapping the design in the Zachman Framework Matrix.

Enterprise Integration Using Zachman Framework

The company has chosen the Zachman framework because of its comprehensive framework,
which includes a lot of perspectives that should be noted when implementing the integration of
the enterprise(Abbas et al., 2019). The recruitment system is viewed from the perspective of the
owner and planner which is described according to the Zachman matrix.
Perspective HR Manager (Owner) IT Manager (Planner)
Asset Data ( What ) Hiring Process Server, Database and Resources
Motivation (Why) Objective of Recruitment Reason for application needs
System
Function Process Manual communication(use System Interaction
(How) case)
Person in Charge Recruiter and Applicants Operator CRM Module
(How)
Location (Where) Core System Application HRIS Application
Time (When) Project Duration Time Schedule
Figure5. Zachman Framework (Row) based on Recruitment Process (Journal & Ranggadara,
n.d.).

Using the Zachman system, the study developed an organizational integration model for the
recruitment system module after data was obtained and analyzed. Tables 5 above define the
description in the Zachman context against the case study background and the recruitment
system scope.

Integration of communication process

There are processes involved in the Recruitment system. From the Owner's (HR) perspective, the
applicant must first login/register, then check for the opening of the job and apply for it Once
he/she has applied, they must undergo a personality test and a technical test and wait for
Recruiter's response. On the other hand, Recruiter will post available jobs, view all of the
applications, review the test result, and, if the applicant falls into the criteria they are looking for,
then they will schedule the interview.

Recruiter
Figure6. Use Case Diagram

The figure 6 above demonstrates the use-case diagram between applicant and recruiter
interacting in the application; there are multiple modules in application and recruiter as
communication to execute the hiring process.

Student No. 2200005 Page 7

Systems Architecture and Technology Integration - IT8x19

Figure7. Activity Diagram Applicant to System &

Figure 8. Activity Diagram Recruiter to System

According to Planner (IT) perspective, figure 7

demonstrates the activity of the applicant in the system,
in order to start the recruitment process, the applicant on
the applicant side must log in or register his account.
You will see the job listing in the application field, you
will need to insert your curriculum vitae, take the
personality test, and take the technical test before
applying it(Journal & Ranggadara, n.d.). On the
recruiter aspect, Figure 8 show recruiter to the system,
recruiter need to login account to view the menu job
posting, they can create new job posting by inserting
document job qualification, then the system needs to
create personality test and technical test by inserting the
document, and then send it to the system.

Mapping data into Zachman Model for the recruitment process

Perspective Data Function Network People Time Motivatio

n
Scope integration Integratio as per IT Organizati as per IT current
entity n Process on chart goal
for
integration
unit

Student No. 2200005 Page 8

Systems Architecture and Technology Integration - IT8x19

Business Model Business as per IT functions Improveme Process

Data flow Process of nt & time- efficiency
diagram Modeling integration line on
Notation hiring
process
System Model as per IT Activity Additional Roles and Improving Effectiven
Diagram system scope of recruitment ess
access- integration event
integration trigger
and
recruitmen
t portal
Technology DB system Compone as per IT Manual to Technolog
Model integration process nt for automation y
integration recruitmen supported
t portal and
readiness
Detail Goal of data Integratio Enterprise Involving Integration Recruiting
representation(in to integration n and integration Entity in schedule Goals
tegration) developm Architectu integration
ent re
process
Functioning Final Implementation
Figure9. Zachman integration(Abbas et al., 2019).

Integration is the unit responsible for setting up and managing the integration process between
systems within the enterprise so that the different entities and processes can be integrated
together to provide a standardized hiring mechanism(Abbas et al., 2019). The table shows the
Zachman Framework for Enterprise Integration in Recruitment Process.

Conclusion

Successfully developed e-Recuritment system productive to speed up the operation. This can be
accomplished by combining a variety of silos and independent information subsystems into a
single device that functions as one. Implementing strategic integration is, however, a dynamic
process, because it needs multiple people across. Therefore it is helpful to provide a framework
or architecture as a basis for giving the company a clearer understanding until the actual
integration is introduced.

REFERENCES

Abbas, W. F., Siti Hajar Ismail, & Haron, H. (2019, March 18). Enterprise Integration of

Employee Onboarding Process Using Zachman Framework.

Student No. 2200005 Page 9

Systems Architecture and Technology Integration - IT8x19

https://www.researchgate.net/publication/331828999_Enterprise_Integration_of_Employ

ee_Onboarding_Process_Using_Zachman_Framework/link/5c8f026992851c1df9481391/

download

AbuZail, H. (2015, March 3). Top Enterprise Architecture Methodologies |.

https://7hill.be/blog/top-enterprise-architecture-methodologies/

FEAF - Enterprise Architecture. (n.d.). Retrieved April 26, 2020, from

http://iea.wikidot.com/feaf

Journal, I., & Ranggadara, I. (n.d.). Zachman Framework Approach for Designing Recruitment

System Modules in HRIS Application (Case Study in PT. Karya Impian Teknologi

Abadi). IJCSMC. Retrieved April 21, 2020, from

https://www.academia.edu/35966975/Zachman_Framework_Approach_for_Designing_R

ecruitment_System_Modules_in_HRIS_Application_Case_Study_in_PT._Karya_Impian

_Teknologi_Abadi_

nitmansub. (2014, April 26). Importance of online recruitment software [Business].

https://www.slideshare.net/nitmansub/importance-of-online-recruitment-software

Pereira, C., & Sousa, P. (2004). A method to define an Enterprise Architecture using the

Zachman Framework. 1366–1371. https://doi.org/10.1145/967900.968175

Sousa, P., Caetano, A., Vasconcelos, A., Pereira, C., & Tribolet, J. (2007). Enterprise

Architecture Modeling with the Unified Modeling Language (pp. 67–94).

https://doi.org/10.4018/978-1-59904-174-2.ch004

TOGAF | The Open Group. (n.d.). Retrieved April 26, 2020, from

https://www.opengroup.org/togaf

Student No. 2200005 Page 10

Systems Architecture and Technology Integration - IT8x19

TOGAF Strength and Weaknesses. (n.d.). Retrieved April 26, 2020, from

https://www.eacomposer.com/knowledge-base/togaf-strength-weakness.aspx

Zachman, J. A. (n.d.). The Concise Definition of The Zachman Framework by: John A. Zachman.

Zachman International | Enterprise Architecture. Retrieved April 26, 2020, from

https://www.zachman.com/about-the-zachman-framework

Student No. 2200005 Page 11