원문정보
초록
영어
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.
목차
1. Introduction
2. Sources of Requirements Recovery on Existing Application Software
3. End-to-End Interaction
4. End-to-end Interaction Ontology Model
4.1. WIMP-UI Ontology Model
4.2. USI Ontology Model
4.3. Merging WMP-UI and USI Ontology Models
5. Requirements Elicitation vs Requirements Recovery
5.1. Elicitation Techniques
5.2. Requirements Recovery Using WIMP-UI⊔USI Ontology Model
6. Conclusion
7. Future Research
References
