hiho,
I'm
with R. Maksimchuk here on the suspicion that your use case model is not
centered around the real goals of the actors. For some articles that
specifically mention this issue with respect to CRUD operations see: http://www.evanetics.com/Presentations/UC-Part1-demo.pdf and
http://www.sdmagazine.com/articles/2000/0001/0001d/0001d.htm.
When
you are really in a pinch and you need to specify that something gets
Created/Read/Updated/Deleted and there is no possible business-centric
place in which this belongs, then you can fall into the "Maintain
Blah" as a better option than having the four separate use
cases.
You
are right that the pre and post conditions are notably different, but one
usually finds significant business rule overlap (when you create Blah it
typically must be just as valid as when you update Blah). And it never
feels good to have a use-case model so blown out with four use cases for each
major Blah that must be maintained.
-------- b
--
Brian G.
Lyons
Number Six Software - Voted Rational's
Best Complementary Service Provider
1655
North Fort Myer Drive, Suite 1100
Arlington,
VA 22209-3196
http://www.numbersix.com
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pankaj Chatterjee
Sent: Monday, January 29, 2001 3:55 AM
To: 'Rose Forum'
Subject: (ROSE) Use Case for CRUD functions
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pankaj Chatterjee
Sent: Monday, January 29, 2001 3:55 AM
To: 'Rose Forum'
Subject: (ROSE) Use Case for CRUD functions
Hi
everyone,
How does one depict the CRUD (create, retreive. update, delete) functions associated with database? Suppose the
application I am building is related to data management, I have created a use
case 'Create File', 'Remove File' for creating and removing files, but what do I
do about the CRUD function required to be performed on a file? Do I draw 4
separate use cases or just one 'Edit File'? There can be a huge amount of
processing logic, pre and post condition associated with each of the CRUD
functionalities. Documenting this as a single use case would become quite
tedious. What is the general opinion?
Thanks
Pankaj
