FINAL YEAR PROJECT STUDENT TO SUPERVISOR DISTRIBUTION … · MOHD AZWAN BIN MD SAAD 043896 BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT) WITH HONOURS FACULTY OF INFORMATIC AND

FINAL YEAR PROJECT STUDENT TO SUPERVISOR DISTRIBUTION

AND ABSTRACT TEXT ANALYSIS SYSTEM

MOHD AZWAN BIN MD SAAD

043896

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE DEVELOPMENT) WITH HONOURS

FACULTY OF INFORMATIC AND COMPUTING

UNIVERSITY SULTAN ZAINAL ABIDIN

2018

ii

DECLARATION

I hereby declare that this report is based on my original work except for quotations

and citations, which have been acknowledged. I also declare that it has not been

previously or concurrently submitted for any other degree at Universiti Sultan Zainal

Abidin or other institutions.

_____________________________

Name : Mohd Azwan bin Md Saad

Date : ____ / ____ / ___________

iii

CONFIRMATION

This is to confirm that:

The research conducted and the writing of this report was under my supervision.

__________________________

Name : Dr.Mumtazimah binti Mohamad

Date : _____/_____/_______

iv

DEDICATION

Grateful for Allah s.w.t with his permission and bless so I have

opportunity to complete my final year project. During the course of this final

degree project, I have acquired a valuable experience of bittersweet and sweet in

my life as a student.

On this occasion, I would like to thank all parties involved directly or

indirectly in completing this assignment. Thank you especially to my supervisor

Dr Mumtazimah binti Mohamad as she has been giving much guidance and advice

to me throughout the course of this final degree project. Thousands of gratitude

also to lecturers and individuals involved throughout my studies for three and a

half years in the Bachelor of Software Development program at Sultan Zainal

Abidin University (UniSZA). The infinite thanks and gratitude are specifically

directed to my family members who have been giving much moral support and

financial assistance to completing my final project. Hopefully their contribution

will be rewarded from Allah s.w.t. Thank you.

v

ABSTRACT

Final Year Student to Supervisor Distribution and Abstract Text Analysis is

proposed as a system to allocate student to supervisor and analyse student’s

abstract. In Faculty Informatics and Computing program run by University Sultan

Zainal Abidin (UniSZA), student are required to develop a software prototype and

write a proposal for their final project. In order to start their project, a group of

student will assigned under a supervisor. Faculty management responsible to

allocate student with supervisor. There are several weakness on current procedure

when allocating supervisor to student which is some lecturers do not get a

balanced CGPA’s student in the group. Then students do not have supervisors in

accordance with their expertise to assist in the project to be done. Supervisor also,

difficult to recognize either the title suggest already taken by previous student or

not. This System will be able to divide the group fairly, student can get their

needed supervisor expertise and the proposal will compared with previous to

make sure the project different and new. This system using TF-IDF (Term

frequency–inverse document frequency) and priority method. Therefore, this

system uses web based platform that has been developed and will solve the faculty

management problem, and ease the student.

vi

ABSTRAK

Pengagihan Pelajar tahun akhir kepada Penyelia dan Analisis Teks Abstrak

Pelajar Tahun Akhir dicadangkan sebagai sistem untuk memperuntukkan pelajar

kepada penyelia dan menganalisis abstrak pelajar. Dalam program Informatik

dan Pengkomputeran Fakulti yang dikendalikan oleh Universiti Sultan Zainal

Abidin (UniSZA), pelajar dikehendaki membangunkan prototaip perisian dan

menulis cadangan untuk projek akhir mereka. Untuk memulakan projek mereka,

sekumpulan pelajar akan ditugaskan di bawah penyelia. Pengurusan fakulti

bertanggungjawab memperuntukkan pelajar dengan penyelia. Terdapat

beberapa kelemahan pada prosedur semasa apabila memperuntukkan penyelia

kepada pelajar yang mana sesetengah pensyarah tidak mendapat pelajar CGPA

yang seimbang dalam kumpulan. Kemudian para pelajar tidak mempunyai

penyelia yang sesuai dengan kepakaran mereka untuk membantu dalam projek

itu. Penyelia juga, sukar untuk mengenali sama ada tajuk yang dicadangkan

sudah diambil oleh pelajar terdahulu atau tidak. Sistem ini akan dapat

membahagikan kumpulan secara adil, pelajar boleh mendapatkan kepakaran

penyelia yang diperlukan dan cadangan itu akan dibandingkan dengan

sebelumnya untuk memastikan projek itu berbeza dan baru. Sistem ini

menggunakan Term frequency–inverse document frequency TF-IDF dan priority

method. Oleh itu, sistem ini menggunakan platform berasaskan web yang telah

dibangunkan dan akan menyelesaikan masalah pengurusan fakulti, dan

memudahkan pelajar.

vii

CONTENTS

PAGES

DECLARATION ii

CONFIRMATION iii

DEDICATION iv

ABSTRACT v

ABSTRAK vi

CONTENTS vii

LIST OF TABLES x

LIST OF FIGURES xii

LIST OF ABBREVIATIONS xiv

LIST OF APPENDICES xv

CHAPTER 1 INTRODUCTION

1.1 Background 1

1.2 Problem statement 3

1.3 Objective 3

1.4 Scopes 3

1.5 Limitation of works 4

1.6 Expected Outcome 4

1.7 Report Structure 5

CHAPTER 2 LITERATURE REVIEW

2.1 Introduction 6

2,2 Study on the available system 6

2.2.1 Final year project management system 7

for information technology programmes

viii

2.2.2 Final year supervision management system 8

as a tool for monitoring computer science projects

2.2.3 Final year project management system .9

2.2.4 Priority Technique 10

2.2.5 Term Frequency Inverse Document

Frequency (TF-IDF) 12

2.3 Summary 14

CHAPTER 3 METHODOLOGY

