|
-
Dec 19th, 2003, 08:32 AM
#1
Thread Starter
Frenzied Member
ASP.NET app design...
Here I am with yet another design issue...
I have a very small asp.net application with a single page
There are a few listboxes, textboxes and 3 datepickers
This app is for system administrators to be able to add "system shutdown descriptions" the data they have enterend will then be distributed via webservice for everyone who want to see them...
This is simply the admin part, where the admin can enter new shutdowns and update old ones and delete them. I don't use the datagrid cause of lots of multiselectboxes...
Anyway how can I design this with OO? What possible usecases are there? I have only found one actor, the administrator
Usecases:
* AddShutDown
* UpdateShutDown
*DeleteShutDown
How detailed should the usecase diagram be in this case? Should I incorporate database issues like a usecase for "save shutdownitem"?
Suggestions?
kind regards
Henrik
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|