Scribd
Upload
33 views7 pages

Ekattor School Management System - Laravel: Developer Manual

The document describes the source code structure of an Ekattor School Management System built with Laravel. It follows the MVC structure and details the app, public, and other directories containing controllers, models, views, CSS/JS files and more to develop the different modules of the school management system.

Uploaded by

Pablo
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views7 pages

Ekattor School Management System - Laravel: Developer Manual

The document describes the source code structure of an Ekattor School Management System built with Laravel. It follows the MVC structure and details the app, public, and other directories containing controllers, models, views, CSS/JS files and more to develop the different modules of the school management system.

Uploaded by

Pablo
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Ekattor School Management System -Laravel

Developer Manual
Copyright 2019 Creativeitem. All rights reserved.
Source Code Structure:
We followed standard MVC structure within powerful Php Laravel
framework to develop this project.
1.(a) Structure of app directory
● Controllers: Every controller has specific
functionalities for each module. As this
application has bunch of module, it has
approximately same amount of
Controller. Like,
○ AccountantController
○ AddonController
○ BookController
○ BookIssueController
○ ClassController
○ ClassRoom Controller
○ DailyAttendanceController
○ DepartmentController
○ EventCalendarController
○ ExamController
○ ExpenseCategoryController
○ ExpenseController
○ GradeController
○ Installation
○ InvoiceController
○ LibrarianController
○ MarkController
○ ParentController etc.
1(b) Structure of app Directory:
● Models: Like Controllers,
approximately each module has at
least one Model. Which is responsible
for database queries and table
relationship. We’ve used bunch of
models like,
○ Accountant
○ Addon
○ Book
○ BookIssue
○ Classes
○ ClassRoom
○ DailyAttendance
○ Department
○ Enroll
○ EventCalendar
○ Exam
○ Expense
○ ExpenseCategory
○ Grade
○ Invoice
○ Language
○ Librarian
○ Mark
○ Menu
○ Parent
○ Profile etc.
1(c) Structure of views:
● Views: We’ve separated all the
view files in a standard way.
Like we created folder module
wise and kept all the view files
inside the relevant folder.
2(a) Structure of Public directory:
● Backend:​ This directory
contains all the CSS, JS,
essential plugins and images of
backend panel.

You might also like