3.1 Introduction 15

3,2 Methodology in system development 16

3,3 Analysis of system requirements

3.3.1 Development Software Requirements 18

3.3.2 Development Hardware Requirements 19

3.4 Framework Design 20

3.5 Process Model

3.5.1 Context Diagram 21

3.5.2 Data Flow Diagram Level 0 22

3.5.2.1 DFD Level 1 Process 2.0 24


` 3.5.2.3 DFD Level 1 Process 4.0 26


3.5.3 Entity Relationship Diagram 28

3.6 Database Design 29

3.7 Summary 33

CHAPTER 4 IMPLEMENTATION AND RESULT

4.1 Implementations and output

4.1.1 Introduction 34

ix

4.1.2 Development / Configuration 35

4.1.3 Programming Language 35

4.1.4 Interfaces 36

4.2 Testing

4.2.1 Black Box Testing 43

4.2.2 White Box Testing 43

4.3 Test Case

4.3.1. Login 44

4.3.2 Coordinator 45

4.3.3 Student 47

4.3.4 Supervisor 48

4.3.5 Distribute student to supervisor 49

4.4 Summary 49

CHAPTER 5 CONCLUSION

5.1 Discussion 50

5.2 Future Work 51

5.3 Summary 51

REFERENCES 52

APPENDIX A 53

x

LIST OF TABLES

TITLE PAGES

Table 2.1 Analysis on Final Year Project Management

System for Information Technology Programmes 7

Table 2.2 Analysis on Final Year Supervision Management

System as a Tool for Monitoring Computer Science Projects 8

Table 2.3 Final Year Project Management System 9

Table 3.1 Development Software Requirements 18

Table 3.2 Development Hardware Requirements 19

Table 3.3 Table Student 29

Table 3.4 Table Supervisor 30

Table 3.5 Table Coordinator 30

Table 3.6 Table Course 31

Table 3.7 Table Supervising 31

Table 3.8 Table Session 32

Table 3.9 Table Abstract 32

Table 4.1 Test case for Coordinator login 44

Table 4.2 Test case for Student login 44

Table 4.3 Test case for Supervisor login 44

xi

Table 4.4 Test case for add list of student 45

Table 4.5 Test case for add list of supervisor 45

Table 4.6 Test case for delete list of supervisor 46

Table 4.7 Test case for delete list of student 46

Table 4.8 Test case for update list of student 46

Table 4.9 Test case for update list of supervisor 47

Table 4.10 Test case for update student profile 47

Table 4.11 Test case for add abstract 47

Table 4.12 Test case for update abstract 48

Table 4.13 Test case for view student’s abstract 48

Table 4.14 Test case for distribute student to supervisor 49

Table 4.15 Test case for generate report list of supervising 49

Table 1 Milestone 53

Table 2 Gantt chart 54

xii

LIST OF FIGURES

FIGURE TITLE PAGES

Figure 3.1 Methodology Phase 16

Figure 3.2 Framework Design 20

Figure 3.3 Context Diagram 21

Figure 3.4 Data Flow Diagram 22

Figure 3.5 Data Flow Diagram Level 1 Process 2.0 24




Figure 3.9 Entity Relationship Diagram 28

Figure 4.1 Login interface 36

Figure 4.2 Coordinator homepage 36

Figure 4.3 Add Student 37

Figure 4.4 Manage student 37

Figure 4.5 Add Supervisor 38

Figure 4.6 Manage Supervisor 38

xiii

Figure 4.7 Add course 39

Figure 4.8 manage course 39

Figure 4.9 Supervising page 40

Figure 4.10 Student-supervisor list 40

Figure 4.11 Student page 41

Figure 4.12 Abstract analyse page 41

Figure 4.13 Supervisor page 42

Figure 4.14 Student-supervisor list report 42

xiv

LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram

DFD Data Flow Diagram

ERD Entity Relationship Diagram

FYP Final Year Project

TFIDF Term Frequency Inverse Document Frequency

xv

LIST OF APPENDICES

APPENDIX TITLE PAGE

A Milestone 54

Gantt Chart 55

1

CHAPTER 1

INTRODUCTION

1.1 BACKGROUND

The final year project is the culmination of the degree it gives students a

chance to demonstrate all they have learned. In the computer science faculty, a

student must agree upon one of many choices of the project which can generally

be categorized into developing a software application for supporting real-world

needs, conducting an experiment to study the real-world problem via computer

simulation or developing a prototype for answering to innovation needs (M.A.

Mohamed et al, 2017). Although students are supervised, student need to define

the problem boundaries, to investigate possible solutions, and to present the

results in writing, verbally and in action. Apart from an initial briefing session

there are no formal lectures to attend. Teaching consists of regular individual or

small group meetings to discuss progress. For assessment, students submit reports

of their progress and final results, and give in-person presentations and

demonstrations of their work. The project tests students' ability to design, engineer

and evaluate quality systems, research their chosen subject area, make good

decisions, overcome unforeseen problems, work within constraints of limited

2

resources, work to a professional code of conduct, communicate technical

concepts both orally and in writing.

Current at the University of Sultan Zainal Abidin, processes of assigning

supervisor to a group of student are manually and highly rely on traditional ways

for communication and assessment submission. For example, in project selection

and allocation, students are form group randomly by faculty management and fill

in their topic in Microsoft Excel online. Faculty will collect all and approve then

proceed to next task. It can become a tedious and time consuming task when the

number of groups arrived 20 or more. Moreover, the assignment of projects not

requires sorting out the priorities of groups based on their average GPA so will

not be a fair result.

Therefore, Final Year Student-Supervisor Distribution and Abstract

Analysis System help faculty management to allocate supervisor with student

equally based on their CGPA, student’s identity, supervisor’s identity and

expertise using priority technique. Besides that, the system able to compare

project proposal either already taken by previous final year student using TFIDF,

short for term frequency–inverse document frequency, is a numerical statistic

that is intended to reflect how important a word is to a document in a collection

or corpus (Rajaraman, A,2011).

In this report, we developed a web application that can be used to help

Faculty Management to allocate student with supervisor process at the Faculty of

Informatics & Computing, University Sultan Zainal Abidin become smoothen

and easily. An addition, heads of department will improve their management

process become more efficiency and increase the chances for students to enhance

their performance.

3

I.2 PROBLEM STATEMENT

Current system of managing FYP student in traditional ways have contributed to

several problem:

I. Faculty management needs to specify the supervisor for each student

manually from Microsoft Excel.

II. Students do not have a supervisor who is in the skills required to continue

the final project.

III. There is no check or comparison of the FYP titles ever made or not.

I.3 OBJECTIVES

I. To design a system that capable of solving the problems in assigning

supervisor to Final Year Student

II. To develop a Final Year Student to Supervisor Distribution and Abstract

Text Analysis System that works well.

III. To test the functional of the proposed system.

1.4 SCOPE

There are several users involved in this system and responsible for various student

affairs. Among these users are coordinator, lecturers and students. So through this

system the following users can:

1.4.1 Coordinator

Coordinator is the main user this system. Coordinator responsibility to distribute

supervisors fairly to final year students based on CGPA and program. Coordinator

4

also have to manage student’s data and supervisor’s data and set quota for each

supervisor before distribute the student.

1.4.2 Student

Student is one of the user. Student allowed to key in student’s attribute into the

system. They also can submit draft proposal after the system distribute the

supervisor for them.

1.4.3 Supervisor

Supervisor also a part of user who allowed to key in their attribute, expertise and

identity. Supervisor have to approve draft proposal that have been submitted by

student after the system compare the draft proposal either already taken or not.

1.5 LIMITATION OF WORK

The system will only manage allocating supervisor to student and comparing the

draft proposal of the Final Year Project for Degree’s student. It cannot monitor

progress of FYP project.

1.6 EXPECTED OUTCOME

The expected result of the project are the system will run on any web browser,

system will view to student who their supervisor based on what criteria of student

and supervisor. The system can detect either the title project already taken or not.

5

1.7 REPORT STRUCTURE

This report contains of six chapters which are chapter 1 to chapter 6. Chapter 1 is

introduction which contains background, problem statement, objective, scope,

limitation of work and report structure. Chapter 2 is literature review which

contains introduction, existing system, and technique and theory that has been

carried out by other researchers. Chapter 3 is Methodology consists introduction,

methodology in system development, system requirement analysis and

conclusion. While in Chapter 4 is system design and model contains introduction,

framework design, process model, database design and conclusion. Then chapter

5 is implementation and testing consist introduction, testing result, programming

language, result analysis, conclusion. Last, chapter 6 is conclusion contains

introduction, result summary and suggestion for improvement.

6

CHAPTER 2

LITERATURE REVIEW

2.1 INTRODUCTION

This chapter explains literature studies related to developed systems. The

description in this chapter encompasses existing systems and analysis of existing

systems. This study was conducted to ensure that the existing system

vulnerabilities were identified. Next, be able to find solutions to the shortcomings

or weaknesses of the system.

2.2 STUDY ON THE AVAILABLE SYSTEM

Existing system of Final Year Project Supervising Management System

used by Faculty in using manual system in assigning and distribute supervisor to

final year student. There are some lack with existing systems such as the process

to determine the supervisor is slow because coordinator needs to choose the

student himself from Microsoft Excel and group it under each supervisor. Besides

the process for the student to send and get approval for proposal from supervisor

for the final project also need to be done manually.

7

2.2.1 FINAL YEAR PROJECT MANAGEMENT SYSTEM FOR

INFORMATION TECHNOLOGY PROGRAMMES

Table 2.1 shows the summarize of Analysis on Final Year Project Management System

for Information Technology Programmes

Table 2.1: Analysis on Final Year Project Management System for Information

Technology Programmes

K.C. Li et al. (Eds.), 2015

Description The Development of a Final Year Project Management System

for Information Technology Programmes. It is a web-based

system to better support the three kinds of users; they are the

FYP programme organizer (PO), project supervisors and the

project group members. Project supervisors will also be able to

employ the system for keep tracking the progress of the projects.

Advantages 1. PO collect student’s assessments and markers’ scores via the

submission and grading module.

2. Use project management tools, and online chat function.

3. Project group member can share resources about the project

including source code and data files using our online repository.

Disadvantages 1.Not have allocating supervisor with student function

2. Cannot compare either the project title already taken or not.

8

2.2.2 FINAL YEAR SUPERVISION MANAGEMENT SYSTEM AS A TOOL

FOR MONITORING COMPUTER SCIENCE PROJECTS

Table 2.2 shows summarize of Analysis on Final Year Supervision Management as a

Tool for Monitoring Computer Science Projects

Table 2.2: Analysis on Final Year Supervision Management System as a Tool for

Monitoring Computer Science Projects

Marini Abu Bakar et al, 2011

Description Final Year Supervision Management System as a

Tool for Monitoring Computer Science Projects.

It is a web based system to improve project

monitoring and supervision to replace log book.

Once the prototype is completed, we plan to

conduct a user acceptance test.

Advantages 1. The initial prototype consists of three modules,

namely user profile, project monitoring (of

software development and report writing) and

appointment setting.

Disadvantages 1.Not have allocating supervisor with student

function

2. Cannot compare either the project title already

taken or not.

9

2.2.3 FINAL YEAR PROJECT MANAGEMENT SYSTEM.

Table 2.3 shows summarize of Final Year Project Management System

Table 2.3: Final Year Project Management System

.

M.A. Mohamed,2011

Description An Implementation of Final Year Project Management

System. This system to monitor the progress of students.

It also allows students to easily update on the problems

or progress of the project from time to time. The system

is to replace the manual method based on the form

booklet is still being used by lecturers and is known to

be outdated and problematic for both parties. This

system is developed based on modules

Advantages 1. Immediate response, especially when supervisors are

not on campus.

2. Reduce time on update progress and problem.

Disadvantages 1.Not have allocating supervisor with student function

2. Cannot compare either the project title already taken

or not

10

2.2.4 PRIORITY TECHNIQUE

A prioritization technique is one of the more commonly used tools for

prioritization and is ideal when if the problems are considered against a large

number of criteria or when an agency is restricted to focusing on only one priority

health issue. Although decision matrices are more complex than alternative

methods, they provide a visual method for prioritizing and account for criteria

with varying degrees of importance.

There are a few steps outline the procedure for applying a prioritization

matrix First, create matrix. List all issues vertically down the y axis (vertical axis)

of the matrix and all the criteria horizontally across the x axis of the matrix so that

each row is represented by a issue and each column is represented by a criteria.

Include an additional column for the priority score.

Second rate against specified criteria. Fill in cells of the matrix by rating

each issue against each criteria which should have been established by the team

prior to beginning this process. An example of a rating scale can include the

following CGPA(excellent) = 3.50 > 4.00, CGPA(average)= 3.00 > 3.50 ,

CGPA(weak) =< 3.0.

Third weight the criteria. If each criterion has a differing level of

importance, account for the variations by assigning weights to each criterion. For

example, if ‘CGPA(excellent)’ is highest priority. CGPA(average) is second

priority. CGPA(weak) is last priority. Multiply the rating established in Step 2

with the weight of the criteria in each cell of the matrix. If the chosen criteria all

have an equal level of importance, this step can be skipped.

11

Fourth, calculate priority scores. Once the cells of the matrix have been

filled, calculate the final priority score for each problem by adding the scores

across the row. Assign ranks to the problems with the highest priority score

receiving a rank of ‘1.’(Duttweiler, M. 2007)

Example:

So, each supervisor will be able to get a student of the same course that consists of

CGPA excellent, average and weak.

CGPA Weightage

3.5 > 4.0 0.65

3.0 > 3.5 0.25

< 3.0 0.10

Name CGPA W

Name 1 3.33 0.25

Name 2 3.67 0.65

Name 3 3.85 0.65

Name 4 2.89 0.10

Name 5 2.76 0.10

Name 6 3.45 0.25

Supervisor Student

1

Student

2

Student

3

Supervisor

A

3.67 3.33 2.89

Supervisor

B

3.85 2.76 3.45

Supervisor A

Weightage =0.65 + 0.25 +0.10

W=1 Supervisor B

Weightage =0.65 + 0.10 + 0.25

W=1 Supervisor B

Weightage =0.65 + 0.10 + 0.25

W=1

12

2.2.5 TERM FREQUENCY INVERSE DOCUMENT FREQUENCY (TF-IDF)

Term Frequency Inverse Document Frequency (TF-IDF) to determine

what words in a corpus of documents might be more favourable to use in a query.

As the term implies, TF-IDF calculates values for each word in a document

through an inverse proportion of the frequency of the word in a particular

document to the percentage of documents the word appears in. Words with high

TF-IDF numbers imply a strong relationship with the document they appear in,

suggesting that if that word were to appear in a query, the document could be of

interest to the user (Ramos, J. 2003).

To implement this technique it need a mathematical framework and

algorithm. This formula will use in this technique, tf - idft,d = tft,d x idft. tf(w)

represent Number of times term w appears in a document divide by Total number

of terms in the document. While idf(w) represent log e Total number of

documents divide by Number of documents with term w in it.2.6.

13

Example:

TF(w) = (Number of times term w appears in a document) / (Total number

of terms in the document)

IDF(w) = log_e(Total number of documents / Number of documents with

term w in it)

For example, when a 100 word document contains the term “cat” 12 times,

the TF for the word ‘cat’ is

TFcat = 12/100 i.e. 0.12

The IDF (inverse document frequency) of a word is the measure of how

significant that term is in the whole corpus.

For example, say the term “cat” appears x amount of times in a 10,000,000

million document-sized corpus (i.e. web). Let’s assume there are 0.3

million documents that contain the term “cat”, then the IDF (i.e. log {DF})

is given by the total number of documents (10,000,000) divided by the

number of documents containing the term “cat” (300,000).

IDF (cat) = log (10,000,000/300,000) = 1.52

∴ Wcat = (TF*IDF) cat = 0.12 * 1.52 = 0.182

14

2.3 SUMMARY

Overall, to summarize this chapter several case study of available systems

and analysis of available systems have been done and used in the development

process of Final Year Student to Supervisor Distribution and Abstract Text

Analysis System. Priority technique and TF-IDF method is applied to improve

the existing system. Some function from existing system and application also

applied in this project.

.

15

CHAPTER 3

METHODOLOGY

3.1 INTRODUCTION

Methodology is very important in the process of building a system. This

is because it is a complete method that includes the techniques that need to be

followed in executing every activity that exists in the system development life

cycle. To facilitate the development process of Final Year Project Supervising

Management System, the waterfall method will be used. This methodology

selected for use in the development of this system is because it has many

advantages, which can make the system development process seamlessly and

timely. With this, indirect work can be done more regularly and effectively. In

this waterfall methodology, there are five phases involve which are :

16

Figure 3.1 shows five phase of the methodology phase

Figure 3.1 Methodology Phase

3.2 METHODOLOGY IN SYSTEM DEVELOPMENT

This methodology chosen for use in system development is because it has

many advantages, which can make the process of developing this system smooth

and timely. Below are the following phases:

3.2.1 Investigation Phase

It is a phase to identify problems faced on existing system of assigning

supervisor management before developing a system. In this phase, discussions

with supervisors, interviewing certain parties and seeing relevant system

examples have be done.

3.2.2 System Analysis Phase

This phase conducted after the first phase of the initial investigation is completed.

To achieve the objectives contained in the first phase, study on existing system

Investigation Phase

System Analysis Phase

System Design Phase

Development and System Implementation Phase

Support and Operational Phase

17

and case study related the project have been done to ensure system development

work can be carried out at the designated time. Requirement is analyse based on

observation and discussion with faculty management.

3.2.3 System Design Phase

In this phase, some computer software are used for design Context Diagram (CD),

Data Flow Diagram (DFD) and Entity Relationship Diagram (ERD). It used for

reference purposes to facilitate system development. There are three entities

involve in CD, Six process in DFD and seven entities in ERD. Table and interface

is design based on diagram that have been produced.

3.2.4 Development and System Implementation Phase

System development is continued in this phase after all three phases are

completed. System interfaces will be provided in this fourth phase. The HTML,

PHP and JavaScript programming languages are used to ensure the smooth

running of the system interface. Development involve writing code for user

interface and function.

3.2.5 Support and Operational Phase

It is the last phase of the waterfall modelling. It involves the process of upgrading

the interface and database system in the event of an error in testing the system.

Improvements will be made so that objectives can be achieved entirely and meet

the needs of users.

18

3.3 ANALYSIS OF SYSTEM REQUIREMENTS

In the process of developing a system, requirements such as hardware and

software are an important requirement. There are a number of tools used to

develop the Final Year Student to Supervisor Distribution and Abstract Test

Analysis System as shown in Table 3.1 and Table 3.2

3.3.1 Development Software Requirements

There are several software requirement involve for developing this project that show

in Table 3.1

Table 3.1: Development Software Requirements

Software Description

Windows 8.1 Used as a platform for system development.

Visual Studio Code Used as a platform for writing system programs.

Php MyAdmin Used as a database for the system.

19

3.3.2 Development Hardware Requirements

There are several hardware requirement involve for developing this project that show

in Table 3.2

Table 3.2: Development Hardware Requirements

Hardware Description

Laptop ASUS A450L Series

Pendrive 4 GB

Printer Canon E510 Series

20

3.4 FRAMEWORK DESIGN

Figure 3.2 shows the framework design. It have three section which are contains

Users, FYP Management System and Database

Figure 3.2: Framework Design

Framework design gave us a better understanding of how the system will

work. Firstly, student and supervisor sign up or sign in into the system for

validation. Student can submit their draft proposal then student can view who their

supervisor.

While supervisor need to approve the submitted draft then supervisor can

view list student that have been assign under him/her. Lastly, Coordinator act as

admin for this system. Coordinator can manage data student and supervisor.

Coordinator also will get report from the system.

21

3.5 PROCESS MODEL

3.5.1 CONTEXT DIAGRAM

In the context diagram of the Final Year Student Management System there are

three entities namely coordinator, students and supervisors, as shown in Figure

3.3.

Figure 3.3: Context Diagram

Among the activities involved is that, the coordinator will include the

student’s and supervisor’s data to establish a record as a system user. Students

and Supervisors use the same record to enter the system. Furthermore, through

this system the student may upload a proposal and will obtain a supervisor

determined by the system. Students can also update their profile. While the

supervisor needs to confirm the draft of the uploaded proposal and will get a list

of the students set out below. Supervisors may also update their information.

Lastly, the coordinator will receive reports on students, supervisors and

supervising.

22

3.5.2 DATA FLOW DIAGRAM LEVEL 0

Figure 3.4 shows the data flow diagram of the system. It have two entities, six

processes and seven data store.

Figure 3.4: Data Flow Diagram

Referring to Figure 3.4 the process involved is the process of managing

the account. This process allows students and supervisors to log in into the system

by entering the username and password as input. Then the received user

information will be compared if the user is valid or not. Users can also update

their account for change username and password.

The second process is manage student. This process is done by the

coordinator and the student. Coordinators can manage students such as adding

student records, updating student records and deleting student records. The

accepted student data will be stored in the table student in database. Students can

23

update themselves. Please refer to Figure 3.5 data flow diagram level 1 process

2.0

The third process is the manage supervisor. This process is done by

coordinator and supervisor. Coordinators can manage supervisors such as adding

supervisor records, updating supervisor records and deleting supervisor records.

The accepted supervisor data will be stored in the database in supervisor table.

The Supervisor may also update the information. Please refer to Figure 3.6 data

flow diagram level 1 process 3.0

The fourth process is assign supervisor to student. This process will

involve student data and supervisor data. Both of these data will be used for

system assigning process based on priority that has been resolved. After

completion of this process will issue a list of each supervisor with their student

and that data is stored in the database in supervising table. Please refer to Figure

3.7 data flow diagram level 1 process 4.0

The fifth process is compare abstract process. This process involves a

student and a supervisor where the student submits a draft proposal and the system

will compare whether the selected title has been performed by another student or

not. After that the supervisor needs to confirm the uploaded abstract. Refer to

Figure 3.8 data flow diagram level 1 process 5.0

The last process is the report generation process. This process will take

data from table student, supervisor and supervising. The coordinator will handle

this process. The coordinator can print all of these reports as a system report.

24

3.5.2.1 DATA FLOW DIAGRAM LEVEL 1 PROCESS 2.0

Figure 3.5 shows a level flow data flow for a 2.0 process in the Final Year

Student Management System. Process 2.0 is a process of managing student where

there are three more processes involved, namely insert student process, student

update and delete student.

Figure 3.5 Data Flow Diagram Level 1 Process 2.0

25


Figure 3.6 shows a level flow data flow for process 3.0 in the Final Year

Student Management System. Process 3.0 is the process of manage supervisor where

there are three more processes involved under it, namely insert supervisor, update

supervisor and delete supervisor

Figure 3.6: Data Flow Diagram Level 1 Process 3.0

.

26



Student Management System. Process 4.0 is the process of assign supervisor to

student where there are two more processes involved under it, set quota and

distribute using priority technique


.

27



Student Management System. Process 5.0 is the process compare draft proposal

where there are two more processes involved under it, upload draft and compare

draft using TF-IDF technique


28

3.5.3 ENTITY RELATIONSHIP DIAGRAM

Figure 3.9 shows the entity relationship diagram of the system. It contain six

entities and one composite entity.

Figure 3.9: Entity Relationship Diagram

29

3.6 DATABASE DESIGN

Once the system architecture is identified, the database is developed

according to the predefined specifications. Database is designed to store data on

supervisor, student, supervising, draft, coordinator and course information. It

enables information to be quickly and more structured.

Table 3.3 shows Student Tables are divided into six fields namely

student_id, student_name, cgpa, gender, course_code and password. Student_id

is used as a Primary Key in this table.

Table 3.3: Table Student

Name Type Collation Null

student_id Varchar(10) latin1_swedish_ci No

student_name Varchar(50) latin1_swedish_ci No

Cgpa Decimal(4,2)

No

Gender Varchar(10) latin1_swedish_ci No

course_code Varchar(10) latin1_swedish_ci No

Password Varchar(12) latin1_swedish_ci No

30

Table 3.4 show the supervisor table is divided into four fields namely the sv_id,

sv_name, password, course_code. The primary key in this table is sv_id.

Table 3.4: Table Supervisor

Table 3.5 show the coordinator table is divided into two fields namely the

username and password. The primary key in this table is username.

Table 3.5: Table Coordinator


sv_id Varchar(10) latin1_swedish_ci No

sv_name Varchar(50) latin1_swedish_ci No

password varchar(12) latin1_swedish_ci No

course_code Varchar(10) latin1_swedish_ci No


Username varchar(50) latin1_swedish_ci No

Password varchar(10) latin1_swedish_ci No

31

Table 3.6 show the course table is divided into two fields namely the course_code

and course_name. The primary key in this table is course_code.

Table 3.6: Table Course


course_code varchar(10) latin1_swedish_ci No

course_name varchar(10) latin1_swedish_ci No

Table 3.7 show the supervising table is divided into three fields namely the sv_id,

student_id and session. The foreign key in this table is sv_id, student_id and

session.

Table 3.7: Table Supervising


sv_id Varchar(10) latin1_swedish_ci No


Session Varchar(10) latin1_swedish_ci No

32

Table 3.8 show the session table is divided into three fields namely session, start

and end. The primary key in this table is session.

Table 3.8: Table Session

Table 3.9 show the abstract table is divided into three fields namely abstract_id,

student_id, title and content. The primary key in this table is

abstract_id.student_id as foreign key.

Table 3.9: Table Abstract


Session Varchar(10) latin1_swedish_ci No

Start Date

No

End Date

No


abstract_id Int(10)

Yes


Title Varchar(50) latin1_swedish_ci

content Text latin1_swedish_ci No

33

3.7 SUMMARY

The methodology and technique to be used to develop the system has been

described in detail in this chapter. This methodology has the appropriate phases

to assist in the development of the software system development process. In

addition, system requirements including the hardware and software requirements

used in developing the system are described. In this chapter, the system design

has been described in detail. Context diagrams, data flow diagrams, entity

relationship diagrams and database designs have been shown clearly.

34

CHAPTER 4

IMPLEMENTATION AND RESULT

4.1 IMPLEMENTATIONS AND OUTPUT

4.1.1 INTRODUCTION

This chapter describe the implementation of Final Year Student-Supervisor Distribution

and Abstract Text Analysis System. It consist of three part on implementation which is

system for coordinator, system for student and system for supervisor. System for

coordinator include manage user, student, supervisor and get analysis result generate

from system. System for student include, manage profile, upload abstract and get

supervisor. While system for supervisor include manage profile, approve abstract and

get a list of student under their supervision.

35

4.1.2 DEPLOYMENT/ CONFIGURATION

Several language programming had been used for development of Final Year Project

Student to Supervisor Distribution and Abstract Text Analysis System. PHP is use as

server side programming language. PHP is widely-used open source general- purpose

scripting language that is especially suited for web development and can be embedded

into HTML

Validation is this system had been used HTML5, PHP and JavaScript.

Validation is important to ensure that the user fill in all the important details needed in

the system. Open source database MySQL and Apache localhost server are used in this

system. Visual Studio Code is used for write the code.

4.1.3 PROGRAMMING LANGUAGE

i. PHP –use for form processes

ii. HTML5- use to design interface and validation

iii. JavaSript – use for validation

36

4.1.4 INTERFACES

Figure 4.1 shows the login interface for Final Year Student-Supervisor System for all

user involve in the system.

Figure 4.1: Login interface

Figure 4.2 shows the coordinator homepage after login. This page view the number of

student, supervisor, user, course, and supervising.

Figure 4.2: Coordinator homepage

37

Figure 4.3 shows the page for add student. Coordinator can add student by fill in the

form or upload the excel file. After submit the form the system will notify coordinator

by showing a popup message “The record has been successfully added”.

Figure 4.3: Add Student

Figure 4.4 shows the page for manage student. By click the “Student View” button,

Coordinator can view list of student, update the student and delete the student.

Figure 4.4: Manage student

38

Figure 4.5 shows the page for add supervisor. Supervisor can be add by fill in the form

or upload excel file. After submit the form the system will notify coordinator by

showing a popup message “The record has been successfully added”.

Figure 4.5: Add Supervisor

Figure 4.6 show the page for manage supervisor. This page allow user to view list of

supervisor, update supervisor and delete supervisor.

Figure 4.6: Manage Supervisor

39

Figure 4.7 shows the page for add course by fill in the form. After submit the form the

system will notify coordinator by showing a popup message “The record has been

successfully added”.

Figure 4.7: Add course

Figure 4.8 shows the page for manage the course. This page allow to view list of course,

update the course and delete the course.

Figure 4.8: manage course

40

Figure 4.9 shows the page for generate distribution of assigning student and supervisor.

Result will produce after select session and click distribute button.

Figure 4.9: Supervising page

Figure 4.10 shows the page for list of student with their supervisor for all course.

Coordinator able to print the list by click the print icon.

Figure 4.10: Student-supervisor list

41

Figure 4.11 shows the homepage for student. This page show who his supervisor and

allow student to update profile. Student also can submit their Final year project title and

abstract.

Figure 4.11: Student page

Figure 4.12 shows abstract page where student can update their title and abstract.TF-

IDF applied in this page which every keyword of the abstract is compared with other

abstract. If similarity is 20% and above, the system will show the popup.

Figure 4.12: Abstract analyse page.

42

Figure 4.13 show the homepage for Supervisor. List of student is showing and

supervisor can click “view” button to view abstract of each student that was assigned

by system.

Figure 4.13: Supervisor page.

Figure 4.14 shows the report for student-supervisor list. Coordinator can save or print

this report.

Figure 4.14: Student-supervisor list report.

43

4.2 TESTING

After the system are already complete. It was test using two technique of software

testing which are black box testing and white box testing in order to get respective input

and output for each process.

4.2.1 Black box testing

Module involve this testing are:

i. Login

ii. CRUD Coordinator

iii. CRUD Supervisor

iv. CRUD Student

v. Distribute student to supervisor

vi. Abstract analysis

4.2.2 White box testing

Module involve this testing are:

i. Generate report.

44

4.3 TEST CASES

4.3.1 Login

Table 4.1, Table 4.2 and Table 4.3 show the step, procedure and expected result of test

case for login.

Table 4.1: Test case for Coordinator login

Step Procedure Expected result Pass/Fail

1 Login page Preview page loaded Pass

2 Enter the following details:

Username : CO123

Password : 123

Validation if not fill in the detail Pass

3` Click “Login” button Login successful

