ONLINE STUDENT FEEDBACK SYSTEM FOR BATTICALOA CAMPUS

A PROJECT REPORT PRESENTED BY

MAHENDRARAJAH ARULKUMARAN

to the Board of Study in Information and Communication Technology of the

POSTGRADUATE INSTITUTE OF SCIENCE

in partial fulfillment of the requirement

for the award of the degree of

MASTER OF SCIENCE IN INFORMATION AND COMMUNICATION

TECHNOLOGY

of the

UNIVERSITY OF PERADENIYA
SRI LANKA

2018
 II

DECLARATION

I do hereby declare that the work reported in this project report was exclusively carried out
by me under the supervision of Dr. Amalka J. Pinidiyaarachchi and Mr. Prabhath
Gunathilake. It describes the results of my own independent research except where due
reference has been made in the text. No part of this project report has been submitted
earlier or concurrently for the same or any other degree.

Date: ……………………. ……..……………………………………

Signature of the Candidate

Certified by:

1. Supervisor (Name): …………………………… Date: ………………..

(Signature): …………………………………

2. Supervisor (Name): …………………………… Date: ………………..

(Signature): …………………………………

PGIS Stamp:
 III

ONLINE STUDENT FEEDBACK SYSTEM FOR BATTICALOA CAMPUS

M. Arulkumaran

Postgraduate Institute of Science, University of Peradeniya, Peradeniya, Sri Lanka Department of

Information and communication technology, Faculty of Science, Peradeniya, Sri Lanka.

The project is aimed to automate the Student Feedbacks which is manually maintained.
After the automation this will mean better services and good keeping of records, data
integrity, data security, quick search and also paperless environment. The project has
mainly tackled management of information for the Dean.

Every user of the system will have to log into the system using username and password so
that security and authentication will be ensured. Once logged in, a user can make and check
status or even give feedback. The system administrator is able to manage user information
and also update records.
 IV

ACKNOWLEDGEMENTS

I have taken efforts in this Project. However, it would not have been possible without the
kind of support and help of many individuals and organization. I would like to extend my
sincere thanks to all of them. I am highly indebted to UNIVERSITY OF PERADENIYA
for their guidance and constant supervision as well as for providing necessary information
regarding the project & also for their support in completing the project.

I would like to express my gratitude towards my parents & lecturers of UNIVERSITY OF

PERADENIYA for their kind co-operation and encouragement which help me in
completion of this project. I would like to express my special gratitude and thanks to Dr.
Amalka J. Pinidiyaarachchi and Mr. Prabhath Gunathilake for giving me such
attention and time.

I pleasure to express, my sense of gratitude to one and all, who directly or indirectly, have
lent their hand in this venture.

Your Faithful Student

…………………………
M.Arulkumaran
PGIS/SC/MSc/IT/16/04
 V

TABLE OF CONTENTS

DECLARATION ................................................................................................................ II

ACKNOWLEDGEMENTS .............................................................................................. IV

TABLE OF CONTENTS ................................................................................................... V

TABLE OF FIGURES ....................................................................................................... X

INTRODUCTION .......................................................................................................... 1

1.1 Problem Statement .................................................................................................... 2

1.2 Proposed Solution ..................................................................................................... 2

1.3 Proposed Project Title ............................................................................................... 2

1.4 Justification ............................................................................................................... 2

1.5 Existing system ......................................................................................................... 3

1.6 Proposed system........................................................................................................ 3

1.7 Risks.......................................................................................................................... 4

1.8 Mitigations ................................................................................................................ 4

1.9 Monitoring and evaluation ........................................................................................ 4

OVERALL DESCRIPTION ............................................................................................... 5

2.1- System Environment................................................................................................ 5

2.2 Functional Requirements Specification ............................................................... 5

2.2.1 Student sequence .............................................................................................. 6

2.2.1.1 Brief Description ................................................................................................. 6

2.2.1.2. Initial Step-By-Step Description ........................................................................ 6

2.2.2 Administrator sequence .................................................................................... 8

2.2.2.1Brief Description .................................................................................................. 8

2.2.2.2. Initial Step-By-Step Description ........................................................................ 8

 VI

2.2.3 Lecturer Activity............................................................................................. 10

2.2.3.1 Brief Description ............................................................................................... 10

2.2.3.2 Initial Step-By-Step Description ....................................................................... 10

2.2.4 Dean Activity.................................................................................................. 11

2.2.4.1 Brief Description ............................................................................................... 11

2.2.4.2 Initial Step-By-Step Description ....................................................................... 11

IMPLEMENTATION (CODING AND TESTING) ........................................................ 12

3.1 Introduction ............................................................................................................. 12

3.2 Coding ..................................................................................................................... 12

3.3 Application and Database Connection .................................................................... 12

3.4 Testing..................................................................................................................... 12

3.4.1 Functional Testing ............................................................................................... 13

