It further makes use of the questionnaire-based approach to develop the remaining unpopulated parts of the use case template. The approach uses Natural Language (NL) parser to identify Parts-Of-Speech (POS) tags, Type Dependencies (TDs) and semantic roles from the input text specification to populate use case elements. In this paper, we propose a systematic transformation approach that automatically extracts various use case elements from textual problem specifications.
Develop code from use case diagrams software#
Several approaches have been proposed to maintain the synergy of use cases with other software models, but no systematic transformation approach is available to extract use case scenarios from the textual requirements specification. Use case modeling refers to the process of identifying scenarios written in some natural language text, particularly to capture interactions between the system and associated actors. The results of this experiment demonstrate that using SSUCD leads to an improvement in consistency between use case models and their associated descriptions. This experiment also investigates the impact of improving consistency amongst Use Case models on other key Use Case modeling quality attributes. This paper presents a controlled experiment, which evaluates the reduction of inconsistencies resulting from deploying a new structure called (Simple Structured Use Case Descriptions) SSUCD, which is used to assist with the development of Use Case descriptions. The repercussions of inconsistencies have been well documented, but little progress has been made towards reducing and remedying their effects.
In Use Case driven approaches, the damaging effects of inconsistencies escalate as inconsistencies have a detrimental influence on every aspect of the development process. The problem of inconsistencies in Use Case models has plagued practitioners over the years and has been a topic of interest for many researchers.
0 kommentar(er)
