Option 3 is a really good one.
In one of our projects we expanded the internal structure of the Rose's
UseCase class with seperate fields for each section of the Use case
description, which is recommended in the literature.
Using this way, SoDa could be used to select sepecific UseCases.
[EMAIL PROTECTED]
n-nrw.de To: [EMAIL PROTECTED]
Sent by: cc:
owner-rose_forum@r Subject: AW: (ROSE) PRE and POST
conditions
ational.com
18.02.2002 11:09
Please respond to
Jan.Materne
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
... my other documentation ...
<precondition> .... </precondition>
<postcondition> .... </postcondition>
... some more
Maybe with a root node
<documentation> .... </precondition> </postcondition> </documentation>
2) Write external files <usecasename>_pre.{txt|xml} <usecasename>
_post.{txt|xml}
3) Add your own Pre/Postconditions-Tab (like conditions of operations).
mit freundlichen Gr��en
Jan Mat�rne
RZF NRW
Sachgebiet 314-P Methodenberatung
Internet: [EMAIL PROTECTED]
-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Gesendet am: Montag, 18. Februar 2002 11:02
An: [EMAIL PROTECTED]
Betreff: (ROSE) PRE and POST conditions
Hi all,
According to RUP, usecases have Pre and Post conditions.
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.
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?
Greetings,
Arno Leenders
-----------------------------------------------------------------
ATTENTION:
No legal consequences can be derived from the content of this
e-mail and/or its attachments. Neither is sender committed to
these. The content of this e-mail is exclusively intended for
addressee(s) and information purposes. Should you receive this
message by mistake, you are hereby notified that any disclosure,
reproduction, distribution or use of this message is strictly
prohibited. Sender accepts no liability for any damage resulting
from the use and/or acceptation of the content of this e-mail.
Always scan attachments for viruses before opening them.
-----------------------------------------------------------------
************************************************************************
* 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
*************************************************************************