3.4.2 System Testing ..................................................................................................... 13

3.4.3 Recovery Testing ................................................................................................. 13

3.4.4 Acceptance Testing .............................................................................................. 13

3.4.5 User Acceptance testing ....................................................................................... 13

3.4.6 Unit testing ........................................................................................................... 14

3.5 Test Data ................................................................................................................. 14

3.6 File Conversion ....................................................................................................... 14

3.7 Control .................................................................................................................... 14

IMPORTANCE OF STUDENT FEEDBACK ................................................................. 15

4.1 How is Student Feedback Obtained? ...................................................................... 15

4.2 Focus of the Student Feedback Form...................................................................... 15

4.3 Objectives of Student Feedback on Study-units ..................................................... 16

4.4 Anonymity of Student Feedback ............................................................................ 16

 VII

SUMMARY, LIMITATION, CONCLUSION AND RECOMMENDATIONS ............. 18

5.1 Introduction ............................................................................................................. 18

5.2 Summary ................................................................................................................. 18

5.3 Limitations .............................................................................................................. 18

5.4 Conclusions ............................................................................................................. 18

SYSTEM DEVELOPMENT METHODOLOGY (SDLC) .............................................. 19

6.1 FACT FINDING TECHNIQUES ........................................................................... 19

6.1.1 Observation .......................................................................................................... 19

6.1.2 Interviews ............................................................................................................. 19

6.1.3 Secondary Data Collection .................................................................................. 20

6.2 Waterfall Model ...................................................................................................... 20

6.2.1 Feasibility study ................................................................................................... 21

6.2.2 Design .................................................................................................................. 21

6.2.3 Coding/Implementation ....................................................................................... 21

6.2.4 Testing.................................................................................................................. 21

6.2.5 Maintenance ......................................................................................................... 21

6.3 Benefits of waterfall model ..................................................................................... 22

6.4 Criticisms of waterfall model.................................................................................. 22

REQUIREMENTS ANALYSIS ....................................................................................... 23

7.1 User Requirements .................................................................................................. 23

7.2 Functional Requirements ........................................................................................ 23

7.3 Non-functional Requirements (NFR) ..................................................................... 23

7.4 System Requirements.............................................................................................. 24

7.4.1 Hardware requirements .................................................................................... 24

7.4.2 Software Component System Requirement: .................................................... 24

 VIII

7.5 SYSTEM CONSTRAINTS .................................................................................... 25

7.5.1 User Interface Constraints................................................................................ 25

7.5.2 Hardware Constraints....................................................................................... 25

7.5.3 Software Constraints ........................................................................................ 25

7.5.4 Data Management Constraints ......................................................................... 25

7.5.5 Design Standards Compliance ......................................................................... 25

SYSTEM DESIGN ........................................................................................................... 26

8.1 Introduction ............................................................................................................. 26

8.2 Data Modeling .................................................................................................... 26

8.2.1 Conceptual design ............................................................................................ 26

8.3 Data dictionary ........................................................................................................ 28

8.4 Physical design implementation ............................................................................. 29

8.4.1 Import database ................................................................................................ 29

8.4.2 Login System ................................................................................................... 29

8.4.3 Form Validation ............................................................................................... 30

8.4.7 Forget Password ............................................................................................... 32

8.4.8 Reset Password ................................................................................................ 33

8.4.9 Login Interface ..................................................................................................... 33

8.4.10 Add Lecturer .................................................................................................. 34

8.4.11 Search Lecturer .............................................................................................. 34

8.4.12 Update Lecturer ............................................................................................. 35

8.4.13View Student ................................................................................................... 36

8.4.14 Update Student ............................................................................................... 36

8.4.15 Add Faculty.................................................................................................... 37

8.4.16 Student Login History .................................................................................... 37

 IX

8.4.17 Feedback home .............................................................................................. 38

8.4.18 Individual feedback ........................................................................................ 39

8.4.19 Overall feedback summary ................................................................................ 40

ADVANTAGES/DISADVANTAGES ............................................................................ 41

9.1 Advantages .......................................................................................................... 41

9.2 Disadvantages ..................................................................................................... 41

CONCLUSION AND FUTURE DEVELOPMENTS ...................................................... 42

10.1 add more questions ........................................................................................... 42

10.2 Add question value for process ......................................................................... 43

Project implementation Plan Approval ............................................................................. 44

Reference .......................................................................................................................... 45
 X

TABLE OF FIGURES

Figure 1- Use Case Diagram ............................................................................................... 5

