Enhancement of UWE Navigation Model.pdf

8/18/2019 Enhancement of UWE Navigation Model.pdf

1/16

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

ISSN: 1738-9984 IJSEIA

Copyrightⓒ 2014 SERSC

Enhancement of UWE Navigation Model: Homepage

Development Case Study

Karzan Wakil1, Amirhossein Safi2 and Dayang. N. A. Jawawi2

1College of Science & Technology, University of Human Development-Iraq2 Faculty Of Computing ,University Technology Malaysia, J.B.,Skudai 81300,

Malaysia

[email protected], [email protected] , [email protected]

Abstract

UML-based Web Engineering (UWE) is a web engineering methodology which provides a systematic approach to development of web applications. It provides a UMLextension, defining modeling elements considering the extension mechanisms that are

offered by UML. Navigation model is presented as a very critical characteristic in all thehypermedia and web methodologies; also homepage one of the most important pages onthe web sites, because it is the key to showing the quality of websites. The UWEnavigation 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 ofthe 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 theUWE navigation model through defining six elements by using an extension mechanismto 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. Since1999, web application has been extended constantly [1-3]. UWE is method based onstandards. UWE focused on visual modeling together with systematic design andautomatic generation, whose objective is to cover the entire life cycle of webapplication development [4].

UWE metamodel is a design considered as the conservative extension of theUnified Modeling Language (UML) metamodel, in other words that the modelingelements of the UML metamodel are inherited from the UML metamodel, and theyare 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 defineObject Constraint Language (OCL) restrictions on further static semantics and it isequivalent to well-formed rules in the UML specs [4].

Homepage one of the most important pages on the website because clearlycommunicates the site's purpose, and show all major options available on the pageand the key to showing the quality of website. Solving the usability in homepagehelp 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 tosupport 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


2/16


Vol.8, No.4 (2014)

198 Copyrightⓒ 2014 SERSC

methodology and presents new approaches for improving the navigation modeldefined 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 thehomepages directly because the UWE navigation model does not have enough

elements to represent the content of homepages, also it is a design considered as theconservative extension of the UML metamodel, also the metamodel provides a gooddescription to development homepages.

The paper is organized as follows: Section 2 explains the background work forthe UWE metamodels especially navigation model. In Section 3 we selected the casestudy and analyzed it. Section 4 consists of designing a case study by UWE. InSection 5 we enhance the UWE navigation model. In Section 6 we redesignnavigation model for the case study after enhancement. In Section 7 we makecomparison and evaluation UWE navigation model. In the last section we presentsome concluding remarks and points to future works.

2. Background Work

In the past few years, some Web Engineering methods have suggested anoperation to the development of Web Applications. The significance of thenavigation between the application nodes is the meaning of the navigational modelwhich is one of the fields [8].

Several researchers in the Web Engineering community have exploitedmetamodeling and UML extensions in defining web models [9-14].

A “lightweight” UML profile developed in the last works that are the notationused 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 utilizinga conventional notation that does not affect the interchange formats and can besupported by tools without any difficulty. The design features required to design

various characteristics of web applications, such as navigation, presentation, usertask, and adjustment aspects are defined by stereotypes and tagged values and areincluded in the UWE profile. And showed the package of the navigation model inUWE at Figure 1 [3].

Figure 1. UWE Navigation Package [3]


3/16


Vol.8, No.4 (2014)

Copyrightⓒ 2014 SERSC 199

UWE Navigation categories, connections and a group of indexes, guided toursand queries are created from the navigation model. The perceptions over theconceptual categories are the navigation categories and connections. Likewise, theuser 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 designmodels[4].

The pioneering work of Conallen [10] uses, in conjunction with the standardUML diagrams, the Web Application Extensions (WAE), which comprise thetypical Web artifacts (server pages, client pages, forms and frames). The mainadvantage of WAE proposal is that its simplicity allows efficiency the designartifacts the Web Interface, as well as to drive the implementation of such asinterface. On the other hand, this same simplicity evidences a lack of elements formodeling navigation and representing technology and device independentrequirements.

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 spaceand structure, UWE still needs to be improved. Koch, Kraus, and R. Hennickeridentified 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 isone of the goals of UWE, according to its author [15-16].

