R3ST for Requirements Recovery of Legacy Runtime Code | Zendy

Eko K. Budiardjo | Zendy; Elviawaty Muisa Zamzami | Zendy; Wahyudianto | Zendy

AI Assistant Blog Pricing

Home ZAIA Blog

Open Access

R3ST for Requirements Recovery of Legacy Runtime Code

Author(s) -

Eko K. Budiardjo,

Elviawaty Muisa Zamzami,

Wahyudianto

Publication year - 2014

Publication title -

lecture notes on software engineering

Language(s) - English

Resource type - Journals

ISSN - 2301-3559

DOI - 10.7763/lnse.2015.v3.155

Subject(s) - computer science , completeness (order theory) , consistency (knowledge bases) , software engineering , ontology , code (set theory) , programming language , legacy system , set (abstract data type) , software , database , artificial intelligence , mathematical analysis , philosophy , mathematics , epistemology

—In reality, we often find that proven and workable software, exist without source code. Identifying end-to-end interaction within existing legacy runtime code is a promising way for requirements recovery. Those identified interaction forms a set of use cases. Based on use case modeling concept, ontology is created for each finding interaction in order to check for completeness and consistency. OWL serves as platform for ontology development. That ontology reflects the recovered requirements. The procedures to identify the end-to-end interaction has been formulated and tested for university information systems. R3ST, tighly couple to Prote ge , has been developed with the objective to assist and automate those procedures.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.

Having issues? You can contact us here

Accelerating Research