Figure 2- Student Sequence Diagram ................................................................................. 6
Figure 3- Student activity Diagram..................................................................................... 7
Figure 4- Admin Sequence Diagram .................................................................................. 8
Figure 5- Administrator Activity Diagram ......................................................................... 9
Figure 6 - Lecturer Activity Diagram ............................................................................... 10
Figure 7- Dean Activity Diagram ..................................................................................... 11
Figure 8- Waterfall Diagram ............................................................................................. 20
Figure 9- ER Diagram of entire system ............................................................................ 27
Figure 10- class Diagram of entire system ....................................................................... 28
Figure 11- Home page menu............................................................................................. 29
Figure 12- Student Registration Form .............................................................................. 29
Figure 13 - required Data Validation ................................................................................ 30
Figure 14- Email Validation ............................................................................................. 30
Figure 15- Character Validation ....................................................................................... 30
Figure 16- Username alert validation ............................................................................... 31
Figure 17- Password Validation........................................................................................ 31
Figure 18- Retrieve List data from database ..................................................................... 32
Figure 19- Forget Password .............................................................................................. 32
Figure 20- Forget Password .............................................................................................. 32
Figure 21- Reset Password................................................................................................ 33
Figure 22- Login Interface ................................................................................................ 33
Figure 23- Add Lecturer ................................................................................................... 34
Figure 24- Search Lecturer ............................................................................................... 34
Figure 25- Update Lecturer ............................................................................................... 35
Figure 26- View Student ................................................................................................... 36
Figure 27- Update Student ................................................................................................ 36
Figure 28- Update Student ................................................................................................ 36
Figure 29- Add Faculty ..................................................................................................... 37
 XI

Figure 30- Student Login History ..................................................................................... 37

Figure 31- Feedback home................................................................................................ 38
Figure 32- Individual feedback ......................................................................................... 39
Figure 33- Overall feedback summary ............................................................................. 40
Figure 34-Create New Question ....................................................................................... 42
Figure 35- Add question value for process ....................................................................... 43
 1

CHAPTER 1

INTRODUCTION
We have developed The Online Student Feedback System to get feedbacks from students
about their satisfaction on academic activities in the college. The Online Student Feedback
System provides capabilities for selecting particular lecturer to give feedback and generate
the output automatically, about each lecturer’s performance in teaching. The Online Student
Feedback System is a feedback system that provides the proper feedback questionnaires to
the students with categories of options like poor, normal, good, better and best.

In the existing system students give feedbacks about the lecturers manually. Afterwards
every student’s feedbacks are collected by the faculty and calculated the overall grade for
each lecturer. After that those all grade report is viewed by the Head of Department and
Dean which is given by the students. So, the existing system takes more time to perform
these works. This is the main disadvantage of the existing system for giving feedback about
the lecturers and viewing report of lecturers manually. For this reason, The Online Student
Feedback System is implemented.

Through this system student can give feedback in online without wasting their time. Student
feedback is an essential matter in an academy such as college and universities for quality
assurance. Questionnaires are primary importance and the best tool to get feedback from
students. With the help of these questionnaires we get detailed information about lecturers’
performance and students’ satisfaction on academic activities. Also we get information about
the course's strengths and weaknesses with the help of these questionnaires. The aim of this
system is saving time, giving easy way to give feedback for students and helping
management to do their works easily.
 2

1.1 Problem Statement

Currently students have to do give their feedbacks in paper work so it takes so much time
also it doesn’t have privacy and also many students not interested in doing paper works

1.2 Proposed Solution

The proposed online feedback system will eliminate all these manual interventions and
increase the speed of the whole process. The system will allow users to register online and
successfully submit their feedbacks.

The system has inbuilt validation system to validate the entered data. The users can login to
the system to check on the status of the feedbacks. The system will show the already given
feedbacks for lectures to collect. This data will be stored in the database for further reference.

1.3 Proposed Project Title

Title of the project is clearly stated, i.e. Online Feedback System.

1.4 Justification
Online Feedback system will break the geographical barriers and bring the whole process
into a quick and easy way to access Feedbacks. It will automate the traditional feedback
system into a modern computerized system. This will enhance data retrieval, storage and
security. It is also cost effective since it will cut down on travelling cost to get your feedbacks
taken and also going to check if your feedback has been made and is ready for collection.

The clients can access their online feedbacks 24/7 and at any location provided they are
connected to the internet.
 3

1.5 Existing system

Coming to the existing system the feedback is done by manual process. In the existing system
students can give feedback about the lecturers by using paper and pen. After giving feedback
by every student papers are collected by the dean’s and calculate the overall grade for each
lecturer. After that those all grade report is viewed by the principal which is given by the
dean’s. Hence estimating the performance of lecturers and giving counseling to college staff.

So, the existing system is carries more time to do a piece of work for this reason. The online
system feedback is implemented. This is the major advantage of the existing system for
giving feedback about the lecturers and viewing report of lecturers.

1.6 Proposed system

Here we aimed to design online web application for issuing the feedback about the lecturers
by students, this is named as student feedback system. Student feedback system to provide
feedback in an easy and quick manner to the college lecturers and dean. So we call it as
student feedback system which delivers via the student staff interface as online system which
acting as a service provider by using this technology we can make fast feedback about the
staff by students on time to head of departments as they referred in online system.

