Are there actors in your system that would really
walk up to the system and say "I want to Remove File"? Or is "Remove File"
and the other such functions merely steps in a larger, overall use case (my
guess is its the second option). Such basic operations as Read, Update,
etc. may be how you implement a use case but they are usually not use cases in
themselves. They are not complete flows, initiated by an actor, that
provide value to that actor. I would treat them merely as steps in your
overall flow of events for a larger use case (e.g. don't know what your app is
but, for example, the use case "Add To Shopping Cart" may have a step "update
file", or "Review Portfolio" would "read file" as part of its processing,
etc.)
-----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
