Modeling Database architecture [UML]

[bellaabdelouahab]

in this discussion we will starting modeling of project depending of our use case needs
every update about the classes we create or modify will be displayed here ,
feel free to ask question or give suggestions

[Khalid1G]

Salam everyone, I would like to add this just like a base UML class diagram:

These are some of the main entities that could be included in the UML class diagram for the student organizer website. Depending on the specific requirements and functionalities of the website, we may need to include additional entities or modify these entities accordingly.

@startuml
class User {
  - username: String
  - password: String
  - email: String
  - preferences: Preferences
}

class Course {
  - courseCode: String
  - name: String
  - description: String
  - resources: List<Resource>
}

class Assignment {
  - title: String
  - description: String
  - deadline: Date
  - status: String
}

class Reminder {
  - title: String
  - description: String
  - date: Date
}

class Collaboration {
  - groupMembers: List<User>
  - discussions: List<Discussion>
  - sharedResources: List<Resource>
}

class ResourceLibrary {
  - resources: List<Resource>
}

class ProgressTracking {
  - completedAssignments: List<Assignment>
  - grades: List<Grade>
  - milestones: List<Milestone>
}

class Analytics {
  - performanceData: PerformanceData
}

class Preferences {
  - theme: String
  - notifications: Boolean
}

class Resource {
  - title: String
  - url: String
}

class Event {
  - title: String
  - description: String
  - date: Date
}

class Discussion {
  - participants: List<User>
  - messages: List<Message>
}

class Grade {
  - assignment: Assignment
  - value: Double
}

class Milestone {
  - title: String
  - date: Date
}

class Message {
  - sender: User
  - content: String
  - timestamp: Date
}

User "1" -- "1" Preferences
User "1" *-- "*" Course
Course "1" *-- "*" Assignment
Reminder "1" -- "1" User
Collaboration "1" -- "*" User
Collaboration "1" *-- "*" Discussion
Collaboration "1" *-- "*" Resource
ResourceLibrary "1" -- "*" Resource
ProgressTracking "1" -- "*" Assignment
ProgressTracking "1" -- "*" Grade
ProgressTracking "1" -- "*" Milestone
Analytics "1" -- "1" User
Analytics "1" -- "1" PerformanceData
Discussion "1" -- "*" User
Discussion "1" *-- "*" Message
@enduml

[muttaqin1]

perfect 💯

[bellaabdelouahab]

fantastic 👌
i will wait for active collabs to give feedback

@yassineboujrada
@bouslama-hamza
@muttaqin1

[bellaabdelouahab]

but first you can update the user model with the existing one on backend
@Khalid1G

[Khalid1G]

Considering my most recent project (SPE), I believe the user class still requires a few extra fields. after including the fundamental features like RBAC and password reset. The model in use looked like this:

class User {
  - fname: String
  - lname: String
  - password: String
  - email: String
  - password: String
  - roles: List<Message>
  - tel: String
  - delete : Boolean
  - changePasswordAt: DateTime 
  - preferences: Preferences
  - passwordResetToken: String,
  - passwordResetExpires: Date,
}

I think no need for an address, also about changePasswordAt DateTime This field helps in JWT auth, in case of the user changes his password after generating the JWT token, the token is still valid so we need to check this case, and throw 401 error @muttaqin1.

About the fields authorities and restrictions I don't understand the logic of it, I will add I unit test and if pass well I will merge your code and add those fields.

[bellaabdelouahab]

sure thing, those field can help with the password restore logic;
here is the issue if you want to contribute in it [#22]

we can also add other base fields at some point like "createdBy", "createdDate", "lastModifiedBy", "lastModifiedDate"

[Khalid1G]

about createdDate and lastModifiedDate is already exist, when we set { timestamps: true } .

[bellaabdelouahab]

Yeah, they are my bad.

[bellaabdelouahab]

I want to add these fields

• activationKey : when a user signup his account will not be active until he verifies his email
• resetKey : to impl the password restore logic we need this field
• resetDate : we can also check this to prevent changing password many times

I need some feedbacks

@muttaqin1 @Khalid1G @yassineboujrada @bouslama-hamza

[Khalid1G]

May you need also the resetTokenExpire: the password reset token must be valid for a few minutes.
You can try to merge this field with last fields i provided

[muttaqin1]

How many times do you plan to let the users reset their password?
@bellaabdelouahab

[bellaabdelouahab]

I think each 48 hours but for now i don't know

[Khalid1G]

@bellaabdelouahab the recommended time is about 5 to 10 min.
@muttaqin1

[muttaqin1]

@bellaabdelouahab the recommended time is about 5 to 10 min.
@muttaqin1

Suppose i have changed my account password.
Then my girlfriend find out my account Password and logged in.
Now i am helpless because I only can reset my password once in 48 hour's.
So I request make this time shorter if possible.
@bellaabdelouahab

[bellaabdelouahab]

that's one down side of having a gf 😂.
anyway lets not add it for now,we will keep it open

[bellaabdelouahab]

about the delete field ? should i add deleted field ? and then when ever a doc deleted i just set delete to true

[bellaabdelouahab]

but there will be a problem of unique fields

[bellaabdelouahab]

@Khalid1G