This project has four kinds of users student, staff, dean, and admin. The student can give
feedback in online system provided by college staff. Students and can give feedback about
the lecturers.

These feedback reports were checked by the dean. He can view overall grades and view the
grades obtained to the lecturers and give this report to the principal and he can give
counseling to the college staffs compared to the manual system, online system is very simple
to use and also understand.
 4

1.7 Risks
Some of the risks and threat that can affect this project are: -

• Hosting – some host may be unreliable

• Security risk – hackers and virus attack

• Time – not able to complete the project in time

• Cost of resources – not having adequate budget

1.8 Mitigations
• Look for reliable people/company to host your program.

• Use of security measures e.g. firewalls to protect from unauthorized people.

• I will ensure that project schedule is followed for the project to finish in time.

• Ensure that the required resources are available and within my budget.

1.9 Monitoring and evaluation

It was done by weekly meeting with my supervisors. I was able to report the progress and
challenges encountered. I also worked and highly appreciated on changes recommended to
improve the quality of this project to this level of standard.
 5

CHAPTER 2
OVERALL DESCRIPTION

2.1- System Environment

Figure 1- Use Case Diagram

The Online Feedback System has four active actors and one cooperating system. the Student,
Lecturer, Dean and Administrator accesses the Online Feedback through the Internet.

2.2 Functional Requirements Specification

This section outlines the Sequence for each of the actors separately. The Student, the
Lecturer and the Dean have only one use case apiece while the Administrator is main actor
in this system.
 6

2.2.1 Student sequence

Figure 2-– Student Sequence Diagram

2.2.1.1 Brief Description

The Student accesses the Online Feedback Website, searches for an lecturer and generate
feedback it to his/her machine.

2.2.1.2. Initial Step-By-Step Description

1. The Student Can register themselves
2. The Student can login with his username password
3. The Student can Reset his password If Password lost
4. The system displays the choices to the Lecturer.
5. The Student generate lecture feedback.
 7

Figure 3- Student activity Diagram

 8

2.2.2 Administrator sequence

Figure 4- Admin Sequence Diagram

2.2.2.1Brief Description
The Administrator accesses the Online Feedback Website, update and monitor.

2.2.2.2. Initial Step-By-Step Description

1. The Admin can login
2. The Admin add lectures
3. The Admin add Faculties
4. The Admin edit student and lecture data
5. The Admin monitor login history
 9

Figure 5- Administrator Activity Diagram

 10

2.2.3 Lecturer Activity

Figure 6 – Lecturer Activity Diagram

2.2.3.1 Brief Description

The Lecturer accesses the Online Feedback Website, monitor his individual feedback .

2.2.3.2 Initial Step-By-Step Description

1. The Lecturer can login

2. The Admin view lectures
3. The Admin view Students
4. The Admin view his own feedback
 11

2.2.4 Dean Activity

Figure 7- Dean Activity Diagram

2.2.4.1 Brief Description

The Dean accesses the Online Feedback Website, monitor all individual lecturer
feedbacks and overall feedback summary.

2.2.4.2 Initial Step-By-Step Description

1. The Dean can login
2. The Dean view lectures
3. The Dean view Students
4. The Dean view lecturers feedbacks
5. The Dean view overall feedback summary
 12

CHAPTER 3

IMPLEMENTATION (CODING AND TESTING)

3.1 Introduction
Implementation is the stage in the project where the theoretical design is turned into a
working system. The implementation phase constructs, installs and operates the new system.
The most crucial stage in achieving a new successful system is that it will work efficiently
and effectively.

3.2 Coding
Coding is the construction of the actual system using specific language. For this proposed
system, I have used PHP to actualize the system. It is a scripting language, more secure and
web based.

3.3 Application and Database Connection

The constructed system is connected to the Mysql Database through a data environment. The
tables should be created and normalized. The data should also be validated. A connection
should also be set and established in the design of the respective forms.

3.4 Testing
Testing is the process of verifying and validating the system for the conformance with
specification and meeting the client’s requirements. The objectives of testing are to
ensure that the system programs is error free, guarantee the system end users can interact
with the system well and ensure that the components of the system interface are working
well.
 13

3.4.1 Functional Testing

The purpose of functional testing is to ensure that the program performs all the functions
that were originally specified, that all the input is correctly accepted. It relates to the whole
system and does not require a technical understanding of the system. All the functions of the
system as originally specified are systematically tested to ensure that nothing has been
accidentally omitted or misinterpreted. A positive attempt is made to anticipate errors than
an inexperienced user might make, and tests made to check the effect of such errors and
ensure that they do not result in incorrect actions or bad data being stored in the database.

3.4.2 System Testing

