Hi, I agree with your ask. For example, I split the requirements in packages (user req. system req., etc) and I have visually the requirements inside of its packages. I cannot do the relationship between two requirement of different packages, because callouts are not available.
I hope this feature will be implemented soon. Cordially, CarlosG On Mon, Mar 16, 2009 at 5:43 PM, <[email protected]>wrote: > Hi, > > The palette for the requirements diagram does allow the inclusion of a > UseCase (or many other NamedElements) in the diagram (an instance of such a > usage is shown in figure 16.4 on p.153 of the SysML specification), nor are > the various Callouts available. > > In *16.3.2.3 Requirement*, p.150 of *OMG SysML , Version 1.1*, the > following attributes are defined: > > • /satisfiedBy: NamedElement [*]Derived from all elements that are the > client of a «satisfy» relationship for which this requirement is a supplier. > • /verifiedBy: NamedElement [*]Derived from all elements that are the > client of a «verify» relationship for which this requirement is a supplier. > • /tracedTo: NamedElement [*]Derived from all elements that are the client > of a «trace» relationship for which this requirement is a supplier. > ... > • /refinedBy: NamedElement [*]Derived from all elements that are the client > of a «refine» relationship for which this requirement is a supplier. > > At the least, I think that the Callouts should be implemented - it may be > easier to do, and they are more useful in complex designs. > > Thanks, > > Van Lepthien > > > _______________________________________________ > Topcased-users mailing list > [email protected] > http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users >
_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
