final year project supervising management system … · mohd azwan bin md saad 043896 bachelor of...

FINAL YEAR PROJECT SUPERVISING MANAGEMENT SYSTEM

MOHD AZWAN BIN MD SAAD

043896

BACHELOR OF COMPUTER SCIENCE

SOFTWARE DEVELOPMENT WITH HONOURS

FACULTY OF INFORMATIC AND COMPUTING

UNIVERSITY SULTAN ZAINAL ABIDIN

DECEMBER 2018

i

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. FYP management 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 (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.

ii

TABLE OF CONTENTS

ABSTRACT ................................................................................................................................ i

TABLE OF CONTENTS ........................................................................................................... ii

LIST OF TABLES .................................................................................................................... iv

LIST OF FIGURES ................................................................................................................... v

CHAPTER 1 INTRODUCTION ............................................................................................... 1

1.1 BACKGROUND .............................................................................................................. 1

1.2 PROBLEM STATEMENT .............................................................................................. 3

1.3 OBJECTIVES .................................................................................................................. 3

1.3 SCOPE ............................................................................................................................. 3

1.4 LIMITATION OF WORK ............................................................................................... 4

1.5 EXPECTED OUTCOME ................................................................................................. 4

1.6 REPORT STRUCTURE .................................................................................................. 5

1.7 APPENDIX ...................................................................................................................... 6

CHAPTER 2 LITERATURE REVIEW .................................................................................... 8

2.1 INTRODUCTION ............................................................................................................ 8

2.2 STUDY ON THE AVAILABLE SYSTEM .................................................................... 9

2.2.1 FINAL YEAR PROJECT MANAGEMENT SYSTEM FOR INFORMATION

TECHNOLOGY PROGRAMMES .................................................................................... 9

2.2.2 FINAL YEAR SUPERVISION MANAGEMENT SYSTEM AS A TOOL FOR

MONITORING COMPUTER SCIENCE PROJECTS .................................................... 10

2.2.3 FINALYEAR PROJECT MANAGEMENT SYSTEM. ......................................... 11

2.3 SUMMARY ................................................................................................................... 12

CHAPTER 3 DEVELOPMENT METHODOLOGY .............................................................. 13

3.1 INTRODUCTION .......................................................................................................... 13

3.2 METHODOLOGY IN SYSTEM DEVELOPMENT .................................................... 14

3.2.1 Investigation Phase .................................................................................................. 14

3.2.2 System Analysis Phase ............................................................................................ 14

3.2.3 System Design Phase ............................................................................................... 15

3.2.4 Development and System Implementation Phase ................................................... 15

3.2.5 Support and Operational Phase ................................................................................ 15

3.3 ANALYSIS OF SYSTEM REQUIREMENTS ............................................................. 16

3.3.1 Development Software Requirements ..................................................................... 16

3.3.2 Development Hardware Requirements .................................................................... 16

3.4 FRAMEWORK DESIGN .............................................................................................. 17

3.5 PROCESS MODEL ....................................................................................................... 18

iii

3.5.1 CONTEXT DIAGRAM .......................................................................................... 18

3.5.2 DATA FLOW DIAGRAM LEVEL 0 ..................................................................... 19

3.5.3 ENTITY RELATIONSHIP DIAGRAM ................................................................. 24

3.6 DATABASE DESIGN ................................................................................................... 25

3.7 TECHNIQUE ................................................................................................................. 29

3.7.1 PRIORITY TECHNIQUE ....................................................................................... 29

3.7.2 TERM FREQUENCY INVERSE DOCUMENT FREQUENCY (TF-IDF) .......... 31

3.8 SUMMARY ................................................................................................................... 33

REFERENCES ........................................................................................................................ 34

iv

LIST OF TABLES

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

Programmes ............................................................................................................................... 9

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

Computer Science Projects ...................................................................................................... 10

Table 2.3: Final Year Project Management System. ............................................................... 11

Table 3.1: Development Software Requirements .................................................................... 16

Table 3.2: Development Hardware Requirements ................................................................... 16

Table 3.3: Table Student .......................................................................................................... 25

Table 3.4: Table Supervisor ..................................................................................................... 26

Table 3.5: Table Coordinator ................................................................................................... 26

Table 3.6: Table Course ........................................................................................................... 27

Table 3.7: Table Supervising ................................................................................................... 27

Table 3.8: Table Session .......................................................................................................... 28

Table 3.9: Table Abstract ......................................................................................................... 28

v

LIST OF FIGURES

Figure 3.1 Methodology Phase ................................................................................................ 14

Figure 3.2: Framework Design ................................................................................................ 17

Figure 3.3: Context Diagram ................................................................................................... 18

Figure 3.4: Data Flow Diagram ............................................................................................... 19

Figure 3.5 Data Flow Diagram Level 1 Process 2.0 ................................................................ 21

Figure 3.6: Data Flow Diagram Level 1 Process 3.0 ............................................................... 22



Figure 3.9: Entity Relationship Diagram ................................................................................. 24

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. The FYP normally runs

for one whole semester or in some universities, it is spread over two semesters.

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[1]. 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

2

constraints of limited 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, FYP management 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[4].

In this paper, 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

1.2 PROBLEM STATEMENT

Current system of managing FYP student in traditional ways have contributed

to several problem:

1.2.1 Faculty management needs to specify the supervisor for each student manually

from Microsoft Excel.

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

final project.

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

1.3 OBJECTIVES

1.2.4 To design a system that capable of solving the problems in assigning supervisor

to Final Year Student.

1.2.5 To develop a FYP Management system that works well.

1.2.6 To test the functional of the proposed system..

1.3 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.3.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 also have to manage student’s data and supervisor’s data and set

quota for each supervisor before distribute the student.

4

1.3.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.3.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.4 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.5 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.6 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

1.7 APPENDIX

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

7

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

8

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.

9

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.

2.2.1 FINAL YEAR PROJECT MANAGEMENT SYSTEM FOR

INFORMATION TECHNOLOGY PROGRAMMES

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

Programmes

Author Chun-Hang Leung, Chung-Lun Lai, Tsun-Kit Yuan, Wai-Man Pang,

Jeff K. T. Tang, Wai-Shing Ho, Tak-Lam Wong

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 [3].

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.[3]

Disadvantages 1.Not have allocating supervisor with student function

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

10

2.2.2 FINAL YEAR SUPERVISION MANAGEMENT SYSTEM 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

Author Marini Abu Bakar, Norleyza Jailani, Zarna Shukur, Noor

Faezah Mohd Yatim(UKM)

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.[2]

Advantages 1. The initial prototype consists of three modules, namely

user profile, project monitoring (of software development

and report writing) and appointment setting [2].


2. Cannot compare either the project title already taken or

not.

11

2.2.3 FINALYEAR PROJECT MANAGEMENT SYSTEM.

Table 2.3: Final Year Project Management System.

Author Mohamad Afendee Mohamed. (UniSZA)

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 [1].

Advantages 1. Immediate response, especially when supervisors are

not on campus.

2. Reduce time on update progress and problem.


2. Cannot compare either the project title already taken or

not

12

2.3 SUMMARY

Overall, this chapter describes the study of available systems and analysis

of available systems to assist in the development process of Final Year Project

Supervising Management System.

.

13

CHAPTER 3

DEVELOPMENT 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 :

14

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 before developing a system. In this phase,

discussions with supervisors, interviewing certain parties and seeing relevant

system examples should be done.

3.2.2 System Analysis Phase

This phase can be conducted after the first phase of the initial investigation is

completed. To achieve the objectives contained in the first phase, detailed

definitions need to be made. Project planning must be thoroughly analysed to

ensure system development work can be carried out at the designated time.

Investigation Phase

System Analysis Phase

System Design Phase

Development and System Implementation Phase

Support and Operational Phase

15

3.2.3 System Design Phase

In this phase, some computer software such as Context Diagram (CD), Data

Flow Diagram (DFD) and Entity Relationship Diagram (ERD) are used for

reference purposes to facilitate system development.

3.2.4 Development and System Implementation Phase

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

completed. System interfaces should be provided in this fourth phase. The

HTML, PHP and JavaScript programming languages are used to ensure the

smooth running of the system interface.

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.

16

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 and tools

used to develop the Final Year Project Supervising Management System

3.3.1 Development Software Requirements

Table 3.1: Development Software Requirements

3.3.2 Development Hardware Requirements

Table 3.2: Development Hardware 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.

Hardware Description

Laptop ASUS A450L Series

Pendrive 4 GB

Printer Canon E510 Series

17

3.4 FRAMEWORK DESIGN

Figure 3.2: Framework Design

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

work. Firstly, student and supervisor sing 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.

18

3.5 PROCESS MODEL

3.5.1 CONTEXT DIAGRAM

Figure 3.3: 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. 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.

19

3.5.2 DATA FLOW DIAGRAM LEVEL 0

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

20

can 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.

21

3.5.2.1 DATA FLOW DIAGRAM LEVEL 1 PROCESS 2.0

Figure 3.5 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.

22


Figure 3.6: Data Flow Diagram Level 1 Process 3.0

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.

23




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.

24




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

3.5.3 ENTITY RELATIONSHIP DIAGRAM

Figure 3.9: Entity Relationship Diagram

25

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: Table Student

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.

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

26

Table 3.4: Table Supervisor

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.5: Table Coordinator

The coordinator table is divided into two fields namely the username and

password. The primary key in this table is username.


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

27


course_code varchar(10) latin1_swedish_ci No

course_name varchar(10) latin1_swedish_ci No

Table 3.6: Table Course

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.7: Table Supervising

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.


sv_id Varchar(10) latin1_swedish_ci No


session Varchar(10) latin1_swedish_ci No

28

Table 3.8: Table Session

The session table is divided into three fields namely session, start and end. The

primary key in this table is session.

Table 3.9: Table Abstract

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.


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

29

3.7 TECHNIQUE

3.7.1 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 prority. 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.

30

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.’[5].

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

31

3.7.2 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.

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.

32

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

33

3.8 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

REFERENCES

[1] 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] Final Year Supervision Management System as a Tool for Monitoring

Computer Science Projects. Available online 25 June 2011.

[3] Springer-Verlag Berlin Heidelberg 2015. The Development of a Final Year

Project Management System.

[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).

final year project supervising management system … · mohd azwan bin md saad 043896 bachelor of...

Documents