I am happy to report that www.rationalrose.com appears to be alive and well
with several selections of the VOPC script available.  I wouldn't model
without it, myself.

Eric, I will send you a presentation I delivered at the Rational Users
Conference 2 years ago on Risk Management.  Hope it helps.
cve

-----Original Message-----
From: Dunnavant, Todd [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 12:51 AM
To: ROSE_FORUM
Subject: RE: (ROSE) From Use Case to Use Case Realiztion



Eric, 


None online.  I'm trying to find a RoseScript that can create a VOPC easily
from a UCR with an arbitrary number of object interaction diagrams.  This
script used to be at www.rationalrose.com, but that Web site appears to be
inactive.  Pity.  It was a great one.

Does anyone else know where the vopc2 and vopc3 scripts can be had?

I don't know how to convince anyone to use a particular approach to project
management :-)  We strongly advocate a risk-driven approach to PM, whereby
you prioritize the major risks to be addressed first.  The art comes into
identifying which functions of the system will exercise the pieces of the
system that are associated with that risk.  Sometimes that is easy to figure
out.  For example, if your major risk is something like, "We have never used
CMP Entity EJBs before", most any use case that involves manipulating
persistent data in a J2EE system can be used to exercise code associated
with that risk.  A tougher example would involve a performance-related risk.
Performance is almost always associated with architectural issues, but you
might actually have to implement multiple use cases at the same time in
order to create a system that was full-featured enough to investigate the
system's performance characteristics.

******************************************************** 
R a t i o n a l
the software development company(tm) 

Todd Dunnavant
Technical Lead, IBM Global Account Team
Office Phone #:  (281) 431-8751
Fax Phone #:     (281) 431-8791
E-mail address:   [EMAIL PROTECTED] < mailto:[EMAIL PROTECTED]> 

Rational's Mission:  "To ensure the success of Customers who 
depend on software development and deployment."
******************************************************** 



-----Original Message-----
From: Eric D. Tarkington [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 12:33 AM
To: Dunnavant, Todd; ROSE_FORUM
Subject: Re: (ROSE) From Use Case to Use Case Realiztion


Todd,

I like your description of the VOPC, and I have to teach this stuff, so
please riddle me this:  Does Rational have any good examples of VOPCs
that I can look at online?

I also like your description of the relationship between risk and the
realization process.  Any tips on how to convince Dilbert's boss to
actually use this in the long run?  (Please don't suggest anything
involving a blow torch and duct tape.)

-Eric

"Dunnavant, Todd" wrote:
> -  A (single!) class diagram, what we call the View of Participating
Classes
> (VOPC) diagram, that shows the relationships between ALL the classes that
> are involved in ANY of the scenarios.  Well, this might actually be taking
> the concept too far.  If I am using subsystem-based development, I most
> likely would stop at the subsystem boundaries.  That is, the UCR
interaction
> diagrams wouldn't go deeper than the subsystem interfaces, and the VOPC
> wouldn't show the classes that implement the interface operations.
> 
> The VOPC is a very powerful diagram.  In our approach to iterative systems
> development, we commonly determine the functionality to be implemented
> during an iteration by:
> -  Identifying the risks we wish to retire during that iteration, then
> -  Identifying the use cases that will make us face those risks when we
> implement them.
> 
> Let's say that a risk is architectural in nature.  We select a use case
that
> WE THINK will force us to design and implement that piece of the
> architecture.  During system design, we can use the VOPC to confirm that
we
> are, indeed, touching the pieces of the system's innards that we expected,
> or we can see that we AREN'T.  If we catch this faux pas early enough, we
> might still have time to touch our risky piece of the system by revisiting
> the project plan and implementing a different use case.
************************************************************************
* 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
*************************************************************************

Reply via email to