PHP FRAMEWORK DESIGN WITH HIERARCHICAL MODEL-VIEW-

CONTROLLER ARCHITECTURE
Ahmad1, Zainal Arifin2, Dyna Marisa Khairina3
Computer Science Department, Mathematics and Natural Science Faculty Mulawarman University Samarinda 1,2,3
rawndummy@gmail.com1, zainal_arifin@fmipa.unmul.ac.id2, dyna.ilkom@gmail.com3

Abstract
The development of internet today makes website as the most popular information system media. Among several
programming languages that can be used to build a website, PHP is the open source web-programming language and
very popular among any programmers. Web building method from time to time also has its progress. From the
beginning using the conventional method raises some obstacles, until finally evolved to the use of the framework that
has many advantages in terms of management and library files. The framework has been widely spread on the internet
that can be used to create a website, especially for users of PHP today. Among the many frameworks, architectures
used affect the effectiveness of the use of the framework. The purpose of this research is to design a PHP framework
that implements the architecture of the Hierarchical Model-View-Controller (HMVC) system which was originally
developed for desktop applications. HMVC is an architecture that consists of a layer of MVC (Model-View-Controller)
that has a derivative relationship hierarchically. The final results is the form of a PHP application framework with
HMVC architecture which results in a system that can help make large-scale websites and worked as a team.
Keywords: PHP, Framework, Website, Hierarchical Model-View-Controller (HMVC).

1 INTRODUCTION Model-View-Controller). HMVC split into sections per

