Keywords : Goal Oriented Requirement Engineering (GORE), Goal Model, OWL, Software Product Line, e-

  Volume VII 7 No 1 (2016): JEMT Volume VII, Issue 1(13) Spring 2016 DOI: https://doi.org/10.14505/jemt.v7.1(13).00

  

Addresing Consistency Checking Of Goal Model For

Software Product Line Government Tourism System

  Ahmad Nurul Fajar, Master of Information System Department Bina Nusantara University,

  Jakarta,Indonesia, afajar@binus.edu Imam Marzuki Shofi

  Informatics Department UIN Syarif Hidayatullah, Tangerang, Indonesia, imam_shofi@uinjkt.ac.id

  Suggested Citation: Natalia A. ZAITSEVA, Anna A. LARIONOVA, Igor G. MINERVIN, Ruslan V. YAKIMENKO, Irina V. BALITSKAYA (2015).Foresight Technologies Usage in Working Out Long Term. Forecasts of Service and Tourism Personnel Training System Development, (Volume VI Issue 2(12) Winter 2015 2(10): 410-417 doi:10.14505/jemt.v5.2(10).01 .Available from: http://www.asers.eu/asers_files/jemt/JEMT_VolumeVI_Issue2%2812%29_Winter2015_online.pdf

  Article’s History: Received Februari, 2016; Revised March, 2016; Accepted March, 2016.

  2016. ASERS Publishing. All rights reserved.

  Abstract :

Software Product Line Development needed inconsistency checking in order to improve software

quality.In order to handle conflict (inconsistency) is one of active areas in the research of Goal Oriented

Requirements Engineering (GORE). Ontology is used to capture the knowledge of certain domain wished.

One of the features of Ontology described using OWL is the checking of consistency. The case study is

Indonesian Government Tourism System. This paper presents how to develop software product line in

Indonesian Government with the Ontology OWL that used for the consistency checking in the software

product line for e-government applications. It is important, because the software product line would be

derived from goal model that has been consistent and no conflict These paper presents how the

Ontology OWL act to handle inconsistency checking in goal model. The first step conducted is to convert

the goal model into Ontology using Protégé. Parallel with the first step, Ontology with equipped carried

out the checking consistency of terminology, designation, and structure. The next step is to conduct the

checking of logic consistency (Strong conflict and/or Weak conflict) by defining the rules using SWRL

Tab

Keywords : Goal Oriented Requirement Engineering (GORE), Goal Model, OWL, Software Product Line, e-

  government

  JEL Classification: Industrial Organization

1. Introduction

  Requirement Engineering (RE) is the process of discovering purpose of system software, this process with identifying stakeholders and their needs, and also documenting these in a form that will be guidance to analysis, communication, and subsequent implementation (Lapouchnian, A, 2005). There are difference between RE and

  J

ournal of Environment Management and Tourism Ahmad Nurul Fajar

  more promising than other system- and functionality-based techniques used in most of the traditional Software Engineering methodologies (Donzelli et al, 2003). Goal Oriented Requirement Engineering (GORE) is an approach in which is having orientation of Goal and Actor recently has the popularity that increased dramatically.

  The main reason for this is more better than of the traditional systems analysis approaches when dealing with more and more complex software systems (Lapouchnian, A, 2005). The quality of software consists of much indicator. It has been long recognized that inadequate, incomplete, ambiguous, or inconsistent requirements have a significant impact on the quality of software (Anwar et al,2006). There are 5 types of consistencies: terminology clash, designation clash, structure clash, strong conflict, and weak conflict (Donzelli et al, 2003). There are many domain research area in GORE. Handling Goal Conflicts in GORE is a part of active area in the research of GORE. It can be a separate challenge to do a research (Anwar et al,2006). The conflict basically emerges from the goal model. Although it is possible that the conflict occurs in the operational model, but it will take root from the underlying goal, so that it must be handled in the goal model (Nuseibeh et al, 2000).Ontologies are used to capture knowledge about some domain of interest , and then,one of the features of Ontology described using OWL is that it can be processed the checking of consistency (Serrano et al, 2012).

2. Theoritical Foundation

  GORE is an approach in the RE that having orientation of Goal and Actor recently has the popularity that increased dramatically. Goal is a condition or state of affairs in the world that the stakeholders would like to achieve. There are concepts of goal: goal type, belief, constraint, levels of abstraction, taxonomies, requirement, assumptions, attributes, and link (Serrano et al, 2012).The goal type is based on functional requirement and non- functional consisting of 3 types: achievement goal, soft goal, and maintenance goal (Anwar et al,2006). Figure 1 below explains about mind map of GORE. _{Metode Lihat MindMap Metode GORE Highest GORE} Level Abstraksi High _{Agent Low Hard Maintenance Achievement} Goal Type _{Atribut Priority Name Soft Specificationm Utility Konsep Constraint Gaol Taxonomies} Feasibility Asumption Belief

  

Figure 1. Mind Map of GORE (Shofi et al, 2012)

  Goal under responsibility of single agent in the software-to-be becomes requirement (Serrano et al, 2012). Goal under responsibility of a single agent in the environment of the software-to-be becomes an assumption (Anwar et al,2006). Goal links provides the means to ensure different kind of traceabilities (Serrano et al, 2012). The software systems that have commonality and variability features can be managed by Software Product Line Engineering (SPLE). SPLE is an approach to produce a software system with diversity software system. (Pohl, 2005). SPLE consists of domain engineering and application engineering (Pohl, 2005). ZEF Framework are the framework for aligning SOA and BPM in Indonesian Government System (Budiardjo et al, 2013).

  Volume VII 7 No 1 (2016): JEMT Volume VII, Issue 1(13) Spring 2016

3. Case Study

  In this paper, we presented the solution of the mapping of Goal Model in the GORE, in this case we selected the GSP framework into OWL that can be seen in the following table (Shofi et al, 2012)

  

Table 1. Correspondence between Components of GSP and OWL

Component GSP Component OWL

  Goal Class Sub Goal Sub Class Relation AND Property with relation AND Relation OR Property with relation OR Contribution Link Property Skills Class Preferences Class

  We proposed Framework in figure 2 below, this framework is guidance for develop Indonesian Software Product Line Tourism System.

  

Figure 2 . Proposed Framework

  According to figure 2 above, figure 3 below describe the conceptual of software product line tourism system in Indonesian Government. It consists of domain engineering and application engineering.

  

Figure 3 . Software Product Line Government Tourism System

Indonesian Government Tourism System has variation of commonality and variability features (Fajar et al, 2012).

  The commonality feature has the same function in various systems software. The variability feature has a variety functions in systems software due to locality (Fajar et al, 2014). It is a challenge to re-use or modify parts of the features due to change in similar domain without distracting the whole system. The ability to respond to government regulation changing is possible by software product line. Whilst software system developers use various approach to capture features through requirement analysis (Fajar et al, 2014). Figure 5 below describes the role of information systems development.It shows that the diversity of software systems developers with diverse technologies and designs to develop features of software system based on the results. It is used to monitor the development of software systems by multiple software system developers to develop government tourism systems. It provides development flexibility in applying of design and technologies based on the regulatory requirement corridor.The Software Product Line Government Tourism System could be used as a

  J

ournal of Environment Management and Tourism Ahmad Nurul Fajar

  platform for development of new system in domain Tourism and Hotel System. It can make a flexible environment in dynamic system, especially Government Tourism System, that called adaptable. _{Software Product Line (SPL)}

  REQUIREMENTS DESIGN _{U L}

_{AT Developer of software systems Product}

_{IO N}

_{BPM ….n ….n}

_{F M} ^{IMPLEMENTATION TESTING}

₁

_{1 R} EG

Figure 5 . Software Product Line adaptable (Fajar et al, 2014)

  A case study has been also carried out to the Module of Government Tourism System , in this case ”Application of

  Management and Controlling of Program/Activities that we called as LAKSANA. Goal Model of the application can be seen in the following figure 4: _{ProgramManaged BuggetManaged Program&BuggetManaged AND AnnualBuggetPlanningCreated BuggetPlanned BuggetRealized BuggetMonitored BuggetEvaluated AND AnnualBuggetPlanningRevised} AND

_{CreatedFromScratch CopiedFromPrevious}

_{MigratedFromExistingFormatFile} OR _{OR CreatedUsingTemplate}

_{StandardExcelFormatProvided StandardExcelFormatRead StandardExcelFormatConverted}

MigratedFromExcelFormatFile _{AND MigratedFromOtherFormatFile}

  

Figure 4. Goal Model LAKSANA

Consistency checking of Goal Model

  The inconsistency checking of terminology, designation, and structure has been conducted with reasoner (Pellet 1.5.2) available in the Protégé 3.4.8 by clicking the menu "Check Consistency (Gopalakrishnan Nair et al, 2010). And then it has been carried out the consistency checking of its logic. We conducted with the following prosedures:

  1. Made new class "GoalConflict" to accommodate the goal that having a potential conflict, and class "SoftwareAgent" that representing Software Agent

  2. Made the rules with SWRL Tab enabling the occurrence of conflict among the goal

  3. Execute the rules We already do those steps in our cases. For example, in our LAKSANA case, besides the addition of new classes (GoalConflict & SoftwareAgent), we also needed to add new properties: "open", "close" to simulate the occurrence of conflict in the goal "StandardExcelFormatRead" if conducted Open ExcelFormatFile as well as

  Volume VII 7 No 1 (2016): JEMT Volume VII, Issue 1(13) Spring 2016

Figure 6. Defining Rules with SWRLTab

  Conclusion

  This research focuses on Requirements Analysis phase in developing the Software Product Line (SPL).Premise of this research is features of Indonesian Government System are not optimize and not fully in accordance with regulation. Another condition, difficulty in managing commonality and variability of features that developed by developers of software systems so diverse. This condition can be overcome by developing the software Product Line (SPL).Based on the discussion that has been carried out in the previous chapters, so it can be concluded that to develop software product line in government tourism system, we can use Ontology OWL used to represent the GORE based on the rules of mapping presented can be used for the inconsistency checking. The inconsistency checking for terminology, designation, and structure has been performed using (Pellet 1.5.2) available in the Protégé 3.4.7. and then for the consistency checking of its logic (strong & weak conflict) by utilizing Jess Tab and SWRL Tab to manage the rules of its logic. The consistency checking with SWRL Tab generally can be conducted although it is still in the limited cases so that it is necessarily improved more. The next step to be conducted is to do the accomplishment of its consistency checking such as the defining of library in order that it can be used for all cases. In addition, it also needs for the improvement of its Ontology modeling such that the built-in goal model of Ontology indicates [subject]+predicate+[object] so that it facilitates in the consistency checking of its goal .

  CKNOWLEDGEMENTS A

  This work was supported by to Professor Zainal A Hasibuan, Professor Heru Suhartanto and Dr. Eko K Budiardjo at Faculty of Computer Science University of Indonesia.

  References Book

  1. Lapouchn ian, A., “Goal-Oriented Requirements Engineering: An Overview of the Current Research”, Department of Computer Science University Of Toronto, 2005, Canada.

2. Pohl, K, Guinter,B, & Frank VL, Software Product Line Engineering, Foundations, Principles, and

  Techniques,SPRINGER, 2005

  Journal article 1.

  T.R.Gopalakrishnan Nair and V. Suma ,The Pattern of Software Defects Spannin Across Size Complexity, Int.J. of Software Engineering, IJSE Vol.3 No.2 July 2010 2.

  Budiardjo EK., Ahmad N.F, Zainal.A.H.. ZEF Framework on E-Government Applications : Featuring SOA and BPM Allignment. International Journal Computer Theory and Engineering (IJCTE),

  IACSIT,2013

  J ournal of Environment Management and Tourism Ahmad Nurul Fajar

  Paper presented at a meeting or conference 1.

  Donzelli, P., Bresciani, P., “Goal Oriented requirements Engineering: a case Study in eGovernment”, proceedings of the 15th Conference on Advanced Information Systems Engineering (CAISE’03), Klagenfurt, Austria, 16-20 June, 2003, Austria 2. .Anwer, S., Ikram, N., “Goal Oriented Requirement Engineering: A Critical Study of Techniques”, XIII ASIA PACIFIC SOFTWARE ENGINEERING CONFERENCE (APSEC'06), 2006.

  3. B. Nuseibeh, S. Easterbrook. “Requirements Engineering: A Roadmap”. Proc. Conference on the Future of Software Engineering.Limerick, Ireland, June 2000, Ireland

4. M.A. Serrano, J. G´omez-

  Romero, M.A. Patricio, J. Garc´ıa, J.M. Molina. “Ontological representation of time-of-flight camera data to support vision-based AmI. 4th International Workshop on Sensor Networks and Ambient Intelligence 2012, Lugano (23 March 2012). Lugano 5. Shofi IM, Eko K. Budiardjo, "/ Addressing OWL Ontology for Goal Consistency Checking/", The 14th

  International Conference on Information Integration and Web-based Applications & Services (iiWAS) 2012, 3 - 5 Desember 2012, Sanur, Indonesia, 2012 6. Fajar AN, Eko K Budiardjo, Zainal A Hasibuan R2FM Method for Requirement Analysis in Software

  Product Line For E-Government Applications, IPCT,Rhome, Italy, 2014 7. Fajar AN., Eko K.B., Zainal A.H.. System Architecture in Dynamic Environment based on Commonality and Variability Business Processes. 8th ICCM Seoul,IEEE,Seoul, 2012