Coordinator page display

Pass

Table 4.2: Test case for Student login




Username : 043896

Password : student



Student page display

Pass

Table 4.3: Test case for Supervisor login




Username : ABC123

Password : sv1



Supervisor page display

Pass

45

4.3.2 Coordinator

Table 4.4 and Table 4.5 show step, procedure and expected result of test case for add

list of student and supervisor

Table 4.4: Test case for add list of student


1 Click Student navigation Form to add student Pass


Student ID : 043012

Name : Amirul bin Mohammad

CGPA : 3.65

Gender : Male

Course Code : (choose) ISM SK

PP

Session : 2018/2019

Semester : 6

Phone : 0123445678

Validation if not fill in

the detail

Pass

3 Click “Register” button Message preview

successful or failure

Pass

4 OR

Click “browse” button

Pop up directory folder Pass

5 Select “studentlist.xlsx” then

click “open” button

Pass

6 Click “upload” button Message preview


Pass

Table 4.5: Test case for add list of supervisor


1 Click Supervisor navigation Form to add supervisor Pass


Supervisor ID : DEF456

Name : DR All BIN

MOHAMAD


PP


the detail

Pass

3 Click “Register” button Message preview


Pass

4 OR

Click “browse” button

Pop up directory folder Pass

5 Select “supervisorlist.xlsx” then

