Abstract
UML2.0 recently made a correction which eectively means that they finally abandoned the ACU conjecture, admitting it was wrong. The ACU conjecture is a fallacious statement that makes people believe that actors call operations of a use case. It originated in OOSE and was implicitly employed by UML. It caused serious defects in UML’s specification of the use-case class. Although the correction was made, it is utterly limited; the statement suggesting that actors call use-case operations disappeared, but all the defects caused by the conjecture remain untouched. This eloquently proves that UML people do not still recognize how wrong the ACU conjecture is. The paper first states what kinds of defects the ACU conjecture caused. It then makes a model of a designer’s simulation of a use case, derives a use-case class/object, and then specifies its static and dynamic properties. In relation with this, it clarifies the meaning of a use-case diagram that has been left ambiguous.
Sign-in/Register to access full text options 
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 callDisclaimer: 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.
