Campus Management System
Campus Management System
Campus Management System
System
Learning Management System
Introduction
Existing system
Problem Statement
Functional Requirements
Non-Functional Requirement
System Design
Methodology
Tools
Deliverable
Future Work
3
Introduction
The main reason for working on this project is that our university
doesn’t have a CMS implemented at the moment and if we achieve our
targets we will be able to deploy the system on our campus.
For teachers there will be a separate portal for their daily usage, for
example, class schedule, enrolled students, assignments section,
resource, uploading, etc.
Scope
We will have to incorporate parts of the other modules defined in the list above to establish a basic system
and a database so that our LMS can run properly.
This will be the overview of our scope. We will be aiming to create a functional system with the following
facilities.
1. User Management
a. Create new users with authentication method
b. Management of application rights for users
c. Management of user roles and user rights
2. Campus Management
a. Campus information, address, contact detail etc.
b. Campus Faculty Management
i. Personal Information
ii. Academic Record
c. Date sheet and examination schedule management, examination deadlines for
results submission etc.
Modules of our project
For Admin
Login
Dashboard
• Home
– Student List
• University Profile
Admin
• Create Users
• Create Students into Classes/Batches
University
• Departments
• Discipline
• Class
• Semester
• Courses
• Exam
Announcements
• Date sheet
• Create Schedule
Functional Requirements
For Students
Login Page
Dashboard Menu
• Home
– Student Profile (Basic Personal Information)
– Announced Courses
» Select Courses
– Assignment Schedule
– Quiz Schedule
– Current Result Card
Your Profile
Resources
• Lectures
• Notes
• Articles
Exam
Functional Requirements
For Teachers
Login page
Dashboard
• Home
• Profile
Resources
• Lecture
• Articles
• Notes
Exam
• Quiz
• Assignment
• Mid Term
• Final Term
• Lab Test
• Projects
• Tasks
Attendance
Non-Functional Requirements
a) Compatibility:
Our web-application must run on all web browsers and also on the mobile phone and
tabs.
b) Reliability:
The system will be reliable to use. All data which is kept on the database will be
available/accessible at all times with a backup power system.
c) Security:
The system will be secure by making it password protected. Only the account holder
or admin can make changes in passwords. The database server will be in-house to
further
secure the data.
Non-Functional Requirements
d) Maintainability:
The admin and developer can easily maintain the application through documentation.
Since the employee and student numbers aren’t that larger we can manage with the
current infrastructure, hardware and IT employees available.
e) Extensibility:
The code of application may be modified, later changes or content added in
application according to requirement. Increase in departments and courses etc. can be
modified.
f) Performance:
For this web application the response time will be depend on internet speed, efficient
coding and design
System Design
System Design
System Design
Methodology
It’s a step-by-step process that flows from one part to the next in a
sequential order, hence the name waterfall.
As the requirements are set and will not change so we have a solid
path to follow till the end, we can design and implement it with ease.
Tools: HW/SW
Hardware Specifications:
Software Specification:
Web Server: XAMPP
Database: MySQL
Languages:
HTML
CSS
PHP
JavaScript
Framework:
Bootstrap
Laravel
Angular JS
DELIVERABLES
SRS
Web-based Application
Project Report
22
Future Work
23
DB Connection
Login Page
Admin Dashboard
Create User
Department Section
Create Discipline
Create Classes
Create Semester
Create Courses
Create Student
Create Schedule Entries
Teacher Dashboard
Create Teacher Profile
Upload Resources
Student Dashboard
Student Profile
Registered Course
View Resources