The following script will add a Tool (a tab in the specification) and or
Property to the specified modeling object.
See the online documentation for "AddDefaultProperty".
------------------------------------------------------------------
'Add New Property
Sub Main
Dim defProps As DefaultModelProperties
Set defProps = RoseApp.CurrentModel.DefaultProperties
'AddDefaultProperty will create the tool specified (Extra) if it
'does not already exist
worked = defProps.AddDefaultProperty("UseCase", "Extra", "default", _
"Example", "Text", "")
MsgBox "Done"
End Sub
------------------------------------------------------------------
The example:
worked = defProps.AddDefaultProperty("UseCase", "Extra", "default", _
"Example", "Text", "")
The format:
worked = theProperties.AddDefaultProperty (theClassName, theToolName,
theSetName, thePropName, thePropType, theValue)
theClassName -
The name of the Rose object you want to create an entry for.
The following is a script that will identify the property value to use for
"theClassName" in AddNewProperty.
Select something in the Browser and run the script. It will indicate the
element type. Use the type to replace "UseCase" in the AddNewProperty
script to add the Tool and/or the Property to the Specification for that
type.
------------------------------------------------------------------
'Identify Model Elements
Sub Main
Dim model As Model
Dim items As itemCollection
Dim anItem As RoseItem
Dim i As Integer
Set model = RoseApp.CurrentModel
Set items = model.GetSelectedItems()
For i = 1 To items.count
Set anItem = items.getat(i)
MsgBox anItem.IdentifyClass()
Next i
End Sub
------------------------------------------------------------------
theToolName -
The name of the Tab to add or modify.
theSetName -
Identifies the set to modify.
Note: The "default" set can be "Cloned" to make a new set of properties.
This Cloned set of properties can be modified separately from the default
set and be applied to selected objects. See the online help
"Contents:Rational Rose:How To...:Manage Model Properties" to find out more
about Model Properties and Cloning (Creating a New Model Property Set).
thePropType -
The possible Property types are:
Text
Integer
Float
Boolean (Use "T" or "F" in the script to set the default)
theValue -
An optional default value.
You can do things like:
worked = defProps.AddDefaultProperty("UseCase", "Status", "default", _
"Milestone", "Text", "")
worked = defProps.AddDefaultProperty("UseCase", "Status", "default", _
"Completed", "Boolean", "")
This will add a Tool "Status" to the Use Case Specification with 2
properties "Milestone" and "Completed". The Text type property, Milestone,
can contain a description of the milestone and the Boolean property,
Completed, can signify True or False indicating if the milestone has been
completed.
-----Original Message-----
From: Les Munday [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 11:07 AM
To: [EMAIL PROTECTED]
Subject: Re: AW: (ROSE) PRE and POST conditions
This is the solution I wanted some years ago. Does anyone have
access to this solution?
Les.
>
> 3) Add your own Pre/Postconditions-Tab (like conditions of
operations).
>
>
>
> mit freundlichen Gr=FC=DFen
> Jan Mat=E8rne=20
>
> RZF NRW=20
> Sachgebiet 314-P Methodenberatung=20
> Internet: [EMAIL PROTECTED]=20
>
>
>
> > -----Urspr=FCngliche Nachricht-----
> > Von: [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED]]
> > Gesendet am: Montag, 18. Februar 2002 11:02
> > An: [EMAIL PROTECTED]
> > Betreff: (ROSE) PRE and POST conditions
> >=20
> >=20
> > Hi all,
> >=20
> > According to RUP, usecases have Pre and Post conditions.=20
> > We want to model the Pre and Post conditions in Rational
Rose as =
> well.
> > The problem is that in Rational Rose we are not able to put
them =
> anywhere
> > and then use this to generate reports with Rational SoDa.
> >=20
> > Typically the Pre and Post conditions are part
of 'documentation'of a
> > usecase. However in the report we want to split the Pre and
Post =
> condition
> > in a seperate paragraph.
> > Does anyone have any ideas on how to model the Pre and Post
condition
> =
> for
> > a
> > usecase within Rational Rose?
> >=20
> > Greetings,
> > Arno Leenders
> > ------------------------------------------------------------
-----
> > ATTENTION:
> > No legal consequences can be derived from the content of
this=20
> > e-mail and/or its attachments. Neither is sender committed
to=20
> > these. The content of this e-mail is exclusively intended
for=20
> > addressee(s) and information purposes. Should you receive
this=20
> > message by mistake, you are hereby notified that any
disclosure,=20
> > reproduction, distribution or use of this message is
strictly=20
> > prohibited. Sender accepts no liability for any damage
resulting=20
> > from the use and/or acceptation of the content of this e-
mail.=20
> > Always scan attachments for viruses before opening them.=20
> > ------------------------------------------------------------
-----=20
> >=20
> > =
>
****************************************************************
********=
>
> > * 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
> > =
>
****************************************************************
********=
> *
>
>
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server
version =
> 5.5.2651.75">
> <TITLE>AW: (ROSE) PRE and POST conditions</TITLE>
> </HEAD>
> <BODY>
>
> <P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">1) Write
the =
> conditions into the documentation field. You can use your own
special =
> style if you want that other programs get that data. Maybe a =
> XML-style</FONT></P>
>
> <P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> =
> ... my other documentation ...</FONT>
> <BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> =
> <precondition> .... </precondition></FONT>
> <BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> =
> <postcondition> .... </postcondition></FONT>
> <BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> ... =
> some more</FONT>
> <BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> Maybe
with a
> =
> root node</FONT>
> <BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> =
> <documentation> .... </precondition> </postcondition>
> =
> </documentation></FONT>
> </P>
>
> <P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">2) Write
external =
> files <usecasename>_pre.{txt|xml} =
> <usecasename>_post.{txt|xml}</FONT>
> </P>
>
> <P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">3) Add
your own =
> Pre/Postconditions-Tab (like conditions of operations).</FONT>
> </P>
> <BR>
> <BR>
>
> <P><FONT SIZE=3D2 FACE=3D"Arial">mit freundlichen
Gr=FC=DFen</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">Jan Mat=E8rne </FONT>
> </P>
>
> <P><B><FONT COLOR=3D"#008000" FACE=3D"Arial">R</FONT><FONT =
> COLOR=3D"#808080" FACE=3D"Arial">Z</FONT><FONT
COLOR=3D"#FF0000" =
> FACE=3D"Arial">F</FONT><FONT COLOR=3D"#008000"
FACE=3D"Arial"> =
> N</FONT><FONT COLOR=3D"#808080" FACE=3D"Arial">R</FONT><FONT =
> COLOR=3D"#FF0000" FACE=3D"Arial">W</FONT><FONT
COLOR=3D"#008000" =
> FACE=3D"Arial"></FONT></B>=20
> <BR><FONT COLOR=3D"#008000" SIZE=3D1
FACE=3D"Arial">Sachgebiet 314-P =
> Methodenberatung </FONT>
> <BR><FONT COLOR=3D"#008000" SIZE=3D1 =
> FACE=3D"Arial">Internet: =
> [EMAIL PROTECTED] </FONT>
> </P>
> <BR>
> <BR>
> <UL>
> <P><FONT SIZE=3D1 FACE=3D"Arial">-----Urspr=FCngliche =
> Nachricht-----</FONT>
> <BR><B><FONT SIZE=3D1 FACE=3D"Arial">Von: </FONT></B> =
> <FONT SIZE=3D1 FACE=3D"Arial">[EMAIL PROTECTED] =
> [SMTP:[EMAIL PROTECTED]]</FONT>
> <BR><B><FONT SIZE=3D1 FACE=3D"Arial">Gesendet =
> am: </FONT></B> <FONT SIZE=3D1 FACE=3D"Arial">Montag, =
> 18. Februar 2002 11:02</FONT>
> <BR><B><FONT SIZE=3D1 =
> FACE=3D"Arial">An: </FONT></B> <FONT SIZE=3D1 =
> FACE=3D"Arial">[EMAIL PROTECTED]</FONT>
> <BR><B><FONT SIZE=3D1 =
> FACE=3D"Arial">Betreff: </FONT>=
> </B> <FONT SIZE=3D1 FACE=3D"Arial">(ROSE) PRE and POST =
> conditions</FONT>
> </P>
> <BR>
>
> <P><FONT SIZE=3D2 FACE=3D"Arial">Hi all,</FONT>
> </P>
>
> <P><FONT SIZE=3D2 FACE=3D"Arial">According to RUP, usecases
have Pre =
> and Post conditions. </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">We want to model the Pre
and Post =
> conditions in Rational Rose as well.</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">The problem is that in
Rational Rose =
> we are not able to put them anywhere</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">and then use this to
generate reports
> =
> with Rational SoDa.</FONT>
> </P>
>
> <P><FONT SIZE=3D2 FACE=3D"Arial">Typically the Pre and Post
conditions =
> are part of 'documentation'of a</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">usecase. However in the
report we =
> want to split the Pre and Post condition</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">in a seperate
paragraph.</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">Does anyone have any ideas
on how to =
> model the Pre and Post condition for a</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">usecase within Rational
Rose?</FONT>
> </P>
>
> <P><FONT SIZE=3D2 FACE=3D"Arial">Greetings,</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">Arno Leenders</FONT>
> <BR><FONT SIZE=3D2 =
> FACE=3D"Arial">-----------------------------------------------
----------=
> --------</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">ATTENTION:</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">No legal consequences can
be derived =
> from the content of this </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">e-mail and/or its
attachments. =
> Neither is sender committed to </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">these. The content of this
e-mail is =
> exclusively intended for </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">addressee(s) and
information =
> purposes. Should you receive this </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">message by mistake, you are
hereby =
> notified that any disclosure, </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">reproduction, distribution
or use of =
> this message is strictly </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">prohibited. Sender accepts
no =
> liability for any damage resulting </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">from the use and/or
acceptation of =
> the content of this e-mail. </FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">Always scan attachments for
viruses =
> before opening them. </FONT>
> <BR><FONT SIZE=3D2 =
> FACE=3D"Arial">-----------------------------------------------
----------=
> -------- </FONT>
> </P>
>
> <P><FONT SIZE=3D2 =
>
FACE=3D"Arial">*************************************************
********=
> ***************</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Rose Forum is a public
venue for =
> ideas and discussions.</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* For technical support,
visit <A =
> HREF=3D"http://www.rational.com/support"; =
> TARGET=3D"_blank">http://www.rational.com/support</A></FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">*</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Post or Reply to: =
> [EMAIL PROTECTED]</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Subscription Requests: =
> [EMAIL PROTECTED]</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Archive of
messages:</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* <A =
>
HREF=3D"http://www.rational.com/support/usergroups/rose/rose_for
um.jsp"
> =
>
TARGET=3D"_blank">http://www.rational.com/support/usergroups/ros
e/rose_f=
> orum.jsp</A></FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Other Requests: =
> [EMAIL PROTECTED]</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">*</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* To unsubscribe from the
list, =
> please send email</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* To: =
> [EMAIL PROTECTED]</FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Subject: =
> <BLANK></FONT>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">* Body: unsubscribe
> =
> rose_forum</FONT>
> <BR><FONT SIZE=3D2 =
>
FACE=3D"Arial">*************************************************
********=
> ****************</FONT>
> </P>
> </UL>
> </BODY>
> </HTML>
>
>
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
************************************************************************
* 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
*************************************************************************
************************************************************************
* 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
*************************************************************************