Carvalho, and Junia 2005, presented here some proposal's to extend UWEmethod, in order to improve the web navigation project, through this work, theycould identify the need of representing the call of methods of a navigation class thatis used to achieve the system functionality in the navigation model. They proposedto represent the call of methods of a particular class through the addition of self-relationships that role names are the same of the method signatures. They could alsoidentify the need of representing implicit links that result from relationships ofaggregation and inheritance established in the conceptual model. They proposed anew 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) – CustomerView [17]


4/16


Vol.8, No.4 (2014)


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

3. Case Study and AnalysesThere are many classifications for the typology of web pages and homepages,

Jackson showed four ways for categorize of web pages according to organizeridentity, number of pages, organizer’s goal, and based on measure and success web pages [18]. moreover Alistair Kennedy and Michael Shepherd classified homepagesfor three categories are: personal homepage, corporate homepage and organizationhomepage [19]. We choosing a case study in each of categories as shown in Table 1.

Table 1. Categories of Homepage with Case Study

Category Case study

organization homepage UTM homepage [20]

corporate homepage Apple homepage [21] personal homepage Maher Zain homepage [22]

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

Figure 3. UTM Homepage

In this paper for enhancement UWE navigation model, we utilize the UniversityTechnology Malaysia (UTM) homepage as the case study, because it is a longhomepage 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


5/16


Vol.8, No.4 (2014)


like Chat, Feedback. Briefly UTM homepage has all modules when used in Appleand Maher Zain homepage. Figure 3 shows the UTM homepage, this picture wastaken 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 designwe grouped them according to Joomla script [23-24] as shown in Table 2, thatshows the types of modules design, types of content, and categories for the UTMhomepage content.

Table 2. Classification of the UTM Homepage Contents

No. Homepage contentsType of the Module

Web DesignType of Content

Name of

categories

1 Logo Image Image Image

2 Head menu-Accessibility

Menu Info Information

3 Head menu-My UTM Menu Info Information

4 Languages-English Menu Switch language Languages5 Languages-Malay Menu Switch language Languages

6 Search Search Search info Service

7 Top Menu 1-About Us Main menu Info Information

8 Top Menu 1-Admission Main menu Application Application

9 About Us-introduction Sub menu Info Information

10 About Us-facts &

history

Sub menu Info Information

11 Top Menu 2-Staff Menu Info Information

12 Top Menu 2-Alumni Menu Info Information

13 Flash News Flash New News News

14 Begin Virtual Tour Image Album Image

15 Visitor’s Counter Counter Counter Service16 Where we are Menu Info Information

17 News & Announcement Multi data News News

18 Events @ UTM Multi data News News

19 Find Us on-face book Multi data Contact Connection

20 Find Us on- twitter Multi data Contact Connection

21 Marquee Link marquee Info Information

22 Online service Custom Model Service info Service

23 Course Finder Custom Model Service course Service

24 Frame Frame Info Information

25 Faculties and Schools Custom model Info Information

26 Media Custom model Movie information

27 Campus Image Image Image

28 About Us-Vision &

Mission

Menu Info information

29 Map and Direction Image Image Image

30 Partners – KPT Custom Model External Link Partners

31 Partners – Msc Custom Model External Link Partners

32 Text Custom mode Info Information

33 Footer Menu-Agency

Policy

Menu Info Information

34 Footer Toolbar-Chat Application Application Application

35 Feed Back Application Contact Connection


6/16


Vol.8, No.4 (2014)


4. Design Current UWE Navigation Model

This section presents the current UWE structure of models, and designs the UseCase 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, thenavigation space and the interfaces of web systems. It defines a UML profileincluding 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 isshown 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 othermodels.

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, sincethe 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 moredetails 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.


7/16


Vol.8, No.4 (2014)


Two types of Use Cases are distinguished by UWE: navigation Use Cases depictactivities of navigation of the user, similar to seeing the news and events. On theother hand, the business logic of the web application is captured by standard UMLUse Cases. During the procedure of modeling, these Use Cases will be filteredsubsequently.

Another diagram in UWE is called the Use Case diagram is explained forimplementation reasons of ArgoUWE as a plugin module, which th e only differencefrom the UML Use Case diagram is permission for Use Cases of navigation. Figure4 shows the Use Case Diagram for UTM homepage.

Figure 4. Use Case Diagram for UTM Homepage


8/16


Vol.8, No.4 (2014)


4.3. Content Model

