International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014), pp.197-212

http://dx.doi.org/10.14257/ijseia.2014.8.4.21

Enhancement of UWE Navigation Model: Homepage

Development Case Study
Karzan Wakil1, Amirhossein Safi2 and Dayang. N. A. Jawawi2
1
2

College of Science & Technology, University of Human Development-Iraq

Faculty Of Computing ,University Technology Malaysia, J.B.,Skudai 81300,
Malaysia
karzan.wakil@uhd.edu.iq, samirhossein2@live.utm.my , dayang@utm.my
Abstract

UML-based Web Engineering (UWE) is a web engineering methodology which

provides a systematic approach to development of web applications. It provides a UML
extension, defining modeling elements considering the extension mechanisms that are
offered by UML. Navigation model is presented as a very critical characteristic in all the
hypermedia and web methodologies; also homepage one of the most important pages on
the web sites, because it is the key to showing the quality of websites. The UWE
navigation model defined as a new proposal meaning still now need it to improve, the
problem is elements of the UWE navigation model until now cannot support modules of
the homepage especially new modules as Tab, Flash News, Main Menu, Frame, Multi
Data and Application Icons, meaning it has weaknesses, in this paper we enhance the
UWE navigation model through defining six elements by using an extension mechanism
to fully support homepage development.
Keywords: UWE, navigation model, enhancement model, web engineering, homepage

1. Introduction
UWE is a software engineering method to develop of web applications. Since
1999, web application has been extended constantly [1-3]. UWE is method based on
standards. UWE focused on visual modeling together with systematic design and
automatic generation, whose objective is to cover the entire life cycle of web
application development [4].
UWE metamodel is a design considered as the conservative extension of the
Unified Modeling Language (UML) metamodel, in other words that the modeling
elements of the UML metamodel are inherited from the UML metamodel, and they
are not modified by adding new features or additions to the modeling elements
class. Any additional features or relationship if using the metamodel to implement
then they can be specified in different metamodel modeling element and then define
Object Constraint Language (OCL) restrictions on further static semantics and it is
equivalent to well-formed rules in the UML specs [4].
Homepage one of the most important pages on the website because clearly
communicates the site's purpose, and show all major options available on the page
and the key to showing the quality of website. Solving the usability in homepage
help the homepage to elegance, clarity, easy user interface and easy to understand
[5-6].
In this context, UWE, proposed by Koch in her Ph.D. thesis, arises as a tool to
support web system modeling with a special focus on systematization and
personalization. UWE extends the UML, considering extension mechanisms defined
by the UML itself, and provides a set of modeling elements and an authoring
process to construct the system models during several modeling steps. UWE

ISSN: 1738-9984 IJSEIA

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

methodology and presents new approaches for improving the navigation model
defined by some methodologies. A case study is performed applying the methods
presented in [6-7].
The problem is that the current UWE navigation model cannot fully support the
homepages directly because the UWE navigation model does not have enough
elements to represent the content of homepages, also it is a design considered as the
conservative extension of the UML metamodel, also the metamodel provides a good
description to development homepages.
The paper is organized as follows: Section 2 explains the background work for
the UWE metamodels especially navigation model. In Section 3 we selected the case
study and analyzed it. Section 4 consists of designing a case study by UWE. In
Section 5 we enhance the UWE navigation model. In Section 6 we redesign
navigation model for the case study after enhancement. In Section 7 we make
comparison and evaluation UWE navigation model. In the last section we present
some concluding remarks and points to future works.

2. Background Work
In the past few years, some Web Engineering methods have suggested an
operation to the development of Web Applications. The significance of the
navigation between the application nodes is the meaning of the navigational model
which is one of the fields [8].
Several researchers in the Web Engineering community have exploited
metamodeling and UML extensions in defining web models [9-14].
A lightweight UML profile developed in the last works that are the notation
used for design, e.g. (Koch and Kraus, 2002). A UML profile is a UML adjunct
based on the adjunct systems denoted by the UML itself with the benefit of utilizing
a conventional notation that does not affect the interchange formats and can be
supported by tools without any difficulty. The design features required to design
various characteristics of web applications, such as navigation, presentation, user
task, and adjustment aspects are defined by stereotypes and tagged values and are
included in the UWE profile. And showed the package of the navigation model in
UWE at Figure 1 [3].

