Final Year Project on Student ERP Software

Academic-Nexus
Project Report Submitetd
in partial fulfillment of the requirements for the award of the

Bachelor of Technology
in
Computer Engineering
by
Akankhya Mishra
(B520004)

Under the supervision of

Dr. Muktikanta Sahu

Department of Computer Engineering

International Institute of Information Technology, Bhubaneswar
May 2024
 APPROVAL OF THE VIVA-VOCE BOARD

May 16, 2024

Certified that the report entitled “Student ERP(Academic-Nexus)” submitted by Akankhya

Mishra (B520004) to International Institute of Information Technology Bhubaneswar in partial
fulfillment of the requirements for the award of the Bachelor of Technology in Computer Engi-
neering under the BTech Programme has been accepted by the examiners during the viva-voce
examination held today.

(Supervisor) (Panel Head)

(Internal Examiner 1) (Internal Examiner 2)

i
 CERTIFICATE

This is to certify that the report entitled “Student ERP(Academic-Nexus)” submitted by

Akankhya Mishra (B520004) to International Institute of Information Technology Bhubaneswar
is a record of bonafide project work under my supervision, and the report is submitted for end-
semester evaluation of the BTech Degree project work.

(Supervisor)

ii
 DECLARATION

I certify that

1. The work contained in the report has been done by myself under the general supervision of
my supervisor.

2. The work has not been submitted to any other Institute for any degree or diploma.

3. I have followed the guidelines provided by the Institute in writing the thesis.

4. I have conformed to the norms and guidelines given in the Ethical Code of Conduct of the
Institute.

5. Whenever I have used materials (data, theoretical analysis, and text) from other sources, I
have given due credit to them by citing them in the text of the thesis and giving their details
in the references.

6. Whenever I have quoted written materials from other sources, I have put them under quota-
tion marks and given due credit to the sources by citing them and giving required details in
the references.

Akankhya Mishra
B520004

iii
 ACKNOWLEDGMENTS
This project is done as a major project, as a part course titled Student Academic Management
System. I really grateful and wish my profound my indebtedness to Supervisor Dr. Muktikanta
Sahu, Assistant Professor, Department of CSE ,IIIT Bhubaneswar. Deep Knowledge keen interest
of my supervisor in the field of web applications has helped me enormously to carry out this
project. His endless patience, scholarly guidance, continual encouragement, constant and energetic
supervision, constructive criticism, valuable advice, reading many inferior drafts and correcting
them at all stage have made it possible to complete this project. I would also generously welcome
each one of those individuals who have helped me straight forwardly or in a roundabout way
in making this project a win. In this unique situation, I might want to thank the various staff
individuals, both educating and non-instructing, which have developed their convenient help and
facilitated my undertaking. Finally, I must acknowledge with due respect the constant support and
patients of my parents.

Akankhya Mishra

iv
 ABSTRACT

The main objective of this project is to build a student database system that will store records of
students. It is purposed to reduce time spent on administrative tasks. The system is intended to
accept process, generate students. The system is also intended to provide better services to users,
provide meaningful, consistent, and timely data and information and finally promotes efficiency by
converting paper processes to electronic form. The system was developed using basic technologies
such as MySQL database and PHP. The system is free of errors and very efficient and less time
consuming due to the care taken to develop it. All the phases of software development cycle are
employed and it is worthwhile to state that the system is user friendly and strong. Provision is
made for future development in the system.

Keywords: Administrative tasks, PHP development, User-friendly interface, Software develop-

ment cycle, technology stack

v
Contents
1 Introduction 1

2 Literature Survey 2
2.1 Study of Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1.1 Disadvantages of Existing System . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1.2 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1.3 Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 Scope of the Project 3

4 Objectives 4

5 Feasibility Study 4
5.1 Technical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.2 Implementation Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.3 Economic Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

6 Life Cycle of the Project 6

6.1 Project Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Software Requirement Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2.1 Problems faced by students . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2.2 Problems faced by Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2.3 Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2.4 Software Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2.5 Study of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.3 System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.3.1 Use-Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.3.2 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.3.3 Context-level DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.4 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.4.1 Admin Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.4.2 Teacher Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.4.3 Student Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.4.4 DB Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.5 Testing and Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.5.1 Unit Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.5.2 Validation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7 Limitations 32

8 Future Enhancement 32

9 Conclusion 33

vi
1 Introduction

Student Management System is software which is helpful for students as well as the school

authorities. In the current system all the activities are done manually. It is very time consuming and

