Polytechnic FP621 Final Project Project Content

1.
0 INTRODUCTION
The student project is a compulsory course to be taken by level 6 diploma
students. Each student will complete a project based on their study fields.
This project will allow students the opportunity to practice their theoretical
knowledge and to solve problems in the area of information technology.
Students will be assessed on their skills in designing, problems solving, and
performing technical management work.
1.1 Objective
The objective of this project manual is to provide guidelines for students in
the selection of projects topic according to their field of study. This manual
serves as a reference in standardizing the procedures of Project Course for
Diploma students in Information Technology, which is outline by the
Department of Polytechnic Education (DPE). It is for this reasons that DPE has
initiated the development of this Project Guideline for Polytechnic
Information Technology Programme.
1.2 Credit and Duration
Projects are carried out in groups of TWO (2) to FOUR (4) students. Students
can form group of FOUR (4) only if the scope of the project is extensive and
should be delay approved by supervisor concerned. Every member must be
involved in ALL aspects of the project.
1.2.1
Total Credit Hour
The project carries SEVEN (7) credit hours where Level 5 consists of THREE (3)
credit hours and LEVEL 6 is FOUR (4) credit hours. Both courses comprising of
120 hours work.
1.2.2
Project Title Selection Criteria
i. Projects must be developed in accordance with the requirements of

industry (industry driven) or community and can be commercialized if
appropriate.
ii. Projects should have future upgrade values, which can be made to
improve the quality of the project.
iii. All invented projects must be original. Students who are caught to
have plagiarized will be STRICTLY penalized, and result in automatic
failure.
iv. Selection of project title can be done by choosing the title suggested
either by the coordinator, supervisor and student can also choose the
topic themselves, and must be approved by the coordinator or
supervisor.
Page 1 of 74
1.3 Project Scope

Projects should be sufficiently challenging to allow the students to
demonstrate a variety of skills, including the ability to plan their work, perform
the necessary research, manage their time and resources adequately, work
as a team, show initiative and originality and present their work orally and in
writing. Students must develop the project based on their fields of study. Any
project with a similar scope to a class assignment will not be accepted.
Three project types comprising of:
i. Programming
ii. Networking
iii. Game Development
1.3.1
Programming
The project title may ranges from system development areas such as the
database development, stand-alone application, web-based application,
mobile (eg. PDA, handphone), to other relevant ideas. The projects may be
developed on any platform. For example, in web development student can
develop a dynamic web page or a commercial webpage which responds
to the users needs, and provides relevant information by accessing
information in a connected database. For stand-alone application, students
may develop computer software that can work offline, which does not
necessarily require network connection to function.
1.3.2
Networking
The project title may range from computer networking areas such as, the
emerging networking technologies, network application, network security,
wireless technologies, architectures, systems, services to other network and
related area. This may include network simulation, network design, and
network analysis.
In network simulation, student will create a program that models the
behavior of a network either by calculating the interaction between the
different network entities (hosts/routers, data links, packets, etc) using
mathematical formula, or actually capturing and playing back observations
from a production network. The behavior of the network, the various
applications and services the network supports can then be observed in a
test lab; various attributes of the environment can also be modified in a
controlled manner to assess how the network would behave under different
conditions.
In networking analysis student is required to perform a detailed study on a
certain area related to the networking. A large portion of the research will be
dedicated for documenting his studies. For example, a student who chose to
perform a study on issues related to network security can develop a small
Page 2 of 74
application such as a packet sniffer to demonstrate the security threats that

he read in the literature can actually happen in real life.
1.3.3
Game Development
The project titles may range from game development areas such as, standalone game, web-based game, mobile or multimedia game to other
relevant areas. In this project, students will use their programming skills to
develop a video game for commercial, educational and other purposes.
Students will select a theme and general design for their 2D or 3D video
game and use a programming language of their choice to develop their
digital activities by combining graphics, music, sound effects, sprite and pixel
art, modelling, texturing, animation and level design in the project. Focusing
on a central task of modeling a character, students will analyze and build
complex 3D objects piece by piece.
1.4 Procedures
1.4.1
Change project title
Level 6 students are only allowed to change their titles up to week 6 (add
and drop week). (Refer Appendix A). If they change the title they have to
redo all their level 5 assesments.
1.4.2
Attendance
Attendance must be at least 80% , if not students coursework assesments

marks will be disregarded.
1.4.3
Copyright
The Polytechnic shall be the owner of all findings, designs, patents and other
intellectual property rights of the projects.
1.4.4
Plagiarism
Students may discuss with their supervisors should they are in doubt of the
nature of plagiarism. If caught committing plagiarism, strict action will be
taken against the students.
Page 3 of 74
1.5 Responsibility and Roles

1.5.1
Student
Once a the students project is approved, it will be the students responsibility

to consult their supervisors in order to ensure that they understand the
objectives of the project, expectations from the project, the Outcome as
well as the financial limitations. The students should then plan their work
(Gantt Chart or equivalent) to monitor their progress. Students must set up
weekly or regular meetings with their supervisor to seek advice and to review
the progress of their project
1.5.2
Evaluator
The project coordinator appoints the evaluators. The role of the evaluators is
to evaluate the final project presentations.
1.5.3
Coordinator
The main role of project coordinator is to ensure smooth operation of the

final year project overall process.
The coordinators task is to:
a) Identify suitable supervisors for every type of projects.
b) Plan and distribute number of group project per supervisor.
c) Create timetable for all supervisors in charge in project lab.
d) Set a timeframe for regular scheduled progress meeting between
supervisors and student.
e) Brief the students about overall procedures and process.
f) Inform the regulations related to the final year projects:
i. timeframe of every process; choosing supervisor, project registration,
proposal, oral presentation and final project report
ii. Group Formation
iii. project Registration
iv. evaluation
g) Advise students on the preparation of final project report and the oral
presentation.
h) Organize the Final Project Presentation session at the end of the
semester; arrange details of the date and venue, poster, presentation
materials and set up schedule of the presentation panels.
i) Collect the evaluation forms from supervisors and presentation panels,
and work out the final grades.
j) Distribute the manual project and log book.
Page 4 of 74
1.5.4
Supervisor
A project supervisor is an eligible lecturer that has been assigned by Head of

Department and also Project Coordinator to supervise each group project
commencing since the students are in level 5 until level 6. Students may
choose their preferred supervisor using Project Registration Form refer to
Appendix. The role and responsibilities of the project supervisors:
a) guide and encourage the students in conceptualizing their project,
ensures that the project objectives and scopes are relevant to Diploma
in Information Technology (IT) program, valid to qualify as a project,
feasible within the timeframe and have commercial value.
b) follow progress meeting and discussion scheduled (according to the
timetable given) between supervisor and student, and verify the
project progress summary (signature in the log book at least once a
week).
c) monitor students time management (based on weekly schedule given
by project coordinator) and also encourage the students work and
progress soon after the allocation of project titles.
d) provide a guideline on the project requirements to ensure the students
accomplish a project needs.
e) recommend approaches, techniques and methods appropriate to
achieve the projects objectives.
f) provide frequent informal feedback or comments on progress
achieved by the student during weekly project meetings.
g) guide on relevant literature on the topic under study and appropriate
literature sources.
h) guide on writing of final project report according to the standard
format expected.
i) review students project reports draft and provide feedback before
submitting the final report.
Page 5 of 74
2.0 IMPLEMENTATION
2.1 Teaching and Learning Process
Teaching and learning process for project analysis and design consist
of theory and practical. Refer Table 2.1 for teaching and learning
detail.
Level
5
6
Table 2.1 : Teaching and Learning Process

Course
Context Hour
Teaching & Learning
Implementation
Project
30 LECTURE
2 hours Theory (Lecturer)
Analysis & 30 PRACTICAL
2 hours Practical
Design
(Supervisor)
Project
15 LECTURE
1 hour Consultation
45 PRACTICAL
3 hours Practical (Students
complete their project in lab)
2.2 Planner
Refer to Appendix Project Analysis & Design planner.
Page 6 of 74
2.3 Gantt Chart

Level
Week / Activity
Project Briefing.
Select project title and project
supervisor.
Create and compile project
capstone
Guidance & Consultation
Prepare project proposal for
approval
Proposal presentation
Submit proposal report
Analysis presentation and submit
analysis report
Design presentation and submit
design report
Submission of capstone project
Reviewed project and proposal
Guidance & Consultation
1st Demonstration
2nd Demonstration
3rd Demonstration
Submit Final draft
Presentation, and submit
capstone project
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13
W14
W15
Figure 2.1: Project Analysis & Design Gantt Chart
Page 7 of 74
2.4 Project Flow (Level 5)

Flow Chart
Explanation
Outcome
START
Project coordinator briefs level

5 students
Project analysis and design briefing
List of titles published

for students to
choose
Students
propose title
No
Supervisor
agrees
No
Students choose
titles from list
Yes
Yes
Fill in registration form and submit
The projects title may be

proposed by lecturers or
students.
The coordinator or supervisor
will release the list of approved
projects to the students.
Coordinator publishes group title

Discuss project with supervisor
Yes
Amendment
No
Proposal preparation and oral presentation
Yes
Amendment
No
Discuss project with supervisor

and make any amendment
that necessary.
Submit project proposal and
deliver oral presentation to
supervisor.
Project
Proposal
Make any amendment that

necessary.
Submit Project Planning Report
Submit project planning report

to supervisor.
Project Analysis Report and oral

presentation
Submit project analysis report

and delivers oral presentation
to supervisor.
Project Design Report and oral

presentation
Submit capstone project

END
Submit project design report

and deliverers oral
presentation to supervisor.
Submit capstone project to
supervisor.
Project
planning report
Project Analysis
report
Project Design
report
Capstone
Project and
Project
Document
Figure 2.2 : Project Analysis and Design Flow Chart
Page 8 of 74
2.5 Project Flow (Level 6)

Flow Chart
Explanation
Outcome
START
Final year project review
Consultation with supervisor
Discuss the progress of

the project development
with supervision.
Present the development
stage to the supervisor
st
1 Progress demonstration
Yes
Proposal and project

review.
Make any amendment

that necessary
Amendment
No
nd
Present the testing stage

to the supervisor.
Yes
Amendment
Present the
implementation stage to
the supervisor
Amendment
Demontration
3
Make any amendment

that necessary
No
Submit final draft
Final report and presentation
END
Demontration
2
Make any amendment

that necessary
No
rd
Yes
Demontration
1
Submit final draft to

supervisor
Submit final report to the
supervisor. Present final
presentation to
evaluators.
Final draft
report
Final report,
Capstone
Project, User
Manual, End
Product.
Figure 2.3: Project Flow Chart
Page 9 of 74
3.0 ASSESSMENTS
3.1 Type of assessments
All students assessment will be evaluated based on their performance
during implementing the project every week. Log book and presentation are
assessed individually. Type of assessment rubric is divided into the elements
as follows:
Table 3.1 Assessment Level 5 and Level 6
Type of Assessment
Peer Assessment
Presentation
Demonstration
Capstone
1. Proposal
2. Portfolio
3. Logbook
4. Analysis Report
5. Design Report
6. Final Report
7. End Product
8. User Manual
Total
Level 5
Individual
(20%)
(30%)
(10%)
(10%)
(10%)
100%
Group
(15%)
(5%)
-
Level 6
Individual
(10%)
(25%)
(15%)
Group
-
(10%)
100%
(5%)
(20%)
(10%)
(5%)
3.1.1 Peer Assessment

Each student will be assessed by his group members based on:
Table 3.2 : Peer Assessment
Level 5
Knowledge
Level 6
Social skills & Responsibilities
Communication
Leadership
Team work
Management & Entrepreneurial Skills

Leadership
Team work
3.1.2 Presentation
The evaluation for presentation is done individually. It will be assessed by
Supervisor and Invited Assessor. Evaluation mark will be based on soft skill
only. However, student should bring together their report for presentation.
Page 10 of 74
a. Soft Skill Presentation/Demonstration