click “open” button

Pass

6 Click “upload” button Message preview


Pass

46

Table 4.6 and Table 4.7 show the step, procedure and expected result of test case for

delete list of supervisor and student.

Table 4.6: Test case for delete list of supervisor


1 Click “View Supervisor” button List of supervisor Pass

2 Choose Supervisor

Pass

3 Click “X” icon button Confirmation box:

“Are you sure”

Pass

4 Click “ok” button Message preview


Pass

Table 4.7: Test case for delete list of student


1 Click “View Student” button List of student Pass

2 Choose Student

Pass

3 Click “X” icon button Confirmation box:

“Are you sure”

Pass

4 Click “ok” button Message preview


Pass

Table 4.8 and Table 4.9 show the step, procedure and expected result of test case for

update list of supervisor and student.

Table 4.8: Test case for update list of student


1 Click “View Student” button List of student Pass

2 Choose Student

3 Click “update” icon button Editable form of student


Student ID : 043012


CGPA : 3.65

Gender : Male


PP

Session : 2018/2019

Semester : 6

Phone : 0123445678


the detail

Pass

47

5 Click “Update” button Message preview

updated or not updated

Pass

Table 4.9: Test case for update list of supervisor


1 Click “View Supervisor” button List of supervisor Pass

2 Choose supervisor