This is where the system is checked whether it has met the user requirements and performs
as per expectations. The following are the tests to be used. On completion of the whole
system, each of it is tested to ensure no errors have been introduced. The system is tested
with a realistic amount of test data; although the researcher is not expected to spend days
typing in hundreds of records, the system should be tested with about 50 records in each of
the main tables.

3.4.3 Recovery Testing

Recovery testing can be carried out to determine what happens, for example if there is a
power failure in the middle of data entry. Is the whole database corrupted?

3.4.4 Acceptance Testing

The user is invited to test the system to ensure that it fulfills the stated objectives. If
possible the researcher should observe this testing and not stop the user from mistakes. The
system should cope with unexpected user behavior.

3.4.5 User Acceptance testing

This is testing of the system by the user department after the system has passed the systems
test
 14

3.4.6 Unit testing

After the parts of the system are completed they are first tested. All the new hardware,
procedural manuals and all system interfaces must be tested to ensure that they meet the
required standards.

3.5 Test Data

The purpose of test data is to verify and make sure that the system is operating well and
according to the standards set. It involves checking the new system if it is working correctly.
It is tested in modules to establish if there is any problem in any module. This is whereby
each module is tested on its own. While testing entries should be inputted as they are so as
to be acceptable in the database else errors will occur. As an example, if student’s Id should
be in numbers so the field should not accept text.

3.6 File Conversion

The analyst changes the existing files into a form where it can be used by the new system.
The procedure is as follows; the analyst first record the file data then Transcribe the
documents to suitable media and Verifies data to ensure it is error free

3.7 Control
Control measures to be put in place for the system is; Password where the user is required to
enter his/her password to log in. It is only to authorize users.

The antivirus software should be used to clean up the viruses harmful to the application.
Physical security such as keeping the system in a safe room- Ensure that there are firm
windows and Doors and guarding the place.
 15

CHAPTER 4
IMPORTANCE OF STUDENT FEEDBACK

The University Collage to offer the best possible environment and learning experience to
encourage students to perform to their full potential.

Students play a critical part in the evaluation, development and enhancement of the quality
of this learning experience. Feedback from students allows the University Collage to
evaluate how its service provision is viewed by its most important group of stakeholders,
namely its students.

The Bologna has put an increasing emphasis on the need for involvement of students in the
quality assurance of higher education. Student involvement requires that students act as
collaborators in rather than merely passive receivers of teaching and learning.

4.1 How is Student Feedback Obtained?

Students are invited, by means of an email providing a link, to complete a brief online
feedback form, on an anonymous basis, towards the end of selected study-units. This process
occurs on a twice-yearly basis: towards the end of the first semester, in January, and towards
the end of the second semester, in June. In each case, feedback is collected after students
have been assessed on that particular unit, but prior to publication of results.

4.2 Focus of the Student Feedback Form

The student feedback form focuses on the following issues:
 Comparison between study-unit description and actual delivery
 Lecturing methodology
 Lecturer attributes
 Method of assessment
 Administration and resources
 Any additional comments
 16

4.3 Objectives of Student Feedback on Study-units

Student feedback on study-units has three main objectives:

 To provide students with the opportunity to comment on the quality of their

learning experiences, as required in preparation for and as part of review processes
 To assess the success of academic provision in relation to the expectations of
students
 To provide feedback to lecturers in order to improve delivery and/or content of the
study-unit

4.4 Anonymity of Student Feedback

The student feedback exercise is entirely confidential and anonymous. The procedures
below have been put in place to maintain anonymity and to ensure that students are not
adversely affected by the feedback they submit:

 Students who complete the online form are not asked at any stage for their names
or any other personal details which may be used to identify them.

 Student response data is grouped together for the entire class for the purpose of
data analysis. It is therefore impossible to associate comments and responses
provided with any individual student. Lecturers receive a report which summarizes
all the information collated as percentage values.

 Although students must log on to System to provide feedback, the system uses this
information to present students with the relevant study-units for review. All student
login data is kept separate from their feedback responses.

 The online course evaluation system provides security and confidentiality that far
exceeds that which is possible with traditional paper and pencil methods. The
online format adopted is more conducive to maintaining student anonymity, since
traditional paper and pencil methods require open-ended comments to be
 17

handwritten. In addition to this, students are able to provide their feedback in

privacy, rather than during class time and in the presence of lecturers and other
students.

 Lecturers receive the aggregated results of student feedback after they have
submitted the grades for study-units being reviewed. This ensures that the grades of
students, even though not identifiable on an individual basis, are not affected as a
group by the feedback which is submitted.

 Only those study-units attended by a considerable number of students are included

in the student feedback exercise.

 Participation in student feedback is on an entirely voluntary basis. The system

generates automatic reminder emails to those students who have not completed the
feedback form. However, these students are not identified on an individual basis.
There is also no penalty for abstaining from submission of feedback, since all
grades are published irrespective of participation or non-participation in the student
feedback exercise. Nonetheless, students are strongly encouraged to provide their
feedback and use this opportunity to voice their opinions, since the validity of this
exercise, and thus the continuing improvement of teaching at the University, relies
on a high response rate.
 18