Level 5 and Level 6
The evaluation will be based on communication, answering ability,
posture and eye contact, enthusiasm, leadership and team work,
material ans added tools, intonation and volumn and self
appearence. It is compulsory to be evaluated in every presentation
which are Proposal Presentation, Analysis Presentation and Design
Presentation.
b. End Product Presentation
The evaluation for end product will be based on achievement of the
objectives, construction and functionality, feasibility, user interface
layout, testing, marketability, originality and creativity.
c. Capstone
Capstone Project is intended to be intensive, active learning
projects, require significant effort in the planning and
implementation, as well as preparation of a substantial final written
work product. The capstone project demonstrates the student's
analytical and interpretive skills. It serves as a summative expression
of what a student has learned in the Diploma program.
Level 5 and Level
The evaluation will be based on Table 3.3.
Table 3.3: Capstone Project
1.
2.
3.
4.
5.
FP521 (Level 5)
Report Proposal
Portfolio
Log book
Report Analysis
Report Design
15%
5%
10%
10%
10%
1.
2.
3.
4.
5.
FP621 (Level 6)
Portfolio
Log book
Final Report
End Product
User Manual
5%
10%
20%
10%
5%
d. Portfolio
A student portfolio is a systematic collection of students work and
related material that depicts a student's activities, accomplishments
and achievements in one or more subjects. The collection should
include evidence of students reflection and self-evaluation,
guidelines for selecting the portfolio contents, and criteria for judging
the quality of the work.
Page 11 of 74
Level 5 and Level 6

The evaluation will be based on the required items and overall
organization including log book.
e. Development Demonstration
Student will demonstrate the project progress to the Supervisor.
Level 6
There are three development demonstrations.
Demonstration 1 Development Demonstration
The evaluation will be based on input development, output
development, user interface development, project application
development, system security and features and progress of project
development.
Demonstration 2 Testing Demonstration
The evaluation will be based on testing plan, unit testing, integration
testing and system testing.
Demonstration 3 Implementation Demonstration
The evaluation will be based on feasibility/functionality,
marketability, objectives achievement, originality and user interface.
3.2 Rubric/Schema
Refer to Appendices for all assessments.
Page 12 of 74
4.0 DOCUMENTATION FORMAT

4.1 Documentation
This section describes the documentation guidelines for manual Final Year Project as
described in previous section. These guidelines must be strictly followed by the final
year students and supervised lecturers.
Table 4.1: Documentation Format Content
No.
1.
Items
Cover Page
2.
Paper and Size
3.
Margin
4.
Typesetting
5.
Figure and
Table
6.
Project
Proposal (Level
5)
Analysis and
Design Report
(Level 5)
Final Project
Report (Level
6)
Paging
References
7.
8.
9.
10.
Description
The cover for all proposal, report and documentation
must contain the project title, author names,
registration number, department name, polytechnic
name and session of study. See Appendix B1.
Use only high quality white A4 70-gram or A4 80-gram
paper, size 210mm X 297mm.
For each page, the margin should be:
Left: 40 mm
Right, Top and Bottom: 25 mm
Header and Footer: 15 mm
1.5 spacing should be use in preparing the proposal,
report and documentation includes for tables or
charts. The typesetting which acceptable is:
Font Type: Times New Roman, Font Size : 12 pt
Chapter Title: Uppercase, Bold, Centered
Chapter Sub-section: Title Case, Bold, Align left
Paragraph: Justify
All tables, charts, figures, and graphs should be
numbered and have titles. Both the number and the
title should be centered either directly above or
directly below the table. The numbering must be
related to the Chapter. For example: Figure 2.4 is the
fourth figure in Chapter 2.
Project Proposal must be written in minimum of 10
pages length. It is only considered text EXCLUDING
front page, appendix and references.
Analysis and Design Report must be written in
maximum of 5 pages length. It is only considered text
EXCLUDING front page, appendix and references.
Final Project Report must be written in not more than
100 pages length. It only considered text EXCLUDING
front page, appendix and references.
Bottom right
Any material taken from another source must be
identified, and a brief reference to its source included
in the text. A complete reference to the document is
included in the reference at the end of student final
Page 13 of 74
11.
Binding
project report. The student must follow The American

Psychological Association (APA) reference citations
style for references in text. See Appendix C1.
Semester 5: All report must be using Black Tape
Binding with white cover.
Semester 6: Report cover must be Buckram
(hardcover), gold printing and 1418 times New
Roman font face. See Appendix B1 and Appendix B2.
4.2 Proposal
Supervisor and coordinator will check students project proposal to determine
whether or not the title and content can be accepted based on the DIP curriculum.
The contents of proposal must include the entire list in Table 4.2.
Table 4.2: Proposal Content
Description
Table of Contents
Each students contribution to the relevant chapters and section should
clearly be indicated by chapter in the proposal.
1.0 Introduction
Briefly explain on introductory project that carried out together current
issue related to project.
2.0 Problem Statement
Briefly explain the problems that arise which made project chosen to be
conducted.
3.0 Objective
List the reason why the project is carried out. It should be in form point
(1....2.3.) and not in paragraph form. The objectives must be specific,
measurable, achievable, relevent and time oriented (using SMART criteria)
4.0 Scope
Student needs to state the scope or project boundaries while doing this
project. This scope will make sure that this project will be done correctly
according to the stated scope.
a. System Scope
This section refers to the coverage of your. The project scope and
concept is also related your target users.
b. Users Scope
Target users are people who can interact with your. However, you may
want to narrow down your target users based on the accessability of
your project.
5.0
Project Significant
Briefly explain the interest of implementing project that carried out.
6.0
Literature Review
Briefly explain about the study that was carried out by other project
existing, related to project field which is on going. It is also make an
explanation on the comparison between current projects with the project
that need to develop. (Can probably stated previous project weakness).
Briefly explains about the technique / method / equipment or technology
Page 14 of 74
that would be taken in implementing project. Students need to make

numerous references comprise whether from books, conference working
paper, journal article, magazine, report or Internet. All source of reference
need to be recorded clearly in text and are stated in index. Minimum of 3
literature review.
7.0 Methodology
Briefly explain the project development model and framework
comprehensively that adopt in systems development or study
implementation. The content can be contained method, technique or
approach which will be used during design and project implementation
phase.
8.0 Conclusion
Briefly summarize the whole chapters that were implemented for the
project.
Reference
References mean a list of works cited from published books, public
document, journals, articles, thesis, magazines, films, videos, slides, maps,
unpublished materials and electronic materials including websites. The
way of written is follow the American Psychological Association (APA)
format. Minimum of 5 references.
Gantt Chart
Create the timeline of the project progress to complete the project.
Page 15 of 74
4.3 Report
Table 4.3: Project Outcome
Outcome
Final
project
report
Portfolio
Description
A final project report is a written documentation of the project
and declare with signature saying the report represent the
students original work and no act of plagiarism is present in
their work.
Project portfolio is a complete record of all the work or
documentation done by the students based on the project
progress. Students need to complete the checklist form for final
submission to the supervisor
User
manual
Documentation that contains major functions performed by

the system and describes the architecture of the system in nontechnical terms.
Final
product
Student must produce a final product in softcopy (CD) to

supervisor and coordinator.
4.3.1 Final Project Report

A final project report is a written documentation of the project and declare with
signature saying the report represent the students original work and no act of
plagiarism is present in their work. The contents of final project report must include the
entire list in the Table 4.4.
Table 4.4: Final Report Content
No.
1.
2.
3.
4.
5.
6.
7.
8.
9.
Description
Cover & Report Backbone
See Appendix.
Plain paper
Title Page
See Appendix.
Declaration of Originality
Student makes declaration on their project originality, with the exclusion of
quotations in the written report. See Appendix.
Approval for Submission
See Appendix
Acknowledgements
See Appendix.
Abstract
An abstract is not same as synopsis or project overview. It must state the
scope project domain, problem statement, the solution, research
methodology and the outcome. Abstract should be a one page summary of
150 300 words and typed in 1.5 line spacing. See Appendix.
Table of Contents
Each students contribution to the relevant chapters and section should
clearly be
indicated by chapter in the project report I. See Appendix.
List of Tables
List of table title with page numbers. The number sequence must follow the
chapter. See Appendix.
Page 16 of 74
10.
11.
12.
13.
14.
15.
List of Figures
Figures include pictures, photograph, painting, graph, cart and map. Same
with table list, the figure must have page number and it is sequence follow the
chapter. See Appendix.
List of Appendices
This page will list all the Appendices in the project. Include all relevant
documentation, source code of system, screen displays, user manual and
Gantt Chart. See Appendix.
Chapter 1 (Introduction)
i. Introduction
Explain on introductory project that carried out together current issue
related to project.
ii. Problem Statement
Explain the problems that arise which made the chosen project is carried
out.
iii. Objective
List the reason why the project is carried out. It should be in form point
(1....2.3.) and not in paragraph form. The objectives must be
measurable and achievable.
iv. Scope
Student needs to state the scope or project boundaries while doing this
project. This scope will make sure that this project will be done correctly
according to the stated scope.
a. System Scope
This section refers to the coverage of your system (area, time, payment,
delivery, cancellation). Student needs to elaborate objectives of project.
b. Users Scope
Target users are people who can interact with your system (e.g: E
Learning: target user: students, lecturers). However, you may want to
narrow down your target users based on the accessability of your
project.
v. Project Significant
Explain the interest of implementing project that carried out.
vi. Conclusion
Summarize the chapter content that were implemented for the project.
Chapter 2 (Literature Review)
Explain about the study that was carried out by other existing project, related
to the project being carried out. Its also provides the comparison between
current projects with the project that needs to be developed. (Can probably
stated project weakness earlier). Minimum of three(3) literature reviews.
It explains the technique / method / equipment or technology that would be
taken in implementing project. Students need to make numerous references
from books, conference working paper, journal article, magazine, report or
Internet. All source of references need to be recorded clearly in the text and
are stated in index.
Chapter 3 (Methodology)
Explain the project development model and framework comprehensively that
adopt systems development or study implementation. The content should of
method, technique or approach which will be used during design and project
implementation phase.
Chapter 4 (Analysis & Design)
Students need to explain and show the detailed project analysis and design
that has been done to complete the project. It includes all system
development diagrams, flowcharts, schematic diagrams and screenshots.
Students need to refer to level 5 for the content of analysis report and design
report .
Page 17 of 74
16.
17.
18.
Chapter 5 (Development and Testing)

Students need to explain the development process and their result of the
project. The testing processes also must be done to verify the functionality of
the project.
Chapter 6 (Suggestion and Conclusion)
Student must make some conclusion about the project and discuss about
importance of the outcome. Students also have to make some suggestion in
order to enhance the project.
Reference
References mean a list of works cited from published books, public document,
journals, articles, thesis, magazines, films, videos, slides, maps, unpublished
materials and electronic materials including websites. The way of written is
follow the APA style format. Refer Appendix.
4.3.2 Project Analysis Report

Table 4.5: Analysis Report Content
Outcome
Analysis
Report
Contents of Analysis Report

- A comprehensive analysis of a particular data using
fact-finding techniques:
1. Interviews
2. Documentation review
3. Observation
4. Sampling
5. Research
Students need to interpret and explain the results or
findings of the project critically to link the achievement of
the project objectives.
- Literature Review (minimum THREE)
Students should explain the theory or writing related to
the projects. This is necessary to obtain background
information and assist students in achieving the
objectives. This would avoid duplication of projects
implemented.
Page 18 of 74
4.3.3 Project Design Report

Table 4.6: Design Report Content
Outcome
Design
Report
Contents of Design Report

Written to introduce the structure of the project that will be
implemented.
1. Logical Design
- Entity Life History
- Relational Data Analysis
- Context Diagram
- Data Flow Diagrams
- Entity Relational Diagrams
Logical designs are according to project background.
2. Physical Design
- Graphical User Interface Design
- Flow chart
- Storyboard
- Task-Flow-Network
Physical designs are according to project background.
4.4 User Manual

User manual is a technical communication document intended to give assistance to
user using a particular system. Most user manual contains both a written guide and
the associated images. Students must include screenshots of how the project should
appear and hardware manuals with clear or simplified diagrams.
4.5 Final Product
Students must produce a final product in hardcopy and softcopy (CD) to supervisor.
a. Hardcopy Binded Final Project Report (1 copy department).
b. Softcopy User Manual, System, Final Project Report and source code of system.
4.6 Log Book
4.6.1 Introduction
The Final Project Log Book is used specifically for writing notes on all the activities and
work done by students throughout the duration of the project. The Log Book is one of
the ways in which the department can identify and assess the attitude, initiative,
achievement of the students project. It is one of a requirement for students to
complete during the project is carried out either work individually or in a team under
supervision of respective supervisors. Therefore, it is important for students to fully utilize
the Log Book and submit to a panel of examiners for evaluation.
Page 19 of 74
4.6.2 Reminder To The Students

