The project consists in developing a global marketplace which specializes in the sale of gaming related digital products using redemption keys.
In the fourth artefact, the focus was designing the UML diagram for the relational database. By the end of this iteration, we were able:
- Gain a clear vision of what the relational model will be.
- Clarify new Business Rules and refine the ones already especified in Artifact 3.
Note: The majority of new business rules are included in the UML, here we list those that because of graphical organization of the UML diagram were not included there
| Business Rule ID | Description |
|---|---|
| BR01 | When an admin wants to delete a product, if at least one user has already bought a key for that product, the product is not deleted and instead a boolean attribute in the class is set to false deleted product |
First submission: 19/03/2020
Changes made to the first submission: 23/03/2020
- Made Deleted Product a subclass of Product
- Added Active Product as a subclass of Product
- Added a restriction to Offer
- Joined arrows of User subclasses
- Fixed mispelling and arranged classes
- Added Cart class
- Added Ban Appeal class
- Added missing multiplicities
Changes made to the second submission: 27/03/2020
- Changed multiplicities regarding users, due to delete operations problems found in a5
Changes made to third submission: 02/04/2020
- Added missing date fields in Feedback and Product
- Added derived attributes on classes regular_user, product, key and offer
- Added notes explaining new restrictions associated with offer relation
GROUP2043, 02/04/2020
- Luís Ramos, [email protected]
- José Guerra, [email protected]
- Martim Silva, [email protected]
- Ruben Almeida, [email protected] (Editor)