CHAPTER 5
SUMMARY, LIMITATION, CONCLUSION AND RECOMMENDATIONS

5.1 Introduction
This chapter describes the objectives of the system stipulated in earlier chapter, limitation
of the system, conclusion and recommendation of the system.

5.2 Summary
As discussed in the previous chapters the main problem addressed was dealing with online.
It is the above situation that drove us to techniques of developing this Online to enable users
handle details of their s efficiently and effectively. The project has implemented Most of
the objectives stipulated in earlier chapters. The online feedback system offers a number of
benefits to the user and can capture data, store, and view, add and delete the records entered.

5.3 Limitations
Problems Encountered during System Design: Limited time to finish up the work, limited
numbers of computers with the internet in the faculty hence it becomes difficult to download
PHP codes from the internet and inadequate financial support to facilitate the project. It’s as
a result of time factor also that limited the development and incorporation.

5.4 Conclusions
The core reason for the establishment of a feedback system is to enable the customers and
administrators in a convenient, fair and timely manner of interaction. Therefore, the IT used
by whoever uses the system should support the core objective of the system if it is to remain
relevant. A lot still needs to be done in the IT department in order to make available
technology effective. This may involve training of the staffs on how to enter right and
relevant data into the system and the management to keep updating the hardware and
software requirements of the system. IT and computer systems need to be kept being
upgraded as more and more IT facilities software are introduced in today’s IT market.
The researcher acknowledges the fact that this system does not handle all staffs.
 19

CHAPTER 6
SYSTEM DEVELOPMENT METHODOLOGY (SDLC)

System development methodology is a technique that is used to show how the proposed
system will have developed. In this case, the methodology used will be a waterfall model.

6.1 FACT FINDING TECHNIQUES

It shows how data will be collected from the users of the system. The data collection
techniques to be used include:

6.1.1 Observation
I will use this technique to collect information about how the current system operates and its
processes. This involves systematically watching and recording the behaviors and
characteristics of operations and processes. It gives more detailed and context related
information and can adapt to events as they occur, however, the method may be time
consuming.

6.1.2 Interviews
I will conduct an oral interview whereby I will interview Admin, Lectures and Students to
get a deeper insight of how the system is going to work. I prefer this method because it gives
more information from various interviewees and offers greater flexibility as the opportunity
to restructure questions is there, especially in case of unstructured interview. It’s preferred
because it will provide a closer contact between the users and the developer hence dispelling
the probability of the completed system being rejected by users.
This technique also:
• Permits clarification of questions

• Has high response rate than written questionnaires

• It is suitable for use with both literate and illiterates

• Get full range and depth of information

• Develops relationship with users

• Can be flexible with users

 20

6.1.3 Secondary Data Collection

This is data I will collect from existing sources e.g. from the books, internet, journals and
magazines that where collected by other researchers and analysis was done. It is from this
data that I will then compare with the primary data and make a final decision and conclusion.

6.2 Waterfall Model

It is comprised of the stages that the developer will use when developing the system. It is a
sequential model hence the name waterfall. The developer has to finish with one stage before
going to the next one. It comprises of the feasibility study, analysis phase, design phase,
coding phase, testing phase, implementation phase and finally the maintenance phase. It is a
simple model and easy to use and understand. With waterfall development based
methodologies, the analysts and users proceed sequentially from one phase to the next. The
deliverables from each phase are voluminous and are presented to the project sponsor for
approval as the project moves from phase to phase. Once the phase is approved by the
sponsor it ends and the next phase begins.

Figure 8- Waterfall Diagram

 21

6.2.1 Feasibility study

Here, I will carry out a study to gain an understanding of the user’s current system and
problems experienced in this system through interviews, observations, participations etc. I
will use the obtained data to determine the viability of the system being proposed in terms
of technical, economic and social feasibilities.

6.2.2 Design
At this stage I will make an overall design of the system architecture and physical design
which includes User interface and Database design. It’s at this stage that I will identify any
faults before moving onto the next stage. The output of this stage is the design
specification which is used in the next stage of implementation.

6.2.3 Coding/Implementation
At this stage, I will begin coding as per the design specification(s). The output of this step
is one or more product components built according to a pre-defined coding standard and
debugged, tested and integrated to satisfy the system architecture requirements.

6.2.4 Testing
In this stage, I will ensure both individual and integrated whole are methodically verified
to ensure they are error free and satisfy customer requirements. I will involve both unit
testing of individual code modules, system testing of the integrated product and acceptance
testing conducted by or on behalf of customer. I will ensure bugs found are corrected
before moving to the next stage. I will also prepare, review and publish Product
documentation at this stage.

