Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m working in system analysis. Should I take all system operations (including basic operations, such as add/delete/edit) as use cases or not?
Should I focus on core system operations, or must I include all possible operations?
Instead of adding separate use cases for “add/delete/edit,” I usually add one “CRUD” (Create Read Update Delete) use case. This greatly reduces the number of use cases, but still gets your point across. Then again, if it’s not a very important part of the system, you might not need to include it.