>From: "Wilson, Matt" <[EMAIL PROTECTED]> >To: "ROSE_FORUM" <[EMAIL PROTECTED]> >Sent: Monday, December 11, 2000 9:12 PM > The original problem *sounds* like a location problem. > > You used the keyword yourself when you said *realized*. Ok, ok... I don't want to be boring... but "to realize" in UML is a verb not used just for the predefined steretype <<realize>> in use case.. in general should be used everytime you want to get inside something and start watching at the internal implementation... think of Jackobson... "an interface (not a GUI he refers to) is realized by the methods of the hidden class"... Sorry for the accademy. > Although there has been some debate here before, I put the use case > realizations in the analysis view (a special package I put under the logical > view - along with a another folder at the same level for design). The > "main" diagram I have for these views are where I identify my tractability > between the original use case & the realizations. > > It would be *COOL* if someone (or even Rational) wrote into the product (via > script or other means) ways to "browse to..." your linked objects through > certain stereotype relationships (i.e. realized). > > Maybe...the flow could be ... > Select a use case. right mouse click - in the pop up menu have the ability > to jump to the objects that shares a particular association with the > selected object. The jump could just be in the tree browser or even jump to > the "main" diagram for the target object. Depending on the details of the > association you would know who realized whom & be able to go in either > direction!! I agree with you.. let's hope someone from Rational is reading us... One of the nicest and more useful concept in RUP is the tracebility... but I cannot see it inside Rose... for example think of Business Modelling: how can I trace that a particular system use case helps a particular activity in a business activity diagram? You can immagine it... with an hyperlink. In short there's not a real link in the model itself. > In the meantime... you can use the notes "hyperlink" as mentioned linking > your diagrams. > I hope this helps. If now I just rambled off a wish list item. :) Sure it helps... debating always helps Thanks Matt. Alberto Fossati [EMAIL PROTECTED] ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * *************************************************************************
Re: (ROSE) Problems with big sequence diagram
Alberto Fossati [ND Solutions] Mon, 11 Dec 2000 13:34:28 -0800
- (ROSE) Problems with big sequence diagram Jose Carlos Alves de Almeida
- Re: (ROSE) Problems with big sequence ... Eric D. Tarkington
- (ROSE) big sequence diagram: Gaaag... Eric D. Tarkington
- Re: (ROSE) Problems with big seque... Eric D. Tarkington
- (ROSE) Big System Traceability Eric D. Tarkington
- RE: (ROSE) Big System Trac... Jason Gorman
- (ROSE) Problems with big sequence diag... Jose Carlos Alves de Almeida
- RE: (ROSE) Problems with big sequence ... Singh, Shiv
- RE: (ROSE) Problems with big sequence ... Wilson, Matt
- RE: (ROSE) Problems with big seque... Alberto Fossati [ND Solutions]
- RE: (ROSE) Problems with big sequence ... Ahmed, Khawar
