Use Case Diagram help

mishy

Hi guys, I am drafting up my first use case diagram and need to know if it is correct. It is for a music collection library app that allows users to add, delete, edit and search their music collection. They will only be one user managing their music collection. I have attached a copy of what I have done so far.

image002.jpg

philz1982

You can consolidate your CRUDE use cases. You need to think through the reasons and results of the search use cases are these for a web query or to support the DB CRUDE's?

I would create a
1) Login UC
2) Maintain DB UC to include CRUDE On music
3) Query functionality for user
4) DB Maintain UC on the app dev side.

You need to think through secondary actors, Access or SQL DB's, web servers ect.