1. The Log Book must be handed in to the supervisor to be graded and verified at
least once in every week.
2. Students must bring along their Log Book at every meeting and discussion with
their supervisor so that verification can be done after the session.
3. The Log Book must be handed in to the supervisor with the Final Project Report
for evaluation and grading.
4.6.3 Meeting Duration
The students attendance will be taken during SLT by the superviser as follow:
1. FP521 2 hours theory and 2 hours practical in a week
2. FP621 1 hours theory and 3 hours practical in a week
4.6.4 Log Book Format
Forms and Conditions of the Log Book
1. Students must write down their activities for the whole week during the semester.
2. Supervisor is advisable to comment every task that student has done.
3. The number of words should be not more than 100 words.
Page 20 of 74
POLYTECHNIC XXX
KPT LOGO
JABATAN PENGAJIAN POLITEKNIK
POLYTECHNIC
LOGO
FINAL PROJECT LOG BOOK

DIPLOMA OF INFORMATION TECHNOLOGY (PROGRAMMING)
INFORMATION TECHNOLOGY & COMMUNICATION DEPARTMENT

JABATAN PENGJIAN POLITEKNIK
Page 21 of 74
INFORMATION TECHNOLOGY & COMMUNICATION DEPT.

POLYTECHNIC XXX
KEMENTERIAN PENGAJIAN TINGGI MALAYSIA
STUDENT INFORMATION
Please insert
photograph here
YEAR / SESSION
STUDENT INFORMATION
NAME
REGISTRATION NUMBER
CLASS
COURSE
PHONE
NUMBER
ADDRESS
PROJECT INFORMATION
TITLE
SUPERVISOR
Student Signature,
Page 22 of 74
CONTENTS
1.0
2.0
3.0
4.0
5.0
PAGE
Introduction
Reminder to the Students
Meeting Duration
Format of Log Book
Weekly Activities Report
Page 23 of 74
WEEKLY ACTIVITIES REPORT

Week : 7
Date : 18/03 22/03/2012
Time : 2.00pm
This report has to be written in every week and enclosed detail attachment to support
your report if necessary.
Weekly planning
Weekly achievement
1) Design Order form interfaces

2) Create following tables in Ms Access
database:
a) Order table
b) Customer table
c) Stock table
3) Create tables relationships.
4) Connect Order form and Order table
using PHP and SQL.
Reflective
1) Completed
2) All tasks are completed accept Stock
table still in progress.
3) Completed
4) Unsuccessful.
1) I cant complete item 4 because time limitation

2) I understood how to create table relationship
Supervisors comment:
1) Order form - OK
2) Data group in Order table is not fixed. Please modify where applicable.
3) Please refer to suitable book for the connection above.
Verified by
Supervisors Signature:
Date: 20/07/2012
(Amyzah binti Ahmad)

Figure 4.1: Log Book Example
Page 24 of 74
Table 4.1: Reference List for Book

Basic Format for Books
Author, A. A. (Year of publication).

Title of work: Capital letter also for
subtitle. Location: Publisher.
Note: For "Location," you should always
list the city, but you should also include
the state if the city is unfamiliar or if the
city could be confused with one in
another state.
Edited Book, No Author
Edited Book with an

Author or Authors
A Translation
Note: When you cite a republished work

in your text, it should appear with both
dates: Laplace (1814/1951).
Edition Other Than the

First
Article or Chapter in an
Edited Book
Author, A. A., & Author, B. B. (Year of

publication). Title of chapter. In A. Editor
& B. Editor (Eds.), Title of book (pages of
chapter). Location: Publisher.
Note: When you list the pages of the
chapter or essay in parentheses after
the book title, use "pp." before the
numbers: (pp. 1-21). This abbreviation,
however, does not appear before the
page numbers in periodical references,
except for newspapers.
Multivolume Work
Calfee, R. C., & Valencia, R. R.

(1991). APA guide to preparing
manuscripts for journal
publication. Washington, DC:
American Psychological
Association.
Duncan, G.J., & Brooks-Gunn, J.

(Eds.). (1997). Consequences of
growing up poor. New York:
Russell Sage Foundation
Plath, S. (2000). The unabridged
journals (K.V. Kukil, Ed.). New
York: Anchor.
Laplace, P. S. (1951). A
philosophical essay on
probabilities. (F. W. Truscott & F.
L. Emory, Trans.). New York:
Dover. (Original work published
1814).
Helfer, M.E., Keme, R.S., &
Drugman, R.D. (1997). The
battered child (5th ed.).
Chicago: University of Chicago
Press
Rogoff, B., & Mistry, J. (1985).
Memory development in cultural
context. In M. Pressley & C.
J.Brainerd (Eds.), Cognitive
learning and memory in children
(pp. 117-142). New York:
Springer-Verlag.
Scruton, R. (1996). The eclipse of

listening. The New Criterion,
15(30), 5-13.
Page 25 of 74
5.0 CONCLUSION
5.1 References
Table 5.1: Reference List for Articles in Periodicals
Basic Form
The APA style dictates that authors are named last name followed by initials;
publication year goes between parentheses, followed by a period. The title of the
article is in sentence-case, meaning only the first word and proper nouns in the
title are capitalized. The periodical title is run in title case, and is followed by the
volume number which, with the title, is also italicized or underlined.
Author, A. A., Author, B. B., & Author, C. C. (Year). Title of article. Title of Periodical,
volume number(issue number), pages.
Article in
Journal
Paginated by
Volume
Journals that are paginated by volume

begin with page one in issue one, and
continue numbering in issue two where
issue one ended.
Harlow, H. F. (1983). Fundamentals for

preparing psychology journal articles.
Journal
of
Comparative
and
Physiological Psychology, 55, 893-896.
Article in
Journal
Paginated by
Issue
Journals paginated by issue begin with

page one in every issue. Therefore, the
issue number gets indicated in
parentheses after the volume. The
parentheses and issue number are not
italicized or underlined.
Scruton, R. (1996). The eclipse of

listening. The New Criterion, 15(30), 513.
Article in a
Magazine
Article in a
Newspaper
Letter to the
Editor
Review
Unlike other periodicals, p. or pp.

precedes page numbers for a
newspaper reference in APA style.
Single pages take p., e.g., p. B2;
multiple pages take pp., e.g., pp. B2, B4
or pp. C1, C3-C4.
Henry, W. A., III. (1990, April 9). Making

the grade in today's schools. Time, 135,
28-31.
Schultz, S. (2005, December 28). Calls
made to strengthen state energy
policies. The Country Today, pp. 1A, 2A.
Moller, G. (2002, August). Ripples versus

rumbles [Letter to the editor]. Scientific
American, 287(2), 12.
Baumeister, R. F. (1993). Exposing the
self-knowledge myth [Review of the
book The self-knower: A hero under
control ]. Contemporary Psychology,
38, 466- 467.
Page 26 of 74
Table 5.2: Reference List for Other Print Sources

An Entry in an
Encyclopedia
Work Discussed in
a Secondary
Source
List the source the work was

discussed in:
Coltheart, M., Curtis, B., Atkins, P.,
& Haller, M. (1993). Models of
reading aloud: Dual-route and
parallel-distributed-processing
approaches.
Psychological
Review, 100, 589-608.
NOTE: Give the secondary
source in the references list. In
the text, name the original work,
and give a citation for the
secondary source.
Dissertation
Abstract
Government
Document
Report from a
Private
Organization
Conference
Proceedings
Published
Conference Paper
Bergmann, P. G. (1993). Relativity. In

The new encyclopedia britannica
(Vol. 26, pp. 501-508). Chicago:
Encyclopedia Britannica.
For example, if Seidenberg and
McClelland's work is cited in
Coltheart et al. and you did not read
the original work, list the Coltheart et
al. reference in the References. In the
text, use the following citation:
In Seidenberg and McClelland's
study (as cited in Coltheart, Curtis,
Atkins, & Haller, 1993), ...
Yoshida, Y. (2001). Essays in urban

transportation (Doctoral dissertation,
Boston College, 2001). Dissertation
Abstracts International, 62, 7741A.
National Institute of Mental Health.
(1990). Clinical training in serious
mental illness (DHHS Publication No.
ADM 90-1679). Washington, DC: U.S.
Government Printing Office.
American Psychiatric Association.
(2000). Practice guidelines for the
treatment of patients with eating
disorders (2nd ed.). Washington, D.C.:
Author.
Schnase, J.L., & Cunnius, E.L. (Eds.).
(1995). Proceedings from CSCL '95:
The First International Conference on
Computer Support for Collaborative
Learning. Mahwah, NJ: Erlbaum.
Hasmah Zanuddin,& Azizah Hamzah.
(2007).
International
trade
agreement of intellectual property
rights (TRIPS), copyright issues &
burden to enforce in Malaysia. In
Choi K. Y. (Ed.), Korean studies in
Southeast
Asia:
Strategic
cooperation and development in
research
and
education:
Proceedings of the 2nd International
Conference of the Korean studies
Association of Southeast Asia held on
29 January 1 February 2007 at the
University of Malaya, Kuala Lumpur
(pp.
121-138).
Kuala
Lumpur:
University of Malaya.
Page 27 of 74
Unpublished
Conference Paper
Academic Exercise
/ Thesis
(Unpublished)
Nadaraja Kannan. (2006, Nov). The

economic depression of the 1930s :
Its impact on race relations in the
Federated Malay State. Paper
presented
at the International
Association of Historians of Asia
Conference, Manila, Philippines.
Santini, S. N. (2008). Research
methods for business: A skill building
approach. Unpublished
masters
thesis, University of Malaya, Kuala
Lumpur.
Page 28 of 74
Table 5.3: Reference List for Electronic Sources

Article From an
Online Periodical
/ Databases
Online Scholarly
Journal Article
Online Scholarly
Journal Article
with Printed
Version Available
Article From a
Database
Nonperiodical
Web Document,
Web Page, or
Report
Online articles follow the same

guidelines for printed articles. Include
all information the online host makes
available, including an issue number in
parentheses.
Bernstein, M. (2002). 10 tips on writing

