RE: (ROSE) CRUD and Use Cases

[Smith, Jeff]

There's a really good book forwarded by Ivar Jacobson entitled Advanced Use Case Modeling by Frank Armour and Granville Miller.  They actually anticipate this discussion on CRUD and Use Cases in Chapter 12.  Pages 201-5 focus specifically on how to use the CRUD Matrix.  They argue that CRUD is limited, but because it's a good structured analysis tool to start with, it's also worthwhile seeing how a CRUD matrix might be expanded to capture more details of object responsibilities.  They devise a an expanded CRUD referred to as a use case object model (UCOM) matrix.  I'm using it for a client who has provided me with nothing but CRUD (no pun intended).

 

--Jeff

-----Original Message-----
From: Pankaj Chatterjee [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 19, 2001 9:36 PM
To: 'Rose Forum'
Subject: (ROSE) CRUD and Use Cases

Hi everyone,

 

Just wanted a new approach

 

Sometime back I had put up a question in the Rose forum on whether or not we should define use cases for CRUD functions. The general concensus was that we should not as in general CRUD type use cases do not add value to the system. However, in most of the applications we develop, there is a lot of create,update,delete and retreive activity. All persistent object that we develop require CRUD functionality. So what's wrong in this approach?

 

Consider this

1) A system has an Administrator, The administrator can grant access to new users, revoke access permission from existing users, modify existing user profile.

2) A order fullfilment system allows sales persons to - Accept new Orders, Cancel existing orders, Change Ordered Items

 

If these are not example of CRUD functionality then what are they? I could have written - An Administrator can - Create User, Update User, Delete User  and the end functionality could still be the same. So whats the difference between 'Create User' and 'Grant Access to new Users'?

 

Thanks in advance

 

Pankaj