Visual Representation of a plugin in a use case diagram built with starUML -
the question says all, how can build visual representation of plugin? have idea should regard else or not display can't find evidence (in high enough amount) sure of this.
should not display plugin in use case in situation @ all?
do need represent plugin package or actor instead? (if connection should have, include?)
or should represent interface?
maybe i'm off track here, last time made ucd year ago or something, it's slipping away when don't use stuff! wouldn't mind "beginners" advice here :)
use cases analysis, not design, therefore should omit architecture structure. when have plugin, system , therefore might system under development or actor. if system under development , use cases consider plugin, show using boundary box in diagram encompassing use cases (some tools don't allow that, make implicit). otherwise, if have use cases describe behaviour of system, interacts plugin, depict plugin actor.
Comments
Post a Comment