A Domain Ontology for Eliciting Usability Features

  • Authors

    • Chian Wen Too
    • Sa’adah Hassan
    • Abdul Azim Abdul Ghani
    • Jamilah Din
    2018-12-09
    https://doi.org/10.14419/ijet.v7i4.31.23360
  • Ontology, Pattern, Requirement Engineering, Usability.

  • One of the crucial factors that can influence user preferences of software is usability.  It assesses the extent of which software able to facilitate user and use the software easily and effectively.  Typically, usability requirements are specified at the design stage of software development due to its characteristic that is subjective in nature and hard to be elicited at the early stage. As a result, the lack identification and improper treatment of usability features always caused the failure of a software product. Consequently, it increased the cost and effort of rework. Essentially, it suggested that usability need to be specified at the requirements engineering stage to complement the software functional requirements.  This paper presents a preliminary study on current efforts to support the activities in identifying usability attributes in the software functional requirements. The potential of adopting pattern and ontology for identifying usability features are also presented. The development of domain ontology is proposed to fill the gap of the current efforts where there is lack of usability driven semantic knowledge model to support the usability elicitation tasks. The designed domain ontology is expected to overcome the problems resulted from software developer that lack of sufficient knowledge or expertise in eliciting usability features at requirements engineering level. The main contribution is to provide a guideline to aid the requirements engineer to elicit and specify usability requirements start from the early stage of development phases.  

     

     

  • References

    1. [1] Shneiderman B (1986), Designing the User Interface: Strategies for Effective Human–Computer Interaction. Addison-Wesley, Reading, MA.

      [2] Nielsen J (1993), Usability Engineering. Morgan Kaufmann, 1994.

      [3] Cysneiros LM & Leite JCSDP (2004), Nonfunctional requirements: from elicitation to conceptual models. IEEE Transactions on Software Engineering, 30(5), 328–350.

      [4] Cysneiros LM, Werneck VM & Kushniruk A (2005), Reusable knowledge for satisficing usability requirements. 13th IEEE International Conference on Requirements Engineering (RE’05).

      [5] Jokela T, Seffah A, Gulliksen J & Desmarais MC (2005), Eight Guiding Designers to the World of Usability: Determining Usability Requirements through Teamwork. Springer Netherlands, Vol.8, 127-145.

      [6] Cronholm S & Bruno V (2008), Do you Need General Principles or Concrete Heuristics?: A Model for Categorizing Usability Criteria. In the 20th Australasian Conference on Computer-Human Interaction: Designing for Habitus and Habitat,ACM, Cairns,Australia.

      [7] Juristo N, Moreno AM & Sanchez M (2007), Guidelines for Eliciting Usability Functionalities. IEEE Transactions on Software Engineering, 33(11): 744-758.

      [8] Too CW, Hassan S, Ghani AAA, Din J (2017), Towards Improving Usability Requirements Elicitation and Specification Using Ontology-Driven Approach. Advanced Science Letters, Vol.23, No.5, May 2017, pp:4077-4081(5).

      [9] Juristo N (2009), Impact of usability on software requirements and design. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) Vol.5413, pp:55–77.

      [10] Ormeño YI & Panach JI (2013), Mapping study about usability requirements elicitation. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) Vol.7908 LNCS, pp:672–687.

      [11] Roder H (2012), Specifying Usability Features with Patterns and Templates. UsARE 2012, Zurich, Switzerland, pp:6-11.

      [12] Bass L & John BE (2000), Achieving usability through software architectural styles. CHI ’00 Extended Abstracts on Human Factors in Computing Systems, pp:171.

      [13] Bass L & John B (2003), Linking Usability to Software Architecture Patterns through General Scenarios. The J. Systems and Software, vol.66, no.3, pp:187-197.

      [14] Juristo N, Lopez M, Moreno AM & Sánchez MI (2003), Improving software usability through architectural patterns. International Conference on Software Engineering (ICSE), pp:12-19.

      [15] Ferre X, Juristo N, Windl H & Constantine L (2001), Usability Basics for Software Developers. IEEE Software, Vol.18, No.1, pp:22-29.

      [16] Laura Carvajal (2012), Usabilidad-Oriented Software Development Process, 1(2), 272. Retrieved from http://oa.upm.es/10599/1/LauraElena_Carvajal_Garcia.pdf

      [17] Trienekens JJM & Kusters RJ (2012), A framework for characterizing usability requirement elicitation and analysis methodologies (UREAM). IARA, pp:308–313.

      [18] Yu E (1997), Towards Modelling and Reasoning Support for Early Phase Requirements Engineering. In Proc. Of the 3rd IEEE Int. Symp. On Requirements Engineering, pp:226-235.

      [19] Rafla T, Robillard PN & Desmarais M (2007), A method to elicit architecturally sensitive usability requirements: Its integration into a software development process. Software Quality Journal, Vol.15, No.2, pp:117–133.

      [20] Folmer E, Van GJ & Bosch J (2003), A framework for capturing the relationship between usability and software architecture. Software Process Improvement and Practice, Vol.8,No.2, pp:67–87. http://doi.org/10.1002/spip.171

      [21] Rivero L, Barreto R &Conte T (2013), Characterizing Usability Inspection Methods through the Analysis of a Systematic Mapping Study Extension. Latin-American Center for Informatics Studies Electronic Journal, Vol.16, No.1.

      [22] Hassan S, Too CW & Kesava PR. (2013), An Analysis Framework for Identifying Usability Requirement in Mobile Application Development. Journal of Next Generation Information Technology (JNIT) Vol.4, No.4, June 2013.

      [23] Gruber TR (1993), Toward Principles for the Design of Ontologies Used for Knowledge Sharing. Proc. Int'l Workshop on Formal Ontology 1992.

      [24] Arpírez JC, Corcho O, Fernández-López M & Gómez-Pérez A (2003), WebODE in a nutshell. AI Magazine, Vol.24, No.3, pp:37-47.

      [25] Borst W (1997), Construction of Engineering Ontologies. PhD thesis, Institute for Telematica and Information Technology, University of Twente, Enschede, The Netherlands.

      [26] Studer R, Benjamins VR & Fensel D (1998), Knowledge Engineering Principles and Methods. Data and Knowledge Engineering, 25, 61-197.

      [27] Allemang D, Hendler JA (2008), Semantic Web for the Working Ontologist: Modeling in RDF, RDFS and OWL. Elsevier, Amsterdam.

      [28] Castaneda V, Ballejos L, Caliusco ML & Galli MR(2010), The use of Ontologies in Requirements Engineering. Global Journal of Researches in Engineering, Vol.10, No.6.

      [29] Ricardo de AF, Crediné Silva de M, Ana RR (1998), A Systematic Approach for Building Ontologies. IBERAMIA 1998: pp349-360.

      [30] Dermeval D, Vilela J, Bittencourt II, Castro J, Isotani S & Brito P (2015), Applications of ontologies in requirements engineering: A systematic review of the literature. Requirements Engineering, pp:1–33.

      [31] Fu Gh & Cohn A (2008), Utility Ontology Development with Formal Concept Analysis. Conference: Formal Ontology in Information Systems. Proceedings of the Fifth International Conference, FOIS 2008, Saarbrücken, Germany, October 31st - November 3rd, 2008, pp:297-310.

      [32] Noy NF & McGuinness DL (2001), Ontology Development 101: A Guide to Creating Your First Ontology. Stanford Knowledge Systems Laboratory, 25.

      [33] Fernández LM., Gómez P & Juristo N (1997), METHONTOLOGY: From Ontological Art Towards Ontological Engineering. AAAI-97 Spring Symposium Series, SS-97-06, pp:33–40. http://doi.org/10.1109/AXMEDIS.2007.19.

      [34] De Almeida FR (2014), SABiO: Systematic approach for building ontologies. CEUR Workshop Proceedings, 1301.

      [35] Shneiderman B & Plaisant C (2010), Designing the User Interface:Strategies for Effective Human-Computer Interaction. Fifth Edition. Pearson Addison-Wesley.

      [36] International Organization For Standardization ISO (2001), ISO/IEC 9126-1. Software Process: Improvement and Practice. http://doi.org/10.1002/(SICI)1099-1670(199603)2:1<35::AID-SPIP29>3.0.CO;2-3

      [37] International Organization For Standardization ISO (2011), ISO/IEC 25010: 2011. Software Process: Improvement and Practice Vol.2. Retrieved from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35733

      [38] Baader F, Calvanese D, McGuinness DL, Nardi D & Patel-Schneider PF (2010), The Description Logic Handbook: Theory, Implementation and Applications. Kybernetes, 32(9/10), 624. https://doi.org/10.1108/k.2003.06732iae.006

      [39] Kaiya H & Saeki M (2005), Ontology based requirements analysis: lightweight semantic processing approach. In Quality Software, 2005 (QSIC 2005). Fifth International Conference on IEEE, pp: 223-230.

      [40] Antoniou G, Franconi E & Harmelen FV (2005), Introduction to Semantic Web Ontology Languages, Norbert Eisinger Jan MaÅ‚uszy Ìnski (Eds.), LNCS: Reasoning Web, First International Summer School, July 25-29, 2005, pp:1-21. Springer.

  • Downloads

  • How to Cite

    Wen Too, C., Hassan, S., Azim Abdul Ghani, A., & Din, J. (2018). A Domain Ontology for Eliciting Usability Features. International Journal of Engineering & Technology, 7(4.31), 160-167. https://doi.org/10.14419/ijet.v7i4.31.23360