Improving UML's definition of the use-case class

✍ Scribed by Sadahiro Isoda

• Publisher: John Wiley and Sons
• Year: 2005
• Tongue: English
• Weight: 244 KB
• Volume: 36
• Category: Article
• ISSN: 0882-1666
• DOI: 10.1002/scj.20305

✦ Synopsis

Abstract

UML is shown to contain two defects concerning the use‐case class that originated in OOSE. These defects are: (1) the use‐case class and its instances are unusually defined, and (2) a conjecture that is against the definition of a use case is introduced without any reason. These defects have been causing unnecessary confusion in UML's specification of the use‐case class. An object‐oriented real‐world model is built that represents a typical situation of the employment of a use case in the analysis and design stages, and then another specification of the use‐case class is constructed, which successfully solves the problems. © 2005 Wiley Periodicals, Inc. Syst Comp Jpn, 36(6): 14–25, 2005; Published online in Wiley InterScience (www.interscience.wiley.com). DOI 10.1002/scj.20305