fyp project guidelines - is
TRANSCRIPT
COLLEGE OF INFORMATION TECHNOLOGY
Handbook for the Supervision of
Final Year Project
CGNB413& CGNB424 for Information
Systems Students
Document No.: COIT/PR/G–2008/2
Prepared by:
IS Department
College of Information Technology
Universiti Tenaga Nasional
Last Updated:
May 2011
2
Table of Contents
1. Introduction to Final Year Project
2. Project Calendar
3. Project 1 (CGNB413/CPRB413) a. Activities
b. Acceptable types of project
c. Passing requirement d. Initial report
e. Deliverables
f. Assessment
g. Report contents
4. Project 2 (CGNB424/CPRB423 / CPRB424)
a. Activities
b. Deliverables
c. Assessment
d. Report contents e. Presentation guidelines
5. Supervisor’s responsibilities
6. Examiner’s responsibilities 7. Presentation panel’s responsibilities
8. Student’s responsibilities
9. Project Grades 10. Remarking Process
11. Procedure for Buying Equipments / Software
12. Policies on Common Issues
13. Forms
a. Forms used for Project 1
b. Forms used for Project 2
Appendix A: IS FYP Assessment System
Appendix B: Project 2 Process Flow
3
Introduction to Final Year Project The final year project is one of the requirements that have to be taken by COIT
students in order to graduate. The project is divided into two phases: Project 1 (CGNB413/CPRB413) and Project 2 (CGNB424/CPRB423/CPRB424). Each of the
projects is taken in one semester and should be taken consecutively. The objectives or rationales of having a final year project for BIT and BCS students are as follows:
1. To apply knowledge/skills acquired from previous classes.
2. To gain experience in system development.
3. To learn new technologies and techniques not taught in class.
It is hoped that by undergoing the development of the final year project, a student will
be more prepared to perform jobs in the real world.
4
Project Calendar
Project 1 (CGNB413/CPRB413)
Tasks Deadline Action
Submission of proposals Before committee meets to vet
projects Supervisors
Vetting through proposals 1 week before class starts Committee
Project briefing 1 or 2 week after class starts Committee
Topic selection 3 weeks after class starts Students
Submission of initial report 4 weeks after class starts Students
Assignment of examiner 7 weeks after class starts Committee and
examiners
Submission of draft report 4 weeks before end of class
Students,
supervisors and examiners
Presentation 2 or 3 weeks before end of class Students, supervisors and
examiners
Submission of final report 1 week before end of class
Students,
supervisors and examiners
Project 2 (CGNB424/CPRB423 / CPRB424)
Tasks Deadline Action
Submission of draft report 2 weeks before final exam Students and
supervisors
Demo project output to supervisor & examiner
4 weeks before final exam
Students,
examiners and supervisors
Presentation and submission
of report 1 week before final exam
Supervisors, examiners and
students
Remark 1. All IS projects must be supervised by an IS supervisor or examined by an IS
lecturer (either one)
2. Supervisor is responsible 70% of the marks allocation and examiner’s portion is
30%, for the Project 1 and Project 2.
5
Project 1 (CGNB413/CPRB413)
Activities
Students taking project 1 are required to do the following:
1. Find and register for a project. The students can either:
a. Pick one of the projects proposed by lecturers based on students’
specialization. For example, students specializing in Software
Engineering are only allowed to take Software Engineering project.
b. Propose your own project.
i. In order to propose a project, the student is required to write a
brief proposal of the project and find a supervisor who is
willing to supervise the project.
ii. The students are only allowed to propose topics based on their
specialization.
iii. The proposal should contain the title of the project, a brief
description on what the student is planning to implement and
the outcome of the project.
2. Submit an initial report. a. The initial report will contain the student’s general plan for the project
and the expected deliverables / outputs for both project 1 and project 2. b. The plan should be agreed upon by both the student and the supervisor.
3. Keep a logbook.
a. The logbook should be written prior to consulting project supervisor.
4. Set a meeting with supervisor every week.
a. Students need to meet their supervisor regularly.
b. During the meeting, the students are supposed to show their logbook
and explain their progress.
c. The supervisor is required to sign the logbook to verify that the
students has come and meet the supervisor for that particular week.
d. Note that a student must come and see her/his supervisor at least five
times throughout the semester, failing of which, the supervisor has the
right to disallow the student from presenting her/his project.
5. Write and submit the draft report a. This report should be the final report from the student’s point of view.
b. Supervisors and examiners would then read the report and give comments.
c. This report will not be graded.
6. Perform a presentation a. Presentation will be done between the student, supervisor and
examiner.
b. Conducted in the supervisor’s room.
6
7. Write and submit the final report
a. This report should include changes suggested by supervisor and
examiner.
b. This report will be graded.
Acceptable types of project
The college has a regulation on the type of project that can be accepted as a final year
project. In particular, only the following types of project can be accepted:
1. Complete system development (with reasonable scope).
2. Studies / research work + small development.
3. Installation and configuration + analysis or small development.
Explanation for each type of project is given below.
System Development
This includes any software or system development on any platform. This platform
includes any PC operating systems (Windows, Linux), mobile devices (PDA,
handphone) and embedded boards. The scope of the project should be big enough for
a final year project, which means that it should take roughly 2 to 3 months for
requirement analysis and design (project 1) and another 2 to 3 months for
development (project 2). Any project with a scope similar to that of a class assignment
will not be accepted. Examples of projects that fall under system development include
information systems, web-based systems, courseware, multimedia applications, and
stand-alone computer software.
Studies / research work + small development
A student doing this type of project is required to perform a detailed study on a certain area related to computer science and information technology. A large portion of the
report will be dedicated for documenting his research / studies. At the end, the student is required to develop a simple application or system related to what he has studied.
For example, a student who chose to perform a study on issues related to network
security can then develop a small application such as a packet sniffer to demonstrate
that the security threats that he read in the literature can actually happen.
Installation and configuration + analysis / small development
Installation and configuration applies to both hardware and software. Hardware
installation and configuration means buying readily available hardware, such as a
video camera, and setting it up to get it to work. Software installation and
configuration means getting software developed by other people, installing and
configuring it to get it to run. A student doing this type of project is required to do
either one of the installation and configuration early on in the project. The student
would then need to use the installed hardware/software to perform meaningful analysis or develop a small application to enhance the usefulness of the installed
hardware/software. For example, the student can choose to install IDS (Intrusion
7
Detection System) software and then use it to analyze network security threats on the
campus network. Another example would be for the student to install and configure a
firewall application on a Linux platform and then write an application that can be
used to easily configure and start the firewall.
If any supervisor or student would like to propose any other types of project, they
should refer to the committee for permission.
It is encouraged that the supervisors and students propose a “good” project. The committee has defined that a “good” project should have some of the following
characteristics:
1. The project involves solving problems of the real world. 2. The project outcome is useful and useable.
3. The project requires performing extra studies on materials not taught in any
courses at UNITEN.
4. The project receives good comments from users.
5. The result of the project is accepted to be published in conferences.
Assessment Criteria Students should adhere to the activities and deliverables stated in the assessment
criteria as stated in Appendix A. The students are responsible to ensure that Project 2 is a continuity of Project 1.
Deliverables At the end of project 1, the students are required to:
1. Submit a report.
2. Perform a presentation.
3. Adhere to the other deliverable as stated in Appendix A.
Logbook
Students are required to keep track of their meetings with supervisors using the log
book. The same log book is to be used for both Project 1 and Project 2.
Assessment
Assessment for Project 1 is done by the supervisor and the examiner. The assessment
would mainly concentrate on the research, analysis and design of the project.
8
Overall Assessment
The general objective of Project 1 is to have the student to perform an academic
research on related topics pertaining to the system to be developed and then design the
system. However, specific objectives may depend on the project and the agreement
between the student and the supervisor. In general, the evaluation of Project I should
cover these three aspects:
a) The process/method of conducting the project. b) The ability of the student to present his/her findings and progress.
c) The documentation of what the student has done so far.
The breakdown of the assessment criteria for Project 1 is as stated in
Appendix A.
Project Proposal (10%)
The project proposal is a write up (about 2 to 3 pages) that contains the plan for the whole project. This proposal should be agreed upon by both the supervisor and the
student. The proposal should contain the following items. 1. Title of the project
2. Brief description of the project 3. Objectives and scopes
4. Expected outcome of the project 5. Gantt Chart
Presentation (20%)
The presentation for Project 1 is done only between the student, supervisor and the
examiner. The presentation should take around 20 to 30 minutes. The place of the
presentation can be in the lecturer’s room or in any other room agreed by the three
parties above. The presentation has the following objectives: a) To evaluate the ability of the student to present what has been done so far.
b) To enable the supervisor and examiner to ask questions and give feedback or
comments regarding the project.
Usually, the presentation is the time when the supervisor and examiner give their final
comment or advice before the final report is submitted.
The marking scheme is as stated in Appendix A.
Final Report (70%)
The content of the report may vary depending on the type of project undertaken by the
student. However, since most of the projects in this department involve system
9
development, the marking scheme for the report would be based on system
development type of project. The marking assessment is as stated in Appendix A.
The report needs to have the following criteria for it to be accepted:
1) Acceptable level of English
2) Proper referencing 3) No plagiarism
4) Proper formatting
Any report that does not meet the above criteria should be rejected. The student then needs to correct the error and resubmit.
Report Contents
The report contents may VARY depending on the project types and methodology
used. However, SAMPLE content for Project 1 report is shown below.
1) Introduction a. Problem statement
b. Project Background c. Objectives
d. Scopes e. Expected benefits
f. Requirements and constraints
2) Research
a. Literature reviews on topics related to the project
b. Review of Research methodology
c. Review on several software development methodology
d. Review of possible development tools and software to be used
e. Review of current systems
f. Review of similar systems
3) Analysis
a. Software development methodology of choice (give reasons for your
choice and explain how do you adapt the methodology to the project
development)
b. Surveys and its results
c. Decide on system functionalities based on the studies made in the research
chapter (or based on the survey results)
d. Decide on development tools and software to be used (give reasons for
your choice)
4) Design
a. Explanation of the proposed system
b. System and algorithm flowcharts
c. System structure chart d. DFD and ERD
10
e. Storyboard
f. Interface design
g. Sketches of graphics to be drawn
5) Conclusion
a. Progress / outcome of project 1
b. Problems encountered c. Planning for project 2
11
Project 2 (CGNB424/CPRB423/CPRB424)
Activities
Project 2 is supposed to be a continuation of project 1. The students are required to pick up from where they left in project 1 and continue till the completion of the
project.
Students doing project 2 are required to do the following:
1. Keep a Log Book.
a. The log book contain the list of (weekly) work scopes agreed between
the supervisor and students
2. Set a weekly meeting with supervisor (or once every two weeks).
a. Students need to meet their supervisor regularly.
b. During the meeting, the students are supposed to show their progress
based on the work scopes listed in the log book.
c. The supervisor is required to sign the log book to verify that the
students has come and meet the supervisor for that particular week.
d. The supervisor and student are required to set the ‘next’ work scope for the student to fulfill.
e. Note that a student must come and see her/his supervisor at least five times throughout the semester, failing of which, the supervisor has the
right to disallow him/her from presenting his project
3. Write and submit the draft report a. This report should be the FINAL report.
b. Supervisor and examiner would then evaluate the report.
4a. In order to obtain a grade of A or A-, the supervisor must nominate the student
for a panel presentataion. The panel will consist of the coordinator, examiner
and one lecturer from the IS dept.
4b.In other cases excluding item 4a,
a. Project presentation will be done by the student in front of the
supervisor and examiner.
b. The presentation details will be set by the supervisor and examiner.
4. Write and submit the final report
a. This report should include changes suggested by supervisor and examiner.
12
Deliverables
At the end of project 2, the students are required to: 1. Produce a system (and/or any other results) as agreed upon with the supervisor
and examiner during project 1. 2. Perform a project presentation.
3. Submit a report. The report should contain the materials from Project 1 plus all the work that has been done in Project 2.
4. Submit a softcopy of the developed project, either in a CD or install it in a
server provided by the College.
Assessment
Assessment for Project 2 is done by the supervisor and examiner. The project is
graded based on the assessment stated in Appendix A.
Report (70%)
Report is to reflect on the existing work from Project 1 and the changes inclusive of
the additional chapters as agreed by both the supervisor and examiner.
Presentation (30%)
The presentation for Project 2 is done only between the student, supervisor and the
examiner. The presentation should take around 30 to 40 minutes. The place of the
presentation can be in the lecturer’s room or in any other room agreed by the three
parties above.
The marking scheme is as stated in Appendix A.
Report Contents
The actual content of the final report may VARY from project to project. However, SAMPLE content for the final report is shown below.
1) Introduction
a. Project Background b. Problem statement
c. Objectives
d. Scopes
e. Expected benefits
f. Requirements and constraints
13
2) Research
a. Literature reviews on topics related to the project
b. Research methodology
c. Review on several software development methodology
d. Review of possible development tools and software to be used
e. Review of current systems f. Review of similar systems
3) Analysis
a. Software development methodology of choice (give reasons for your choice and explain how do you adapt the methodology to the project
development) b. Surveys and its results
c. Decide on system functionalities based on the studies made in the research
chapter (or based on the survey results)
d. Decide on development tools and software to be used (give reasons for
your choice)
4) Design
a. Explanation of the proposed system
b. System and algorithm flowcharts
c. System structure chart
d. DFD and ERD
e. Storyboard
f. Interface design
g. Sketches of graphics to be drawn
5) Implementation a. Description of the developed system
b. Technical details of implementation c. Screenshots of developed system
6) Testing and Verification
a. User comments and feedback
7) Conclusion
a. Results / achievements / findings
b. Problems faced
c. Limitations
d. Future work
Supervisor’s Responsibilities
1. Offer final year project topics in SPMS and verify that the topics offered are reasonable for degree-level final year projects.
14
2. Take a reasonable number of project students every semester and ensure that
sufficient time can be allocated for each student throughout the semester.
3. In the case where students offer their own topics, verify that the topics proposed is
reasonable for degree-level final year projects.
4. Set weekly (or bi-weekly) meeting time for each project student and be available during the allocated time slot.
5. Sign the student’s logbook when he/she comes for weekly meeting. This would
become the proof of the student’s attendance. If a student misses three meetings in a row, the supervisor can send a warning letter to the student’s parents. If two
warning letters have been sent, the supervisor has the right to bar the student from presentation.
6. Remind students of any related deadlines.
7. Remind students to go and discuss with their examiners.
8. Check and correct draft reports submitted by students.
9. Conduct project 1 and project 2 presentation together with student and examiner.
10. Verify that a student’s project has achieved the required standard before allowing
the student to present (project 2).
11. Verify that no plagiarism is committed either in the student’s report or in the application developed by the student or in the result presented by the student.
12. Give marks to each deliverables and other criteria required for evaluation (report,
presentation, etc).
13. Submit project marks into SPMS.
15
Examiner’s Responsibilities 1. Choose to become an examiner to a reasonable number of project students every
semester.
2. Check and correct draft reports submitted by students.
3. Attend project 1 and project 2 presentation together with student and supervisor.
4. Give marks to each deliverables and other criteria required for evaluation (report,
presentation, etc).
5. Submit project marks into SPMS.
Student’s Responsibilities
1. Attend project briefing and workshops.
2. Secure a project (and a supervisor) before the given deadline. Otherwise, drop the
subject.
3. Keep a logbook and write all activities related to the project in the logbook.
4. Come to the meeting set by the supervisor and examiner. Bring the logbook to the meeting.
5. Take note and abide with any deadlines given by the committee.
6. For project 1 and 2, discuss presentation time with both supervisor and examiner.
7. Fulfill and submit all the tasks and deliverables required for the project
(presentation, report, development, etc).
8. If any extension is required, get an approval from BOTH the supervisor and
examiner. Should any one of them disagree, no extension can be given and the
supervisor / examiner have the right to give 0 to any late submission (project 1).
9. Perform any changes or modifications specified by the supervisor on project
deliverables (report, developed system / software).
16
Project Grades At the end of both project 1 and project 2, students will receive a letter grade. The
grades are assigned based on the total marks obtained from the project assessment. The table below shows the grades obtained based on the marks.
Total Marks Grades
85 – 100 A
80 – 84 A-
75 – 79 B+
70 – 74 B
65 – 69 B-
60 – 64 C+
55 – 59 C
50 – 54 C-
45 – 49 D+
40 – 44 D
0 – 39 E
Even though the grade is given based on the total marks, the grade should reflect the
quality of the project. In general, the relationship between the quality of the project
and the grade given can be summarized as follows:
Grade Characteristic of the Produced System
A The system works very well and contains some enhancement or added
values
B The system functions as intended
C The major functionalities of the system works, but some features may not be working.
D The system barely meets its objectives and the passing requirement.
E The system does not achieve the intended standard and objectives / The
system presented is not developed by the student / Plagiarism has been
committed.
Supervisors and examiners / chief panel only need to enter their portion of marks into
the system. The system will generate the corresponding letter grade.
A student may get an E grade if: 1) The student commits plagiarism / cheating.
2) The total mark obtained is below 40. 3) The student is given FAIL by the presentation panel (in the case of project 2).
17
Remarking Process If a student is not satisfied with the grade obtained, he/she can ask for a remarking by
going through the registrar’s remarking process (fill in a form, pay RM75, etc). Depending on the cases, different actions may be taken.
For Project 1:
The student has to re-present the presentation portion (20%) to a random panel
selected by the coordinator. Logbook will also be accessed by the panel.
For Project 2:
The student has to re-present the presentation portion (30%) to a random panel
selected by the coordinator. Logbook will also be accessed by the panel.
It is expected that students who developed a system / application wrote the codes
himself / herself. The students should be able to explain how their system / application
and the codes work. However, in case where the student fails to prove that the system or application is his / her own work (i.e. does not able to explain the coding or lack of
understanding on the system / software being implemented) this student is considered as cheating and would then be charged as having committed plagiarism. In this case,
the student CANNOT request for remarking.
18
Appeal Process Students who fail project 2 presentation due to plagiarism, may submit an appeal
letter to the Dean of COIT. This appeal is to be made the if the student does not agree to the decision from the supervisor or examiner that he or she has committed
plagiarism, an investigation committee will be formed to investigate this matter. The student, the supervisor and the examiner will be called by this committee to obtain
information from all the relevant parties. The investigation committee will then decide
whether plagiarism has really taken place. If there is no case of plagiarism, the student
would then be allowed to request for remarking. However, if the investigation
committee found out that the student has been lying about his act of plagiarism, the
investigation committee can suggest for further disciplinary action to be taken against
the student.
19
Procedure for Buying Equipment / Software
Each student is allocated RM 400 that can be used to purchase equipment or software required to conduct the project. The procedure to do the purchasing is as follows:
1. The student should go and see one of the COIT lab technicians. 2. Fill in the required form.
3. Bring the form to the supervisor so that the supervisor can verify the item(s) to
be purchased by signing and stamping on the form.
4. Bring the form back to the lab technician.
5. The technician will buy the item(s) and give the item(s) to the student.
The whole process may take a few days or weeks, depending on the items purchased.
In general, any items below RM 400 can be purchased. However, the allocated money
CANNOT be used to purchase the following:
1. Pirated software.
2. Books.
3. Software that is already available in the college.
Bear in mind that all the items bought belong to the college. After the student has
finished with the project, all items should be returned to the lab.
20
Policies on Common Issues 1. If a student can not complete project 1 by the given deadline, the supervisor may
give an extension to the student. The student will then be given a BS and extra time is given to the student to complete the project until the first week of the
following semester. Failure to complete the project by this time may cause the student to get an E straight away. Note that the supervisor has the right NOT to
grant any extension to the student if the supervisor thinks that the student does
not deserve any extension.
2. If a student can not complete project 2 by the given deadline, the supervisor may
give an extension to the student. The student will then be given a BS and extra
time is given to the student to complete the project until the end of the following
semester. Failure to complete the project by this time may cause the student to get
an E straight away. Note that the supervisor has the right NOT to grant any
extension to the student if the supervisor thinks that the student does not deserve
any extension.
3. The deadline for handing in draft report and final report must be followed strictly.
In the case where a student needs an extension for report submission, the student
needs to ask permission from both the supervisor and also the examiner
(project 1). If the student hands in the report later than the given deadline without asking permission, both the supervisor and examiner have the right to give zero.
4. If a student fails to attend the presentation session allocated for him/her, the
student will be automatically given an E grade unless the student has a very valid reason for not showing up (MC, etc). Even then, the MC or any related letter
should be submitted to the supervisor and the committee within 3 days of the
scheduled presentation day. In the case where there is a valid reason, the student
will be scheduled for another presentation as soon as possible by the project
coordinator. The student will then need to present his/her project in front of a
panel appointed by the final year project committee.
5. The student is allowed to change his/her project title in the middle of project 1
with the permission of the supervisor. However, changing project title during project 2 is NOT allowed.
6. Students are not allowed to change supervisor except with the permission from
project coordinator.
7. If a student is caught cheating in their project, the supervisor and the committee
has the right to give an E to the project. There are a number of acts that can be
considered cheating. Among them are:
a) Asking somebody else to write the program.
b) Copying other people’s report / report.
c) Plagiarism in project report / report.
d) Faking the survey or questionnaires results.
8. In the case where the supervisor suddenly become unavailable (maternity leave, study leave, warded, pass away), the student should request to the committee to
21
find another supervisor. However, in the case where the absence can be planned, it
is advisable that the student and supervisor try to find a replacement in advance.
The committee, however, still needs to be informed.
9. In the case where there are major discrepancies between the marks given by the
supervisor and the marks given by the examiner or presentation panels, the
committee has the right to re-evaluate the project.
10. The committee has the right to override the grade of any project.
22
Forms Used for Project 1 The following forms are used in project 1 assessment:
1. Project 1 evaluation form (overall evaluation)
• To be filled in by the supervisor
2. Project 1 presentation form
• To be filled in by the supervisor and the examiner
3. Report evaluation form
• To be filled in by the supervisor and the examiner
23
College of Information Technology
Universiti Tenaga Nasional
Evaluation Form for Project I
Student Name
Student ID
Supervisor
Examiner
Project Title
Evaluation
Aspects
Full
Marks
Description Marks Obtained
Supervisor
(70%)
Examiner
(30%)
Report 70 Total mark for report
Presentation 20 Marks given by during the
presentation session.
Miscellaneous 10 It may include effort taken,
level of project difficulty, etc.
Total (Out of 100)
Marks Distribution (70%: 30%)
Final Marks
Letter Grade
Date: Signature: Supervisor / Examiner
(Please circle)
24
College of Information Technology
Universiti Tenaga Nasional
Evaluation Form
Project 1 Presentation
Student Name
Student ID
Supervisor
Project Title
Evaluation
Aspects
Full
Marks
Description Marks
Obtained
Introduction 3 The student is supposed to make the
audiences understand what the project is all about and what is it that the student is
trying to solve/achieve.
Research 6 The student needs to present a review of the research that has been performed.
Proposed solution 6 The student needs to present the proposed
solution or the proposed system to be
implemented in Project 2.
Fluency,
confidence and
entertainment value
3 This evaluates the presentation style of
the student.
Presentation
material organization
2 This evaluates the appropriateness and
the organization of the presentation material prepared by the student.
Total (Out of 20)
Date: Signature:
Supervisor / Examiner (Please circle)
25
College of Information Technology Universiti Tenaga Nasional
Evaluation Form Final Report for Project 1
Student Name
Student ID
Project Title
Evaluation Aspects Full Marks
Description Date Completed*
Marks Obtained
Proposal & Timeline 3 weeks after start of semester
5 Students create a proposal that explain briefly about the system to
be developed.
Initial Report
4 weeks after start of semester
5 Student states clearly the
objectives to be achieved at the
end of the project and the scopes of the project.
Chapter 1: Introduction
5 Student explains the background
of the project and gives a description introduction on the
system that is to be developed.
Chapter 2: Literature Review
15 Student presents the information that has been obtained through
his/her research. The research can be in the form of literature review,
surveys, comparisons with existing systems, etc.
Chapter 3: Research Methodology
10 Student performs his/her own
analysis on matters related to the
project. These matters may include the choice of
methodology, algorithms to be used, etc.
Chapter 4: Analysis & Design
15 Student presents the design of the system to be developed. The student may also present his/her
own method or algorithm.
Content/Interface/Process/Database Design
Format, language, clarity, continuity of chapters, tidiness,
etc.
Chapter 5: Project Outcome
10 Students presents the outcome or
final deliverables of Project 1.
Chapter 6: Conclusion
5 The student needs to summarize the project and gives his/her own
comments regarding the progress of the project.
Total (Out of 70)
Please make sure that the report fulfills the following requirements:
Acceptable level of English Proper formatting
There is no plagiarism Proper referencing
Any project that does not meet the four compulsory requirements above should be rejected. The student would then need to correct the error and resubmit.
26
Lecturer’s Name: ______________________
Supervisor / Examiner (Circle one)
Date: ____________________
Signature: _______________________
*Supervisor must record the date of each completed milestones.
27
Forms Used for Project 2 The following forms are used in project 2 assessment:
1. Project 2 evaluation form (overall evaluation)
• To be filled in by the supervisor
2. Project 2 presentation form
• To be filled in by the presentation panels
3. Report evaluation form
• To be filled in by the supervisor
28
College of Information Technology
Universiti Tenaga Nasional
Evaluation Form for Project II
Student Name
Student ID
Supervisor
Examiner
Project Title
Evaluation
Aspects
Full
Marks
Description Marks Obtained
Supervisor
(70%)
Examiner
(30%)
Report 70 Total mark for report
Presentation 30 Marks given by during
the presentation session.
Total (Out of 100)
Marks Distribution (70%: 30%)
Final Marks
Letter Grade
Date: Signature:
Supervisor / Examiner
(Please circle)
29
College of Information Technology
Universiti Tenaga Nasional
Evaluation Form
Project 2 Presentations
Student Name
Student ID
Supervisor
Project Title
Evaluation Aspects Full
Marks
Description Marks
Obtained
Introduction 3 The student is supposed to make the audiences
understand what the project is all about and what
is it that the student is trying to solve/achieve.
Design 2 The student is supposed to show his/her approach
to the project and present his/her solution.
Result 3 The student is supposed to show the outcome of
his/her project and specify whether the project has
achieved the target set earlier during project 1. If
the student cannot achieve the target, he/she needs
to give reason(s) for the failure.
Presentation Style 2 Proper attire, presentation style, etc.
Demo 15 Student needs to show a demo of his/her system or
project outcome.
Project Quality 5 How do you rate the quality of this project? The
quality can be evaluated from either one of these
aspects:
1. Difficulty level: How difficult is the project?
2. High technical contents: The student need to
go into an in-depth study of a technical
material not taught in detail in any of the
courses here at UNITEN.
Total (Out of 30)
Tick one of the following:
This is definitely an A project Pass FAIL
30
College of Information Technology Universiti Tenaga Nasional
Evaluation Form Final Report
Student Name
Student ID
Project Title
Evaluation Aspects Full Marks
Description Date Completed*
Marks Obtained
Preparation of development platform
5 Student prepares the project development platforms.
Database and dummy
data inserted,
web site content prepared, etc
2 weeks after start of
semester
15 Student prepares databases and inserts
dummy data to it, prepares content of
website.
Basic interface ready, main functions' codes
working, etc
2.5 months after start
of semester
15 Student prepares the basic interface for the system, and the codes for the main functions
are working.
Furnished interface completed
(colour scheme, font,
graphics, etc)
1 month before end of
semester
15 Student has completed all interfaces of the system.
Test plan prepared, test users selected
5 Student must also explain any testing that was done and the result of the testing.
Test conducted, test results
documented
10
Chapter 7: Conclusion
5 Student presents the outcome of the project
(the resulting system).
Total (Out of 70)
Please make sure that the report fulfills the following requirements: Acceptable level of English Proper formatting
There is no plagiarism Proper referencing
Any project that does not meet the four compulsory requirements above should be rejected. The student would
then need to correct the error and resubmit.
Lecturer’s Name: ______________________
31
Supervisor / Examiner (Circle one)
Date: ____________________
Signature: _______________________
*Supervisor must record the date of each completed milestones.
32
Appendix B: Project 2 Process Flow
Begin
Student is
allowed to
present?
Grade = E
Project meets
passing
requirement?Grade = E
Student able to
explain code?Grade = E
Grade = P
Student satisfied
with final grade?
Apply for
remarking
Student satisfied
with grade?
Apply for
remarking
Project meets
passing
requirement?
Student satisfied
with grade?
Send appeal letter
to the College
Investigation by
investigation panel
Appeal
succeed?
Final grade
submitted
End
Submit name to
HEP for further
disciplinary action
A new panel will be
appointed.
New presentation
marks will be given.
Project cannot be
improved.
Can only be done if
the student has not
applied for remarking
before.
Only the thesis will be
remarked.
A new examiner will
be appointed.
NO
YES
YES
NO
NO
YES
YES
NO
YES
YES
NO
NO
YES
NO
YES
NO
Perform
presentation and
submit report