the living Web. A List Apart: For
People Who Make Websites, 149.
Retrieved
2
May
2006,
from
http://www.alistapart.com/articles/ci
te living
Author, A. A., & Author, B. B. (Date of

publication). Title of article. Title of
Online
Periodical,
volume
number(issue number if available).
Retrieved day, month, year, from
http://www.someaddress.com/full
/url/
Author, A. A., & Author, B. B. (Date of Kenneth, I. A. (2000). A Buddhist
publication). Title of article. Title of response to the nature of human
Journal, volume number. Retrieved rights. Journal of Buddhist Ethics,
month
day,
year,
from 8.Retrieved 20 February 2001, from
http://www.cac.psu.edu/jbe/twocon
/url/
t.html
If the article appears as a printed Whitmeyer,
J.M.
(2000).
Power
version as well, the URL is not required. through appointment [Electronic
Use "Electronic version" in brackets version]. Social Science Research, 29,
after the article's title.
535-555.
When referencing material obtained Smyth, A. M., Parker, A. L., & Pease, D.
from an online database (such as a L. (2002). A study of enjoyment of
database in the library), provide peas. Journal of Abnormal Eating,
appropriate print citation information 8(3). Retrieved 20 February 2003, from
(formatted just like a "normal" print PsycARTICLES database.
citation would be for that type of
work). Then add information that gives
the date of retrieval and the proper
name of the database. This will allow
people to retrieve the print version if
they do not have access to the
database from which you retrieved
the article.
List as much of the following information as possible (you sometimes have to
hunt around to find the information. If there is a page such as
http://www.somesite.com/somepage.htm, and somepage.htm does not carry
the information you are looking for, move up the URL to
http://www.somesite.com/)
Author, A. A., & Author, B. B. (Date of publication). Title of document.
Retrieved day, month, year, from http://Web address.
Title of document (Date of publication). Retrieved day, month, year, from
http://Web address
NOTE: When an Internet document is more than one Web page, provide a URL
that links to the home page or entry page for the document. If the date is
unavailable for the document use (n.d.) for no date.
Page 29 of 74
Chapter or
Section of a Web
Document
Online Forum or
Discussion Board
Posting
Computer
Software
Author, A. A., & Author, B. B. (Date

of publication). Title of article. In
Title of book or larger document
(chapter or section number).
Retrieved day, month, year, from
/url/.
NOTE: Use a chapter or section
identifier and provide a URL that
links directly to the chapter section,
not the home page of the Web
site.
For a message posted to an online
newsgroup, forum, or discussion
group, include the title of the
message, and the URL of the
newsgroup or discussion board.
NOTE: If only the screen name is
available for the author, then use
the screen name. However, if the
author provides a real name, use
their real name instead. Be sure to
provide the exact date of the
posting. Follow the date with the
subject line, the thread of the
message (not in italics). Provide any
identifiers in brackets after the title,
as in other types of references.
Engelshcall, R. S. (1997). Module

mod_rewrite : URL Rewriting Engine. In
Apache HTTP Server Version 1.3
Documentation (Apache modules.)
Retrieved March 10, 2006, from
http://httpd.apache.org/docs/1.3/mod/
mod_rewrite.html
Frook, B. D. (1999, July 23). New

inventions in the cyberworld of toylandia
[Msg
25].
Message
posted
to
http://groups.earthlink.com/forum/mess
ages/00025.html
Ludwig,
T.
(2002).
PsychInquiry
[computer software]. New York: Worth.
Page 30 of 74
Table 5.4: Reference List for Other Non-Print Sources

Interview, Email,
and Other
Personal
Communications
Motion Picture
A Motion Picture
or Video Tape with
International or
National
availability
A Motion Picture
or Video Tape with
Limited
Availability
Television
Broadcast or
Series Episode
Single Episode of
a Television Series
No personal communication is (E. Robbins, personal communication,

included in your reference list; January 4, 2001).
instead, parenthetically cite the A. P. Smith also claimed that many of
communicators name and the her students had difficulties with APA
date of the communication in style
(personal
communication,
your main text only.
November 3, 2002).
Basic reference list format:
Producer, P. P. (Producer), & Director, D.D. (Director). (Date of
publication). Title of motion picture [Motion picture]. Country of origin:
Studio or distributor.
Note: If a movie or video tape is unavailable in wide distribution, add the
following to your citation after the country of origin: (Available from
Distributor name, full address and zip code).
Smith, J.D. (Producer), & Smithee, A.F.
(Director). (2001). Really big disaster
movie [ Motion picture]. United States:
Paramount Pictures
Harris, M. (Producer), & Turley, M. J.
(Director). (2002). Writing labs: A
history [Motion picture]. (Available
from Purdue University Pictures, 500
Oval Drive, West Lafayette, IN 47907)
Producer, P. P. (Producer). (Date
of broadcast or copyright). Title
of
broadcast
[
Television
broadcast or Television series ].
City of origin: Studio or distributor.
Writer, W. W. (Writer), & Director,
D.D.
(Director).
(Date
of
publication). Title of episode
[Television series episode]. In P.
Producer (Producer), Series title.
City of origin: Studio or distributor.
Television
Broadcast
A Television Series
Music Recording
Songwriter, W. W. (Date of
copyright).
Title
of
song
[Recorded by artist if different
from song writer]. On Title of
album [Medium of recording].
Location: Label. (Recording date
if different from copyright date).
Wendy, S. W. (Writer), & Martian, I.R.

(Director). (1986). The rising angel and
the falling ape [Television series
episode]. In D. Dude (Producer),
Creatures and monsters. Los Angeles:
Belarus Studios.
Important, I. M. (Producer). (1990,
November 1). The nightly news hour
[Television broadcast]. New York:
Central Broadcasting Service.
Bellisario, D.L. (Producer). (1992).
Exciting action show [Television series].
Hollywood: American Broadcasting
Company.
Taupin, B. (1975). Someone saved my
life tonight [Recorded by Elton John].
On Captain fantastic and the brown
dirt cowboy [CD]. London: Big Pig
Music Limited.
Page 31 of 74
6.0 APPENDICES
APPENDIX A
Project Planner
LEVEL
WEEK
1
TASK
3
4
5
8
9
10
11
12
13
14
OUTCOME
Student Registration
Divide students into groups of
two-three.
Discuss project title.
Assign each group to a
Project registration form
supervisor
Discuss project development
Create project capstone
Discuss methodologies
Discuss and prepare proposal
Draft proposal paper
Discuss project proposal
Present proposal
Get supervisors approval
Discuss Preliminary Investigation
Prepare fact-finding materials
Discuss the tasks in planning a
project
Develop a plan
Discuss and construct Gantt
Chart
Prepare a planning report
Discuss preliminary analysis
Perform fact-finding
Presentation 1
Analyze the gathered
(Proposal Report)
information
Discuss detailed analysis
Design data analysis
Design diagram
Design entity relationship
diagrams
Discuss and prepare analysis
Presentation 2
report.
(Analysis Report)
Present analysis report
Discuss project design
Illustrate project Design
Discuss input design
Design effective source
documents and input controls.
Page 32 of 74
15
16
Discuss output design

Present project design
Compile the project
documentation
Demonstrate initial prototype for
a new system
Demonstration
Capstone Project
Project document
17
LEVEL
WEEK
1
2
TASK
10
11
Presentation 3
(Design report)
OUTCOME
Student registration
Project proposal review
Review project plan and project
design
Discuss and develop problem
specification, design, and code
the program
Report and discuss the progress
of the project development
PEER ASSESSMENT 1
Develop the project
Develop the project
Demonstration
DEMONSTRATION 1
Develop the project
Demonstration
Develop the project
Demonstration
Develop the project
Demonstration
Develop the project
Demonstration
Develop the project
Demonstration
Discuss testing
Conduct unit testing, integration
DEMONSTRATION 2
testing and system testing
Page 33 of 74
12
13
14
15
16
17
Discuss the findings of project

testing
PEER ASSESSMENT 2
Rectify the errors detected in the
system
Review Outcome
Perform implementation plan
Demonstration
Review Outcome
Perform implementation plan
Demonstration
Compile project documentation
DEMONSTRATION 3
Present the project
Inter-polytechnic final project
PEER ASSESSMENT 3
competition
FINAL PRESENTATION
Page 34 of 74
APPENDIX B
Gantt Chart
Level
WEEK / ACTIVITY
Project Briefing.
Select project title
and project
supervisor.
Create and compile
project capstone
Guidance &
Consultation
Prepare project
proposal for approval
Proposal presentation
Submit proposal
report
Analysis presentation
and submit analysis
report
Design presentation
and submit design
report
Submission of
capstone project
Reviewed project and
proposal
Guidance &
Consultation
1st Demonstration
2nd Demonstration
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13
W14
W15
W16
W17
Page 35 of 74
Level
WEEK / ACTIVITY
3rd Demonstration
Submit Final draft
Presentation, and
submit capstone
project
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13
W14
W15
W16
W17
Page 36 of 74
APPENDIX C
Level 5: RPP
POLITEKNIK XXX
SEMESTER LESSON PLAN
DEPARTMENT OF INFORMATION AND COMMUNICATION TECHNOLOGY
SESSION: ________
LESSON PLAN
Lecturers Name
Department / Unit
Code & Course Name
:
: INFORMATION & COMMUNICATION TECHNOLOGY
: FP521 - PROJECT ANALYSIS AND DESIGN
Session
Class / Club
:
:
PLO :
1. Apply fundamental principles of computing and mathematics to be competent and possess strong understanding in
programming.
2. Apply appropriate methodologies, models and techniques that provide a basis for analysis, design, development, testing
and implementation, evaluation, maintenance and documentation of a software system.
3. Communicate effectively with it professionals, other professionals and community
4. Demonstrate strong analytical and critical thinking skills to troubleshoot and solve problems within realistic constraints by
applying knowledge, principles and skills in information technology.
5. Demonstrate an awareness of and consideration for society, health, safety, legal and cultural issues and their consequent
responsibilities.
6. Engage in life-long learning and professional development to enrich knowledge and competencies;
7. Inculcate entrepreneurial skills in the related discipline that contributes towards national growth and be competitive in it
industries;
8. Adhere to professional codes of ethics and enhance humanistic values to adapt to
the real challenges in working
environment; and
9. Demonstrate effective leadership and teamwork skills.
Page 37 of 74
CLO :
1. Explain the activities that involves in Project Development and Project Management. (PLO1)
2. Construct a comprehensive information technology project proposal with high usability user interface, input design and
output design. (PLO4,PLO5)
3. Communicate effectively the feasible and significance project for the community. (PLO3,PLO9)
Week
(Period )
W1
W2
Topics, General Outcomes, Specific Outcomes and Coursework

Assessment
STUDENT REGISTRATION WEEK
Implementation
date
Notes/Reflection
1.0 INTRODUCTION
1.1
Discuss project development and project management
1.1.1
State the definitions of project development and project
management.
1.1.2
Compare the process in project development and project
management.
1.1.3
Explain the methodologies that can be use in developing a
project.
1.1.4
Describe these three constraint and how it relate to each other in
project management.
a. Time
b. Cost
c. Scope
1.1.5
Demonstrate knowledge and understanding of intellectual
properties
1.1.6
Explain common types of intellectual property:
a. Patent
b. Trademarks
c. Trade secrets
d. Copyright
e. Intellectual property laws
1.1.7
Adhere to the professional ethics by avoiding plagiarism and
copyright.
1.1.8
Demonstrate the human relations involve in communication,
Page 38 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
teamwork, leadership, and responsible ethical and moral

behaviour in project development
1.2
W3
1.3
1.4
Explain System Development life Cycle (SDLC).

1.2.1
Describe the activities in different phases of SDLC.
a. Planning
b. Analyze
c. Design
d. Development
e. Testing
f. Implementation
g. Maintenance
1.2.2
Identify the various types of life cycle models such as:
a. Waterfall model
b. Spiral model
c. Fountain model
d. Prototyping model
e. Iterative and Incremental development
f. Rapid Application Development (RAD)
g. Joint Application Development (JAD)
h. Extreme Programming (XP)
i. Agile Model
Discuss project reports and documentation
1.3.1
Describe types of reports:
a. Portfolio report
b. Planning report
c. Analysis report
d. Design report
1.3.2
Explain project documentation requirement , structures and
styles.
1.3.3
Justify the importance of documentation.
Demonstrate the use of project portfolio.
1.4.1
Create project portfolio that includes the following such as:
a. Technical memo
b. User documentation
c. Technical requirement
Page 39 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
d. Phases of project life cycle

e. Matrix table comprises of Summary of references
f. Self or peer evaluation statement
1.5
W4
W5
Draft project proposal

1.5.1
Define the purpose of a project proposal.
1.5.2
Determine the potential product or software that needs to be
developed with high level programming language:
a. Database programming
b. Web programming
c. Multimedia programming
d. Games programming
e. Networking
1.5.3
Gather and compile information of literature review based on
project proposal.
1.5.4
State the objectives and goals of the project.
1.5.5
Justify the requirements in a proposal paper:
a. Project Synopsis
b. Introduction / background
c. Problem Statement
d. Objectives
e. Project Significance
f. Methodology
g. Conclusion
1.5.6
Prepare proposal paper and present the proposal.
2.0 PLANNING
2.1
Discuss Preliminary Investigation
2.1.1
Identify the steps in preliminary investigation:
a. Understand the problem or opportunity
b. Define the project scope and constraints
c. Perform fact-finding
d. Evaluate feasibility
e. Estimate project development time and cost
f. Present results and recommendations to management
2.1.2
Identify the appropriate title for the project.
2.1.3
Identify the scope and nature of the problem.
Page 40 of 74
Week
(Period )
W6
W7
W8
W9

Assessment
Implementation
date
Notes/Reflection
2.1.4
Prepare a research to identify project and user requirements.
2.1.5
Identify the stakeholders of a system and formulate their needs.
2.2
Planning the Project
2.2.1
Discuss the tasks in planning a project
a. Objectives of plan
b. Develop a plan
c. Construct project planning diagram
d. Identify timing duration of each activity in planning diagram
e. Identify costs and labor/personnel associated with each
activity
2.2.2
Use a appropriate application to construct the Gantt Chart to
show the activities and milestone of project.
2.2.3
Estimate the budget for the major activities of the project.
2.2.4
Use Work Breakdown Structure (WBS) in the project.
2.2.5
Prepare planning report and present.
3.0 ANALYSING
3.1 Conduct Preliminary Analysis
3.1.1
Identify the following elements related to project requirements:
a. Input
b. Output
c. Process
d. Performance
e. Control
3.1.2
Justify in depth the techniques used in fact-finding:
a. Interviews
b. Documentation review
c. Observation
d. Questionnaires
e. Sampling
f. Research
3.1
Conduct Preliminary Analysis
3.1.3
Use the appropriate technique of fact-finding.
3.1.4 Analyze the gathered information.
Page 41 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
3.2
W10
W11
W12
W13
W14
Conduct a feasibility study for the project

3.2.1
Identify the functional requirement for the project.
3.2.2
Explain the signficance of different types of feasibility study:
a. Technical Feasibility
b. Operational Feasibility
c. Economic Feasibility
3.3
Construct Detailed Analysis
3.3.1
Identify the techniques employed in analysing the information:
a. Entity Life History
b. Relational Data Analysis
c. Context Diagram
d. Data Flow Diagrams
e. Entity Relationship Diagrams
3.3
Construct Detailed Analysis
3.3.2
Apply the appropriate technique to conceptualise the
framework of the project components.
3.3.3
Prepare analysis report and present the report.
4.0 DESIGNING
4.1
Illustrate User Interface Design
4.1.1
Explain user interface design and human computer interaction.
4.1.2
List specific guidelines for user interface design.
4.1.3
Illustrate user interface techniques such as screen elements and
controls
4.2
Create Input Design
4.2.1
Differentiate data capture and data entry.
4.2.2
List the objectives of input design.
4.2.3
Explain the input and data entry methods:
a. Batch input
b. Online input
4.2.4
Explain guidelines for data entry screen design.
4.2.5
Use validation checks for reducing input errors.
4.2.6
Design effective source documents and input controls.
4.2.7
Justify the designed source documents and input controls.
Page 42 of 74
Week
(Period )

Assessment
4.3
W15
4.4
W16
4.5
Implementation
date
Notes/Reflection
Create Output Design

4.3.1
Distinguish between internal, external and turnaround outputs.
4.3.2
List the objectives of output design.
4.3.3
List and describe several types of output:
a. Printed reports
b. Screens display
c. Audio
d. E-mail
e. Computer microfilm
f.Internet-based
4.3.4
Develop detail reports, exception reports and summary reports.
4.3.5
Explain general principles important to output design:
a. Guidelines
b. Process
4.3.6
Perform output design for a new system as a case study.
Create a prototype to validate the design
4.4.1
Analyze between refining the specifications and building the
working models of the project.
4.4.2
Build abd test the prototype of the project.
4.4.3
Prepare design report and present the projects prototype.
Compile the project documentation.
4.5.1
Prepare project documentation based on:
a. Introduction of the project
b. Literature review
c. Methodology
Prepared by :
-----------------------------------------Signature of Course Lecturer
Date :
Approved by :
-------------------------------------------------Signature of Deputy Director (Academic) /
Head of Department / Programme Leader
Date :
Page 43 of 74
APPENDIX D
Level 6: RPP
POLITEKNIK XXX
SEMESTER LESSON PLAN
DEPARTMENT OF INFORMATION AND COMMUNICATION TECHNOLOGY
SESSION:_______
LESSON PLAN
PROGRAMME
COURSE CODE
COURSE NAME
NAME OF LECTURER
:
: FP621
: PROGRAMMING PROJECT
:
Learning Domains (LD)

LD1: Knowledge
LD2: Practical Skills
LD3: Communication Skills
LD4: Critical Thinking and
Problem Solving Skills
LD5: Social Skills and
Responsibilities
LD6: Continuous Learning and

Information
Management Skills
LD7: Management and
Entrepreneurial Skills
LD8: Professionalism, Ethics
and Moral
LD9: Leadership and
Teamwork Skills
Page 44 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
COURSE LEARNING OUTCOMES (CLO)

Upon completion of this course, the student will be able to:
1. Apply the continuous knowledge and efficient methods to achieve sufficient quality for the Outcome. (P5, C3, A4)
2. Produce a very comprehensive presentation, technical documentation and end product for the project. (P5, A4)
3. Communicate effectively within the project group and supervisor(s) to meet stated tasks and milestones. (A2, A4)
W1
W2
W3
STUDENT REGISTRATION WEEK

1.0 PROJECT PROPOSAL REVIEW
1.1 Prepare project design review and project plan.
1.1.1 Review the project design.
1.1.2 Review the project plan developed in the analysis and
design phase.
1.1.3 Propose a complete project development plan.
1.1.4 Assign tasks to project team members.
1.1.5 Plan the schedule for project group working sessions.
1.1.6 Track the progress of the project development, based on
the Gantt chart develop during planning phase.
1.1.7 Discuss the reviewed design and plan with the supervisor
for approval.
Briefing on the CLOs, Topics,

assessments, SLT requirements of
this course, etc.
Do Entrance Survey
Measurement of Specific Outcomes:

At the end of the Teaching & Learning process, students should be
able to:
i.
Prepare project design review and project plan.
2.0 DEVELOPMENT
2.1 Develop problem specification, design and code the program.
2.1.1 Develop the input, output and user interface of the
project.
2.1.2 Design the application structure.
Page 45 of 74
Week
(Period )
W4
W5
W6

Assessment
Implementation
date
Notes/Reflection
2.1.3
Develop the project application using an appropriate

programming language and development tools.
PEER ASSESSMENT
2.1.4 Apply secure coding and features by implementing the
user controls, validation control etc.
2.1.5 Review the systems program and overall development.
2.1.6 Perform debugging. Identify the errors.
DEMONSTRATION 1
W7
W8
W9
W10
SEMESTER BREAK
Hari Raya Aidilfitri (19 &

20.8.2012)
2.2 Report the progress of the project development.

2.2.1 Maintain revision history for both code and
documentation.
2.2.2 Assign version numbers and revision status of project
progress.
2.2.3 Maintain a change log for each new version or new
revision status.
2.2.4 Keep track of work efforts individually (report time).
Page 46 of 74
Week
(Period )

Assessment
2.2.5
W11
W12
W13
Implementation
date
Notes/Reflection
Document and present the report of the progress

development of the project.

able to:
i.
Develop problem specification, design and code the
program.
ii.
Report the progress of the project development
DEMONSTRATION 2
3.0 TESTING
3.1 Understand type of testing in IT related project.
3.1.1 Explain different types of software testing:
a. Unit testing
b. Integration testing
c. System testing
3.1.2 Identify the testing plan.
3.1.3 Describe policy and practice in system integration and
architecture to ensure secure system operation and
information assurance.
PEER ASSESSMENT 2
3.2 Conduct testing in a project.
3.2.1 Describe testing standards and quality assurance.
3.2.2 Use appropriate tools and techniques to do testing.
3.2.3 Select test cases to be used.
3.2.4 Perform project unit testing and integration testing.
3.2.5 Perform system testing.
Page 47 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
3.2.6 Rectify the errors detected in the system.

3.2.7 Analyze the data from a usability test and recommend
appropriate actions.
3.2.8 Document the testing results.
3.2.9 Validate the fulfillment of the projects requirement
specifications.
able to:
i.
Understand type of testing in IT related project.
ii.
Conduct testing in a project.
DEMONSTRATION 2
Page 48 of 74
Week
(Period )
W14

Assessment
Implementation
date
Notes/Reflection
4.0 IMPLEMENTATION
4.1 Present Outcome for review.
4.1.1 Present the Time and Resource Plan:
a. Milestones and Outcome for defined activities
b. Persons responsible of each activity and deliverable
c. Participants in each activity
d. Perform implementation plan (i.e., iterations test for
first draft version, finish the implementation, fix
identified errors, then test again, and fix remaining
errors).
4.1.2 Review requirement specification:
a. Primary requirements
b. Optional requirements
4.1.3 Review Design specification:
a. Modular description of the complete system (e.g. class
diagram, module diagrams)
b. System usage and interactions between modules (e.g.
based on used cases, interaction diagram, state
charts)
4.1.4 Give oral presentation and present project Outcome:
a. Project plan
b. Interim Report
c. Complete specification and design
Page 49 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
4.2 Implement the project.

4.2.1 Integrate the modular or sub program.
4.2.2 Describe policy to ensure secure system operation and
information assurance.
4.2.3 Deploy the application.
4.2.4 Record each malfunction of the work during
experimentation.
W15
W16

able to:
i.
Present Outcome for review.
ii.
Implement the project.
DEMONSTRATION 3
5.0 DOCUMENTATION
5.1 Prepare project documentation.
5.1.1 Review the formalize and completed project
documentation consist of:
a. Project plan
b. Requirement specification
c. Final design
d. Test description and results
e. Major findings and conclusions
f. Further work and recommendations
g. References
5.1.2 Prepare and compile the project documentation based
on documentation requirement, structures and styles.
5.1.3 Prepare an appropriate user manual for the application.
Page 50 of 74
Week
(Period )

Assessment
Implementation
date
Notes/Reflection
5.1.4
Provide a compilation of the following:

a. Executable program or application
b. Source code
PEER ASSESSMENT 3
5.1.5 Present the final product.
W17

able to:
i.
Prepare project documentation.
Do Exit Survey
PRESENTATION
W18
STUDY WEEK
W19
W20
EXAMINATION WEEK
Prepared by :
Approved by :
------------------------------------------
----------------------------------------------------------
Signature of Course Lecturer
Signature of Deputy Director (Academic) /
Date :
Head of Department / Programme Leader

Date :
Page 51 of 74
APA Format
Single Author
Two Authors
Three to Six Authors
More Than Six Authors
Author - Malay Names

(without family names)
Author - Chinese Names
Author - Chinese Names
APPENDIX E
GENERAL RULES
Last name first, followed by author
initials.
Berndt, T. J. (2002). Friendship quality and

social development. Current Directions in
Psychological Science, 11, 7-10.
List by their last names and initials. Use Wegener, D. T., & Petty, R. E. (1994). Mood
the ampersand (&) instead of "and."
management across affective states: The
hedonic contingency hypothesis. Journal of
Personality & Social Psychology, 66, 1034-1048.
List by last names and initials;
Kernis, M. H., Cornell, D. P., Sun, C. R., Berry, A.,
commas separate author names,
& Harlow, T. (1993). There's more to self-esteem
while the last author name is
than whether it is high or low: The importance
preceded again by ampersand (&).
of stability of self-esteem. Journal of Personality
and Social Psychology, 65, 1190-1204.
If there are more than six authors, list
Harris, M., Karper, E., Stacks, G., Hoffman, D.,
the first six as above and then "et al.," DeNiro, R., Cruz, P., et al. (2001). Writing labs
which stands for "and others."
and the Hollywood connection. Journal of Film
Remember not to place a period
and Writing, 44(3), 213-245.
after "et" in "et al."
Omit bin/binti
Asmah Binti Omar
Cite as
Asmah Omar. (1991). Kemahiran berbahasa.
Kuala Lumpur: Penerbitan Pustaka Antara.
First name first, followed by author
Chu Chin Ning
initials.
Cite as
Chu, C. N. (1995). Simulated counter-current
adsorption processes; A comparison of
modeling strategies. Chemical Engineering
Journal, 56, 59-65.
Family names followed by the initials
Vincent Foo Hiap Khian
Page 52 of 74
with English Names
of the English name and the author

initials
Author-Indian & Sikh

Names
(without family names)
Inherited Names
Omit d/o, s/o, a/l, a/p
Conferred titles
Omit title
Local Government
Institution as Author
Foreign Government
Institution as Author
Cite under state and followed by the

name of department in Malay
Cite under state or country and
followed by the name of department
in English
If the name starts with Foundation
(Yayasan), Board (Lembaga), cite as
it is given
Unique Corporate Body

Names
Organization as Author
Conference Names with
Numbers
Unknown Author
Cite as it is
Do not include the numbers
Cite as
Foo, V. H. K. (1983). Sarawak: Mini episodes of
the past. Petaling Jaya: Fajar Bakti.
Narrayani a/p Jeganathan.
Cite as
Narrayani Jeganathan. (2009).
Raja Ahmad Niza.
Cite as
Raja Ahmad Niza. (2009).
Tun Mahathir Mohamad
Cite as
Mahathir Mohamad
Pahang, Jabatan Alam Sekitar. (2009).
New Zealand, Department of External Affairs.
(2009).
Yayasan Sabah. (2009).
American Psychological Association. (2003).
Fifth Asia-Pacific Physics Conference
Cite as
Asia-Pacific Physics Conference
Merriam-Webster's collegiate dictionary (10th
ed.).(1993). Springfield, MA: Merriam-Webster.
Page 53 of 74
APPENDIX F
Level 5 : Proposal Report Rubric
CRITERIA
Unclear and
incomplete
understanding of
the project to be
taken
Vague
explanations of
the problems
The main
objective is clear
with guidance.
Vague about
the project to
be undertaken
No clear
clarification
between system
scope and user
scope
State very little
about the project
significance
Do not clarify
user between
system scope
and user scope
Introduction
Always clearly
explains the
project to be
undertaken
Clearly explain s
the project to be
undertaken most
of the time
Sometimes clearly
explains the project
to be undertaken
Occasionally
explains the project
to be undertaken
Problem Statement
Always clearly
explains the
problems
The main
objective is very
clear during first
submission.
Always clearly
clarify system
scope and user
scope
Clearly explain the