Figure 1. UWE Navigation Package [3]

198

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

UWE Navigation categories, connections and a group of indexes, guided tours

and queries are created from the navigation model. The perceptions over the
conceptual categories are the navigation categories and connections. Likewise, the
user is designed by a user function, user properties and relationships of these
properties to the theoretical categories. Presently, an adjust of the CASE tool
ArgoUWE is being developed to support the assembly of these UWE design
models[4].
The pioneering work of Conallen [10] uses, in conjunction with the standard
UML diagrams, the Web Application Extensions (WAE), which comprise the
typical Web artifacts (server pages, client pages, forms and frames). The main
advantage of WAE proposal is that its simplicity allows efficiency the design
artifacts the Web Interface, as well as to drive the implementation of such as
interface. On the other hand, this same simplicity evidences a lack of elements for
modeling navigation and representing technology and device independent
requirements.
Although UWE provides a good approach to design web systems, since it
provides stereotypes and methods that allows the designer to model the specific
features of systems that belong to that application domain as the navigation space
and structure, UWE still needs to be improved. Koch, Kraus, and R. Hennicker
identified some limitations during the development of our case study, which have to
be fixed in order to make the modeling process as automated as possible which is
one of the goals of UWE, according to its author [15-16].
Carvalho, and Junia 2005, presented here some proposal's to extend UWE
method, in order to improve the web navigation project, through this work, they
could identify the need of representing the call of methods of a navigation class that
is used to achieve the system functionality in the navigation model. They proposed
to represent the call of methods of a particular class through the addition of selfrelationships that role names are the same of the method signatures. They could also
identify the need of representing implicit links that result from relationships of
aggregation and inheritance established in the conceptual model. They proposed a
new modeling element to represent that kind of links and some new steps in the
construction methods of the navigation structure model. as shown in Figure 2 [17].

Figure 2. Pizza Place Navigation Structure Model (First Step) Customer

View [17]

Copyright 2014 SERSC

199

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

According to previous works, the navigation model is one of the important models in
the process of the developing web applications. However some researcher worked to
improve UWE navigation model, but this model need more improvement for development
of web applications.

3. Case Study and Analyses

There are many classifications for the typology of web pages and homepages,
Jackson showed four ways for categorize of web pages according to organizer
identity, number of pages, organizers goal, and based on measure and success web
pages [18]. moreover Alistair Kennedy and Michael Shepherd classified homepages
for three categories are: personal homepage, corporate homepage and organization
homepage [19]. We choosing a case study in each of categories as shown in Table 1.
Table 1. Categories of Homepage with Case Study
Category
organization homepage
corporate homepage
personal homepage

Case study
UTM homepage [20]
Apple homepage [21]
Maher Zain homepage [22]

The UTM homepage has most of the moduls design for homepages compared to
Apple homepage and Maher Zain's homepage, for example; UTM homepage has
menu, picture, and contact us. Etc, also used in Apple and Maher Zains homepage.
UTM homepage shown in Figure 3.

Figure 3. UTM Homepage

In this paper for enhancement UWE navigation model, we utilize the University
Technology Malaysia (UTM) homepage as the case study, because it is a long
homepage and it has different contents such as News, Search, Switch languages,
Information, and so on. So, it has different types such as Image and Text. And it has
different models as Flash news, Frame and Menu. And linked to some applications

200

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

like Chat, Feedback. Briefly UTM homepage has all modules when used in Apple
and Maher Zain homepage. Figure 3 shows the UTM homepage, this picture was
taken on the 30th October 2012 by using fireshot software for Google chrome
browser.
The content of the UTM homepage consists of different types of models design
we grouped them according to Joomla script [23-24] as shown in Table 2, that
shows the types of modules design, types of content, and categories for the UTM
homepage content.
Table 2. Classification of the UTM Homepage Contents
No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

