Supporting requirements modelling in the Malay language using essential use cases

Massila Kamalrudin*, John Grundy, John Hosking

*Corresponding author for this work

    Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

    3 Citations (Scopus)

    Abstract

    Requirements are typically modelled in natural language, leading to inconsistencies, incompleteness and incorrectness due to inherent natural language ambiguities and lack of precise modelling rules. In previous work, we developed a technique and toolset to support extraction of requirements from English text and supporting semi-formal modelling and roundtrip refinement using Essential use cases, helping to mitigate some of these problems. In this paper we describe new work applying this human-centric approach to requirements engineering to the Malay language. We describe an extension of our original Essential Use Cases toolset to support requirements modelling in the Malay language essential interaction modelling, and results of a preliminary experiment to gauge our tool's effectiveness in supporting Malay natural language extraction and round-trip requirements refinement.

    Original languageEnglish
    Title of host publicationProceedings - 2012 IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC 2012
    Pages153-156
    Number of pages4
    DOIs
    Publication statusPublished - 2012
    Event2012 IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC 2012 - Innsbruck, Austria
    Duration: 30 Sept 20124 Oct 2012

    Publication series

    NameProceedings of IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC
    ISSN (Print)1943-6092
    ISSN (Electronic)1943-6106

    Conference

    Conference2012 IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC 2012
    Country/TerritoryAustria
    CityInnsbruck
    Period30/09/124/10/12

    Fingerprint

    Dive into the research topics of 'Supporting requirements modelling in the Malay language using essential use cases'. Together they form a unique fingerprint.

    Cite this