problems most of
the time
The main
objective is clear
during first
submission.
Clearly clarify
system scope and
user scope most of
the time
Sometimes clearly
explain the
problems
The main objective
needs to be
improved
Occasionally
explains the
problems faced
The main objective
is clear after
review.
Few of the required
system scope and
user scope are
included
Very clear
explanation of
the project
significance
The study carried
out very clearly in
evidence
Methodology
associated with
building projects.
Clear explanation
of the project
significance
Most of the
required
system scope and
user scope are
included
Somewhat clear
explanations of
project significant
Less evidence of
research done
No evidence of
research done
Explanation is too
general
Not state the

explanation
Few of
methodology
associated with
building projects.
Lack of
methodology
associated with
building projects.
Methodology
used was not
appropriate.
Do not correlate
with the
methodology of
project work.
Objectives
Scope
Project Significant
(cannot be
measured)
Literature Review
Methodology
The study carried

out in few
evidence
Most
methodology
associated with
building projects.
Less clear about

project significant
No problem
stated
The main
objective is not
clear
Do Not state the

project
significance
Page 54 of 74
References
Gantt Chart
Cost
Conclusion
More than 5 from

books or journals
and follow APA
styles. Not have
website
reference.
Chart is accurate
based on project
schedule.
Meets all normal
requirements and
reasonable
Student
concludes the
presentation
confidently
5 from books or
journals but not
follow APA styles.
Not have website
reference.
Chart is accurate
based on project
schedule but less
specific.
Meets most
normal
requirements and
reasonable
Student concludes
the presentation
Less than 5
references books
or journals but
follow APA styles.
Not have website
reference.
Chart is accurate
based on project
schedule but not
specific.
Meet few normal
requirements.
Have 5 reference
include books,
journals and
website. Follow
APA styles.
Not have
references.
Meet very little

