Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content Figure D.5 - Establishing Top Level Use Cases for the Hybrid SUV Figure D.6 - Establishing Operational Use Cases for Drive the Vehicle UseCases - UML subject vs SysML Block Package, Model, or SysML Block as UseCase owner SysMLv1: MagicDraw/Cameo: Having a SystemContext as the 'subject' of each main UseCase plays nicely with the feature for automated creation of usage-level allocation swimlanes in SysML Activity Diagrams for part properties. But it's not the only way. SysMLv1: "Should" the 'subject' of a top-level UseCase be a System or (a particular) SystemContext? Answer: Which one would you like to be correct!? [WITH EXTERNAL LINKS] SysMLv1: A common misunderstanding: Just because a UseCase symbol appears inside the rectangle of a subject Classifier does NOT mean that it is owned by that Classifier and can only have that one Classifier as 'subject', and it does not imply ownership! Webel: SysMLv1: Overview of annotated Diagram Slides and Note pages related to UseCases and their combination with a System (of interest), SystemContext, and drill-down to scenario Sequence Diagrams (Interactions) and Activity Diagrams. Source Unified Modeling Language 2.5.1 Copyright information About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes Snippet kind INFO UML keywords UseCase Classifier UseCase::subject Classifier::useCase Previous snippet Full quote subject : Classifier [0..*] (opposite Classifier::useCase) The subjects to which this UseCase applies. Each subject or its parts realize all the UseCases that apply to it. Next snippet Related snippets A UseCase specifies a set of actions performed by its subjects, which yields an observable result that is of value for one or more Actors or other stakeholders of each subject. Related snippets (backlinks) Visit also Visit also (backlinks) Flags