3 Click “update” icon button Editable form of

supervisor


Supervisor ID : DEF456

Name : DR ALl BIN

MOHAMAD


PP


the detail

Pass



Pass

4.3.3 Student

Table 4.10 show the step, procedure and expected result of test case for update student

profile.

Table 4.10: Test case for update student profile


1 Click “Update profile” button Editable form of

supervisor

Pass

2 Edit the following details:


Gender : Male

Phone : 0123445678

Password: 960604024345


the detail



Pass

Table 4.11 show the step, procedure and expected result of test case for add abstract.

Table 4.11: Test case for add abstract


1 At Student Hompage Editable form of title

and abstract

Pass

48

2 Edit the following details:

Title : “write you title here”

Abstract :” here your abstract

here”


the detail



Pass

Table 4.12 show the step, procedure and expected result of test case for update

abstract.

Table 4.12: Test case for update abstract


1 Click “abstract” navigation Pass

2 Fill the following details:

Title : “write you title here”

Abstract :” here your abstract

here”


the detail

3 Click “Submit” button Message preview


Pass

4 Refresh page Message preview

similarity of your

abstract

Pass

4.3.4 Supervisor

Table 4.13 show the step, procedure and expected result of test case for view student’s

abstract.

Table 4.13: Test case for view student’s abstract


