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.Īny users can login only if they have already registered. Thanks in advance.Īny users can create an account by registering. 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.Īny assistance will be really appreciated. 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'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. 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.Īre 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 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).
0 kommentar(er)