Homepage contents
Logo
Head
menuAccessibility
Head menu-My UTM
Languages-English
Languages-Malay
Search
Top Menu 1-About Us
Top Menu 1-Admission
About Us-introduction
About
Us-facts
&
history
Top Menu 2-Staff
Top Menu 2-Alumni
Flash News
Begin Virtual Tour
Visitors Counter
Where we are
News & Announcement
Events @ UTM
Find Us on-face book
Find Us on- twitter
Marquee Link
Online service
Course Finder
Frame
Faculties and Schools
Media
Campus
About Us-Vision &
Mission
Map and Direction
Partners KPT
Partners Msc
Text
Footer
Menu-Agency
Policy
Footer Toolbar-Chat
Feed Back

Copyright 2014 SERSC

Type of the Module

Web Design
Image
Menu

Image
Info

Name of
categories
Image
Information

Menu
Menu
Menu
Search
Main menu
Main menu
Sub menu
Sub menu

Info
Switch language
Switch language
Search info
Info
Application
Info
Info

Information
Languages
Languages
Service
Information
Application
Information
Information

Menu
Menu
Flash New
Image
Counter
Menu
Multi data
Multi data
Multi data
Multi data
marquee
Custom Model
Custom Model
Frame
Custom model
Custom model
Image
Menu

Info
Info
News
Album
Counter
Info
News
News
Contact
Contact
Info
Service info
Service course
Info
Info
Movie
Image
Info

Information
Information
News
Image
Service
Information
News
News
Connection
Connection
Information
Service
Service
Information
Information
information
Image
information

Image
Custom Model
Custom Model
Custom mode
Menu

Image
External Link
External Link
Info
Info

Image
Partners
Partners
Information
Information

Application
Application

Application
Contact

Application
Connection

Type of Content

201

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

4. Design Current UWE Navigation Model

This section presents the current UWE structure of models, and designs the Use
Case diagram, UWE content model, and navigation model for the case study.
4.1. Presenting Current UWE Model
UWE is a formal approach that allows the modeling of the architecture, the
navigation space and the interfaces of web systems. It defines a UML profile
including stereotypes which denote new modeling elements [2-3]. The modeling
process proposed by UWE is composed by four steps:
Requirement Analysis with Use Cases.
Conceptual Model.
Navigation Model.
Presentation Model.
Those models are related to each other through dependent associations as it is
shown Figure 4. This means that the models have to be consistent each other, i.e., if
there is any change the use of the case model, it will be reflected on the all other
models.

Figure 4. UWE Models [2]

Figure 4, Models built during the design of the UTM homepage of the UWE,
adapted from [2] Artifacts of the Use Case model, Conceptual Model and
Navigation Model are exemplified and explained in the next section. However, since
the presentation model is not the focus of this paper, so it will not present any
artifact of that modeling step. Samples of Presentation Model artifacts and more
details about UWE modeling process and its artifacts can be found in [2 -5].
4.2 Use Case Ddiagram for the Case Study
For modeling a web application applying UWE, the initial stage is the
requirements of elicitation that is set in a Use Case model, see Figure 4.

202

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

Two types of Use Cases are distinguished by UWE: navigation Use Cases depict
activities of navigation of the user, similar to seeing the news and events. On the
other hand, the business logic of the web application is captured by standard UML
Use Cases. During the procedure of modeling, these Use Cases will be filtered
subsequently.
Another diagram in UWE is called the Use Case diagram is explained for
implementation reasons of ArgoUWE as a plugin module, which the only difference
from the UML Use Case diagram is permission for Use Cases of navigation. Figure
4 shows the Use Case Diagram for UTM homepage.

Figure 4. Use Case Diagram for UTM Homepage

Copyright 2014 SERSC

203

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

4.3. Content Model

On the basis of requirement's analysis, web application content is modeled in a
conceptual model in UWE and a UML class diagram represents it. Conceptual
classes, associations, and packages are the major model elements. It can be seen
from the Figure 5, that the conceptual model of the UTM homepage is a case study.
In this homepage, the general visitor can access links and homepage contents for
example; Change language, Search Content, Visit links and so on.

Figure 5. UWE Content Model for the UTM Homepage