costly. Our Student Management System deals with the various activities related to the students.

The two main users involved in this system are :

• User(i.e., Students)

• Admin

• Faculty

In the Software we can register a student by the authentication code i.e., student id and password

with help of student id and password student can login his/her account and view all the notices

which is announced by admin. The main purpose of this project is to illustrate the requirements

of the project Student Information Management System and is intended to help any organization

to maintain and manage personal data. It is a comprehensive project developed from the ground

up to fulfill the needs of organisations as they guide their students. This integrated information

management system connects daily operations in the their environment ranging from Attendance

management to communications means among students and administrator. This reduces data error

and ensures that information is always up-to-date throughout the organisation.

Figure 1: Basic Student ERP diagram that explains roles of various users

1
2 Literature Survey

Until recently the place of the Student Management System (CMS). Now-a-days, education is

playing very significant role in the society. Day-by-day, the percentage of illiterates are decreasing

and the percentage of literates is increasing. Education will change the society in all the aspects

and everyone wants to study higher professional degrees. Admissions are increasing day by day

so there by. Ratio of establishment new colleges and schools are also increasing. But the actual

challenge is starting from now. Most of the schools and colleges are maintain student information

in records. When the number of records increased, it is difficult to maintain the information of

each student in the old manual system. Maintaining the records manually leads to error prone and

required more man power and it consumes more time for processing the records. [1].

2.1 Study of Existing System

Despite the prevalence of digital solutions in modern education, many educational institutions

still rely on manual processes for student management, leading to inefficiencies, errors, and a lack

of real-time data access.

2.1.1 Disadvantages of Existing System

• More time

• More money

• More manpower

• More work

• Less work result

• No accuracy

2.1.2 Methodology

1. Apache is used as a web server to host the application.

2
 2. All the environment variables are set.

3. The application is pasted in the web apps folder.

4. Web server is started now.

5. Application is run using the web browser by typing http://www.academic-nexus.cloud/final-

year-project

2.1.3 Proposed System

We resolve all the disadvantages of existing system in our proposed system. Old students can

share their experience, ideas, motivations to their juniors in the organisa-tion. They can provide

information regarding higher studies. RESULT Automation which yields aggregate percentage up

to that instant. Time will be saved, No chance of getting error.

Main Modules Of system:

→Administrator module

→Student Module.

→ Login Module.

→ Registration Module.

→ Notice/Upload Module.

→Query/Result module.

Present state:

→ No System present at all.

→ Time consumed in accessing the records of the students.

→ Manual maintaining student records.

→ Time consumed for registering students and Staff members.

→Manually providing hard copy for any notice or important information.

3 Scope of the Project

3
 • Through this service one can access the complete information about the college campus such

as courses available, admission procedure, placements, college events, achievements etc.

• It gives the attendance status of students. Faculty will update the attendance periodically

and can be seen by students and parents.

• This facility provides the performance of the student in each exam which is conducted by

university or college.

• Users could change their password.

• It will give information about different events that will be conducted by college time to time.

Information about these events will be updated by administrator.

4 Objectives

• In today’s era, every education institution is in the race of proving themselves the best in

offering education at every level.

• As digitization has evolved in every sector of the economy, many sectors are adopting this

technology for their smooth functionality.

• Every organization, big or small, has challenges to overcome and manage the information of

Courses, College, Faculty Exam, Students, etc.

5 Feasibility Study

The aim of the feasibility study activity is to determine whether it would be financially and

technically feasible to develop the system or not. A feasibility study is carried out from following

different aspects:

5.1 Technical Feasibility

The technical feasibility of a student ERP project using PHP and MySQL would involve:
4
 • Evaluating whether the chosen technologies can effectively meet the project’s requirements.

• MySQL is a widely-used relational database management system (RDBMS) that can handle

large volumes of data and transactions. It is well-suited for storing and managing student

related data such as personal information, grades, attendance, and course details.

5.2 Implementation Feasibility

• The project can easily be made online without much consideration of hardware and software.

The required thing is applicant’s side Internet Connection and a web browser.

• Using IDEs like VScode or phpStorm offers robust features for PHP development.

• Git as an open-source distributed version control system can facilitates collaboration among

developers and will allow for easy management of code changes.

• Apache or Nginx can be widely used open-source web servers that can host PHP applications.

5.3 Economic Feasibility

• Initial Investment: INR 122 for domain purchase, AWS free tier for deployment.

