Requirements Recovery Using Ontology Model for Capturing End-to-End Interaction of Proven Application Software

  title={Requirements Recovery Using Ontology Model for Capturing End-to-End Interaction of Proven Application Software},
  author={Elviawaty Muisa Zamzami and Eko Kuswardono Budiardjo and Heru Suhartanto},
  journal={International Journal of Software Engineering and its Applications},
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… 

Figures and Tables from this paper

R3ST for Requirements Recovery of Legacy Runtime Code

R3ST, tighly couple to Prote ge , has been developed with the objective to assist and automate the procedures to identify the end-to-end interaction within existing legacy runtime code.

Towards End-to-end Interaction Ontology Development for Software Comprehension

Identifying end-to-end interaction within existing software is a promising way for run-time software comprehension and OWL serves as platform for ontology development.

Ontologies in human-computer interaction: A systematic literature review

There is an opportunity for HCI and ontology engineering professionals to get closer to build better and more effective ontologies, as well as ontology-based solutions.

Feature Modeling and Variability Modeling Syntactic Notation Comparison and Mapping

The comparison and mapping of FODA, CBFM and OVM to CVL where need to be explored first to define meta model mapping of these several approaches are reported.

Towards an Ontology Network on Human-Computer Interaction

This paper introduces HCI-ON, a Human-Computer Interaction Ontology Network composed of ontologies that have been developed and others found in the literature, which organizes and integrates knowledge, serving as a basis to several applications.



Requirements Recovery by Matching Domain Ontology and Program Ontology

An ontology-based reengineering approach to recovering requirements from existing systems is presented and the algorithm of ontology mapping is developed to match domain ontology and program ontology for requirement recovery.

The Domain Ontology and Domain Rules Based Requirements Model Checking

A formal approach to precisely describe ontology using description logic at first, and then model the integrity rules and derivation rules which restrict the business behavior is suggested.

Requirements recovery from legacy systems by analysing and modelling behaviour

  • Kecheng LiuA. AldersonZubair Qureshi
  • Computer Science
    Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360)
  • 1999
The semiotic approach aims at recovering requirements by studying the legacy system's behaviour by guiding the analysis to be conducted from a number of angles at certain levels of detail using various software engineering and semiotic techniques.

Recovering software requirements from system-user interaction traces

This paper has developed an algorithm, IPM, for interaction-pattern discovery that discovers patterns that meet a user-specified criterion and is robust to insertion errors, caused by user mistakes or by the availability of alternative scenarios for the same user task.

Ontology Modeling and Object Modeling in Software Engineering

The objective of this paper is to simplify object models compare with ontologies models and presents the available tools, methods, procedures, language, reusability which shows the corporation with object modeling and ontologies.


The proposed process uses different sources of information for the requirements of the legacy system, in addition to traditional techniques of analysis for its redocumentation, and is built progressively in successive cycles of execution for its refinement.

Use cases: requirements in context

A use case method for delivering a requirements-oriented set of deliverables and the methodology breaks down the activity of producing requirements into a series of steps, and it answers the questions that usually come up when people employ use cases.

Language engineering for the recovery of requirements from legacy documents

This report proposes that language engineering using tools that exploit probabilistic natural language processing (NLP) techniques offer the potential to ease the problems of exploiting legacy documents.

Reverse engineering goal models from legacy code

This paper refactor stakeholder goal models from two legacy software code bases: an unstructured Web-based email in PHP (SquirrelMail) and a structured email client system in Java (Columba).

A New approach to Requirements Elicitation Using Paper Prototype

An improved approach for requirements elicitation using paper prototype is proposed and an assessment of the new approach using student projects developed for various organizations is assessed.