4.4. Navigation Model
For drawing navigation model from the conceptual model, we are provided by
ArgoUWE and when "Navigation Diagram" from the menu "Create Diagram"
ArgoUWE creates navigation classes and associations for every navigation
relevant conceptual classes and every association among them into a recently
navigation model. Some links can be added by the modeler can add some links by
following the creation of the navigation diagram automatically. As one of the
buttons that are encircled in Figure 6 is chosen, ArogUWE does automatic creation
of indexes and menus. At any time that the diversity on the target end is more than
one, an index is added between two classes of navigation, that are association via an

204

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

organization. All classes that have greater than one outgoing association linked with
Menus. The UTM homepage, Figure 6 shows the navigation model for the UTM
homepage before enhancement which means before adding enhancement elements
(menu, index and query) by current ArgoUWE tool. Also the elements for design
navigation model shown in Table 3.

Figure 6. UWE Navigation for the UTM homepage, before Auto

Enhancement
The next step is to add menus between navigation classes and access primitives.
The user can add indexes, menus, and queries nodes automatically [25]:
Index: are added by the tool between two classes related by an association
whenever the multiplicity on the target end is greater than one.
Menus: added by the tool to every class that has more than a single outgoing
association. Menus are included by composition.
Query: added by the tool to every class that the node related to run a query.
The result of adding indexes, menus, queries and query for Figure 6, is shown in
Figure 7, which shows the navigation model for the UTM homepage after
automatically enhancement by ArgoUWE.

Copyright 2014 SERSC

205

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

Figure 7. UWE Navigation for the UTM Homepage, after Auto Enhancement
In the navigation model diagram as shown in Figure 6, we drew the navigation
model for the UTM homepage from the content model by using ArgoUWE, but this
diagram shows all classes as a one class named is "Navigation Class" which seems
to show that all relationships between the contents and homepage are the same;
therefore we enhanced this diagram by using navigation classes (menu, index and
query)in the ArgoUWE, it enhanced the navigation model automatically as shown in
Figure 7, but also it is not enough to fully support all homepage contents, because
the homepage has more different types of module design, but navigation model has
just three enhancement elements and cannot represent all different elements
concretely. The following shows models designing the UTM homepage where
navigation classes could not support it:

206

Top Menu-1: we using another class (menu) for representing it.

Flash News: we using another class (index) for representing it.
Marquee Link: we using another class (index) for representing it.
Where we are: we using another class (index) for representing it.
News and announcement: we using another class (index) for representing it.
Frame: we using another class (index) for representing it.

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

Chat: we using another class (navigation class) for representing it.

5. Enhance UWE Navigation Model

The process enhancement consists of old UWE, extension UWE and new UWE.
In the old UWE, we explain the structure UWE for extension metamodels and
relation UWE with UML as profitable, in the extension UWE we prepare and define
new elements for supporting homepages content as defined in Section 4.6. in the
new UWE present the new elements and how to use these elements for supporting
homepages content. Figure 8 shows the process enhancement of UWE.

Figure 8. Process Enhancement UWE

5.1. Current UWE
Object-focused, repetitive and cumulative are the characteristics of the UWE
process. Unified Process forms the basis for it [26], and UWE process encompasses
the entire life cycle of web applications concentrating on design and automatic
generation [2-3]. Lightweight UML profile is the UWE representation used for the
examination and design of Web applications [27] and is circulated in several earlier
articles, explained in section 4.
5.2. Extension UWE
Based on the extension tools demarcated by the UML itself, it is a UML
extension, i.e., the extension is conducted by the demarcation of stereotypes, tagged
values and OCL restrictions. The visible depiction of the requisites and in the design
of the theoretical model, the navigation construction, the business logic and the
demonstration characteristics of web applications utilizes these modeling
features[28], Figure.9 shows the mechanism of extension of UWE [29].

Figure 9. Michaniem for Extension UWE [29]

For defining new elements we need the above steps as shown in Figure 6. The
first step is an explain the structure of the models, the second step is defining new
elements, in the third step we define a meta-attributes, in the fourth step we defining
meta associations. In the fifth step we constrain a new element by OCL language, in

Copyright 2014 SERSC

207

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

