USE case to Class Diagram - How do I?

Question

I would like your guidance on how to create classes and their relationships (generalization, association, aggregation and composition) accurately from my USE case diagram (please see below).

I am trying to create this class diagram so I can use it to create a simple online PHP application that allows the user to register an account, login and logout, and store, search and retrieve data from a MySQL database.

Are my classes correct? Or should I create more classes? And if so, what classes are missing? What relationships should I use when connecting the register, login, logout, search_database and add_to_database to the users?

I'm new to design patterns and UML class diagrams but from my understanding, the association relationship relates one object with another object; the aggregation relationship is a special kind of association that allows "a part" to belong to more than one "whole" (e.g. a credit card and its PIN - the PIN class can also be used in a debit card class); and a composition relationship is a special form of aggregation that allows each part to belong to only one whole at a time.

I feel like I have left out some classes or something because I just can't seem to find the relationships from my understanding of relationships.

Any assistance will be really appreciated. Thanks in advance.

USE CASE DIAGRAM

USE case explanation:

Register Any users can create an account by registering. The system will validate the user name and password and will reject them if either they are missing or if the user name is already taken.

Login Any users can login only if they have already registered. Their user name and password will be validated in the same manner as when registering an account.

Search Database Any users will beable to input a searchkey of datatype string and the system will open the database, search for the searchkey, and return true or false depending on whether or not the searchkey was found, and close the database.

Add data to database All users will be able to input some data, the system will open the database, store the data, return true or false depending on whether or not the data was stored, and close the database.

Logout The user will press the logout button, and the system will logout the user

Delete from database Only the administrator can delete data from the database.

Delete regular users Only the administrator can delete a regular user

CLASS DIAGRAM

Answer 1

First, if you're determined to go down a modeling path, then I'd recommend a book by Rosenberg and Stephens, Use Case Driven Object Modeling with UML. This goes through a process exactly what you're describing: how to write good use cases, build class diagrams from them, build sequence diagrams from that, and (ta-da!) code it up into working software. You might be able to Google for the ICONIX process and find details online.

Some casual comments:

• The 'diagram' of any Use Case Diagram is the least useful aspect of use cases. Every oval on the diagram represents a paragraph or two of text telling the story of what's going on. It's that text that's really helpful.
• Usually you have classes for the nouns in your use cases, and methods for the verbs. Some of your verbs (Add_data_to_database, Logout, ...) are classes instead of methods.
  • Sometimes you get this sort of thing if you use a framework that encourages a command pattern. Even then, the command objects can/should just invoke methods on your real classes.
  • I would say you're missing some nouns (what type of data are your storing in the database?). If you had that, then you would find relationships between User's and those data classes.

Answer 2

It seems that there's no problem with the UC diagram.

I agree with the comment from Dave. Beside, i also want to show you my idea to make corresponding class diagram for such a UC diagram. (Just the main point shown.)