1 Choose student Pass

2 Click “view” button View the title and

abstract

3 Refresh page Message preview

similarity of the abstract

Pass

49

4.3.5 Distribute student to supervisor

Table 4.14 show the step, procedure and expected result of test case for distribute

student to supervisor.

Table 4.14: Test case for distribute student to supervisor


1 Add Coordinator Homepage

click “supervising” navigation

Generate supervising

page loaded

Pass

2 Select session 2018/2019 Pass

3. Click “Generate” button View the group of

supervisor with student

in table form.

Pass

Table 4.15 show the step, procedure and expected result of test case for generate

report list of supervising.

Table 4.15: Test case for generate report list of supervising


1 Add Coordinator Homepage

click “supervising” navigation

Generate supervising

page loaded

Pass

2 Click “ view supervising”

button

List of supervising Pass

3. Click “Print” icon button Pop up for printing the

report.

Pass

4.4 SUMMARY

This chapter briefly discussed about the implementation of coding, functionality of the

system and testing of the system. In order to make the system more robust and

functioning properly, all the test case is test carefully to make sure it achieved the

intended result. Besides that, the main process modules flow is discussed. The system

functionality had been tested and evaluated

50

CHAPTER 5

CONCLUSION

5.1 DISCUSSION

Generally, this project has been carried out and already follows the objectives

