Use Case Diagram Extraction Technique from Requirements Specification

KIPS Journal D (2001 ~ 2012) , Vol. 9D, No.4, pp.639-650, April 2002
10.3745/KIPSTD.2002.9D.4.639, Full Text

Abstract

We have to carry out systematic, definite requirements analysis for the successful development of software. The UML gives the ways to grasp user or customer requirements and decide the boundary of business systems from the use case modeling. This paper presents how to extract use case diagram from the requirements specification systematically by applying the standardized rules as a part of the study for use case modeling. We modify requirements specification by applying RRS(Rules for Requirements Specification) and extract actor, use case, relationship by applying RA(Rules for Actors), RU(Rules for Use Cases) and RR(Rules for Relationships) to the modified requirements specification separately and then become to make out use case diagram in the end. By applying the rules presented in this paper to the requirements specification for personnel management, we can reduce the existing difficulties of extracting use case diagram based on the narrative descriptions without any standardized rules.


Statistics

Show / Hide Statistics

Statistics (Cumulative Counts from October 15, 2016)

Multiple requests among the same browser session are counted as one view. If you mouse over a chart, the values of data points will be shown.


Cite this paper

[KIPS Transactions Style]
C. J. Yoo and S. Y. Jeong, "Use Case Diagram Extraction Technique from Requirements Specification," KIPS Journal D (2001 ~ 2012) , Vol.9D, No.4, pp.639-650, 2002, DOI: 10.3745/KIPSTD.2002.9D.4.639.

[IEEE Style]
Cheol Jung Yoo and So Young Jeong, "Use Case Diagram Extraction Technique from Requirements Specification," KIPS Journal D (2001 ~ 2012) , vol. 9D, no. 4, pp. 639-650, 2002. DOI: 10.3745/KIPSTD.2002.9D.4.639.

[ACM Style]
Yoo, C. J. and Jeong, S. Y. 2002. Use Case Diagram Extraction Technique from Requirements Specification. KIPS Journal D (2001 ~ 2012) , 9D, 4, (2002), 639-650. DOI: 10.3745/KIPSTD.2002.9D.4.639.