ABSTRACT - greenskill.netgreenskill.net/suhailan/fyp/report/037731.pdf · ABSTRACT As a student, working in group is one of learning style that student need to be learn. However,

1

ABSTRACT

As a student, working in group is one of learning style that student need to be learn.

However, choosing a suitable group members is an important aspect to make sure that all the

members in group can working together without any problem. Besides that, selecting a team

leader also an important aspect to make sure that the group working with planning. There are

certain criteria(s) that need to be followed. These criteria(s) are important to get the best leader

among the group members. The main objective of this system is to help student find best leader

among group members. By using this system, finding the best leader are more accurate. Student

themselves will fill the data. Hopefully that this system will help student get the best leader for

their group.

2

ABSTRAK

Sebagai seorang pelajar, bekerja dalam kumpulan merupakan salah satu cara

pembelajaran yang perlu dikuasai. Bagaimanapun, pemilihan ahli kumpulan merupakan aspek

penting bagi memastikan semua ahli dalam kumpulan tersebut dapat bekerjasama tanpa

sebarang masalah. Selain itu, pemilihan ketua bagi kumpulan tersebut juga merupakan aspek

penting untuk memastikan ahli kumpulan bekerja mengikut perancangan. Terdapat beberapa

kriteria penting yang perlu dititikberatkan dalam membuat pemilihan ketua. Kriteria-kriteria

ini penting untuk mendapatkan ketua yang terbaik dalam kalangan ahli kumpulan. Objektif

utama sistem ini adalah membantu pelajar mencari ketua yang terbaik dalam kalangan ahli

kumpulan mereka. Pemilihan ketua berdasarkan sistem ini dapat memberi keputusan yang

tepat. Sistem ini membenarkan pelajar sendiri yang mengisi data mengenai diri mereka.

Harapan semoga sistem ini dapat membantu pelajar mencari ketua yang terbaik dalam kalangan

ahli kumpulan tersebut.

3

CHAPTER 1

INTRODUCTION

1.1 Background

University life will teach student how to working in group. Student have to work

in group with variety types of people and it is challenging task because student have to

work with differences of background among the team members. Therefore, teamwork

problem can be the main factor that lead to project failure (Humphrey, 2006) (Marques,

Ochoa, 2014). Selecting the right team members in team especially the team leader is

central to team success. Thus, selecting the team leader is the first task to ensure the

successful of the team performance (Rovira, Ozgen, Medir, Tous, Alabart, 2012).

Team Leader Selection System using Analytic Hierarchy Process (AHP) is a

system that help student to find the best leader to conduct the team based on certain

criteria. Criteria that involved in this Team Leader Selection System are personality

type, academic achievement, teamwork experience and previous programming grade.

AHP are chosen because it able to achieve high accuracy in dealing with selection

process.

4

1.2 Problem statement

After group formation, each group have to find their team leader to make sure

that whole team member working smoothly. Choosing a good team leader is important

because team leader playing an important role in conducting the team and all the

member. Therefore, it is important to choose the best team leader to ensure team

successful team performance.

1.3 Objective

The aim of this project is to find the best team leader based on certain criteria.

The objectives are:

i. To design web based system that can help student to find team leader.

ii. To develop web based system that using AHP technique that accurate in

dealing with selection process.

iii. To test and maintain the usability of the system in order to help student

to make a decision

1.4 Scope of work

The main objective of this project is to help student to find or get the best leader

for their team and the selection task session can be done by using web based system.

For the scope, it can be divided in two; user scope and system scope.

i. User scope: main user that use this system are admin, lecturer and

student. For admin, they can login, register user, manage subject,

manage course, manage semester and prepare question. While for

lecturer, they can manage their profile and generate result based on

selection criteria and student can login, manage their profile, answer

question and get the result

5

ii. System scope: the system are able to give result which candidate are

suitable to be a team leader based on selection criteria that generate by

lecturer. Student can get the result only with answer the question given.

1.5 Project goal

The project goal is to design web based system that can help student to find the

best team leader.

1.6 Limitation of work

There are two things that involve in determining the group, team formation and

selecting team leader. This project only focusing on the selecting the team leader based

on existing team.

6

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

The aim of this project is to develop web based system that can help student to make a

decision using AHP. This chapter will discuss about the basic concept of selecting team leader