that have explained in Chapter 1. This project has introduced a way to distribute student

to supervisor fairly and analyse student abstract by finding similarity among abstract.

Other than that this project provides an efficient method for distribution and analyse

abstract similarity as well as reduce the time taken. Besides this project contributes to a

more efficient to a more efficient process for assigning student to supervisor and

abstract approval as Coordinator does not have to do manually.

51

5.2 FUTURE WORK

There is little suggestion that can be made to improve the system to be more efficient

in future work. Some suggestion that need to be considered are:

i. Add more functionality to the system. For example abstract with 20%

similarity and below will be approved by the system automatically

ii. Make some task for lecturer. For example lecturer can give mark of FYP

student and student will see the result thru system.

iii. Integration with other module such as monitoring FYP progress and FYP

marking system.

5.3 SUMMARY

Final Year Project Student to Supervisor Distribution and Abstract Text Analysis

System is the system that useful for Coordinator, student and supervisor. Student only

have to upload their abstract and coordinator only have to upload list of supervisor and

list of student into the system as this this system will generate the group of student for

each supervisor and analyse the abstract using technique and method was applied. This

system will reduce the time taken for coordinator in process to assign student to

supervisor and approve abstract by the student.

52

REFERENCES

[1] M.A. Mohamed, AF. Abidin, A.A. Jamal, M.A.M. Amin, A. Rozaimee and