The web is currently used for a wide range of
purposes, including to search for information, business,
social media, etc. The fact that it can be accessed
through various devices make use of the web is so
popular. Surely this could not be separated from the
innovation made by web developers. Then the web
attracting some circles to be involved in the world of
web.
Web consists of a set of documents that are
connected to form pages. Web can be run as part of
server software. Server software is software that is
placed on the server to process requests from clients.
There are some server software that can be used in
making the web, one of which is PHP. PHP is a server
software that is open-source and has a lot of developers.
Speaking of making web certainly not out of the
manufacturing techniques. Web which consists of a set
of files must use good programming techniques for
management to be easy to deploy. In the beginning the
web was made not so regular, yet require the use of the
framework. Making the web tend to use the same code
over and over again, then this is where web developers
to develop the framework. Framework to package a
number of codes that can be used repeatedly (reusable)
for all web creation is done.
Making the web then developed using the MVC
architecture (Model-View-Controller). MVC separates
the code into three parts, namely the process
(controller), part of the data (model) and the display
(view). Then allows the use of MVC web workmanship
be divided. Team members who are more likely to be
able to focus on doing the code logic section and team
members were more likely to be the focus of the design
work on the display.
MVC architecture still has some constraints. When
some web code will be imported into other web, the
MVC should be moved to three different locations.
MVC then developed into a more modular.
Development of MVC called with HMVC (Hierarchical
module. Each module has its own MVC layer, so that
when imported moved enough alone. Not only that,
HMVC then allows a module has a derivative like
hierarchy. HMVC first applied to desktop applications.
From there, the author decided to apply the HMVC to
web framework.
2 STRUCTURE OF WRITING
2.1 Problem Formulation
Based on the background, then formulated a
problem, including:
1. How does the process work a PHP framework that
uses HMVC architecture?
2. How is the implementation of the architecture
HMVC PHP framework on a simple website
creation?
3. How to make a PHP framework that is in
accordance with the PSR-0 standard, PSR-1 and
PSR-2?
2.2 Boundary Problem
To avoid the spread of the issues discussed, the
researchers limited the problem:
1. PHP framework that will be built is more devoted to
the development of the website version 2.0.
2. PHP framework that will be built this using OOP
(Object-Oriented Programming) with server PHP
version 5.3 or latest version.
3. the format used by the PHP framework is the path
format.
4. Database library to be used by this PHP framework
is the libraries for MySQL version 5 or latest using
MySQLi extension (MySQL Improved).
5. Users PHP framework that will be built this is a
PHP programmer with intermediate skill level up.
6. Part libraries that will be described on the PHP
framework is a model, view, controller, route, and
database.
2.3 Research Goals
This research was conducted to develop a PHP
framework that uses HMVC architecture, so as to create
a PHP framework has advantages, including:
1. Suitable for large-scale website development and
worked as a team.
2. Provides optimum libraries are loaded to assist in
the development of web applications.
3. It has manual (user guide) for developers to help in
learning the use of this PHP framework.
4. Have tools such as a generator to create models and
modules.
5. Characteristically open source, can be developed by
anyone for free.
2.4 Benefits of Research
The benefits to be gained from this research are:
1. Knowing more profound engineering process that
uses a PHP framework HMVC architecture and
design pattern Singleton Pattern.
2. Find out more specifically how a PHP framework
can work based programming rules that have been
set in it.
3. Can be used as a basis for further development of
the system is more advanced PHP framework.
4. Stimulate interest to web developers use PHP
framework to build a website, either for secondary
level and for the beginner level.
5. Provide knowledge for website developers who use
PHP framework without knowing the inner
workings of PHP frameworks it uses.
3 METHODOLOGY
3.1 PHP (PHP: Hypertext Preprocessor)
PHP stands for "PHP: Hypertext Preprocessor",
which is a scripting language that is attached to the
HyperText Markup Language (HTML). Most of the
language syntax is similar to C, Java and Perl, PHP plus
some specific functions. The main purpose of this
language is to allow web developers to write dynamic
web pages quickly [6].
PHP was created by Rasmus Lerdorf in 1995. At
that time PHP was named FI (Form Interpreted), which
is realized in the form of a set of scripts that are used to
process data from the web form. Furthermore Rasmus
released the source code to the public and named PHP /
FI. With the release of the source code to be open
source, there are many programmers who are interested
in developing PHP. Now the new version of PHP was
developed by Zend, Zend Framework developers.
3.2 Web Application Framework
Web application framework is a software
framework that designed to support developing of
dynamic web, web application and web service.
Framework is a set of statements or basic functions that
form certainly rules and interact with each other so that
in making the application site must follow the rules of
the framework [7]. Framework can be defined as a set
of or a collection of pieces arranged or organized
program such that it can be used to help make the
whole web application without having to make all the
code from scratch [1]. Web Application Framework
ideal for building web-based applications because it is
more flexible, secure and use a more structured pattern.
Examples of Web Application Framework such as
Zend, CakePHP, Kohana, Laravel, CodeIgniter,
Symfony Project Yii, Prado, and others.
In the creation of websites, especially those done in
teams, will be hard to steer thinking if team members
do not use the framework. Development of the
framework is done with the aim of providing a space
for the programmer to not split up of the rules that have
been agreed. A framework must have a standard that
has been set maker. People who use the framework can
still be creative as you wish while still adhering to the
standards set in the framework that is used. Therefore,
the Indonesian framework known as the frame work.
3.3 HMVC (Hierarchical Model-View-Controller)
Architecture
HMVC (Hierarchical Model-View-Controller)
Architecture consists of a layer of MVC (Model-View-
Controller) which can have a hierarchical relationship
derivative [3]. In the article, discusses JavaWorld
HMVC design for desktop applications, especially
those using the Java programming language. However,
in this study will be discussed on how to implement
HMVC PHP framework architecture in website
creation. HMVC is an MVC pattern but a hierarchy in
which the MVC implementation stored in specific
modules so that each module of the model, view, and
controller itself [5].
HMVC architecture provide clear boundaries for
each layer. Limiting layer is referred to as a module
(module). Because HMVC is a development of the
MVC architecture, the term MVC will continue to be
used in its application. Each module has the MVC
which stands independently. A module will not
interfere with other modules. By doing so, the module
is said to have clear boundaries. HMVC architecture
can be seen in figure 1.
Figure 1 HMVC Architecture
When compared to the MVC architecture, HMVC
architecture has several advantages [4], namely:
1. Modularity: HMVC makes it easier to interchange
chunks of code through encapsulation of
functionality.
2. Organization: HMVC allows each module to
contain its own models, views, and controllers
directories, keeping related files contained.
3. Extensibility: By promoting modularity, HMVC
allows systems to be more easily extended by
simply adding or replacing modules.
4. Reusability: Since modules can call each other,
HMVC allows for code to be easily reused.
3.4 Flowchart
Flowchart can be used to show the sequence of
events from a computer-based information systems.
This flow chart shows the sequence of processes in the
system by exposing the media input, output, and other
types of storage media in the data processing [2].
4 RESULTS AND DISCUSSIONS
4.1 System Section
The system in question here is a PHP framework.
PHP framework consists of several parts that work
together to run the application. The system is built
using the PHP file containing the class definition. There
are some classes that are made in the system, but the
part is not shared by the class system. Part of the
system is divided by function.
a. Boot Loader is part of a system that aims to
initialize and load the rest of the system required
by the application.
b. Routing is part of a system which aims to perform
the addressing.
c. System Controller is part of the system which is
the control center module that performs the
execution of the application.
d. System View is part of a system that serves to
process the input from the System Controller into
HTML documents with the help of the DOM
(Document Object Model) HTML.
e. System Model is part of a system that handles the
use of a model made by the application.
f. Database Driver is part of a system that aims to
open up access to the database is done by the
System Model.
g. Helpers are part of the system that served to
provide assistance in the development of web
applications.
4.2 Application Section
Application in question here is a website built by
users. Such a system, the application is also divided
into several sections. This division will help the system
to execute a web application.
a. Bootstrap is a part of the application that is
executed when the web first started. This section
will call and run the Boot Loader section of the
system to execute the application.
b. Configuration is part of the application that is used
to hold settings or the web configuration.
c. Module is part of the application that will be
executed by the system to generate web content.
There are three sub-sections inside, namely
Model, View, and Controller.
d. Model is a sub-part of a module that serves as the
data collection.
e. View is a sub-part of a module whose job is to
display the output of a piece of HTML code that
will form the web content.
f. Controller is a sub-part of a module that serves as
the main controller module, and bridges the
relationship between the model and the view.
g. Plugin is a kind of module, so that there are the
separate parts of MVC. The plugin is used to form
a module with features from third-party providers.
h. Component is part of the application that allows
users to create their own libraries (user-defined)
for use by the application.
i. Asset is part of an application that aims to
accommodate and provide access to client-script
application or media needed by web.
j. Theme is part of the application that provides the
main view to a web page.
Layout is a sub-part of a theme that will be the
content module (container) to form a complete web
page.
4.3 Workflow of System
Workflow is a system design that describes how
the flow from the beginning to the end of a working
system in general. The subject that will be discussed
only the workflow system, not including workflow
applications.
Figure 2 Workflow of Djokka Framework
Figure 2 Shows the workflow of Djokka
Framework when running a web system that is being
executed. When a user accesses a web application, then
the first run is the index.php file located in the root web
application. In this file, the boot loader is called to load
the Djokka Framework system. Once invoked, the boot
loader will be run.
Boot loader is part of a PHP framework that runs
the boot process. The boot process includes loading of
all configurations contained in the web application.
Configuration forms data used to adjust some parts of
the system that can be set. There are several pre-
defined configurations on Djokka Framework, one
example is the database configuration.
Once the configuration is loaded, process is continued
to the routing part. In this section the system will
determine which module to be executed within a web Mulai

application. The determination is done by processing Membaca URI

the URI (Uniform Resource Location). After

determining which module is to be executed, the
Module = “index”
Action = “index”
Dir = ModuleDir()

process continues to the system controller.

System controller is the control center of the
True False
False
URI mengandung
URI kosong?
simbol slash?

process. System controller will execute the modules Routes = Explode(‘/’, URI)
Jml_Rute = Count(Rute)
True Module = URI

that have been determined by the routing part. The Tmp_Mod = null
Prev_Mod = null
Params = Array()
Module = “index”

function performed by this section depends on the i=0

Path = Dir + URI + “/”

process contained in the executable module. Within a i < Jml_Rute

False
Params = ArraySlice(Routes, i + 1)

module are the model, view and controller. The module True Last_Part = UcFirst(LastPart(‘/’, Module);

must have a controller, but it does not necessarily have Module = Routes[i]
Tmp_Mod += Routes[i] + “/”
True
i=0
Route = Module + “/” + Action
Function = “action” + UcFirst(Action)
Class = “Djokka\Controllers\” + Last_Part

to have a view and a model.

False
Module_Dir = Path
Path = Path + “/” + Last_Part + “.php”
Tmp_Mod += “modules/” + Routes[i] + “/”

System controller then becomes the central control Action = Routes[i]

Path = Dir + Prev_Mod

system. Some of the supporting web applications, such

Path = Dir + Tmp_Mod

as: components, plugins, modules, and helpers, will Berkas Path

ditemukan?
False
Selesai

play if in the controller module is written orders calling True

True

to that support part. Thus, the system controller only Prev_Mod += Routes[i] + “/” i=0
False

runs part of the supporting required course. If there is Module += “/” + Routes[i]
Prev_Mod += “modules/” + Routes[i] + “/”

no supporting parts is needed, then the process will

continue to the next stage.
i++

If the module executed has model calling process,
then the part that handles it is system model. In web
application, model can be used for validation or
accessing database. If a model is used for validation,
then system can run supporting part namely Validation.
If model needs database connection, then system model
with the database driver help will open database
connection and give the access. Data from database will
be fed back to database driver then to system model and
get fed back again to system controller. From system
controller then data will be continued to model
accessed by module controller.
Output resulted from system controller is an web
content information and the list of web asset needed by
a module. Web asset is client-script file, like JavaScript
file and CSS. That information will be continued to
system view for further processed. With the DOM
HTML help, system view will run rendering, so that it
results HTML document output. DOM standing for
Document Object Model is library that is actually
available in any web browser. But now it is also
available in PHP. Output resulted from rendering
process is HTML document that will be received by
web browser to be displayed next.
Part of system applying HMVC architecture is
called HMVC engine, it is an engine used to collect the
information of a module according to HMVC
architecture. That information can be used by system
determining module location that will be executed.
Figure 3, shows flowchart forming HMVC architecture
Figure 3 Flowchart Forming HMVC Architecture
4.4 Rule of System
As framework, there is a rule used to give scope to
user in order not to split or out of rule. Those rules
include as system design. Rules that have been decided
to be followed in framework are:
a. Rule of module manufacture
b. Rule of sub-module manufacture
c. Rule of controller module manufacture
d. Rule of action function manufacture
e. Rule of view manufacture
f. Rule of model manufacture
4.5 System Interface Implementation
Error handler is error message that will be
displayed by system when it is found error experienced
when web project execution. Error message displayed
is designed in such a way in order that web programmer
can repair error experienced. Term of this error
correction is called debugging. Figure 4 shows error
message display along trace faults.

Figure 4 Error Message Display along trace faults

 Sometimes a web programmer who first uses a
PHP framework must know the structure of the laying
of the file. In order to facilitate the programmer to
know the directory structure of the files laying, then
made a tool that is embedded in the system Djokka
Framework. This tool is named "Project Builder", is
used to display the directory structure that will be used
by the web project. Display Project Builder tool is
shown in Figure 5.
Figure 5 Views Tooling Project Builder
Tools with the name "Creator Module" is provided
for novice web programmers who will use Djokka
Framework, not knowing how to manufacture the
module, and just want to feel the ease in making
modules. This tool can create a module in accordance
with the rule-making module in Djokka Framework.
Display Module Creator tool can be seen in Figure 6.
Figure 6 Display of Module Creator tool
Active Record is a model that features connectivity
to the database. A tool called "Active Record Creator"
has been implanted in the Djokka Framework, serves to
make the model as an abstraction to a table in the
database that is used. Display Active Record Creator
tool can be seen in Figure 7.
Figure 7 Views Creator Tools Active Record
4.6 System Testing
Testing for the system is done by implementing the
use of Djokka Framework in making a website. The
making of this website will test the success of Djokka
Framework in making website. The website that will be
built is a website that can be used for news publishing.
Website can be managed by an administrator and web
visitor can give feedback comment to news.
Figure 8 Display Home Page
Figure 9 Admin Pages Display
Figure 8 and Figure 9 show the results of websites
that are built using Djokka Framework. As Figure 8
shows the view of the Home page, while Figure 9
shows the view from the Admin.
The test also includes performance measurement
benchmarking. Benchmarking is done by using the
parameter number of requests per second that can be
done as a benchmark. Two well-known PHP
frameworks will be compared with the PHP framework.
Benchmarking is accomplished using the default
console of PHP, which is ApacheBench. Computer /
laptop that is used in this process specification:
a. OS Windows 7 Home Premium 64 bit
b. Intel(R) processor Core i7 2.00 GHz
c. 8 GB RAM
d. Web Server Apache version 2.4.7
e. PHP version 5.5.6
Benchmarking is done by testing Djokka
Framework PHP framework along with two other well-
known people, including: Yii Framework and
CodeIgniter. Each of the PHP framework created a web
test which only displays the message "Hello World".
By using the Command Prompt, each measured
performance PHP framework by typing the command
"ab-n 50 URLs". The intention is to send the command
as many as 50 requests on the URL address of the web
experiments each tested PHP framework. Once the
request is done, then the Command Prompt will appear
benchmarking results. The ratio of the number of
requests made per second is displayed in graphical form
in Figure 10.
Figure 10 Comparison Chart Value RPS (Request
per Second) PHP Framework is tested
5 CONCLUSIONS
From the research that has been done, it can be
concluded:
1. PHP framework architecture using Hierarchical
Model-View-Controller is generated.
2. The PHP framework can avoid collisions between
class attributes and class attributes artificial library
users.
3. The PHP framework can provide a broader space
for the formation of the pages in the website
creation and storage capacity is not too large.
4. The PHP framework complies with the PSR (PHP
Standard Recommended), more specifically: PSR-
0, PSR-1 and PSR-2.
5. Systems can be used in the manufacture of large-
scale web sites which need collaboration of many
people.
6. Based on the test results were compared to three
frameworks, resulting that the Requests per
Second (RPS) for Djokka Framework is higher.
6 REFERENCES
[1] Basuki, A.P. "Membangun Web Berbasis PHP
dengan Framework Codeigniter". Lokomedia,
Yogyakarta, 2010
[2] Bin Ladjamudin, Al-Bahra. "Analisis dan Desain
Sistem Informasi". Graha Ilmu, Yogyakarta, 2005
[3] Cai, Jason., Kapila, Ranjit. dan Pal, Gaurav.
"HMVC: The layered pattern for developing
strong client tiers.",
<http://www.javaworld.com/jw-07-2000/jw-0721-
hmvc.html> accessed on 16 May 2013
[4] Crow, Wesley. "Hierarchical Model-View-
Controller (HMVC): Planning For The Future",
<http://somethingstatic.com/hierarchical-model-
view-controller-planning-future> accessed on 16
May 2013
[5] Hidayat, Eka Wahyu. "Penerapan Pola
Hierarchical Model-View-Controller Pada
Rekayasa Sistem Berbasis Web Framework".
Jurnal Teknologi TechnoScientia, Indonesia,
Volume 3: 2, 2011, ISSN: 1979-8415
[6] Nugroho, Bunafit. "Latihan Membuat Aplikasi
Web PHP dan MySQL dengan Dreamweaver MX
(6, 7, 2004) dan 8". Gava Media, Yogyakarta,
2008
[7] Wardana,. "Menjadi Master PHP dengan
Framework Codeigniter", PT.Elex Media
Komputindo, Jakarta, 2010