Analysis of Use Case Requirements Using SFTA and SFMEA Techniques

Tiwari, Saurabh; Rathore, Santosh Singh; Gupta, Sudhanshu; Gogate, Vaibhav; Gupta, Atul

doi:10.1109/iceccs20050.2012.6299248

Cited by 5 publications

(1 citation statement)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To formulate the conversion procedure, we consider a set of use cases belonging to 20 use case templates obtained from various research articles (e.g. [5,8,9,28,29]) and industrial white papers (e.g. [6,7]).…”

Section: Phase 1: Conversion Of Given Use Case Template Into Intermed...mentioning

confidence: 99%

Automated class diagram elicitation using intermediate use case template

2021

View full text Add to dashboard Cite

Class diagrams, being more illustrative, provide an easier way of understanding software requirements compared to use case descriptions. Both manual and automated methods are used for the extraction of class diagrams from requirements. The automated techniques employ certain extraction rules and natural language processing methods. Each use case description template introduces a small set of extraction rules. However, when all types of templates are considered, the number of rules becomes large and the procedure becomes tedious. Thus, researchers restricted the class diagram extraction procedure to some specific use case description templates. However, such a restriction negatively affects the software developers as they get restricted to working with only limited templates. The proposed work in this paper strives to remove this restriction on developers by introducing an intermediate template. The traditional use case description templates get transformed into the intermediate template and the rule extraction procedure is then applied to this intermediate template. This reduces the total number of extraction rules and hence, brings down the extraction complexity. The class diagrams extracted from use case description templates of different domains using proposed technique show more accuracy in terms of completeness and correctness when compared with the state of the art approaches.This is an open access article under the terms of the Creative Commons Attribution License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited.

show abstract

Section: Phase 1: Conversion Of Given Use Case Template Into Intermed...mentioning

confidence: 99%

Automated class diagram elicitation using intermediate use case template

2021

View full text Add to dashboard Cite

show abstract

Use case specifications: How complete are they?

Tiwari

Gupta

2019

J Software Evolu Process

View full text Add to dashboard Cite

The flexibility of the use cases in specifying requirements from informal textual descriptions to more formal ones makes them usable in different contexts and purposes. However, the versatility of use cases regarding their admissible structure raises a natural concern about the specification completeness. This paper reports on the analysis of the eight different variants of use case template regarding their functional completeness, ability to express the set of particular functionalities, by comparing their information contents exercised by comprehensive questionnaires on five different problem specifications. The questionnaire was obtained from two sources: one based on the understanding of the functionality to be implemented and the other based on the functionality documented in eight different use case templates under study. Our results suggested that use cases can be used to specify a complete set of requirements intended to develop a software system. We found that the choice of a use case template influences the completeness of the specification. A more detailed analysis of the eight different variants of use case template resulted in the identification of 21 significant use case elements. We showed that by incorporating these significant use case elements in a given template, the completeness of the specification could be further enhanced.

show abstract

A Safety Requirement Elicitation Technique of Safety-Critical System Based on Scenario

Wang

Feng

2014

Intelligent Computing Theory

View full text Add to dashboard Cite

Analysis of Use Case Requirements Using SFTA and SFMEA Techniques

Cited by 5 publications

References 22 publications

Automated class diagram elicitation using intermediate use case template

Automated class diagram elicitation using intermediate use case template

Use case specifications: How complete are they?

A Safety Requirement Elicitation Technique of Safety-Critical System Based on Scenario

Contact Info

Product

Resources

About