Professional Documents
Culture Documents
2.1. IT Architecture: Theoretical Foundation
2.1. IT Architecture: Theoretical Foundation
CHAPTER 2
THEORETICAL FOUNDATION
2.1.ITArchitecture
Building a house needs many people from different job ranging from painter,
constructor, carpenter, and etc. Imagine if those people from different job do not know
what will the house looks like only know buld house, it will be disastrous. Each people
will have different perspective. What will happen if owner of the house continually
adding new rooms to meet the requirement, the house will be unattractive [2]. Those will
not happen if there is an architect that architects the house base on the owner
requirements before the house is build. Then the architecture will be distributed to
people that will building the house. The result of it, the house will be built better, no
need another configuration and also the time might be faster.
Looking to what has been done to houses. Business people have to realize that building
an IT system also needs an architect who is called IT architect. The needs of IT
architecture comes to more and more important because the system gives too many
resource silos which means that every business unit own IT systems and too many
platforms. Around 20 years ago, this IT architecture was born. It made architecture
become more important in organization IT strategy. According to IT architecture
bootcamp, the demand of IT architect in the industry is increasing in 2010. The best job
in the US is the software architect among other 100 jobs [3]. It shows that IT
architecture is on demand job and organizations are having problem with their
organization architecture. IT architecture bootcamp stated that only 1% of total IT
workforce are doing IT architect role, only 320,000. Looking to the fact that only 1%
people do the IT architect, it indicates that the job of IT architect is not an easy task. The
next paragraph will explain the definition of the IT architecture and then the framework
of IT architecture.
IT architecture can be described as an underlying infrastructure that enables a disparate
computer systems and networks to work together [2]. The goal of IT Architecture is to
ensure the alignment of information and communications technology to business
strategy [4]. IT Architecture is recognized as a key catalyst that organizations can use to
make progress towards the vision of Boundary less Information Flow [5]. IT architecture
can also be called an Enterprise Architecture.
According to Monash University,
Enterprise architecture (EA) is the discipline of scientifically designing the technology
elements of an enterprise, guided with principles, frameworks, methodologies,
requirements, tools, reference models and standards. [6]
In IT architecture, developing of new system is important to consider other system or
technology as well. For example, change a new email platform looks simple but it
affects not only the user but also other aspects such as the backup and recovery, data
storage, security solutions, instant messaging solutions, existing and future e-mail
integrated applications, network fax or voice mail solutions, and directory services and
authentication [7]. A particular application can affect enterprise performance and
business operational so the technology selection must not only look from the user
requirements but also it must align with enterprise vision and mission.
There are quite a number of frameworks for developing IT architecture. The frameworks
are Zachman, TOGAF and FEA. Those frameworks will be discussed throughout this
chapter. According to the American Heritage Dictionary as quoted by Roger session, a
framework is defined as:
A structure for supporting or enclosing something else, especially a skeletal support used
as the basis for something being constructed; An external work platform; a scaffold; A
fundamental structure, as for a written work; A set of assumptions, concepts, values, and
practices that constitutes a way of viewing reality. [8]
This chapter focuses on Zachman, TOGAF, and FEA. The reason choosing those
frameworks are because 90% of the field in IT architecture use them [8]. This thesis also
uses IASA ITA BOK. IASA ITABOK is a skill from IASA for IT architect when
developing IT architecture.
IASA is the premier association focused on the architecture profession through the
advancement of best practices and education while delivering programs and services to
IT architects of all levels around the world. [9]
The next section will be discussed deeper about IASA ITABOK, Zachman Framework,
TOGAF Framework and FEA Framework.
2.1.1. IASA ITABOK
IASA ITA BOK stands for an association for all IT architect (IASA) IT architecture
(ITA) body of knowledge (BOK). The purpose of IASA ITA BOK is helping the IT
architect in a proper way so it is not needed to have 10 years of IT experiences nor be a
10
EnterpriseArchitecture
Software
Architecture
Infrastructure
Architecture
Information
Architecture
FoundationBodyofKnowledge
Design
HumanDynamics
QualityAttributes
ITEnvironments
BusinessTechnologyStrategy
Business
Architecture
11
2.1.1.1.Business Architecture
Business architecture is needed to expand the role of IT architecture that supports not
only the technological issues but also the business and semantic issues that are required
for management and other business challenges. [10]
The purpose of Business Architecture is creating a link between strategy and the IT
initiatives. It also enables an integration of business to all IT, organizational, and
security architecture [11]. Business architecture and IT architecture should be aligned
and work together. The reason is business architecture can drive the IT planning, the
technology architecture and business solution. The IT architecture also drives business
architecture. Because IT capability is improving, it influences the business design
choices in the capabilities, value chains, processes, and channels [12]. Then business
architecture covers the strategy, policies, business process, and organization. Person who
does business architecture is called business architect. Aaron Tan Dani as the Chief
Architect stated,
Business architects focus on a common, enterprise-level business language and
framework for documenting how the business language and framework for documenting
how the business is structured to support a technology strategy within a business
strategy. [3]
In order for business to align with IT, it needs business architect that develops
documentation about how the current business do and what is the future of the business
based on the framework so the IT and business people will have the same language.
After understand each other, the business will be structured to optimize the technology
based on the business strategy. In building business architecture, business architect
12
needs support from the business domain units, business stakeholders and other IT
architect roles. According to IASA there are five components in the Business
Architecture which are strategic business planning, strategic IT planning, value stream,
integrated enterprise IT architecture, and IT architecture.
2.1.1.1.1.
Strategic business planning discusses about the mission, object and the strategy to strive
the mission. This component describes the formulation of strategy. There are three
frameworks that can be used to develop strategy. The frameworks are Porter
Framework, Resource-Based View, and Delta Framework [13]. The focus of strategic
attention of Porters framework is with the five forces model and the value chain
analysis. The Resource-Based View of the Firm expands the scope of attention to the
full corporation, with a possible full portfolio of business, since that is where the Core
Competencies reside. Finally, the Delta Model extends the scope to include the
Extended Enterprise that is composed by the firm and its key Suppliers, Customers, and
Complementors.
2.1.1.1.2.
Strategic IT Planning
13
Value Stream
14
2.1.1.1.4.
IT Architecture
The last component is IT architecture. IT architecture is the art and science of designing
and delivering valuable technology strategy for the business [3]. It designs and delivers
the technology strategy to support business. Information Technology Architecture is a
high-level map or plan of the information assets in an organization, which guides current
operations and is a blueprint for future directions [16]. The figure 2.3 shows the example
of IT architecture in online travel agency.
15
2.1.1.2.Information Architecture
Information architecture (IA) is the art of expressing a model or concept of information
used in activities that require explicit details of complex systems.[17]
Information architecture describes the data flow in the business process. The flowing of
data in organization from one application to another application is not as simple as the
data is sent and the particular applications receive it. The users only know that the data is
sent and the data is received but actually the sending or receiving data from an
application is having a process on the backend. For example, sending the data from an
application, the data can be routed to the database to be stored and also go to the other
process. Information structure discusses how the information is being stored in database,
file, image or other digital formats, how the information is technically retrieved, usage
and time constraints, how the use of information support the business strategy, and how
the information that is presented to the user is relevant and how the design of the
16
17
Design
18
2.1.1.5.2.
Human Dynamics
Human dynamics are the communication, political and leadership skills necessary for
any person on the job. [3]
Human dynamic focuses on the human side. This body of knowledge describes the
employee behavior based on the organization strategy. The IT architect should analyze
what is the key behavior in order to achieve the business strategy.
2.1.1.5.3.
Quality Attributes
Quality attributes focus on all aspect of IT strategy to monitor the quality of the
technology. The quality can be measure by looking to the performance, reliability,
availability, scalability, manageability, maintainability, extensibility, flexibility,
usability, localization, accessibility, and personalization. Security of the IT architecture
must also be considered in the quality attributes.
2.1.1.5.4.
IT Environment
Business Technology Strategy is the key in the IT architect. It connects all IT architects
with business strategy. It is the foundational BOK base for the whole IT works. It
19
defines the strategy of the business and the IT architecture strategy. The IT architecture
strategy is validated to support business strategy.
2.1.2. Zachman
In 1987 enterprise architecture is established, it is developed with the Zachman
framework [12]. Zachman is established by Zachman Institute for Framework
Advancement (ZIFA). Zachman framework consists of what (data), how (process),
where (locations), who (people), when (time) and why (motivation). Those questions
will be asked to key people such as planner, business owner, designer, builder and
subcontractor. Zacham will help to know what kind of data, process, locations, people,
time, and motivation the key people. Looking how Zachman works, it is like defining an
issue. Roger Session said, "The Zachman "Framework" is actually a taxonomy for
organizing architectural artifacts (in other words, design documents, specifications, and
models) that takes into account both who the artifact targets (for example, business
owner and builder) and what particular issue (for example, data and functionality) is
being addressed [8]. Figure 2.4 describes the Zachman Framework.
20
21
architecture describes the organizing and accessing the datastores. Technical architecture
describes how the interaction of the application and the application will be supported by
the hardware and software infrastructure.
TOGAF is using a process from the general to specific, from the enterprise continuum to
the organizational architecture and the Architecture Development Method (ADM) is the
process driving from the general to the specific. In the figure 2.5 in the below, the
relationship between the ADM and the enterprise continuum is shown clearly. [8]
22
organization. The common systems architecture is a system that any organization would
like to have it [8]. To more specific, the industry architectures are principles to integrate
the common system with the specific system within an organization and then create an
industry solution for the specific customer problem. The most specific is the
Organization Architectures that are described and guided the final of the solution
component and the network base on the customer problem and customer IT environment
[19].
In the figure 2.6 above, it describes the process of ADM that contains a preliminary
phase and then the 8 phases that are cycled. The activities inside each phase are well
defined but it depends on the implementation to determine the suitable activities to get a
required system and the required outcome.
23
Figure 2.7 shows the model based on the TOGAF ADM and COBIT model [20]. The
vision and mission of institution refer to the regulation of institutions. The scope &
requirement refer to the vision and mission of each institution. The business architecture,
information systems architecture and technology architecture refer to the available
resources.
2.1.4. Federal Enterprise Architecture (FEA)
FEAF is a framework issued by the US CIO Council to promote shared development for
common US Federal processes, interoperability, and sharing of information among Federal
Agencies and other Government entities. [19]
FEA is a combination of Zachman and TOGAF; it has taxonomy like Zachman and has
a process of architectural like TOGAF. FEA has FEA reference models to make
everyone on the organization have the same language or the same vision. The FEA has 4
levels. The first level is the architecture drivers and strategic direction architecture. It
24
discuss about transformation from current architecture to the target architecture using
architecture standard and process. The second level discusses about the analysis of
business driver and design driver of architecture. It produces the the target business
architecture and target design architecture. The level 3 discusses more detail about the
target architecture using the business, data, application and technology views for the
target architecture. The last level includes the description of data, function and network
to represent Data Architecture, Application Architecture and Technology Architecture. It
includes the 5 component in the zachman framework. This level also includes the
process of architecture planning. FEA process is similar with TOGAF. It uses
architecture drivers, business drivers, and design driver for the architectural planning.
2.1.5. Framework Comparison
The framework in IT architecture is different from one to another. There is no such best
framework but there is the most suitable framework to the organization. Every
framework has strength and weakness. The above framework will be evaluated using the
criteria from the journal that is conducted by the School of Information Technology in
Swinburne University of Technology [19]. The criteria are divided into 3 parts that are
goals, inputs and outcomes. The criterion that is implemented is from the journal that is
a comparison analysis of architecture framework. The goals are the target of the
organization want to be. The criteria for goals are :
25
The second criteria is the input, it represents the data that can be used to model the
architecture.
Business Requirements all requirement needed for the architecture like user
requirement, functional requirement, data requirement, etc
Non Functional requirements provides the quality attributes for the architecture
(availability, reliabity, security, etc)
26
The third criteria is the outcome, it shows the result of the Architecture.framework that
answering the goal.
Business Model the model of the organization business such as the business
process, policy, and business requirements.
System Model the model of the system includes the future system
improvement
Information Model contains data model, data transformation and data interface
Non-functional Requirements Design helps to design a system that fulfill nonfunctional requirement also
Transitional Design a planning for the transitional, from the current to the
target architecture
27
ZF
FEAF
TOGAF
Architecture
Definition and
Understanding
Architecture
Process
Architecture
Evolution
Support
Architecture
Analysis
Architecture
Models
Design
Tradeoffs
Design
Rationale
Standardization
Architecture
Knowledge
Base
Architecture
Verifiability
Business
Drivers
Technology
Inputs
Business
Requirements
Information
System
Environment
Current
Architecture
Non Functional
Requirements
Goals
Inputs
Outcomes
Business
Model
28
System Model
Information
Model
Computation
Model
Software
Configuration
Model
Software
Processing
Model
Implementation
Model
Platforms
Non-functional
Requirements
Design
Transitional
Design
Design
Rationale
P = Partial
Y = Yes
N = No
Looking to the Table 2.8, TOGAF framework is the most comprehensive framework
compare to the other framework. TOGAF is chosen by the researcher as the
framework to analyze the business architecture in Binus International. It is also
because TOGAF has a complete process, reference model, neutral with vendor,
and information is available. TOGAF has characteristic for university and
information system [21]:
1. University needs a flexible method to integrate all information units and
do information systems planning. TOGAF ables to integrate for different
systems.
29
2. Characteristic of TOGAF is general and flexible that can anticipate for artifact
that might arise because TOGAF has adequate resource base, the standards is
acceptable and can handle changes.
2.2. Benefit of IT Architecture
The benefit of IT Architecture is derived by the business benefits it brings to enterprise
[22]. By understanding its value, better decisions can be to the appropriate level of time,
money, and people resources to invest in the development, implementation, and
maintenance of the IT architecture.
improved business operations, foster business alignment, and guide business innovation.