normal
requirements.
Less than 5
reference include
books, journals
and website and
not follow APA
styles.
Chart is not
accurate based
on project
schedule.
None meet the
normal
requirements.
Student concludes
the presentation
with few point.
Conclusion is
vague.
Inappropriate
conclusion.
No conclusion.
Chart is less
accurate based on
project schedule.
Not have chart.
Not cost
specified.
Page 55 of 74
APPENDIX G
Level 5: Analysis Report Rubric
CRITERIA
Fact finding
technique
Data
Analysis
Literature
Review
5
Questions are
answered thoroughly
with suitable
techniques supported
by data from the fact
finding.
Accurate
representation of the
data using suitable
diagrams. Data is
precise with
accepted values.
Analysis is insightful. All
data are logically
analyzed.
4
Demonstrate most
techniques to
answer the
question.
3
Demonstrate many
techniques to
answer the
question.
2
Demonstrate some
suitable technique
to answer the
question.
1
Demonstrate little
suitable technique
to answer the
question.
0
Demonstrate little
or no suitable
technique to
answer the
question.
Good
representation of
the data using
suitable diagram s
but data lacks
precision.
Analysis is insightful.
All data are most
logically analyzed.
Contains only
some data which
use suitable
diagrams.
Contains only little

data or data is not
accurate
Data is not
presented.
Contains only
some data analysis
Contains only little

data analysis
Analysis is not
presented
Thorough reference to
more than 3 key
literature and explicit
relationship between
the literature and the
project demonstrated
Adequate to good
reference to the
key literature.
Provides adequate
explanation of the
literatures
relationship to the
project.
Brief
representation of
the data using
suitable diagrams
but data lacks
precision.
Analysis is general.
Data are logically
analyzed for the
most part.
Some reference to
the key literature
and provide some
explanation of
relationship of
literature to the
project.
Contains some
related literature
review and some
that are not
related to the
project
Contains literature
review that are not
related to the
project
No literature
reiview
Page 56 of 74
APPENDIX H
Level 5: Design Report Rubric

CRITERIA
Graphical User
Interface (GUI)
(exclude DNS
Project)
Design problem
solution
5
Exemplary user
interface, superior
over GUIs for
similar purposes,
many innovative
ideas.
Clear and
complete
understanding of
design goal and
constraints for the
whole project
Diagram
Reliability
All diagrams are

constructed
accurately based
on information
provided and
calculated.
Problem Solving
Using Diagram
All diagrams are

effectively used to
work towards a
verifiable solution
4
innovative ideas
and user friendly.
3
Some innovative
ideas, relatively
user friendly.
2
Difficult to
understand and
only little effort
have been spent
to design the GUI.
1
GUI are poorly
design
0
GUI is not shown.
Clear and
complete
understanding of
design goal and
constraints for the
most part of the
project
Most diagrams are
accurately
constructed
based on
information
provided and
calculated.
Clear but
incomplete
understanding of
design goal and
constraints for the
whole project
Little
understanding of
design and
constraints for the
whole project
Unclear and
incomplete
understanding of
design and
constraints for the
whole project
Not discussed
Some diagrams
are
accurately
constructed
based on
information
provided and
calculated.
Identifies some
items to include in
the diagrams that
will lead toward a
solution
Diagram are
suitable based on
information
provided
Does not identify

appropriate
information to
include in
diagram.
Diagram not
shown.
Diagrams are
suitable that will
lead toward a
solution
Diagrams are
inappropriate
No diagram used.
Most of the
diagrams are
effectively used to
work towards a
verifiable solution
Page 57 of 74
APPENDIX I
Level 5: Peer Assessment Rubric
KNOWLEDGE
CRITERIA
Comprehension
COMMUNICATI
ON
Content
Nonverbal
Language
Fair grasp of
theoretical
foundations.
Great knowledge
in field of study.
Good amount of
knowledge in field
of study.
Good gestures and
postures.
Consistent use of
direct eye contact
with the audience.
Big and clear.
Fair amount of
knowledge in
field of study.
Good gestures.
Listens to, shares

with, and supports
the efforts of
others.
A definite leader
who contributes a
lot of effort.
Always listens to,

shares with, and
supports the efforts
of others.
A good group
member who tries
hard.
Usually listens to,

shares with, and
supports the
efforts of others.
A strong group
member who tries
hard.
Consistently stays
focuses.
Always stays
focuses.
Stays focuses
most of the time.
Actively looks for

and suggests
solutions to
Always looks for

and suggests
solutions to
Most of the time

looks for and
suggests solutions
Visual Aids
Attractive, big and

clear.
Focus on the Task

Problem-solving
Good grasp of
theoretical
foundations.
Eye Contact
Contributions
Very clear,
comprehensive
understanding of
theoretical
foundations.
Excellent gestures
and postures.
Good eye contact
with the audience.
Working with
Others
LEADERSHIP
Frequently looking
at the audience.
Small but clear.
Vague
conceptions,
but lack of
clarity of
theories and/or
models.
Very basic
knowledge
base.
Weak gestures
and postures.
Sometimes look
at the
audience.
Big but unclear.
Lack of
understanding of
basic theories &
models.
No
understanding of
basic theories &
models.
Very limited
knowledge.
Lack of
knowledge.
Bad gestures and

postures.
Rarely look at the
audience.
No gestures and
postures.
No eye contact
(read the text).
Small and unclear.
Unclear.
Often listens to,

shares with, and
supports the
efforts of other.
A satisfactory
group member
who does what
is required.
Stays focuses
some of the
time.
Refines solutions
suggested by
others.
Rarely listens to,

shares with, and
of others.
Rarely participate.
Does not listen to,

shares with, and
supports the
efforts of others.
Refuse to
participate.
Rarely focuses.
Lost focuses.
Does not suggest or

refine solutions.
Does not try to

solve problems.
Page 58 of 74
Participation
TEAM WORK
Listening
Feedback
Cooperation
Time
Management
problems.
Fully participated.
problems.
Always participate.
to problems.
Most of the time
participated.
Listens carefully to
others ideas.
Always listens to
others ideas.
Usually listens to
others ideas.
Offered detailed,
constructive
feedback when
appropriate.
Treated others
respectfully and
shared the
workload fairly.
Offered
constructive
feedback when
appropriate.
Usually treated
others respectfully.
Offered
constructive
feedback when
appropriate.
Usually shared the
workload fairly.
Completed
assigned tasks on
time.
Always completed
assigned tasks on
time.
Usually
completed
assigned tasks on
time.
Some of the
time
participated.
Sometimes
listens to others
ideas.
Occasionally
offered
constructive
feedback.
Sometimes
treated others
disrespectfully or
did not share
the workload
fairly.
Sometimes
completed
assigned tasks
on time.
Rarely participated.
Does not
participate.
Rarely listens to
others and often
interrupts them.
Rarely offered
constructive or
useful feedback.
Does not listen to

others and often
interrupts them.
Did not offer
constructive or
useful feedback.
Often treated others

disrespectfully or did
not share the
workload fairly.
Treated others
disrespectfully or
did not share the
workload fairly.
Often did not

complete assigned
tasks on time.
Did not complete

most of the
assigned tasks on
time.
Page 59 of 74
APPENDIX J
Level 5 And 6: Soft Skill Presentation/Demonstration Rubric
Criteria
5
Communicates and
interacts with
audience with a high
degree of
effectiveness and
ideas
Accurately answer all
questions posed with
high confidence.
4
Communicates and
interacts with
audience with a
Communication
moderate degree of
effectiveness and
ideas
Accurately answer
almost all questions
Answering Ability
posed with high
confidence.
Hold attention of
Hold attention of
entire audience with entire audience with
the use of direct eye the use of direct eye
Posture and Eye
contact, student
contact, student
Contact
displays relaxed, self- displays relaxed, selfconfident with no
confident with few
mistakes.
mistakes.
Demonstrates a
Demonstrates a
strong, positive
positive feeling
Enthusiasm
feeling about topic about topic during
during entire
entire presentation.
presentation
Good leadership role Assume leadership
and works as a
role and works as a
Leadership & Team
cohesive unit to
cohesive unit to
work
make the
make the
presentation
presentation
Self Appearance
Shows an excellent
Shows presentable
attitude during the
attitude during the
3
Communicates
and interacts with
audience with
some effective
ideas
2
Communicates and
interacts with
audience with
considerable ideas
1
Communicates
and interacts with
audience with
limited ideas
Accurately answer
a few questions
posed with
confidence.
Consistent use of
direct eye contact
with audience,
displays no
nervousness and
stress.
Able to answer some Able to answer

questions with lack some questions
of confidence
posed but lacks of
confident
Consistent use of
Displayed minimal
direct eye contact eye contact with
with audience,
audience, show
displays modest
nervousness and
nervousness and
stress.
stress.
0
Little to no
communication or
interaction with
audience
Unable to answer all
questions posed
and has no
confident.
No eye contact with
audience, show
nervousness and
stress.
shows some
Occasionally Shows
positive feelings
interest towards the
towards the topic. topic presented.
Shows lack of
Shows no interest at
interest in the topic all in topic
presented.
presented
Assist in
coordinating task
and works together
to make the
presentation
Shows a good
attitude along the
Minimum
No contribution to
contribution to the the presentation
presentation
Minimum
contribution
coordinating task
and work together to
make presentation
Shows a mild
attitude along the
Shows a poor
attitude along the
Does not show a

