0% found this document useful (0 votes)
68 views7 pages

Ekattor School Management System: Developer Manual

Uploaded by

Yogesh Yogi
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
0% found this document useful (0 votes)
68 views7 pages

Ekattor School Management System: Developer Manual

Uploaded by

Yogesh Yogi
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

Developer Manual
Copyright 2020 Creativeitem. All rights reserved.
Source Code Structure:
We followed standard MVC structure within powerful Php Codeigniter
framework to develop this project.
1.(a) Structure of application directory
● Controllers:
○ Addons​ : All the controllers of
installed addons will remain here.
○ API​:
■ Admin:​ We are working on
mobile application as well.
Here we will write down all
the API functionalities.
○ [Link]​: It runs all the
functions of admin panel.

○ [Link]​: It runs all the


functions of an accountant panel.

○ [Link]​: All the functionalities


of frontend are written in here.

○ [Link]​: [Link] controller


handles the installation process.

○ [Link]​: [Link]
controller handles all the functions
of Librarian.

○ [Link]​: The functionalities of


processing login system are
written in here.

○ [Link]​: Modal controller has


the functionalities of pop up views.

○ [Link]​: It runs all the


functions of a parent panel.

○ [Link]​: It runs all the


functions of a student panel.

○ [Link]​: It runs all the


functions of a Superadmin panel.
○ [Link]​: It runs all the
functions of a Teacher panel.

○ [Link]:​ We’ve used


[Link] controller for
updating the application.
1(b) Structure of app Directory:
● Models​: All the functions related to
database are written down here.
○ Addons​ : This is where all the
addons models will remain.
○ API
■ Admin_model.php

○ Addon_model.php

○ Crud_model.php

○ Email_model.php

○ Frontend_model.php

○ Payment_model.php

○ Settings_model.php

○ User_model.php
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 Assets:
● Backend:​ This directory
contains all the CSS, JS,
essential plugins and images of
backend panel.
● Frontend:​ This directory
contains all the CSS, JS,
essential plugins and images of
frontend panel.

You might also like