using decision making, AHP. In this chapter too, will discuss more about criteria used to

achieve the goal. Besides that, some related or existing research will be discuss in this chapter.

2.2 Motivation of the study

The use of web based decision making is increasing nowadays because of various type

technique are available to be use. One of the most popular technique of Multi Criteria Decision

Making (MCDM) is Analytic Hierarchy Process (AHP) technique (Dalalah, Al-Oqla,

Hayajneh, 2010). AHP most widely used technique in decision making due to accuracy,

simplicity, theoretical robustness, ability to handle both quantitative and qualitative criteria and

more important ability to measure the consistency of judgment of respondent (Khatrouch,

Boujelbene, Kermad, Elmehamedi, 2014) (Jain, Rao, 2013) (Zendeh, Aali, 2011).

7

2.3 Criteria in selecting the team leader.

2.3.1 Personality

In the past research, personality types have a high impact on team

performance (Acuna, Gomez, Juristo, 2009) (Capretz, Ahmed, 2010) (Omar,

Abdullah, 2010). (Omar, Abdullah, Husin, 2010) added that personality types

plays an important role in team performance.

Expert believed that personality types is four times more important than

academic achievement, three times more important that teamwork experience

and seven times more important than previous programming grade (Mazni,

Zahraa, Mazida, Fauziah, Azman, Haslina, Norida, 2015).

2.3.2 Academic achievement

In order to find the team leader, academic achievement is the one of

criteria that need to be measure. Expert also believed that academic achievement

three times more important that previous programming grade (Mazni, Zahraa,

Mazida, Fauziah, Azman, Haslina, Norida, 2015).

Moreover academic achievement also playing an important role to

determine team performance (Omar, Abdullah, Husin, 2011).

2.3.3 Teamwork experience

Teamwork experience also have an important effect on team

performance (Rutherfoord, 2006) (Chen, Lin, 2004) (Antoniadis, 2012). (Chen,

Lin, 2004) added that teams with more experienced member perform better than

teams that have member with less experienced. Furthermore, expert conclude

that teamwork experience is three times more important than academic

achievement and five times more important than previous programming grade

(Mazni, Zahraa, Mazida, Fauziah, Azman, Haslina, Norida, 2015).

8

2.3.4 Previous programming grade

Previous programming grade is last criteria that need to be measure in

selecting team leader. Good in programming also an important criteria

especially for programming subject and information technology student.

(Tadayor, 2004) said that selection of the members in teams for

programming class must have strong result in programming subject.

2.4. Analytic Hierarchy Process (AHP)

Analytic Hierarchy Process (AHP) is a multi-criteria decision making approaches that

introduced by Thomas L. Saaty (1977,1994). AHP is the most popular technique of Multi

Criteria Decision Making (MCDM). AHP also powerful and flexible multi-criteria decision

making tool for complex problem where both qualitative and quantitative aspects need to be

considered (Bevilacquaa & Bragliab, 2000). AHP allows better, easier and more efficient

identification of selection criteria, their weighting and analysis (Akhtar).

The problem is being represented in hierarchical. The overall objectives are located at

the top of hierarchy and at the bottom is the decision alternatives. In between the main

objectives and decision alternatives is the related attribute of the decision problems such as

selection criteria. The complexity of the criteria will determine the level of hierarchy.

Figure 2.1

9

The goal of using AHP is student ability to be a leader. Step in AHP are:

I. Decomposing

II. Weighting

III. Evaluating

IV. Selecting

10

CHAPTER 3

METHODOLOGY

3.1 Introduction

Methodology can be defined as a particular procedure or set of procedure that use to

complete the project. This chapter would cover the details of explanation about what type

of methodology used to complete this project. The methodology is used to ensure that the

project can fulfil the objective also to make sure the system can be accomplished

successfully.

3.2 Project methodology

Methodology that used to develop Team Leader Selection System is Waterfall

Methodology. Figure 3.1 below show the waterfall model. Waterfall model follows six

main phases which are requirement gathering and analysis, system design, implementation,

integration and testing, deployment of system and maintenance.

Figure 3.1

11

3.2.1 Requirement gathering and analysis

The purpose of this phase is to determine the project’s main goal and how the

overall of Team Leader Selection System can be function. All the information can be

taken by reading the research paper. In this phase, analysis of user requirement is