good attitude in the
Page 60 of 74
Material and
Added Tools
Intonation and
volume
presentation session.
Dresses nicely &
appropriately (tie,
students card,
jacket, shoes)
Dresses nicely &
appropriately (tie,
students card,
jacket, shoes)
Used full effectively

material and new
technology to
explain and
organized
information along the
Used effectively
material and new
technology to
explain and
organized
information along
the presentation
session.
Adjusts intonation
and volume
appropriately to
make the
presentation
attractive.
Intentionally adjusts
intonation and
volume to achieve
purpose.
presentation
session. Dresses
nicely &
appropriately (tie,
students card,
jacket, shoes)
Used effectively
material and
added tools to
explain and
organized
information along
the presentation
session
Voice and the
intonation is slow.
Not enough to
impede
understanding.
Dressing
appropriately (tie,
students card,
jacket, shoes).
presentation
session. Dressing
Dressing
appropriately (tie, inappropriately.
matric card, jacket,
shoes).
Used with moderate

effectiveness
material and added
tools to explain and
organized
information along
the presentation
session
Speaks too fast or
slow in a way that
impedes
understanding.
Voice and the
intonation is slow.
Minimal using of
material and
added tools to
explain and
organized
information along
the presentation
session
Voice and the
intonation is not
clear.
Does not use any

material or tools to
explain and
organized
information along
the presentation
session
Voice and
intonation are not
heard.
Page 61 of 74
APPENDIX K
Level 6: Peer Assessment Rubric
SOCIAL SKILLS & RESPONSIBILITIES
CRITERIA
Self Expression
Response to
Others
Cooperation
Respect
Group
Interaction
MANAGEMENT & ENTERPRENEURAL

SKILLS
Group
Decisionmaking
Planning
Accountability
Renewed
Commitment
Tolerance Of
5
Integrates own
feelings, ideas and
experiences with
those of others.
Listens actively to
others.
Shows consideration
for others.
Uses appropriate
language when
talking with peers.
Works well with
others.
Participate in the
decision-making
process.
Sets challenging
goals with a step-bystep plan and time
frame for achieving
them.
Sets goals, and
achieves them
ahead of schedule;
offers to mentor
others.
Sets new and
challenging goals
independently.
Gives and
encourages a variety
4
Always integrates
own feelings, ideas
and experiences with
those of others.
Always listens actively
to others.
Always shows
consideration for
others.
Always uses
appropriate
language when
talking with peers.
Always works well
with others.
Always participate in
the decision-making
process.
3
Regularly and
accurately expresses
own feelings, ideas
and experiences.
Regularly listens
actively to others.
Regularly shows
consideration for
others.
Regularly uses
appropriate
language when
talking with peers.
Regularly works well
with others.
Regularly participate
in the decisionmaking process.
2
Sometimes expresses
personal feelings,
ideas and
experiences.
Sometimes listens
attentively to others.
Sometimes shows
consideration for
others.
Sometimes uses
appropriate
language when
talking with peers.
Sometimes works well
with others.
Sometimes
participate in the
decision-making
process.
Occasionally sets
goals; does not have
a process for
achieving goals.
1
Rarely expresses
personal feelings,
ideas and
experiences.
Rarely listens to
others.
Rarely shows
consideration for
others.
Rarely uses
appropriate
language when
talking with peers.
Rarely works well
with others.
Rarely participate in
the decisionmaking process.
Rarely sets goals;
does not have a
process for
achieving goals.
0
Does not express
personal feelings,
ideas and
experiences.
Does not listen to
others.
Does not show
consideration for
others.
Does not use
appropriate
language when
talking with peers.
Does not work well
with others.
Does not
participate in the
decision-making
process.
Does not set goals;
does not have a
process for
achieving goals.
Sets realistic,
attainable goals; uses
a process for
achieving them.
Routinely sets goals;

requires assistance to
establish a process
for achieving goals.
Sets and achieves

goals on schedule.
Sets goals and does

not achieve goals.
May not fully

appreciate the
need to set and
reach goals.
Does not
appreciate the
need to set and
reach goals.
Sets challenging
goals independently.
Sets and achieves

goals, or has
reasonable
explanation for not
doing so.
Sets new goals
independently.
Requires assistance to
set new goals.
Lacks motivation to
set new goals.
Encourages a variety
of points of view.
Evaluates differing
points of view.
Considers differing
points of view.
Occasionally
demonstrates
Does not have

motivation to set
new goals.
Demonstrates
intolerance towards
Page 62 of 74
Others
Ideas
LEADERSHIP
Working with
Others
Contributions
Focus on the
Task
Problemsolving
Participation
TEAM WORK
Listening
Feedback
Cooperation
Time
Management
of points of view.
Listens to, shares with,
and supports the
efforts of others.
A definite leader who
contributes a lot of
effort.
Consistently stays
focuses.
Actively looks for and
suggests solutions to
problems.
Fully participated.
intolerance towards
differing points of
view.
Rarely listens to,
shares with, and
of others.
Rarely participate.
differing points of
view.
Rarely focuses.
Lost focuses.
Always listens to,

shares with, and
supports the efforts of
others.
A good group
member who tries
hard.
Always stays focuses.
Usually listens to,

shares with, and
others.
A strong group
member who tries
hard.
Most of the time.
Often listens to,

shares with, and
other.
A satisfactory group
member who does
what is required.
Some of the time.
Always looks for and

suggests solutions to
problems.
Always participate.
Refines solutions
suggested by others.
Does not suggest or

refine solutions.
Does not try to solve

problems.
Some of the time

participated.
Sometimes did not
listen to others ideas.
Rarely participated.
Does not
participate.
Did not listen to
others and often
interrupted them.
Did not offer
constructive or
useful feedback.
Listened carefully to
others ideas.
Always listen to
others ideas.
Most of the time looks

for and suggests
solutions to problems.
Most of the time
participated.
Usually listened to
others ideas.
Offered detailed,
constructive
feedback when
appropriate.
Treated others
respectfully and
shared the workload
fairly.
Offered constructive
feedback when
appropriate.
Offered constructive
feedback when
appropriate.
Occasionally offered
constructive
feedback.
Usually treated others

respectfully.
Usually shared the

workload fairly.
Sometimes treated
others disrespectfully
or did not share the
workload fairly.
Completed assigned
tasks on time.
Always completed
assigned tasks on
time.
Usually completed
assigned tasks on
time.
Sometimes
completed assigned
tasks on time.
Rarely listen to
others and often
interrupted them.
Rarely offered
constructive or
useful feedback.
Often treated
others
disrespectfully or
did not share the
workload fairly.
Often did not
complete assigned
tasks on time.
Does not listen to,

shares with, and
of others.
Refuse to
participate.
Treated others
disrespectfully or
did not share the
workload fairly.
Did not complete
most of the
assigned tasks on
time.
Page 63 of 74
APPENDIX L
Level 6: End Product
Criteria
5
All objectives are
achieved and
Achieve the
exceeded
objectives
expectation.
Always describes
effectively how the
Construction and
system was
functionally
constructed and
how it functions.
Always clearly
communicated
feasibility of
Feasibility
construction and
implementation. No
errors with
notification.
Exceptionally
attractive and
usable layout. It is
User Interface
easy to locate all
Layout
important elements.
organize material
effectively.
test procedures are
clear and well
documented. Results
Testing
are excellently
documented, valid,
and reliable.
4
Most of the
objectives are
achieved.
3
A few of the
objectives are
achieved.
2
only two objectives
are not achieved.
1
0
Only one objective No objective.
is achieved
Most of the time

Sometimes describes
describes how the
how the system was
system was
constructed and
constructed and
how it functions.
how it functions.
Clearly
Sometimes
communicated
communicated
feasibility of
feasibility of
construction and
construction and
implementation most implementation.
of the time. Minor
Minor error.
error.
Almost usable layout, Moderately usable
but may appear
layout, but may
busy or boring. It is
appear busy or
easy to locate most boring. It is easy to
of the important
locate most of the
elements.
important elements.
Occasionally
describes how the
system was
constructed and
how it functions.
Occasionally
communicated
feasibility of
construction and
implementation.
Minor error.
Least attempts are

made to describe
how the system was
constructed and
how it functions.
Least
communicated
feasibility of
construction and
implementation.
Major error.
No attempt is
made to describe
construction or
functionally.
Slightly usable layout,

but may appear
easy to locate most
of the important
elements.
Least usable layout,

but may appear
easy to locate most
of the important
elements.
Cluttered looking
or confusing. It is
often difficult to
locate important
elements.
attempt is made to
document test
procedures most of
the time. Results are
well documented ,
valid and reliable.
Slight attempt is
made to document
test procedures.
Results are
documented but not
valid and reliable.
Least attempt is
made to document
test procedures.
Results are not
documented and
not valid and
reliable.
No meaningful
attempt is made
to document test
procedures.
Moderately attempt
is made to
document test
procedures. Results
are very well
documented but not
valid and reliable.
No meaningful
attempt was
made to develop
a solution. Major
error.
Page 64 of 74
Marketability
Originality
Creativity
project marketability
is clearly
communicated as to
how this design is
different, better, set
apart from what
already exists.
attempt is made to
communicate the
devices
marketability most of
the time as to , how
this design is
apart from what
already exists.
Moderate attempt is
made to
communicate the
devices
marketability as to
how this design is
apart from what
already exists.
Slight attempt is
made to
communicate the
devices
marketability, how
this design is
apart from what
already exists.
Product shows an
excellent original
thought.
Product shows a
good original
thought.
Product shows a
moderate amount
of original thought.
Excellent ideas,
creative and
inventive.
Good ideas, creative Moderate ideas,

and inventive.
creative and
inventive.
Uses other people's

ideas but there is
little reference of
original thinking.
Fairly creative ideas
and inventive
Least attempt is
made to
communicate the
devices
marketability, how
this design is
apart from what
already exists.
No meaningful
attempt is made
to communicate
the projects
marketability, how
this design is
different, better,
set apart from
what already
exists.
Uses other people's No originality and
ideas.
plagiarism.
Lack of ideas,
creativity and
invention.
No creativity
Page 65 of 74
APPENDIX M
Level 6: Final Report Rubric
CRITERIA
5
Describe excellent
and specific
sentence for main
purpose, scope,
Abstract
method, result,
recommendation
and conclusion of
project without
grammatical errors.
Very good
Introduction explanations of the
project
Methodology is
clearly presented,
relevant and
Methodology
appropriate ly
applied to project
development.
Excellent literature
review . Sources are
Literature
cited when specific
review
statements are made
and significant to the
project.
Excellent
,demonstrates clear
understanding and
Analysis
elaboration of
diagrams and flow
charts.
4
Describe good
sentence for main
purpose, scope,
method, result,
recommendation and
conclusion of project
without grammatical
errors.
3
Describe clear
sentence for main
purpose, scope,
method, result,
recommendation and
without grammatical
errors.
Clear explanations of
the project
Moderate explanations Not clear explanations Vague explanations No explanation of the

of the project
of the project
of the project.
project.
Methodology is clearly
presented, relevant
and appropriately
applied to project
development.
Methodology is clearly
presented, but not
appropriately or
adequately applied to
project development.
Good literature review.

