Summary of the Work:
Use case modeling can be used to specify the functional requirements of a software system. UML use cases are usually structured and documented using some natural language. Hence issues like ambiguity, inconsistency and incompleteness are inevitably introduced in the specifications. Therefore, the experimental study was conducted to investigate that how increased formalism affects the specification efforts and its use in the analysis modeling. The study is conducted between the UML use case Template [OMG] and the more formal use case template [Tiwari et al. 2012]. The evaluation is made on completeness, correctness and redundancy of the class diagrams obtained during analysis modeling. Moreover, we have also evaluated the usability aspects of both the use case templates using the comprehension questionnaires. The questionnaires include the measures like applicability of the rules, ease of generating analysis models, ease of developing use case templates, and maintainability.
This Web page shows the details of the experiment conducted and the materials like, Rules for generating the use case templates; Examples of the use case templates and class diagrams generated by the subjects; conducted quizzes; comprehension questionnaires; box plots analysis for the eight projects.
Experimental Materials:
I. Software Requirement Specification to Use case Models
Rules for generating UML use case Template
Rules for generating more Formal use case Template
II. Example of the use case templates and class diagrams
III. Conducted Quizzes
Quiz 1 about the use case templates
Quiz 2 about the generation of analysis models from the use case templates
IV. Qualitative Analysis
Web link for the responses
V. Box-Plots analysis for the eight projects.
Other Links or information are updated soon...