• Operational Costs: After the free tier, hosting expenses could renew monthly, estimated at

around INR 500 per month. Additionally, domain renewal costs about INR 200 annually.

• Maintenance Costs: Regular updates and bug fixes may require hiring a developer at an

average monthly cost of INR 10,000.

• Cost-Benefit Analysis: Compare potential revenue against all costs, factoring in income from

premium features, which could amount to INR 1000 per month.

5
6 Life Cycle of the Project

We have used Waterfall Model as Software Engineering life Cycle Process. It is the simplest;

oldest and most widely used process model for software development This model acquires its name

from the fact that classic software life cycle is represented as a sequence of steps.

Figure 2: Incremental life cycle

At each iteration, the procedure itself consists of the Initialization step, the Iteration step, and

the Project Control List. The initialization step creates a base version of the system. The goal

for this initial implementation is to create a product to which the user can react. It should offer a

of the key aspects of the problem and provide a solution that is simple enough to understand and

implement easily. To guide the iteration process, a project control list is created that contains a

record of all tasks that need to be performed. It includes such items as new features implemented

and areas of redesign of the existing solution. The control list is constantly being revised as a result

f the analysis phase. The iteration involves the redesign and implementation of a task from project

6
control list, and the analysis of the current version of the system. The goal for the design and

implementation of any iteration is to be simple, straightforward, and modular, supporting redesign

at that stage or as a task added to the project control list.

6.1 Project Plan

Once we examine that the project is feasible, we undertake project The table below describes

how we planned our project.

Role Responsibility
Project Guide Defining Scope
Providing required resources
Project planning, tracking and monitoring
Analysis and effort estimation
Project Developer Designing and documentation
Execution project as per defined schedule
Reporting to PL
Testing & QA/QC
Software development as per design and documentation

Figure 4: Activity network representation

Figure 3: Work breakdown structure

6.2 Software Requirement Specification

6.2.1 Problems faced by students

• Inefficiency in Accessing Information like academic records, including grades, attendance, and

course schedules.
7
 • Communication between students and faculty/administration can be cumbersome and slow.

• Limited access to resources such as past exam papers, syllabus, or course materials .

• Challenging to track their academic progress, including completed courses, credits earned,

and remaining requirements

6.2.2 Problems faced by Admin

• Data Redundancy and Inconsistency.

• challenges in accessing student records and information.

• Time-Consuming Administrative Processes such as enrollment, fee management, and grading.

• Data Security Concerns.

Functional Requirement Non-functional Requirement

Online Student Portal Performance
Centralized Data Storage Reliability
Development Tools Maintainability
Secure Authentication and Authorization Security
Online Enrollment and Registration Correctness

6.2.3 Hardware Required

• RAM 2gb or higher

• Storage 30gb or higher

• Display Adapter 256mb or higher

6.2.4 Software Required

• OS - Windows, Unix, Linux

• Web Browser - Chrome, Firefox, any

• Language - PHP, Bootstrap, CSS, JAVASCRIPT

8
 • Database - mysql, SQL Server

• XAMPP server

• PHP v6 or higher

• Notepad or text editors like VS-Code or Sublime

6.2.5 Study of the System

Graphical User Interface(GUI) In the flexibility of the uses the interface has been devel-

oped a graphics concept in mind, associated through a browses interface. The GUI’S at the top

level have been categorized as

1. Administrative user interface

2. The operational or generic user interface(student)

3. Faculties

The administrative user interface concentrates on the consistent information that is practically,

part of the organizational activities and which needs proper authentication for the data collection.

The interfaces help the administrations with all the transactional states like Data insertion, Data

deletion and Date updation along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in transactions

through the existing data and required services. The operational user interface also helps the

ordinary users in managing their own information helps the ordinary users in managing their own

information in a customized manner as per the assisted flexibilities.

Teachers are the key stakeholders of the student ERP. Because they are the one who manage,

edit, update the contents of the database of students such as attendance,internal marks, CGPA

etc..

• Number of Modules

The system after careful analysis has been identified to be presented with the following modules:
9
 1. Student tracking: Any company or any organization that want to check the summary about

the student of the college, so that they will be able to choose the particular students.

2. Student attendance status: t gives the attendance status of students. Faculty will update

the attendance periodically and can be seen by students.

3. Student’s performance in exams:This facility provides the performance of the student in

each exam which is conducted by university or college such as midterm performance.

4. Events and notices: it will give information about different events that will be conducted