carried out. Identified the main objective and scope of user for Team Leader Selection

System also be done in this phase. All the possible requirement of the system are

captured in this phase.

3.2.2 System design

All the requirement from the requirement gathering and analysis phase will be

implement in this phase and design of the system is prepared. In this phase also helps

in defining overall system architecture. This is the plan of how the system would like

and how the system will work. In this system phase, flow logical data such as entity

relationship diagram (erd), data flow diagram (dfd) and context diagram.

3.2.2.1 Context diagram

Figure 3.2 shows context diagram for Team Leader Selection System includes

3 main entity which are admin, lecturer and student. These entities are required to login

to the system first before they can access the system. Once they are successfully login

to the system, they will redirect to homepage and from the homepage, they can continue

other process. Admin responsible to manage user and questionnaire survey while

lecturer and student can update their profile and view analysis of result in selecting team

leader. Student also have to answer the questionnaire survey prepared by admin.

12

Fig

ure

3.2

13

3.2.2.2 Data flow diagram

Data Flow Diagram (DFD) is a process that user can do while enter the system.

3.2.2.2.1 Data flow diagram Level 0

For admin, there are five (5) major processes which are register user, question

survey, manage semester, manage subject and manage course. The structure of DFD

Level 0 for admin as shown in figure 3.3

Figure 3.3: DFD Level 0 (Admin)

14

For lecturer, there are four (4) major processes which are manage profile,

manage subject teaching, team leader selection and analysis of leader performance. The

structure of DFD level 0 (lecturer) as shown in figure 3.4.

Figure 3.4: DFD Level 0 (Lecturer)

15

While for student, there are six (6) processes which are manage profile,

personality type survey, teamwork experience survey, manage subject register,

programming grade survey and academic achievement. Structure of DFD Level 0 for

student as shown in figure 3.5

Figure 3.5: DFD Level 0 (Student)

16

3.2.2.2.2 Data flow diagram Level 1

Data flow diagram (DFD) Level 1 show how the system is divided in sub-

processes which deals with one or more of the data flows.

3.2.2.2.2.1 User registration process

Figure 3.6 shows Data Flow Diagram Level 1 for user registration process.

Admin can add or delete lecturer and student. Lecturer and student only can

view and update their details.

Figure 3.6: DFD Level 1 for User Registration Process.

17

3.2.2.2.2.2 Manage semester

Figure 3.7 below show Data Flow Diagram Level 1 for process manage

semester. Admin can add new semester, view all semester, update semester,

delete semester, update current semester and view current semester. All the

question will be stored in semester and current_semester database.

Figure 3.7: DFD Level 1 for Manage Semester

18

3.2.2.2.2.3 Manage course

Figure 3.8 shows Data Flow Diagram Level 1 for manage course. Admin can

add new course, view all course, update course and delete course. All the course data

will be stored in course.

Figure 3.8: DFD Level 1 for Manage Course.

19

3.2.2.2.2.4 Manage subject

Figure 3.9 shows the Data Flow Diagram Level 1 for manage subject. Admin

can add new subject, view subject, update subject and delete. All subject will be stored

in data store subject. Lecturer can view list of subject, add new teaching subject and

delete teaching subject and teaching subject will be stored in lecturer subject data store.

Student can view list of subject, add new subject registered and delete subject

registered. Subject registered will be stored in student subject data store.

Figure 3.9: DFD Level 1 for Manage Subject

20

3.2.2.2.2.5 Manage question survey

Figure 3.10 shows the Data Flow Diagram Level 1 for manage question

survey. Admin can add, view, update, and delete personality question and

teamwork experience question. All the data will be stored in personality type

question and teamwork experience question data store.

Figure 3.10: DFD Level 1 for Question Survey.

21

3.2.2.2.2.6 Team leader selection

Figure 3.11 shows the Data Flow Diagram Level 1 for team leader selection.

Lecturer can generate team leader and view. To generate team leader, TLSS will

collect data from student, personality type, teamwork experience, programming

grade, academic achievement (CGPA) and lecturer subject and calculate data

from all the table.

Figure 3.11: Data Flow Diagram for Team Leader Selection

22

3.2.2.2.2.7 Analysis of leader performance (Personality type)

Figure 3.12 shows the Data Flow Diagram Level 1 for analysis leader