the finally we create a graphic icon for the new elements. For easer application we
are using tabular form for the above steps, Table 3 shows the define new elements.
Table 3. Extension UWE to Define New Elements for Navigation Model
No.

Main
Menu

Stere
otype
Main
Menu

Flash
News

Flash
News

{Tiltle model=Flash
News, text=string,
image=,share=n,ema
il=,Number
Elments=n}

Multi
Data

Multi
Data

Marque
e

Marqu
ee

Frame

Frame

{Title
model=MultiData,
text=string,image=
,Number Elments=n}
{Title
model=Marquee,
text=string,image=
,Number Elments=n}
{Title model=Frame,
text=string,image=
,Number
Elments=n,spaceframe
=}

Applica
tion

Applic
ation

Name

Attribute
{Title
menu=Mainmenu,
Number Elments=n,
name
of
elrmnts=string}

{Title
model=Application,
text=string,image=
,URL=RunFile}

List of
attribute
Name
Number
Elements

Constraints

Icon

context: mainmenu
inv:
name.size()<=40
inv:
number >= 0 &&
number <= 100
inv:
elements.size()<=40

Text
Image
Share
Email
number
scroller
Text
Image
number
scroller
Text
Image
number
move
Text
Image
number
space
Move

context:
inv:
inv:
inv:
inv:

Text
Image
URL

context:
inv:
inv:
inv:

FlashNews
text.size()>=0
image >=0
share.size()<=40
number>=0

context: MultiData
inv:
text.size()<=40
inv:
image=>0
inv:
number >= 0
context: Marquee
inv:
text.size()<=40
inv:
image=>0
inv:
number >= 0
context: Frame
inv:
text.size()<=40
inv:
image=>0
inv:
number >= 0
Framespace.size() >= 0
Application
text.size()<=40
image=>0
URL =Run

As showed in Table 3, we defined new six elements to improve UWE navigation

model where Main Menu, Flash News, Multi Data, Marquee, Frame and
Application. In the next section we will show the ability this elements how to
enhance UWE navigation model through redesign case study.
5.3. New UWE
The new UWE is a current UWE with the addition of the new elements to support
homepage's content. which we can use it for web the applications if need it. The
new elements in UWE can solve most weaknesses of homepage's content, which
consists of (Main Menu, Flash News, Multi Data, Marquee, Frame, Application), as
shown in Table 3, in section 6, we will use the new elements to development UTM
homepage through design navigation model. In the design navigation model for
UTM homepage we will use the new elements instead of weak elements to the
approval of our work.

6. Redesign UTM Homepage by the New UWE

For designing the UTM homepage by the new UWE, we designed only the
navigation model and the presentation model, because the content model does not
change and does not need to define elements, we will design a new Navigation

208

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

model and Presentation model for UTM homepage with applying a new UWE
elements for the navigation model as shown in Figure 10.

Figure 10. UWE Navigation Model for the UTM Homepage, After
Enhancement
After the process extension of the UWE navigation model and defined new
elements we applied the elements to design the UTM homepage as show n in Figure
10. In this figure, we replaced the weak elements with the new elements and we got
a new navigation model for the UTM homepage which as able to fully support the
UTM homepage contents. In this diagram had replaced the following elements:
Top Menu-1: We replaced sub menu element as a new element with menu as
an old element.
Flash News: We replaced flash news element as a new element with index as
an old element.
Marquee Link: We replaced marquee element as a new element with index as
an old element.

Copyright 2014 SERSC

209

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

Where we are : We replaced multi data element as a new element with index
as an old element.
News and announcement: We replaced multi data element as a new element
with index as an old element.
Frame: We replaced frame element as a new element with index as an old
element.
Chat: We replaced application element as a new element with navigation node
as an old element.

7. Comparison and Evaluation

In the following table shows a comparison between UWE navigation model
before and after enhancement.
Table 4. Comparison between old UWE and new UWE
Homepage web
Design Models

Navigation Model
Old UWE

New UWE

Image
Text
Search
Main menu
Menu
Flash News
Counter
Multi Data
Marquee
Frame
Custom Model
Application

Not support
Partially support
Fully support

Not support
Using another class
Fully support