6.2.5 Maintenance
This stage occurs after installation. It involves making modifications on the system to
improve performance. Such changes are user initiated or as a result of bugs being
discovered which were initially not known. These modifications are recorded for
documentation and system update
 22

6.3 Benefits of waterfall model

• It improves on quality: getting requirements and design first helps to catch and
correct possible errors at the design stage than at the testing stage, after all
components have been integrated.
• Simple and easy to understand and use

• Easy to manage due to the rigidity of deliverables and review process Phases
are processed and completed one at a time

6.4 Criticisms of waterfall model

• Advocates of Agile software development argue that waterfall model is a bad
idea in practice – believing it’s impossible for any non-trial project to finish a
phase of software products life cycle perfectly before moving to the next phase
and learning from them. For example, clients may not know exactly what
requirements they need before reviewing a working prototype and commenting
on it. They may change their requirements constantly. Designers and
Programmers may have little control over this. If clients change their
requirements after the design is finalized, the design must be modified to
accommodate new requirements. This effectively means invalidating a good deal
of working hours which means increased cost, especially if a large amount of the
projects’ resources has already been invested in Big design up front.

• Designers may not be aware of future implementation difficulties when writing

a design for an unimplemented software product. That is, it may become clear in
the implementation phase that a particular area of program functionality is
extraordinarily difficult to implement. In this case, it is better to revise the design
than persist in a design based on faulty predictions and that does not account for
the newly discovered problems.
 23

CHAPTER 7
REQUIREMENTS ANALYSIS

7.1 User Requirements

It is very important to get users of the system fully involved such that the problem of change
management does not arise. The system is expected to be:
• Easy to learn and use

• Improve on the efficiency of information storage and retrieval

• Produce results faster reducing on time wasted during to and fro travelling.
• Provides attractive interfaces with easy navigation throughout the system faster,
flexible and convenient.
• A system that stores data and produces result timely and accurately

7.2 Functional Requirements

Functional requirements capture the intended behavior of the system. This behavior may be
expressed as services, tasks or functions the system is required to perform. Therefore, the
proposed system is able to:

7.3 Non-functional Requirements (NFR)

Non-functional requirements are requirements which specify criteria that can be used to
judge the operation of a system, rather than specific behaviors. This is contrasted with
functional requirements that specify specific behavior or functions. NFRs help to achieve
the functional requirement of a system. Thus the proposed system does the following:
• The system has high performance and reliability level. The mean time between
failures, mean time to repair, and accuracy are very high.
• The system has user-friendly interfaces. This ensures the ease with which the
system can be learned or used. The system can allow users to install and operate it
with little or no training.
 24

• Handles growing amounts of work in a graceful manner as can be readily

enlarged i.e. the ease, with which the system can be modified to handle a large
increase in users, workload or Feedbacks.
• The system prevents unauthorized access to the system with user authentication
via login on system.

7.4 System Requirements

7.4.1 Hardware requirements

ITEMS QTY PRICE(Rs)

Computer 1 50 000.00
Processor: core2dual
3GB RAM
500 HDD
External back up (disks) – @ 500 GB 2 16 000.00
Research and internet costs 2 000.00
Printing and photocopying 3 000.00
TOTAL 71 000.00

Table . 1

7.4.2 Software Component System Requirement:

• Browsers: Microsoft Internet Explorer,Chrome, Firefox

• Server: Wamp
• Operating System: Windows XP, 7, 8 and Linux.
• Back end: MySQL.
• Front end: PHP Script and scripting is done using JavaScript.
 25

7.5 SYSTEM CONSTRAINTS

7.5.1 User Interface Constraints

Using this portal is fairly simple and intuitive. A user familiar with basic browser
navigation skills should be able to understand all functionality provided by the portal.

7.5.2 Hardware Constraints.

The portal should work on most home desktop and laptop computers.

7.5.3 Software Constraints

The portal is designed to run on Google Chrome, Mozilla Firefox and Internet Explorer 10.

7.5.4 Data Management Constraints

Portal shall be able to interface with other components according to their specifications.

7.5.5 Design Standards Compliance

The portal shall be implemented in PHP

 26

CHAPTER 8
SYSTEM DESIGN

8.1 Introduction

This involves transforming the software requirements into an architecture that describes its
top level structure and identifies the software components and developing a detailed design
for each software components. For each requirement, a set of one or more design elements
will be produced.

A model is a representation of reality and can be built for existing systems as a way to better
understand those systems or proposed systems as a way to document business requirements
or technical design.

8.2 Data Modeling

This is a technique for organizing and documenting a system’s data.

8.2.1 Conceptual design

Conceptual design is the very first phase of design, in which drawings or solid models are
the dominant tools and products. The conceptual design phase provides a description of the
proposed system in terms of set of integrated ideas and concepts about what it should do,
behave and look like, that will be understandable by the users in the manner intended.
 27

Figure 9- ER Diagram of entire system

 28

Figure 10- class Diagram of entire system

8.3 Data dictionary