On the basis of requirement's analysis, web application content is modeled in aconceptual model in UWE and a UML class diagram represents it. Conceptualclasses, associations, and packages are the major model elements. It can be seenfrom 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 forexample; 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 byArgoUWE and when "Navigation Diagram" from the menu "Create Diagram"

ArgoUWE creates navigation classes and associations for every “navigationrelevant” conceptual classes and every association among t hem into a recentlynavigation model. Some links can be added by the modeler can add some links byfollowing the creation of the navigation diagram automatically. As one of the buttons that are encircled in Figure 6 is chosen, ArogUWE does automatic creationof 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


9/16


Vol.8, No.4 (2014)


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

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

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 associationwhenever the multiplicity on the target end is greater than one. Menus: added by the tool to every class that has more than a single outgoingassociation. 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 inFigure 7, which shows the navigation model for the UTM homepage afterautomatically enhancement by ArgoUWE.


10/16


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 thisdiagram shows all classes as a one class named is "Navigation Class" which seemsto show that all relationships between the contents and homepage are the same;therefore we enhanced this diagram by using navigation classes (menu, index andquery)in the ArgoUWE, it enhanced the navigation model automatically as shown inFigure 7, but also it is not enough to fully support all homepage contents, becausethe homepage has more different types of module design, but navigation model has just three enhancement elements and cannot represent all different elementsconcretely. The following shows models designing the UTM homepage where

navigation classes could not support it:

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.


11/16


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 definenew elements for supporting homepages content as defined in Section 4.6. in thenew UWE present the new elements and how to use these elements for supportinghomepages 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 encompassesthe entire life cycle of web applications concentrating on design and automatic

generation [2-3]. Lightweight UML profile is the UWE representation used for theexamination and design of Web applications [27] and is circulated in several earlierarticles, 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, taggedvalues and OCL restrictions. The visible depiction of the requisites and in the designof the theoretical model, the navigation construction, the business logic and thedemonstration characteristics of web applications utilizes these modelingfeatures[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. Thefirst step is an explain the structure of the models, the second step is defining newelements, 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


12/16


Vol.8, No.4 (2014)


the finally we create a graphic icon for the new elements. For easer application weare 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.

Name

Stere

otype Attribute

List of

attribute Constraints Icon

1

MainMenu

MainMenu

{Titlemenu=”Mainmenu”,

Number Elments=n,

name of

elrmnts=”string”}

Name Number

Elements

context: mainmenu

inv: name.size()= 0 &&

number =0inv: share.size()=0

3MultiData

MultiData

{Titlemodel=”MultiData”,text=”string”,image=””

,Number Elments=n}

TextImagenumber

scroller

context: MultiDatainv: text.size()0inv: number >= 0

4

Marque

e

Marqu

ee

{Title

model=”Marquee”,

text=”string”,image=””,Number Elments=n}

Text

Image

numbermove

context: Marqueeinv: text.size()0inv: number >= 0

5

Frame Frame {Title model=”Frame”,text=”string”,image=””

,NumberElments=n,spaceframe=””}

TextImage

numberspaceMove

context: Frameinv: text.size()0inv: number >= 0Framespace.size() >= 0

6

Applica

tion

Applic

ation

{Title

model=”Application”,

text=”string”,image=””,URL=”RunFile”}

Text

Image

URL

context: Applicationinv: text.size()0inv: 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 andApplication. In the next section we will show the ability this elements how toenhance 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. Thenew elements in UWE can solve most weaknesses of homepage's content, whichconsists of (Main Menu, Flash News, Multi Data, Marquee, Frame, Application), asshown in Table 3, in section 6, we will use the new elements to development UTMhomepage through design navigation model. In the design navigation model for

UTM homepage we will use the new elements instead of weak elements to theapproval of our work.

6. Redesign UTM Homepage by the New UWE

For designing the UTM homepage by the new UWE, we designed only thenavigation 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


13/16


14/16


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 elementwith 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

MarqueeFrame

Custom Model

Application

In the above comparison Table 4, showed the navigation model afterenhancement has a best ability to design and develop UTM homepage. In some ofthe 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 inold UWE such as Main Menu, Flash News, Multi Data, Marquee, Frame andApplication, after enhancement there are fully supported based on UTM homepage.

However the six elements applied on the UTM homepage as our Case Study alsowill 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 andmethods 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 ourcase study, which have to be fixed in order to make the modeling process asautomated as possible which is one of the goals of UWE, according to its author [2-

4].

Not support Not support

Partially support Using another class

Fully support Fully support


15/16


Vol.8, No.4 (2014)


We presented here some proposals to extend UWE methodology, in order toimprove the web navigation project. Through this work, we could identify the needof representing the call of methods of a navigation class that is used to achieve thesystem functionality in the navigation model. We proposed to represent the call ofmethods 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. Wecould also identify the need of representing implicit links that result fromrelationships of aggregation and inheritance established in the conceptual model.We proposed a new modeling element to represent that kind of links and some newsteps in the construction methods of the navigation structure model. Those proposalswere presented in Section 3.3.2. Another need we have identified is relative torepresent the visit to a navigation class to validate the data through an accesselement. For that, we proposed to use the query defined by UWE adding a newsemantic 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 arealso 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 thesystem usability. Finally, such results will be experienced in order to discover newdesign patterns to support the challenge of projecting web systems.

References

[1] H. Baumeister, N. Koch and L. Mandel, "Towards a UML extension for hypermedia design", UML’99-

The Unified Modeling Language, ed: Springer, (1999), pp. 614-629.[2] H. Baumeister, N. Koch and L. Mandel, "Towards a UML extension for hypermedia design", UML’99-

The Unified Modeling Language, (1999), pp. 76-76.[3] N. Koch and A. Kraus, "Towards a common metamodel for the development of web applications", Web

Engineering, (2003), pp. 419-422.

[4] C. Kroiß and N. Koch, "The UWE Metamodel and Profile – User Guide and Reference", Technical

Report 1101, Ludwig-Maximilians-Universität München (2011).[5]

M. O. Leavitt and B. Shneiderman, "Research-based web design & usability guidelines", USDepartment of Health and Human Services, (2006).

[6] N. Koch and A. Kraus, "Towards a common metamodel for the development of web applications", WebEngineering, ed: Springer, (2003), pp. 497-506.

[7] G. Rossi, "Web engineering: modelling and implementing web applications", Springer, vol. 12, (2008).

[8] K. Vlaanderen, F. Valverde and O. Pastor, "Improvement of a web engineering method applyingsituational method engineering", ICEIS (3-1), (2008), pp. 147-154.

[9] J. Conallen, "Building Web applications with UML", Addison-Wesley Professional, (2003).[10] 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).[11] A. Kraus and N. Koch, "A metamodel for UWE", Citeseer (2003).[12] J. Gómez and C. Cachero, "OO-H Method: extending UML to model web interfaces", Information