by college time to time. Information about these events will be updated by administrator.

5. Student’s performance in exams:This facility provides the performance of the student in

each exam which is conducted by university or college such as midterm performance. Marks

obtained by students in exams will be updated by faculties.

6. Viewing schedule: Student can view time schedules for their respective semesters.

7. Study Materials: It will give the facility to download study materials like notes, PYQs,

syllabus semester wise which will be updated by faculties

8. Student Queries: Student can communicate their issues and queries to any departmants

through admin.

9. Fee status : This facility shows student can see their fee status like charges of every semester,

last day payments and could paid receipts.

6.3 System Design

Once the software requirements have been analyzed and specified the software design involves

three technical activities - design, coding, implementation and testing that are required to build

and verify the software.

The design activities are of main importance in this phase, because in this activity, decisions

ultimately affecting the success of the software implementation and its ease of maintenance are

made. These decisions have the final bearing upon reliability and maintainability of the system.
10
 Design is the only way to accurately translate the customer’s requirements into finished soft-

ware or a system. The software is divided into 2 modules which are students, and administrators.

We shall look at each module in detail.

Student: Each student belongs to a class identified by semester and programme. Each class be-

longs to a department and are assigned a set of courses. Therefore, these courses are common to

all students of that class. The students are given a unique username and password to login. Each

of them will have a diferent view.

Admin: The administrator will have access to all the information in the diferent tables in the

database. They will access to all the tables in a list form. They will be able to add a entry in any

table and also edit them. The design of the view for the admin will provide a modular interface so

that querying the tables will be optimized. They will be provided with search and filter features so

that they can access data efficiently.

Faculty: The Faculty could has a separate interface where he/she could see student informa-

tions, upload their results and grades, check and update attendance status, upload study materials,

update time schedule and can view additional informations posted by any departments.

6.3.1 Use-Case Diagram

Figure 5: Student
Figure 6: Admin

11
 Figure 7: Faculty

6.3.2 ER Diagram

Figure 8: E-R Diagram

6.3.3 Context-level DFD

Lvl 0:

12
 Figure 9: Admin
Figure 10: Student

Lvl 1:

Lvl 2:

13
6.4 Implementation

This project designs a Web-based university education and teaching management information

system. By analyzing the requirements of university education and teaching management infor-

mation system, the design principle of the system is determined, the structure design of university

education and teaching management information system is realized, and the management process

of the system is determined. On the basis of the above, by calculating the complexity of university

education and teaching management information, the priority of query information is determined

to effectively improve the processing effect of the system. Finally, the relational database model is

designed to realize the design of university education and teaching management information system.

Flow Chart

Figure 11: System flow Chart

14
6.4.1 Admin Module

Figure 12: Hompage Figure 13: Common login portal for all users

Figure 14: Dashboard Figure 15: Accounts

Figure 16: View Profile Figure 17: Add subjects

15
 Figure 18: Manage programmes Figure 19: Manage Periods

Figure 20: View student status Figure 21: View individual student status

Figure 23: Communications and queries from

Figure 22: Manage organisational event
student

Figure 24: Basic Informations Figure 25: Admin Contact

16
6.4.2 Teacher Module

Figure 26: Manage timetable Figure 27: Add result

Figure 28: Manage result Figure 29: Manage Attendance

Figure 30: Manage study-materials sem-wise Figure 31: Manage study material

17
 Figure 32: Add study-materials

6.4.3 Student Module

Figure 33: Reset password Figure 34: Student registration

Figure 35: Student dashboard Figure 36: View and manage profile

18
Figure 37: Mark and view attendance Figure 38: View study-materials

Figure 39: View results Figure 40: View fee-status

Figure 41: View charges Figure 42: View receipt

Figure 43: Student queries Figure 44: Blocked user

19
6.4.4 DB Design

In database management system file that defines the basic organization of a database. A

data dictionary contains a list of all files in the database, the number of records in each file, and

the names and types of each field. Most database management systems keep the data dictionary

hidden from users to prevent them from accidentally destroying its contents.

Data dictionaries do not contain any actual data from the database, only book keeping in-

formation for managing it. Without a data dictionary, however, a database management system

cannot access data from the database.

Following are the studenterp database tables of the project:

Figure 45: studenterp DB

1. Accounts

The ”accounts” table stores user credentials, such as ID, password, name, email, and im-

age path. It also includes a ”type” field to differentiate between ”admin,” ”student,” and

