Requirements recovery using ontology model for capturing end-to-end interaction of proven application software

Elviawaty M. Zamzami, Eko K. Budiardjo, Heru Suhartanto

Research output: Contribution to journalArticlepeer-review

3 Citations (Scopus)

Abstract

An existing application software perhaps has no requirements document or requirements document does not represent the application. The situation creates a problem in application software maintenance or reengineering. Thus, requirements document should be reconstructed from the existing application software. Effort on reconstructing a requirements document from the existing application software is similar to requirements document construction for a new application software, needs requirements elicitation. Requirements elicitation can be done using an ontology model that captures end-to-end interaction between users and system. Using the ontology model does not need software documentation and source code at all, the only one is the existing application software itself. In this case, the existing application software should be executed and then observed its behavior in term of end-to-end interaction on each starting point in which the interface identified. This set of interaction flows is known as a Use Case Realization (UCR) in Requirements Management with Use Case (RMUC) approach. The appropriate ontology model provides an ease to understand the software requirements semantic meaning. The model consists of two models includes, WIMP-UI (Window Icon Menu Pointer - User Interface) and USI (User - Interaction) ontology models.

Original languageEnglish
Pages (from-to)425-434
Number of pages10
JournalInternational Journal of Software Engineering and its Applications
Volume7
Issue number6
DOIs
Publication statusPublished - 2013

Keywords

  • End-to-end interaction
  • Requirements
  • Requirements Elicitation
  • Requirements Reconstruction
  • USI ontology
  • WIMP-UI ontology

Fingerprint

Dive into the research topics of 'Requirements recovery using ontology model for capturing end-to-end interaction of proven application software'. Together they form a unique fingerprint.

Cite this