(personality type). Student can answer the personality type survey and view

their personality type. Lecturer can view student personality type to their

personality type.

Figure 3.12: DFD Level 1 for Personality Type.

23

3.2.2.2.2.8 Analysis of leader performance (Teamwork experience)

Figure 3.13 shows the Data Flow Diagram Level 1 for analysis leader

(teamwork experience). Student can answer the teamwork experience survey.

Lecturer can view student teamwork experience.

Figure 3.13: DFD Level 1 for Teamwork Experience

24

3.2.2.2.2.9 Manage programming grade

Figure 3.14 shows the Data Flow Diagram Level 1 for programming grade.

In this process, student just need to give their latest programming grade. In this

process also, student can add and view their programming grade. All the data

will be stored in programming grade data store.

Figure 3.14: DFD Level 1 for Programming Grade

3.2.2.2.2.10 Manage academic achievement (CGPA)

Figure 3.15 shows the Data Flow Diagram Level 1 for academic

achievement (CGPA). In this process, student just need to give their latest

CGPA. In this process also, student can add and view their CGPA. All the data

will be stored in CGPA data store.

Figure 3.15: DFD Level 1 for Academic Achievement

(CGPA)

25

3.2.2.3 Entity relationship diagram

Entity Relationship Diagram (ERD) for Team Leader Selection System as

shown in figure 3.16 consists of fifteen (15) entities which are admin, lecturer, student,

course, subject, subject_lecturer, subject_student, semester, personality, teamwork

experience, cgpa, programming_grade, personality_ques, teamwork_ques and

current_semester.

Figure 3.16: ERD for Team Leader Selection System

26

3.2.2.4 Data dictionary

Data dictionary are created based on ERD of Team Leader Selection System.

There are fifteen (15) tables involved in storing data in Team Leader Selection System

as shown in Table 3.2.2.4.1 – Table 3.2.2.4.15

Admin

Column Type Null Default PK/FK Comment

Password int (5) No PK

Username varchar (30) No

Table 3.2.2.4.1 : Data dictionary for Admin

Student

Table 3.2.2.4.2 : Data dictionary for Student


student_id varchar (11) No PK

student_name varchar

(200)

No

course_id int (11) No

Password varchar (10) No

phone_Num varchar (12) No

Gender varchar(10) Yes NULL

27

Personality type

Table 3.2.2.4.3 : Data dictionary for Personality Type

Personality type question

Table 3.2.2.4.4 : Data dictionary for Personality Type Question


student_id varchar (11) No FK

semester_id int (11) No FK

personalStatus varchar (30) No


perQues_id int(11) No PK

perQues text No

Answer text No

perCategory varchar

(100)

No

28

Lecturer

Table 3.2.2.4.5 : Data dictionary for Lecturer

Teamwork question

Table 3.2.2.4.6 : Data dictionary for Teamwork Question


lecturer_id varchar(20) No PK

lecturer_Name varchar(200) No

phone_Num varchar(20) No

password varchar(50) No


teamQues_id int(11) No PK

teamQues text No

Answer int(3) No

29

Subject

Table 3.2.2.4.7 : Data dictionary for Subject

Course

Table 3.2.2.4.8 : Data dictionary for Course


subject_id varchar(10) No PK

subject_Name Text No

semester_Id int(11) No FK Table:

semester


course_id varchar(10) No PK

course_Name vachar(100) No

30

Semester

Table 3.2.2.4.9 : Data dictionary for Semester

Teamwork experience

Table 3.2.2.4.10 : Data dictionary for Teamwork Experience


semester_id int(11) No PK

semester_No int(11) No

semesterSession varchar(20) No


student_id varchar(20) No FK Table:

Student

semester_id int(11) No FK Table:

Semester

Answer int(3) No

31

Programming grade

Table 3.2.2.4.11 : Data dictionary for Programming Grade

Academic achievement (CGPA)

Table 3.2.2.4.12 : Data dictionary for Academic Achievement (CGPA)


programGrade_id varchar(7) No PK

programName varchar(50) No

Grade varchar(3) No


cgpa_id Int No PK

student_id varchar(7) No FK

Session varcha(5) No

Cgpa float No

32

Subject lecturer

Table 3.2.2.4.13 : Data dictionary for Subject Lecturer