”teacher” roles for access control. The ”blocked” flag, set to 1, signifies restricted access for

a user.

20
 Figure 46: accounts

2. Metadata

The ”metadata” table is a versatile repository in the student ERP system. It includes fields

like item ID, meta key, and meta value, enabling dynamic storage of metadata for various

system entities. It captures diverse information, including academic data (e.g., program IDs,

subject IDs) and administrative details (e.g., status updates, financial transactions).

Figure 47: metadata

3. Posts

The ”posts” table serves as a repository for various types of content within the student ERP

system.

Author: Identifies the user who created the post.

Title and Description: Store textual content, providing a concise title and detailed de-

scription.

Type: Categorizes posts (e.g., program, subject) for organization.

Publish Date and Modified Date: Track timestamps of publication and modification.

Status: Indicates publication status for transparency.

21
 Parent: Establishes relationships between posts, enabling hierarchical structuring.

Figure 48: posts

4. Attendance

The ”attendance” table records student attendance, noting their presence or absence on

specific dates. It includes fields for ID, student ID, date, and status, allowing for efficient

tracking and monitoring of attendance records.

Figure 49: attendance

5. Usermeta

The ”usermeta” table enhances user profiles, especially for students, by storing additional

details like contact information, academic history, and parental details. It uses fields for user

ID, meta key, and meta value to accommodate various attributes such as date of birth, contact

numbers, address, academic performance, and parental information.

22
 Figure 50: Usermeta for student details

6. Notices

The ”notices” table holds notices created by administrators, with fields for ID, content, times-

tamp, publisher, headline, and optional file path. Administrators can compose text-based

notices and attach files if needed. Each notice is timestamped upon creation and attributed

to a specific administrator, with a headline providing a summary of its content.

Figure 51: Notices

7. fee payments and semester charges

The ”fee payments” table tracks fee payments by students, including payment ID, student

ID, payment month, status, and date. It records each transaction, indicating the student,

payment month, status (successful or pending), and payment timestamp.

The ”monthly charges” table lists semester-specific charges, with fields for charge ID, month,

title, and amount. It covers expenses like hostel accommodation, tuition, exams, and other

fees.

23
 Figure 52: fee payment

Figure 53: semester charges

8. Campus functions

The ”campus-functions” table holds data on campus events, initiatives, and announcements.

It includes fields for function ID, headline, content, publisher, creation date, and file path.

This table acts as a hub for diverse campus activities like events, sustainability efforts, and

diversity dialogues, each record providing details including headline, description, publisher,

creation date, and associated files.

Figure 54: campus-functions

9. student queries and admin replies

The ”student-queries” table logs student queries with fields for query ID, student ID, sub-

ject, message, and timestamp. The ”admin-replies” table records administrator responses to
24
 these queries, including reply ID, linked query ID, admin ID, reply message, and timestamp.

Together, they enable communication tracking between students and administrators .

Figure 55: student-queries

Figure 56: admin-replies

10. password reset

The ”password-reset” table is used for storing information related to password reset requests.

It includes fields for ID, email, token (a unique identifier for the reset request), and creation

timestamp. This table enables the management of password reset functionality by storing

requests along with their corresponding tokens and timestamps.

Figure 57: reset-password

25
11. study materials

The ‘study-materials‘ table is designed to store information about educational materials.

Each entry includes an ID, title, description, file name, upload timestamp, class ID, subject

ID, and file extension. The data represents various study materials such as notes, past year

questions (PYQ), and syllabi.

Figure 58: study-materials

12. student results

The ‘student-results‘ table records the academic performance of students. It contains fields

for student ID, semester, marks obtained in quizzes, mid-terms, and end-terms, total marks

obtained, grade, and subject ID. Each entry represents a student’s performance in a particular

subject for a given semester.

Figure 59: results

26
6.5 Testing and Integration

We test the software process activities such as Design, Implementation, and Requirement

Engineering. Because, design errors are very costly to repair once system has been started to

operate, it is quite obvious to repair them at early stage of the system. So analysis is the most

important process of any project.

As most interested portion is whether the system is meeting its requirements or not, for that

testing should be planned so that all requirements are individually tested. We checked the output

of certain combination of inputs so that we can know whether it gives desirable results or not.

Strictly sticking to your requirements specifications, give you the path to get desirable results

from the system.

Testing Strategy

There are types of testing that we implement. They are as follows:

1. While deciding on the focus of testing activities, study project priorities. For example, for

