UML Class Diagram - Fahim1505/CSE327-Alumni-Student GitHub Wiki

UML Class Diagram (Implementation Perspective) for Alumni-Student Link 

classDiagram
User <|-- Student
User <|-- Alumni
class User{
- id : Integer 
- name : String 
- email : String
- password : String
+ role : String
# getUserId() Integer
+ getUserName()  String
+ getUserEmail() String 
+ setUserId(id: Integer)  void 
+ setUserName(name: String)  void
+ setUserEmail(email: String)  void 
+ setUserPassword() 
}
class Student{
}
class Alumni{
- graduationYear: integer
+ getGraduationYear()  Integer
+ setGraduationYear(graduationYear: Integer) void

}
User "1" *--"1" Profile
class Profile{
- phone : String
- address 
- currentWork 
- socialLinks 
- imagePath
+ getPhone()  String
+ getAddress()  String
+ getCurrentWork()  String
+ getSocialLinks()  String 
}
Alumni "1" --> "0..*" Job: posts about
Alumni "1"--> "0..*" Event: posts about
Alumni "1" --> "0..*" Donation: makes
Alumni "1" --> "0..*" Announcement: makes
Alumni "0..*" --> "1" Photo Gallery: shares photos in

class Job{
- id : Integer
- title : String
- companyName : String
- description
- applyLink 
- postedBy 
- createdAt : DateTime   
+ getJobId()  Integer 
+ getJobTitle()  String 
+ getCompanyName()  String 
+ getJobDesc()  String 
+ getApplyLink()  String 
+ setJobId(id: Integer)  void 
+ setJobTitle(title: String) void 
+ setCompanyName(companyname: String)  void 
+ setJobDesc(description: String)  void
+ setApplyLink(applyLink: String)  void
}
class Event{
- id : Integer 
- title : String
- description
- startTime : DateTime
- endTime : DateTime
- location 
- createdBy 
+ getEventId()  Integer 
+ getEventTitle()  String 
+ getEventDesc()  String 
+ getEventStartTime() DateTime  
+ getEventEndTime() DateTime
+ getEventLocation()  String 
+ setEventId(id: Integer)  void
+ setEventTitle(title: String)  void
+ setEventDesc(description: String)  void
+ setEventStartTime()  void 
+ setEventEndTime() void 
+ setEventLocation(location: String) void 
}
class Donation{
- id : Integer 
- amount : String
- donationDate : DateTime
- note 
+ getDonationId()  Integer
+ getDonationAmount()  Integer
+ getDonationDate() DateTime 
+ getDonationNote()  String 
+ setDonationId(id: Integer)  void 
+ setDonationAmount(amount: Integer)  void 
+ setDonationDate() DateTime
+ setDonationNote(note: String)  void 
}
class Announcement{
- id : Integer
- title : String
- body
- attachment
- postedBy 
- createdAt 
+ getDonationId()  Integer
+ getDonationAmount()  Integer
+ getDonationDate() DateTime 
+ getDonationNote()  String 
+ setDonationId(id: Integer)  void 
+ setDonationAmount(amount: Integer)  void 
+ setDonationDate() DateTime
+ setDonationNote(note: String)  void 
}
class PhotoGallery{
- id : Integer
- filePath
- caption : String
- uploadedAt 
+ getPhotoId()  Integer 
+ getFilePath() 
+ getCaption()  String 
+ setPhotoId(id: Integer)  void 
+ setCaption(caption: String) void
}
User "1" --> "0..*" Achievement : posts about
class Achievement{
- id : Integer 
- title : String
- description
- imagePath
- createdAt : DateTime
+ getAchievementId()  Integer
+ getAchievementTitle()  String
+ getAchievementDesc()  String 
+ setAchievementId(id: Integer)  void 
+ setAchievementTitle(title: String) void 
+ setAchievementDesc(description: String) void 
}
Loading

UML Class Diagram.pdf

UML Class Diagram V2.pdf

MVC Model Diagram: https://github.com/Fahim1505/CSE327-Alumni-Student/blob/main/wiki_images/MVC%20Model%20Diagram.jpg

MVC Model Diagram-02: https://github.com/Fahim1505/CSE327-Alumni-Student/blob/main/wiki_images/MVC%20Model%20Diagram-02.jpg

<style> </style>

Model–View–Controller (MVC) Architecture

1.      Overview

The MVC pattern separates the system into three main layers, improving scalability, maintainability, and testability.

 

Layer Role Example in Your Project
Model Handles data logic, interacts with the database, defines relationships, and implements business rules. Eloquent Models like User, Profile, Event, JobPost, Announcement, Donation, etc.
View Responsible for UI presentation, showing the data to the user. Blade templates (.blade.php): dashboard.blade.php, profile.blade.php, events.blade.php, etc.
Controller Acts as a bridge between Model and View. Handles requests, processes data, and decides which View to render. Controllers like UserController, EventController, JobController, DonationController, etc.

 

 

 

2.       MVC Flow in Our Project

Example: Student registers and logs in

  1. The View (registration form) sends input to AuthController@register.
  2. The Controller validates the data and calls the Model (User model) to create a new record.
  3. The Model interacts with the database using Eloquent ORM.
  4. Once registration is successful, the Controller redirects the user to the View (dashboard.blade.php) with a success message.

 

3.      Advantages for Our Project

  • Clear separation of concerns — easier collaboration and maintenance.
  • Reusability — Models and Controllers can be reused across modules.
  • Better testing — Unit tests for Models and Controllers separately.
  • Framework alignment — Laravel natively uses MVC, so you’ll follow framework best practices.

 

4.       Supporting Patterns in Laravel

Alongside MVC, Laravel internally leverages several design patterns that will indirectly support our project:

  • Repository Pattern (for complex data access logic)
  • Observer Pattern (for notifications like new event announcements)
  • Service Provider Pattern (for bootstrapping components)
  • Singleton Pattern (used in Laravel’s configuration and database connections)

 

 

 

 

 

 

 

 

 

 

 

         

 

⚠️ **GitHub.com Fallback** ⚠️