F.A. Wahab, World Applied Sciences Journal 35 (8): 1246-1251, 2017. An

Implementation of Final Year Project Management System: A Case Study at

Universiti Sultan Zainal Abidin. Publications, 2017

[2] Marini Abu Bakar. Norleyza Jailani, Zarina Shukur, Noor Faezah Mohd

Yatim, Final Year Supervision Management System as a Tool for Monitoring

Computer Science Projects. Available online 25 June 2011.

[3] Chun-Hang Leung, Chung-Lun Lai, Tsun-Kit Yuan, Wai-Man Pang, Jeff

K.T. Tang, Wai-Shing Ho, and Tak-Lam Wong, The Development of a Final

Year Project Management System for Information Technology Programmes:

ICTE 2014, CCIS 494, pp. 86–97, 2015. © Springer-Verlag Berlin Heidelberg

2015

[4] Rajaraman, A.; Ullman, J.D. (2011). "Data Mining". Mining of Massive

Datasets (PDF). pp. 1–17.

[5] Duttweiler, M. 2007. Priority Setting Tools: Selected Background and

Information and Techniques. Cornell Cooperative Extension.

[6] Ramos, J. (2003, December). Using tf-idf to determine word relevance in

document queries. In Proceedings of the first instructional conference on

machine learning (Vol. 242, pp. 133-142).

53

APPENDIX A

Table 1: Milestone

Milestone Date Status

Topic discussion and determination Week 1 Completed

Project title proposal Week 2 Completed

Proposal writing-Introduction Week 3 Completed

Proposal writing-Literature review Week 4 & 5 Completed

Proposal progress presentation & evaluation Week 6 Completed

Discussion & correction proposal & proposed

solution methodology

Week 7 Completed

proposed solution methodology (continued) Week 8 Completed

Proof of concept Week 9 Completed

Drafting report of the proposal Week 10 & 11 Completed

Submit draft report to supervisor Week 12 Completed

Seminar presentation Week 13 Completed

Report correction Week 14 Completed

Final report submission Week 15 Completed

54

Table 2: Gantt chart

Activity Week

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

1.Project title

decision and

meeting with

supervisor

2.Project title

registration

3. Discussion and

writing for Chapter

1: Introduction

4. Proposal writing

Chapter 2:

Literature Review

5. Presentation and

evaluation for

proposal project

6.correction of the

proposal

7. Proposed

solution Chapter 3:

Methodology

8. Proof of concept

9. seminar

preparation

10. seminar

presentation and

evaluation

11. Finalising

report of the

proposal

12. final report

submission and

evaluation

Documents

FINAL YEAR PROJECT STUDENT TO SUPERVISOR DISTRIBUTION … · MOHD AZWAN BIN MD SAAD 043896 BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT) WITH HONOURS FACULTY OF INFORMATIC AND