GUI prototype generation from scenarios in the requirements elicitation phase

Junko Shirogane, Hiroshige Shibata, Hajime Iwata, Yoshiaki Fukazawa

    Research output: Chapter in Book/Report/Conference proceedingConference contribution

    3 Citations (Scopus)

    Abstract

    In the requirements elicitation phase, operation flows of software are often defined by scenarios. It is necessary to define appropriate operation flows as scenarios in terms of easily comprehended operation flows, efficiency, etc. Then scenarios are implemented as software Graphical User Interfaces (GUIs). If the operation flows are defined inappropriately, the implemented GUIs may require modifications in the late software development phase. Although defining appropriate operation flows is difficult in the requirements elicitation phase, operation flows of GUIs cannot be always modified in the late software development phase. Thus, it is necessary for end users to evaluate the appropriateness of operation flows in scenarios. Herein we propose a method to generate GUI prototypes from scenarios. By parsing the events in the target scenarios, which are written in a natural language, GUI prototypes are automatically generated. Using the generated GUI prototypes, the appropriateness of operation flows can be evaluated by end users. If problems arise, the GUI prototypes can be modified in the early requirements elicitation phase.

    Original languageEnglish
    Title of host publicationProceedings of the IASTED International Conference on Software Engineering, SE 2014
    PublisherActa Press
    Pages31-38
    Number of pages8
    DOIs
    Publication statusPublished - 2014
    EventIASTED International Conference on Software Engineering, SE 2014 - Innsbruck
    Duration: 2014 Feb 172014 Feb 19

    Other

    OtherIASTED International Conference on Software Engineering, SE 2014
    CityInnsbruck
    Period14/2/1714/2/19

    Fingerprint

    Graphical user interfaces
    Software engineering

    Keywords

    • Generation
    • GUI
    • Prototype
    • Scenario

    ASJC Scopus subject areas

    • Software

    Cite this

    Shirogane, J., Shibata, H., Iwata, H., & Fukazawa, Y. (2014). GUI prototype generation from scenarios in the requirements elicitation phase. In Proceedings of the IASTED International Conference on Software Engineering, SE 2014 (pp. 31-38). Acta Press. https://doi.org/10.2316/P.2014.810-021

    GUI prototype generation from scenarios in the requirements elicitation phase. / Shirogane, Junko; Shibata, Hiroshige; Iwata, Hajime; Fukazawa, Yoshiaki.

    Proceedings of the IASTED International Conference on Software Engineering, SE 2014. Acta Press, 2014. p. 31-38.

    Research output: Chapter in Book/Report/Conference proceedingConference contribution

    Shirogane, J, Shibata, H, Iwata, H & Fukazawa, Y 2014, GUI prototype generation from scenarios in the requirements elicitation phase. in Proceedings of the IASTED International Conference on Software Engineering, SE 2014. Acta Press, pp. 31-38, IASTED International Conference on Software Engineering, SE 2014, Innsbruck, 14/2/17. https://doi.org/10.2316/P.2014.810-021
    Shirogane J, Shibata H, Iwata H, Fukazawa Y. GUI prototype generation from scenarios in the requirements elicitation phase. In Proceedings of the IASTED International Conference on Software Engineering, SE 2014. Acta Press. 2014. p. 31-38 https://doi.org/10.2316/P.2014.810-021
    Shirogane, Junko ; Shibata, Hiroshige ; Iwata, Hajime ; Fukazawa, Yoshiaki. / GUI prototype generation from scenarios in the requirements elicitation phase. Proceedings of the IASTED International Conference on Software Engineering, SE 2014. Acta Press, 2014. pp. 31-38
    @inproceedings{44bfb69d519545ce92e067a6af3f2abe,
    title = "GUI prototype generation from scenarios in the requirements elicitation phase",
    abstract = "In the requirements elicitation phase, operation flows of software are often defined by scenarios. It is necessary to define appropriate operation flows as scenarios in terms of easily comprehended operation flows, efficiency, etc. Then scenarios are implemented as software Graphical User Interfaces (GUIs). If the operation flows are defined inappropriately, the implemented GUIs may require modifications in the late software development phase. Although defining appropriate operation flows is difficult in the requirements elicitation phase, operation flows of GUIs cannot be always modified in the late software development phase. Thus, it is necessary for end users to evaluate the appropriateness of operation flows in scenarios. Herein we propose a method to generate GUI prototypes from scenarios. By parsing the events in the target scenarios, which are written in a natural language, GUI prototypes are automatically generated. Using the generated GUI prototypes, the appropriateness of operation flows can be evaluated by end users. If problems arise, the GUI prototypes can be modified in the early requirements elicitation phase.",
    keywords = "Generation, GUI, Prototype, Scenario",
    author = "Junko Shirogane and Hiroshige Shibata and Hajime Iwata and Yoshiaki Fukazawa",
    year = "2014",
    doi = "10.2316/P.2014.810-021",
    language = "English",
    pages = "31--38",
    booktitle = "Proceedings of the IASTED International Conference on Software Engineering, SE 2014",
    publisher = "Acta Press",

    }

    TY - GEN

    T1 - GUI prototype generation from scenarios in the requirements elicitation phase

    AU - Shirogane, Junko

    AU - Shibata, Hiroshige

    AU - Iwata, Hajime

    AU - Fukazawa, Yoshiaki

    PY - 2014

    Y1 - 2014

    N2 - In the requirements elicitation phase, operation flows of software are often defined by scenarios. It is necessary to define appropriate operation flows as scenarios in terms of easily comprehended operation flows, efficiency, etc. Then scenarios are implemented as software Graphical User Interfaces (GUIs). If the operation flows are defined inappropriately, the implemented GUIs may require modifications in the late software development phase. Although defining appropriate operation flows is difficult in the requirements elicitation phase, operation flows of GUIs cannot be always modified in the late software development phase. Thus, it is necessary for end users to evaluate the appropriateness of operation flows in scenarios. Herein we propose a method to generate GUI prototypes from scenarios. By parsing the events in the target scenarios, which are written in a natural language, GUI prototypes are automatically generated. Using the generated GUI prototypes, the appropriateness of operation flows can be evaluated by end users. If problems arise, the GUI prototypes can be modified in the early requirements elicitation phase.

    AB - In the requirements elicitation phase, operation flows of software are often defined by scenarios. It is necessary to define appropriate operation flows as scenarios in terms of easily comprehended operation flows, efficiency, etc. Then scenarios are implemented as software Graphical User Interfaces (GUIs). If the operation flows are defined inappropriately, the implemented GUIs may require modifications in the late software development phase. Although defining appropriate operation flows is difficult in the requirements elicitation phase, operation flows of GUIs cannot be always modified in the late software development phase. Thus, it is necessary for end users to evaluate the appropriateness of operation flows in scenarios. Herein we propose a method to generate GUI prototypes from scenarios. By parsing the events in the target scenarios, which are written in a natural language, GUI prototypes are automatically generated. Using the generated GUI prototypes, the appropriateness of operation flows can be evaluated by end users. If problems arise, the GUI prototypes can be modified in the early requirements elicitation phase.

    KW - Generation

    KW - GUI

    KW - Prototype

    KW - Scenario

    UR - http://www.scopus.com/inward/record.url?scp=84898411106&partnerID=8YFLogxK

    UR - http://www.scopus.com/inward/citedby.url?scp=84898411106&partnerID=8YFLogxK

    U2 - 10.2316/P.2014.810-021

    DO - 10.2316/P.2014.810-021

    M3 - Conference contribution

    AN - SCOPUS:84898411106

    SP - 31

    EP - 38

    BT - Proceedings of the IASTED International Conference on Software Engineering, SE 2014

    PB - Acta Press

    ER -