Sources are cited when
specific statements are
made and significant to
the project.
Moderate literature
review . Sources are
cited when specific
statements are made
and significant to the
project.
Clear analysis and
demonstrates good
deal of understanding
of diagrams.
Good ,demonstrates
clear understanding
and elaboration of
diagrams and flow
charts.
2
Describe moderate
sentence for main
purpose, scope,
method, result,
recommendation and
with moderate
grammatical errors.
Methodology is
moderately presented
but not appropriately
or adequately applied
to project
development.
Only two sources of
literature review are
covered without
citation but related to
the project.
Moderate analysis
and demonstrates
good deal of
understanding
diagrams.
1
Describe less
sentence for main
purpose, scope,
method, result,
recommendation
and conclusion of
project with many
grammatical errors.
Methodology is not
clearly presented,
not appropriately or
adequately applied
to project
development.
Only one sources of
literature review is
covered without
citation and not
related to the
project.
Not very clear
analysis and no
understanding of
diagrams.
0
Sentence is not for
main purpose, scope,
method, result,
recommendation and
with many
grammatical errors.
No methodology is
presented.
No literature review is
presented.
No analysis is
presented
.
Page 66 of 74
Excellently defines
and shows process in
design
Use good testing
Implementati technique and
on & testing
suitable data. Good
result elaboration.
Specific and good
conclusion.
Conclusion
Objectives are
achieved.
Information is
excellently organized
Arrangement with well-constructed
paragraphs and
subheadings.
Diagrams and
Diagram &
illustrations are
illustration
excellent, neat and
accurate.
References are
significant to project
References
and very organized
with well-constructed
using APA format.
Good writing and no
grammatical , spelling
Writing
or punctuation errors.
Design
Very well defines and Clearly shows and

shows process in design elaborates the design
process.
Use good testing
Use suitable testing
technique and show
technique and show
clear result after testing. clear result after testing.
Moderately shows and

elaborates the design
process.
Use suitable testing
technique but not
show clear result after
testing.
Moderate conclusion.
Not clearly shows

and elaborate the
design process.
Use unsuitable
testing technique.
Not shown and

elaborate design
process.
no testing technique.
No specific and
clear conclusion.
No conclusion.
Information is
moderately
organized, but
paragraphs are not
well-constructed.
Diagrams and
illustrations are less
accurate.
Lack of information
Not organized.
Diagrams and
illustrations are
moderate and
accurate.
References are
references are
Reference are not
organized and
significant to the
and follow APA format. project but follow APA
and follow APA format.
format.
Diagrams and
illustrations are not
accurate.
No diagrams and
illustrations are
presented.
Reference does not

follow APA format.
No references
Clear writing and no

No grammatical
Moderate
grammatical spelling, or spelling or punctuation grammatical spelling,
punctuation errors.
errors in writing.
or punctuation errors
in writing.
Few grammatical,
Many grammatical,
spelling, or
spelling, or
punctuation errors in punctuation errors.
writing.
Specific and clear but

only shows a few
objectives are
achieved.
Information is very well
organized, and
paragraphs are wellconstructed.
Diagrams and
illustrations are good,
neat and accurate.
Clear but does not

show the objectives are
achieved.
Information is well
organized, but
paragraphs are not
well-constructed.
Page 67 of 74
APPENDIX N
Level 6: Development Demonstration Rubric
CRITERIA
Input
Development
5
Input Form 100%
complete
Suitable data 100%
can be added using
this form.
Output
Development
100% develop
User Interface
Development
Layout Exceptionally
attractive and userfriendly
Important elements
Easy to locate
Material - Organized
effectively
Project
Application
Development
System
Security and
Features
100% develop
Implement 100%.
4
Input Form More
than 90% complete
Suitable data
More than 90% can
be added using this
form.
More than 90%
develop
3
Input Form More
than 80% complete
Suitable data More
than 80% can be
added using this
form.
More than 80%
develop
2
Input Form More
than 50% complete
Suitable data
More than 50% can
be added using this
form.
More than 50%
develop
1
Input Form
Less than 50%
complete
Suitable data Less
than 50% can be
added using this form.
Less than 50% develop
Layout
Almost
exceptionally
attractive and userfriendly layout.
Important elements
Easy to locate
Material Almost effectively
organized
More than 90%
develop
Layout
Attractive and userfriendly layout
Layout
Not user-friendly
Layout
Not user-friendly
Important elements
Easy to locate most

of the important
elements.
Important elements
Difficult to locate most
of the important
elements.
More than 80%

develop
More than 50%

develop
Less than 50% develop
Implement up to
90%
Implement up to 80%
Implement more
than 50%
Implement less than

50%
Important elements
Easy to locate
Material Moderately
organized
0
0% develope the
input form of the
system.
0% develope the
output of the
system
Layout
Clutter and
confuse
Important
elements
Cannot locate
important
elements.
0% develop the
project
application
0% apply user
controls and
validation
controls
Page 68 of 74
Progress of
Project
Development
100% complete.
More than 90%

complete
More than 80%

complete
More than 50%

complete
Less than 50%

complete
0% complete the
progress of
project
development
Page 69 of 74
APPENDIX O
Level 6: Testing Demonstration Rubric
CRITERIA
Testing Plan
Unit Testing
Integration
Testing
System Testing
100% complete
testing plan
More than 90%

complete testing
plan
100% complete
unit testing
More than 90%

More than 80%
complete unit testing complete unit
testing
More than 90%
More than 80%
complete integration complete
testing
integration testing
100% complete
integration testing
100% complete
system testing
More than 90%

complete system
testing
More than 80%

complete testing
plan
More than 80%

complete system
testing
More than 50%

complete
testing plan
Less than 50%

complete
testing plan
0% complete
testing plan
More than 50%

complete unit
testing
More than 50%
complete
integration
testing
More than 50%
complete
system testing
Less than 50%

complete unit
testing
Less than 50%
complete
integration
testing
Less than 50%
complete
system testing
0% complete
unit testing
0% complete
integration
testing
0% complete
system testing
Page 70 of 74
APPENDIX P
Level 6: Implementation Demonstration Rubric
CRITERIA
More than 90%

complete
Minor Errors
More than 90%
complete
More than 80%

complete
Minor Errors
More than 80%
complete
More than 50%

complete
Minor Errors
More than 50%
complete
Less than 50%

complete
Major Errors
Less than 50%
complete
100% complete
More than 90%

complete
More than 80%

complete
More than 50%

complete
Less than 50%

complete
100% original Ideas,
90% original Ideas,
80% original Ideas,
More than 50%
Less than 50%
Originality
creative and
inventive
original Ideas,
creative and
inventive
Uses other
peoples ideas
but does not
give them credit.
Layout
Almost exceptionally
attractive and userfriendly layout.
Important elements
Easy to locate
Material Almost effectively
organized
Layout
Attractive and userfriendly layout
Layout
Not user-friendly
Layout
Not userfriendly
Layout
Clutter and
confuse
User interface
(layout)
Layout Exceptionally
attractive and
user-friendly
Important
elements Easy to locate
Material Organized
effectively
Important
elements
Difficult to
locate most of
the important
elements.
Important
elements
Cannot locate
important
elements.
Feasibility /
functionality
Marketability
(commercial
value)
Objective
Achievement
100% complete
100% complete
creative and inventive
creative and inventive
Important elements
Easy to locate
Material Moderately
organized
original Ideas,
creative and
inventive
Important
elements
Easy to locate
most of the
important
elements.
0% complete
Major Errors
No meaningful
attempt is made
to communicate
the projects
marketability.
Do not achieve
bjectives at all.
Page 71 of 74
APPENDIX Q
Level 6: Portfolio Rubric

Criteria
Required
items
Overall
Organization
All required items

are included, with
a significant
number of
additions.
Items are clearly
introduced, well
organized, and
creatively
displayed,
showing
connection
between items.
All required items

are included, with a
few additions.
Items are
introduced and
well organized,
showing
connection
between items.
All required items

are included.
A significant
number of
required items are
missing.
Only a slight
number of
required items are
included.
No work
submitted
Items are
introduced and
somewhat
organized,
showing some
connection
between items.
Items are
introduced, lack
of organization
and do not show
any connection
between items.
Items are not

introduced, lack
of organization
and do not show
any connection
between items.
Items are not

introduced and
not organized
Page 72 of 74
APPENDIX R
Level 6: Log Book Rubric

Criteria
Weekly
activities
Supervisor
signatures
Details
Neatness
5
All 15 weeks of
activities are
recorded in the log
book.
Supervisors
signature of
verification is shown
for all 15 weeks.
Log book is
exceptionally
detailed, provide an
in-depth look into
the project activities,
and reflects the
students
commitment.
The log book is
exceptionally neat.
The pages are in
very good condition,
handwriting is neat
and an obvious
effort has been
made to keep the
log book
presentable.
More than 12 weeks

of activities are
recorded in the log
book.
Supervisors
signature of
for more than 10
weeks.
Log book is
exceptionally
detailed, provide an
in-depth look into
the project activities.
More than 8 weeks

of activities are
recorded in the log
book.
Supervisors
signature of
for more than 8
weeks.
An appropriate
amount of detail is
used to explain the
project activities
done.
More than 5 weeks of

activities are recorded
in the log book.
Less than 5 weeks of

activities are recorded
in the log book.
No activity is
recorded in log
book.
Supervisors signature
of verification is shown
for more than 5 weeks.
Supervisors signature
of verification is shown
for less than 5 weeks.
No signature of
verification of the
supervisor.
Details are missing,

insufficient illustration of
the project activities
are done.
Details are missing and

do not illustrate the
project activities done.
No activity done is
recorded.
The log book is neat.

The pages are in
good condition,
handwriting is neat
and some effort has
been made to keep
the log book
presentable.
The log book is

averagely neat. The
pages are in
satisfactory,
readable condition,
handwriting is legible
and some effort has
been made to keep
the logbook
presentable.
The log book is

relatively neat. The
pages are in
unsatisfactory but still in
readable condition,
handwriting is legible
and less effort has
been made to keep
the logbook
presentable.
The log book is

unkempt. The pages
are in unsatisfactory
condition. It is in
virtually unreadable
condition. Handwriting
is illegible. Less effort
has been made to
keep the logbook
presentable.
The log book is in

unsatisfactory
condition. It is in
virtually unreadable
condition.
Handwriting is
illegible. No effort
has been made to
keep the logbook
presentable.
Page 73 of 74
APPENDIX S
Portfolio Checklist
Project Title : ................................................................
Log book
User manual
End product
Final report
Level 6
Log book
Design Report
Student Name
Analysis Report
No.
Registrati
on
Number
Project Proposal
Paper
Level 5
Verified by:
______________________
( Level 5 Supervisor Name )
Date :
Verified by:
______________________
( Level 6 Supervisor Name )
Page 74 of 74

Polytechnic FP621 Final Project Project Content

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Polytechnic FP621 Final Project Project Content

Uploaded by

Copyright:

Available Formats

1.

Total Credit Hour

Project Title Selection Criteria

i. Projects must be developed in accordance with the requirements of

1.3 Project Scope

application such as a packet sniffer to demonstrate the security threats that

Change project title

Attendance must be at least 80% , if not students coursework assesments

1.5 Responsibility and Roles

Once a the students project is approved, it will be the students responsibility

The main role of project coordinator is to ensure smooth operation of the

A project supervisor is an eligible lecturer that has been assigned by Head of

Table 2.1 : Teaching and Learning Process

2.3 Gantt Chart

Figure 2.1: Project Analysis & Design Gantt Chart

2.4 Project Flow (Level 5)

Project coordinator briefs level

Project analysis and design briefing

List of titles published

The projects title may be

Coordinator publishes group title

Discuss project with supervisor

Make any amendment that

Submit Project Planning Report

Submit project planning report

Project Analysis Report and oral

Submit project analysis report

Project Design Report and oral

Submit capstone project

Submit project design report

Figure 2.2 : Project Analysis and Design Flow Chart

2.5 Project Flow (Level 6)

Final year project review

Consultation with supervisor

Discuss the progress of

Proposal and project

Make any amendment

Present the testing stage

Make any amendment

Final report and presentation

Make any amendment

Submit final draft to

Figure 2.3: Project Flow Chart

3.1.1 Peer Assessment

Management & Entrepreneurial Skills

a. Soft Skill Presentation/Demonstration

Level 5 and Level 6

4.0 DOCUMENTATION FORMAT

Paper and Size

project report. The student must follow The American

that would be taken in implementing project. Students need to make

Table 4.3: Project Outcome

Documentation that contains major functions performed by

Student must produce a final product in softcopy (CD) to

4.3.1 Final Project Report

Chapter 5 (Development and Testing)

4.3.2 Project Analysis Report

Contents of Analysis Report

4.3.3 Project Design Report

Contents of Design Report

4.4 User Manual

4.6.2 Reminder To The Students

JABATAN PENGAJIAN POLITEKNIK

FINAL PROJECT LOG BOOK