Subject student

Table 3.2.2.4.14 : Data dictionary for Subject Student


subjectLecturer_id int(11) No PK

subject_id varchar(20) No FK Table:

Subject

lecturer_id varchar(20) No FK Table:

Lecturer

semester_id int(11) No FK Table:

Semester

generate int(11) 0


subjectLecturer_id int(11) No PK

student_id varchar(20) No FK Table:

Student

Leader int(11) Yes NULL FK Table:

Lecturer

33

Current semester

Table 3.2.2.4.15 : Data dictionary for Current Semester


semester_id int(11) No PK

34

3.2

.2.5

Data

Dec

om

posi

tion

This

dat

a is

dat

a dec

om

po

siti

on o

f th

is s

yst

em

:

3.2

.2.5

.1 M

ain

Fig

ure

3.1

7:

Pro

cess

Dec

om

po

siti

on

(M

ain

)

35

3.2

.2.5

.2 A

dm

in

Fig

ure

3.1

8:

Pro

cess

Dec

om

po

siti

on

(A

dm

in)

36

3.2

.2.5

.3 L

ectu

rer

Fig

ure

3.1

9:

Pro

cess

Dec

om

po

siti

on

(L

ectu

rer)

37

3.2

.2.5

.4 S

tud

ent

Fig

ure

3.2

0:

Pro

cess

Dec

om

po

siti

on

(S

tud

ent)

38

3.2.2.6 Interface design

3.2.2.6.1 Login page

Figure 3.21: Login page (Admin)

Figure 3.21 above shows interface login interface for web-based system. This

interface is for admin. If admin enter the wrong username or password, system will

display error message.

39

Figure 3.22: Login page (Lecturer)

Figure 3.22 above shows interface login interface for web-based system.

This interface is for lecturer. If lecturer enter the wrong lecturer id or password,

system will display error message.

40

Figure 3.23: Login page (Student)

Figure 3.23 above shows interface login interface for web-based system.

This interface is for student. If student enter the wrong student id or password,

system will display error message.

41

3.2.2.6.2 Input form design

Figure 3.24: Add user form (Student)

42

Figure 3.25: Update details (Student)

Figure 3.24 and figure 3.25 above shows add new student and update

profile. In figure 3.24, only admin can add new student. If student not register

yet in this system, student have to tell admin to add that student. Admin can

only add student id and default password for student. Other information must

be updated by student themselves at interface in figure 3.25.

43

3.2.2.6.3 Output design

Figure 3.26: Result (Student and lecturer)

Figure 3.24 above shows add new student. In this interface, only admin

can add new student. If student not register yet in this system, student have to

tell admin to add that student. Admin can only add student id and default

password for student. Other information must be updated by student themselves.

44

3.2.3 Implementation

In this implementation phase, all the design need to implement in real system.

Each unit is developed and system design phase is guided for this phase. In this phase,

things that need to be built is real interface, real form and real database by using codes.

All component of the design is implemented as a program module

.

3.2.4 Testing

The implemented system will be tested in this testing phase. Combination of all

modules in entire system is tested for any faults and failures. This is to make sure that

the module of the system work together as in specification. Any error would be fixed

before the system will be released.

3.2.5 Maintenance

The change that occur after the system is handed to user must not affect the

main operation of the system. So that, the system must be developed in a way that it

would adapt to change. Not all problems can be seen directly, but they occur with time

and as other problem they need to be solved.

45

3.3 Software and hardware requirement

Standard requirement would use in software and hardware to develop system.

Each of these requirement is related to each other to make sure that system can be done

smoothly.

3.3.1 Software requirement

List of software that used in this system:

SOFTWARE DESCRIPTION

Microsoft Office 2010 Used for documentation and

presentation

Netbean Platform to coding writing for

develop the system

Mozilla Firefox, Google Chrome Browser used for run the system and

find materials for develop the system

XAMPP Act as local server to run and test the

system

PHPmyAdmin Open source database management

system that uses to store the data of

the system

TABLE 3.3.1 : LIST OF SOFTWARE

3.3.2 Hardware requirement

List of hardware that used in this system:

HARDWARE DESCRIPTION

Laptop (HP) Processor: Intel Core i-7

RAM: 8GB

OS: Window 10

GPU: NVIDIA GeForce