modeling for internet applications, pp. 144-173, (2003).

[13]

A. Schauerhuber, M. Wimmer and E. Kapsammer, "Bridging existing Web modeling languages tomodel-driven engineering: a metamodel for WebML", Workshop proceedings of the sixth international

conference on Web engineering, (2006), pp. 5.[14] S. Meliá, J. Gómez and N. Koch, "Improving web design methods with architecture modeling", E-

Commerce and Web Technologies, ed: Springer, (2005), pp. 53-64.[15] 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).[16] N. Koch and A. Kraus, "The expressive power of uml-based web engineering", Second International

Workshop on Web-oriented Software Technology (IWWOST02), (2002).[17] 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.[18]

T. A. Jackson, "Web page design: a study of three genres", University of North Carolina, (1999).

[19] 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.

[20]

UTM. , UTM homepage. Available: http://utm.my/, (2013).


16/16


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: PearsonPTR, (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", OMG’s UMLWorkshops: 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 UniversityTechnology Malaysia (UTM), Malaysia, 2013. His research areas are:

Web Engineering, Software Engineering and Web System.

[email protected] om or [email protected].

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 (SOA),

distributed systems, Smart Environments, and Web methodologies.

[email protected]

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 andshe is currently serving as the Head of Department since October 2009. She

is a member of the Software Engineering Research Group (SERG), K-

Economy Research Alliance, UTM, [email protected].

http://comp.utm.my/dayang/.
http://comp.utm.my/department-of-software-engineering/http://comp.utm.my/department-of-software-engineering/http://comp.utm.my/dayang/comp.utm.myhttp://www.utm.my/mailto:[email protected]:[email protected]://www.utm.my/http://comp.utm.my/dayang/comp.utm.myhttp://comp.utm.my/department-of-software-engineering/http://comp.utm.my/department-of-software-engineering/

Documents

Enhancement of UWE Navigation Model.pdf