[Daniel Kalderon] "we want everything to be record before getting to design time"
[wmj] "everything" has different meaning in different contexts/phases. I record 'everything' that I am relatively sure will be re-used/included in the next steps products'/artifacts/diagrams. If I am not "relatively sure" than 'investigating' potential 'next steps' should provide some insights. [Daniel Kalderon] For example, I want to use Activity Diagram to show flow of Use Case, and want to add to Use Case element what it is missing because we didn't use Rose ; properties like Pre Condition and Post Condition, ID, Requirement like and more... moreover we wanted to add more properties of our own project. [wmj] Those are real needs. Unfortunately 'template' use case construct does not have sufficient "expressive power". And how to merge extended use cases (structured text) with (Activity) Diagrams? Best WMJ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Ros�n-Lidholm Sent: Thursday, January 10, 2002 2:56 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: (RUP) RE: (ROSE) Define Tools to Rose Elements with Stereotype ( CaseID: v0995872, (ROSE) Define Tools to Rose Elements with Stere otype) "we want everything to be record before getting to design time" I strongly advise you to look at the best practices given by iterative development processes (such as Unified Process and eXtreme Programming) on this subject. If you actually manage to be effective and successful with a waterfall approach, please let us know how you did it! // Martin Ros�n-Lidholm -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Daniel Kalderon Sent: den 7 januari 2002 20:22 To: Cavan G Watson Cc: Buhtz, Greg; [EMAIL PROTECTED] Subject: RE: (ROSE) Define Tools to Rose Elements with Stereotype ( CaseID: v0995872, (ROSE) Define Tools to Rose Elements with Stere otype) Hello Kevin, First, 10x for your quick answer :) I'm Using Rational Rose Enterprise edition 2002, and not having mixed up with what modeling use case is all about... The Idea of adding properties of our own came up when we find out that what Rational designed as an element is not good enough for us, if you don't want Word templates to describe you element (like RUP is giving to describe Use Case).For example, I want to use Activity Diagram to show flow of Use Case, and want to add to Use Case element what it is missing because we didn't use Rose ; properties like Pre Condition and Post Condition, ID, Requirement like and more... moreover we wanted to add more properties of our own project. Stereotypes are ways of making Rose Elements less generic than they are, with 1) Properties common to all same Rose Elements of our projects, that Rose doesn't give with its regular Rose Element (Pre Cond, Post Cond...) 2) Properties for this specific Stereotype of Rose Element acting kind differently from one part of project to another. These properties I want to use before I realize the Use Case, because it is a long lasting project, and we want everything to be record before getting to design time. For now, I think I'll take your (and Rational) Idea to add all Properties needed for all stereotypes of Rose Element, and use according to stereotype in REI and SoDA... Danny --- Cavan G Watson <[EMAIL PROTECTED]> wrote: > Hi'ya > > I don't know which sort of Rose your using. > > But, probably Rose Prof or Enterprise, not Realtime. > So I think your > talking about an 'Analysis to Build Process > Declaration' that might be > 'realized'. In Rose Realtime 2002 these are called > configurations > (organised by plateform, some with quite weirdly > historical naming > conventions, excluding WinCE3 and XP - not yet > released, apparently). > > Consequently you should consider partioning ( sub > grouping ) your > stereotype's and use your Implementation IDE's Build > rules to recognise > appropriately. (STEREOTYPE = Configuration Build). > > I would be interested what tools might be applied. > Try > > IF (<RoseElementName>.Stereotype == > <SpecialisedUseCaseName>.Stereotype,Name) DO <SomePatternBuild> > > You might use a select, but what ever, should you be considering > process and external tool models. Export a model containing > only one kind of > toolName to stereotype. > > I think you have got the controlled units mixed up > with things that can > be built and run. Use Case's describe stuff, not > how stuff that can be > built does what it was built to do, that's described > by a ... Use Case > Realization. > > Please send a reply if you get this, > > Happy New Year > Kevin > > ATTACHMENT part 2 message/rfc822 > Reply-to: "Daniel Kalderon" <[EMAIL PROTECTED]> > From: "Daniel Kalderon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: (ROSE) Define Tools to Rose Elements with > Stereotype > Date: Sun, 30 Dec 2001 12:39:09 -0800 > > > Hello, > I have defined a Stereotype for a Rose Element (like > Special Use Case). > I know I can add toolName to A Rose Element. How can > I > define ToolName to a Rose Element with that specific Stereotype? > > Danny > > ===== > Daniel Kalderon > Tal : 972-3-9520268 > ICQ : 96180450 > > Innovate > > Btw, all my writing thoughts are at : > http://stage.co.il/Authors/DanielKalderon > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! http://greetings.yahoo.com > ************************************************************************ > * Rose Forum is a public venue for ideas and > discussions. > * For technical support, visit http://www.rational.com/support > * > * Post or Reply to: [EMAIL PROTECTED] > * Subscription Requests: [EMAIL PROTECTED] > * Archive of messages: > * > http://www.rational.com/support/usergroups/rose/rose_forum.jsp > * Other Requests: [EMAIL PROTECTED] > * > * To unsubscribe from the list, please send email > * To: [EMAIL PROTECTED] > * Subject: <BLANK> > * Body: unsubscribe rose_forum > ************************************************************************ > * > > ===== Daniel Kalderon Tal : 972-3-9520268 ICQ : 96180450 Innovate Btw, all my writing thoughts are at : http://stage.co.il/Authors/DanielKalderon __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum ************************************************************************ * *************************************************************************** * RUP Forum is a public venue for discussions about the * Rational Unified Process (RUP). * * For technical support of RUP, RPW, Rose or any other Rational * product, please visit: http://www.rational.com/support * * For other discussion groups, such as Rose and UML, please * sign up at: http://www.rational.com/support/usergroups/index.jsp * * To reply to a posting, please "Reply to all" or send * To: [EMAIL PROTECTED] * * Admin.Subscription Requests: [EMAIL PROTECTED] * * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send an email: * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rup_forum * **************************************************************************** ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