Printer HP Deskjet Ink Advantage 2060

TABLE 3.3.2 : LIST OF HARDWARE

46

3.4 Chapter summary

Methodology is very important in system and application development. There also a

lots of different software development methodology that available and can be used to

develop any kind of application. The right methodology can help the project to be done

according to the specified time. The activities in each phase in the methodology are

explained so that it can be understood easily.

47

References

Mazni O., Zahraa A. A., Mazida A., Fauziah B., Azman Y., Haslina M., Norida M. D. ,

[2015]. Team Formation Model Of Selecting Team Leader: An Analytic Hierarchy Process

(AHP) Approach.

Rovira, N., Ozgen, S., Medir, M., Tous, J., & Alabart, J. R. (2012). Human values in the team

leader selection process. Span. J. Psychol., 15(1), 216–226, 2012.

Acuna, S. T., Gomez, M., & Juristo, N. (2009). How do personality, team processes and task

characteristics relate to job satisfaction and software quality?. Inf. Softw. Technol., 5(3),

627–639.

Akhtar, N. (n.d.). A Study On Brand Name Selection Through Analytic Hierarchy Process.

Bevilacquaa, M., & Bragliab, M. (2000). The analytic hierarchy process applied to

maintenance strategy selection.

Capretz, L. F., & Ahmed, F. (2010). Making sense of software development and personality

types. IT Prof., 12(1), 6–13.

Omar, M., & Abdullah, S. L. S. (2010). Identifying effective software engineering ( SE )

team personality types composition using rough set approach. Proceedings of the 2010

International Symposium on Information Technology (ITSim).

Omar, M., Abdullah, S. L. S., & Hussin, N. M. (2010). Analyzing personality types to predict

team performance. Proceedings of the International Conference on Science and Social

Research (CSSR).

Rutherfoord, R. H. (2006). Using personality inventories to form teams for class projects: a

case study. Proceedings of the 7th conference on Information Technology Education( pp. 9–

14).

Chen, S., & Lin, L. (2004). Modeling team member characteristics for the formation of a

multifunctional team in concurrent engineering. Eng. Manag. IEEE Trans., 51(2), 111–124.

48

Antoniadis, D. N. (20120. Complexity and the process of selecting project team members. J.

Adv. Perform. Inf. Value, 4(1).

Omar, M., Abdullah, S. L. S., & Hussin, N. M. (2011). Developing a team performance

prediction model: A rough sets approach. Informatics Engineering and Information Science,

691–705.

Alkadi, G., & Beaubouef, T. (2008). An experimental group for researching and developing

software. J. Comput. Sci. Coll., 23(6), 104–109.

Tadayon, N. (2004). Software engineering based on the team software process with a real

world project. J. Comput. Sci. Coll., 19(4), 133–142.

Dalalah, D., Al-oqla, F., & Hayajneh, M. (2010). Application of the analytic hierarchy

process (AHP) in multi-criteria analysis of the selection of cranes. Jordan J. Mech. Ind. Eng.,

4(5), 567–578.

Khatrouch, I., Boujelbene, Y., Kermad, L., & Elmehamedi, A. (2014). An integrated case-

based reasoning and AHP method for team selection. Int. Conf. Business, Econ. Mark.

Manag. Res., 2, 13–18.

Jain, R., & Rao, B. (2013). Application of AHP tool for decision making of choice of

technology for extraction of anti-cancer bioactive compounds of plant origin. Int. J. Anal.

Hierarchy Process, 5(1), 3–29,.

Zendeh, A. B., & Aali, S. (2011). An AHP approach for selecting the suitable leadership

style. Int. Proc. Econ. Dev. Res., 25, 20–24.

Gibney, R., & Shang, J. (2007). Decision making in academia: A case of the dean selection

process. Math. Comput Model.

Humphrey, W. S. (2006). TSP Leading a Development Team. Pearson Education. 2006.

Marques, M., & Ochoa, S. F. (2014). Improving teamwork in students software projects.

Proceedings of the 2014 IEEE 27th Conference on Software Engineering Education and

Training (CSEE&T) (pp. 99–108).

Documents

ABSTRACT - greenskill.netgreenskill.net/suhailan/fyp/report/037731.pdf · ABSTRACT As a student, working in group is one of learning style that student need to be learn. However,