This contains all data definitions for cross-referencing and for managing and controlling
access to the information repository / database. It provides a very thorough interface
description (comparable to Interface Control Documents) that is independent of the model
itself. Changes made to a model may be applied to the data dictionary to determine if the
changes have affected the model’s interface to other systems.

Data dictionaries do not contain any actual data from the database, only book keeping
information for managing it. Without a data dictionary, however, a database management
system cannot access data from the database.
 29

8.4 Physical design implementation

8.4.1 Import database

Wamp  Php My Admin  Import Database Choose file  Register (Database name)

8.4.2 Login System

Figure 11- Home page menu

First Student must register them self through register tag, If already register can login
through login tag

Figure 12- Student Registration Form

 30

8.4.3 Form Validation

Figure 13 - required Data Validation

Figure 14- Email Validation

8.4.4 Username Validation

Figure 15- Character Validation

 31

Figure 16- Username alert validation

8.4.45 Password Validation

Figure 17- Password Validation

 32

8.4.6 Retrieve data from database for department/lecturer selection

Figure 18- Retrieve List data from database

8.4.7 Forget Password

Figure 20- Forget Password

 33

8.4.8 Reset Password

7.2.5 Login Interfac

8.4.9 Login Interface

Figure 21- Reset Password

Figure 22- Login Interface

 34

8.4.10 Add Lecturer

8.4.11 Search Lecturer Figure 23- Add Lecturer

Figure 24- Search Lecturer

 35

8.4.12 Update Lecturer

Figure 25- Update Lecturer

 36

8.4.13View Student

Figure 26- View Student

8.4.14 Update Student

 37

8.4.15 Add Faculty

Figure 29- Add Faculty

8.4.16 Student Login History

Figure 30- Student Login History

 38

8.4.17 Feedback home

Figure 31- Feedback home

 39

8.4.18 Individual feedback

Figure 32- Individual feedback

 40

8.4.19 Overall feedback summary

Figure 33- Overall feedback summary

 41

CHAPTER 9

ADVANTAGES/DISADVANTAGES

9.1 Advantages

This Project is beneficial for college use. As well as we implemented in offices, institutions
and hotels.

1. Decreases the time consumption

2. Improves Efficiency- It improves efficiency
3. Occurrences of Error is Minimize
4. Decreases the paper and lab our work
5. Manage the entire process

9.2 Disadvantages

1. it’s too tiring to give Computerized Timing.

2. Security Limitations
3. Charts Only Generate on Intranet
 42

CHAPTER 10

CONCLUSION AND FUTURE DEVELOPMENTS

Finally the feedback evaluation will be smart with the developed system, this is not the
overall description about the feedback system. Some more forms can also be added so as to
better retrieve the feedback details. We implemented the system as per the University level
as well as we will implement it in hotels, universities, private institutions, management
offices etc. Further enhancements can be made in designing the screens. Some more forms
can also be added so as to better retrieve the feedback details. Some more Questions can also
be added in the particular system.
10.1 add more questions

Figure 34-Create New Question

 43

10.2 Add question value for process

Figure 35- Add question value for process

 44

CHAPTER 11

Project implementation Plan Approval

The undersigned acknowledge that they have reviewed the Student Feedback System for
University College batticaloa Implementation Plan and agree with the information presented
within this document. Changes to this Project Implementation Plan will be coordinated with,
and approved by, the undersigned, or their designated representatives.
 45

Reference

 . Book:
Puntambeka, A., 2009. Web Technologies. 1st ed. Pune: Technical
Publications Pune.
 Book:
Danny Goodman and Michael Morrison, D., 2004. JavaScript Bible. 5th
ed. none: none.
 Book:
Thomas A. Powell, T., 2000. Completer Reference HTML. 3rd ed.
Osborne: McGowan-Hill.

website:
CSS Tutorial. 2018. CSS Tutorial. [ONLINE] Available
at: https://www.w3schools.com/css/default.asp. [Accessed 17 October
2017].
 website:
HTML Tutorial. 2018. HTML Tutorial. [ONLINE] Available
at: https://www.w3schools.com/html/default.asp. [Accessed 17 October
2017].
 website:
JavaScript Tutorial. 2018. JavaScript Tutorial. [ONLINE] Available
at: https://www.w3schools.com/js/default.asp. [Accessed 17 October
2017].
 website:
SQL Tutorial. 2018. SQL Tutorial. [ONLINE] Available
at: https://www.w3schools.com/sql/default.asp. [Accessed 17 October
2017].
 website:
PHP 5 Tutorial. 2018. PHP 5 Tutorial. [ONLINE] Available
at: https://www.w3schools.com/php/default.asp. [Accessed 17 October
2017].
 website:
tutorialspoint.com. 2018. PHP Tutorial. [ONLINE] Available
at: https://www.tutorialspoint.com/php/. [Accessed 24 October 2017].