an on-line system, pay more attention to response time. Spend more time on the features

used frequently.

2. Decide on the effort required for testing based on the usage of the system. If the system is

to be used by a large number of users, evaluate the impact on users due to a system failure

before deciding on the effort.

3. A necessary part of the test case is a definition of the expected result.

4. Write test cases for invalid and unexpected as well as valid and expected input conditions.

5. Thoroughly inspect the results of each test.

6.5.1 Unit Testing

Intuitively, one can view a unit as the smallest testable part of an application. In procedural

programming, a unit could be an entire module, but it is more commonly an individual function

or procedure. In object-oriented programming, a unit is often an entire interface, such as a class,

but could be an individual method.

27
• Unit testing performed for all the functions in the code and test cases are generated

Actions/functions.php

Figure 60: unit tests of get-teachers, get-classes, get-post

testcases:

28
 Figure 61: unit-tests of get-posts and get-metadata

testcases:

29
 Figure 62: unit-tests for data-output and get-user-data

testcases:

30
 Figure 63: unit tests for get-usermeta

testcases:

6.5.2 Validation Testing

Validations are independent procedures that are used together for checking that a product,

service, or system meets requirements and specifications and that it fulfils its intended purpose.

The words ”verification” and ”validation” are sometimes preceded with ”Independent” (or IVV),

indicating that the verification and validation is to be performed by a disinterested third party.

31
 Overview

Validation is intended to ensure a product, service, or system (or portion thereof, or set thereof)

result in a product, service, or system (or portion thereof, or set thereof) that meets the operational

needs of the user. For a new development flow or verification flow, validation procedures may involve

modelling either flow and using simulations to predict faults or gaps that might lead to invalid or

incomplete verification or development of a product, service, or system (or portion thereof, or set

thereof).

Aspects of Validation

The most tested attributes in validation tasks may include, but are not limited to

• Selectivity/specificity

• Accuracy and precision

• Repeatability

• Reproducibility

7 Limitations

The limitation of the application is more improve in online examination. Limited questions

had been stored and need more updation and maintenance of the application.

Storage capacity too small so that it cannot be stored large amount of data so take back up is

necessary for the future requirement. So limited amount of data can be stored.

8 Future Enhancement

Future enhancement for an ERP system for college management could be the integration of

artificial intelligence (AI) and machine learning (ML) technologies. This could involve the use of

predictive analytics to forecast student enrollment and identify patterns in student behavior and

performance. The system could also use natural language processing (NLP) to enable voiceactivated

commands and conversational interfaces for users. Additionally, the ERP system could incorporate

32
blockchain technology to improve security and transparency in record-keeping, such as student

transcripts and financial aid disbursement. This could also enable the creation of smart contracts

to automate processes and reduce administrative workload.

9 Conclusion

By using Existing System accessing information from files is a difficult task and there is no

quick and easy way to keep the records of students and admin. Lack of automation is also there

in the Existing System. The aim of Our System is to reduce the workload and to save significant

administrators’ time.

Title of the project as student ERP System is the system that deals with the issues related to a

particular institution. It is the very useful to the student as well as the faculties to easy access to

finding the details. The software provides appropriate information to users based on their profiles

and role in the system. The fundamental problem in maintaining and managing the work by the

administrator is hence over come. Prior to this it was a bit difficult for maintaining the time table

and also keeping track of the daily schedule. But by developing this web-based application the

administrator can enjoy the task, doing it ease and also by saving the valuable time. The amount

of time consumption is reduced and also the manual calculations are omitted. Thus the system

developed will be helpful to the administrator by easing his/her task providing the accurate results.

The storage facility will ease the job of the operator.

This project is successfully implemented with all the features and modules of the student manage-

ment system as per requirements.

33
References

[1] Elliot Soloway. Should we teach students to program? Commun. ACM, 36(10):21–24, 1993.

https://www.studocu.com/in/document/amrita-vishwa-vidyapeetham/software-engineering/se-report-

erp-system/31420738?origin=organic-success-document-viewer-cta

https://www.studocu.com/in/document/maharaja-agrasen-institute-of-technology/btech/project-report-

on-college-management-system-using-php-and-mysql/21496170

https://chat.openai.com/

https://technostudy.co.in/

https://www.w3schools.com/php/

https://github.com/crazymodifier/school-management-system/blob/master/actions/login.php

https://stackoverflow.com/questions/tagged/php

https://ieeexplore.ieee.org/document/10162365/

34