In the above comparison Table 4, showed the navigation model after

enhancement has a best ability to design and develop UTM homepage. In some of
the elements old UWE and new UWE has the same ability such as Image, Text,
Search, Menu and Custom Model. But other elements could be supported partially in
old UWE such as Main Menu, Flash News, Multi Data, Marquee, Frame and
Application, after enhancement there are fully supported based on UTM homepage.
However the six elements applied on the UTM homepage as our Case Study also
will be used for the development of other web pages.

8. Conclusion and Future Work

As it can be noted through the case study presented in this paper, although UWE
provides a good approach to design web systems, since it provides stereotypes and
methods that allow the designer to model the specific features of systems which
belong to that application domain as the navigation space and structure, UWE still
needs to be improved. We identified some limitations during the development of our
case study, which have to be fixed in order to make the modeling process as
automated as possible which is one of the goals of UWE, according to its author [2 4].

210

Copyright 2014 SERSC

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

We presented here some proposals to extend UWE methodology, in order to

improve the web navigation project. Through this work, we could identify the need
of representing the call of methods of a navigation class that is used to achieve the
system functionality in the navigation model. We proposed to represent the call of
methods of a specific class through the addition of self-relationships which role
names are the same of the method signatures, as it was stated in Section 3.3.1. We
could also identify the need of representing implicit links that result from
relationships of aggregation and inheritance established in the conceptual model.
We proposed a new modeling element to represent that kind of links and some new
steps in the construction methods of the navigation structure model. Those proposals
were presented in Section 3.3.2. Another need we have identified is relative to
represent the visit to a navigation class to validate the data through an access
element. For that, we proposed to use the query defined by UWE adding a new
semantic to it, as it was stated in Section 3.3.2.
We intend to continue exploring UWE modeling process and to identify other
limitations that the methodology can present proposing solutions for those. We are
also performing experiments in which usability guidelines are considered, and we
intent to explore the impact that the extensions we proposed in this work has on the
system usability. Finally, such results will be experienced in order to discover new
design patterns to support the challenge of projecting web systems.

References
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]

[11]
[12]
[13]

[14]
[15]
[16]
[17]
[18]
[19]
[20]

H. Baumeister, N. Koch and L. Mandel, "Towards a UML extension for hypermedia design", UML99The Unified Modeling Language, ed: Springer, (1999), pp. 614-629.
H. Baumeister, N. Koch and L. Mandel, "Towards a UML extension for hypermedia design", UML99The Unified Modeling Language, (1999), pp. 76-76.
N. Koch and A. Kraus, "Towards a common metamodel for the development of web applications", Web
Engineering, (2003), pp. 419-422.
C. Kroi and N. Koch, "The UWE Metamodel and ProfileUser Guide and Reference", Technical
Report 1101, Ludwig-Maximilians-Universitt Mnchen (2011).
M. O. Leavitt and B. Shneiderman, "Research-based web design & usability guidelines", US
Department of Health and Human Services, (2006).
N. Koch and A. Kraus, "Towards a common metamodel for the development of web applications", Web
Engineering, ed: Springer, (2003), pp. 497-506.
G. Rossi, "Web engineering: modelling and implementing web applications", Springer, vol. 12, (2008).
K. Vlaanderen, F. Valverde and O. Pastor, "Improvement of a web engineering method applying
situational method engineering", ICEIS (3-1), (2008), pp. 147-154.
J. Conallen, "Building Web applications with UML", Addison-Wesley Professional, (2003).
L. Baresi, F. Garzotto and M. Maritati, "W2000 as a MOF Metamodel", Proc. of the 6th World
Multiconference on Systemics, Cybernetics and Informatics-Web Engineering track. Orlando, USA,
(2002).
A. Kraus and N. Koch, "A metamodel for UWE", Citeseer(2003).
J. Gmez and C. Cachero, "OO-H Method: extending UML to model web interfaces", Information
modeling for internet applications, pp. 144-173, (2003).
A. Schauerhuber, M. Wimmer and E. Kapsammer, "Bridging existing Web modeling languages to
model-driven engineering: a metamodel for WebML", Workshop proceedings of the sixth international
conference on Web engineering, (2006), pp. 5.
S. Meli, J. Gmez and N. Koch, "Improving web design methods with architecture modeling", ECommerce and Web Technologies, ed: Springer, (2005), pp. 53-64.
N. Koch, A. Kraus and R. Hennicker, "The authoring process of the uml-based web engineering
approach", First International Workshop on Web-Oriented Software Technology, (2001).
N. Koch and A. Kraus, "The expressive power of uml-based web engineering", Second International
Workshop on Web-oriented Software Technology (IWWOST02), (2002).
A. F. P. de Carvalho and J. C. A. Silva, "Extending UWE to improve Web navigation project-a case
study", Systems, Man and Cybernetics, 2005 IEEE International Conference on, (2005), pp. 2608-2613.
T. A. Jackson, "Web page design: a study of three genres", University of North Carolina, (1999).
A. Kennedy and M. Shepherd, "Automatic identification of home pages on the web", System Sciences,
2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference, (2005), pp. 99c-99c.
UTM. , UTM homepage. Available: http://utm.my/, (2013).

