Abstract

UML is revealed to contain three different defects concerning the use-case class that were buried in OOSE and handed over to it. These defects are: 1) the use-case class and its instance are unusually defined, 2) a conjecture that is against the definition of the class is introduced without any reasons, and 3) the execution procedure of a use-case instance does not actually work because of some flaws concerning the execution control. 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 using a use case in the analysis and design stages, and another definition of the use-case class is constructed that successfully solves the problems.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.