Copyright 2014 SERSC

211

International Journal of Software Engineering and Its Applications

Vol.8, No.4 (2014)

[21] apple., apple homepage. Available: http://www.apple.com/,(2013).

[22] m. zain., maherzain homepage. Available: http://www.maherzain.com/,(2013).
[23] B. M. North, Joomla! 1.6: A User's Guide: Building a Successful Joomla! Powered Website: Pearson
PTR, (2011).
[24] joomla, Joomla! documentation. Available: http://docs.joomla.org, (2013).
[25] A. Knapp, N. Koch, F. Moser and G. Zhang, "ArgoUWE: A CASE tool for Web applications", First
International Workshop on Engineering Methods to Support Information Systems Evolution
(EMSISE'03), (2003).
[26] G. Booch, I. Jacobson and J. Rumbaugh, "The unified software development process", Reading:
Addison Wesley, (1999).
[27] G. Booch, J. Rumbaugh and I. Jacobson, "The unified modeling language user guide", Pearson
Education India, (1999).
[28] A. Knapp, N. Koch, G. Zhang and H. M. Hassler, "Modeling business processes in web applications
with ArgoUWE", 2004-The Unified Modeling Language. Modelling Languages and Applications,
(2004), pp. 69-83.
[29] D. Philippe, "UML Profiles versus Metamodel extensions: An ongoing debate", OMGs UML
Workshops: UML in the. com Enterprise: Modeling CORBA, Components, XML/XMI and Metadata
Workshop, (2000), pp. 6-9.

Authors
Karzan Wakil, He is lecturer at the University of Human
Development-Iraq and Fine Arts Institute in Sulaimaniyah-Iraq,
received BSc. Degree in Computer Science from Salahaddin
University-Iraq-2006 and M.Sc. in Computer Science from University
Technology Malaysia (UTM), Malaysia, 2013. His research areas are:
Web Engineering, Software Engineering and Web System.
karzanwakil@gmail.c om or karzan.wakil@uhd.edu.iq.

Amirhossein Safi, he is graduated from Master of Science in

Computer Science, Universiti Teknologi Malaysia (UTM) in 2013. His
bachelor degree is coming from Faculty of Computer Engineering,
Shahid Bahonar University of Kerman, Iran. His current research
interests include Web services, Service Oriented Architecture (S OA),
distributed systems, Smart Environments, and Web methodologies.
samirhossein2@live.utm.my

Assoc. Prof. Dayang N.A Jawawi, is an Associate Professor in Software

Engineering Department, Faculty of Computing, Universiti Teknologi
Malaysia (UTM). She received her B.Sc. in Software Engineering from
Sheffield Hallam University, UK, and her M.Sc. and Ph.D. in the field of
Software Engineering from Universiti Teknologi Malaysia. She has been an
academic staff at Software Engineering Department for over ten years and
she is currently serving as the Head of Department since October 2009. She
is a member of the Software Engineering Research Group (SERG), KEconomy
Research
Alliance,
UTM,
dayang@utm.my.
http://comp.utm.my/dayang/.

212

Copyright 2014 SERSC