LOG BOOK PROJECT ANALYSIS & DESIGN Type of Assessment Peer Assessment Presentation Demonstration Capstone 1. Proposal 2.

Portfolio 3. Logbook 4. 5. 6. 7. 8. Analysis Report Design Report Final Report End Product User Manual
Total

Level 5 Individual (20%) (30%) (10%) (10%) (10%) 100%

Group (15%) (5%) -

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, initiati ve, 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. 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 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.

POLYTECHNIC UNGKU OMAR JABATAN PENGAJIAN POLITEKNIK

FP521 PROJECT ANALYSIS AND DESIGN

LOG BOOK
DIPLOMA OF INFORMATION TECHNOLOGY (PROGRAMMING)

INFORMATION TECHNOLOGY & COMMUNICATION DEPARTMENT JABATAN PENGAJIAN POLITEKNIK

INFORMATION TECHNOLOGY & COMMUNICATION DEPT. POLYTECHNIC UNGKU OMAR KEMENTERIAN PENGAJIAN TINGGI MALAYSIA

STUDENT INFORMATION

Please insert photograph here

YEAR / SESSION

2012/DECEMBER 2012 STUDENT INFORMATION

NAME REGISTRATION NUMBER COURSE ADDRESS PROJECT INFORMATION TITLE SUPERVISOR FP521 CLASS PHONE NUMBER

Student Signature, ( )

WEEKLY ACTIVITIES REPORT Week : Date : Time :

Weekly planning

Weekly achievement

Reflective

Supervisors comment:

Verified by Supervisors Signature: Date:

( )

WEEKLY ACIVITIES 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 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 Weekly achievement 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

Level 5: Log Book Rubric

Criteria

5 All 15 weeks of activities are recorded in the log book. Supervisors signature of verification is shown for all 15 weeks.

4 More than 12 weeks of activities are recorded in the log book. Supervisors signature of verification is shown for more than 10 weeks. Log book is exceptionall y detailed, provide an in-depth look into the project activities.

3 More than 8 weeks of activities are recorded in the log book. Supervisors signature of verification is shown for more than 8 weeks. An appropriat e amount of detail is used to explain the project activities done.

2 More than 5 weeks of activities are recorded in the log book. Supervisors signature of verification is shown for more than 5 weeks. Details are missing, insufficient illustration of the project activities are done.

1 Less than 5 weeks of activities are recorded in the log book. Supervisors signature of verification is shown for less than 5 weeks. Details are missing and do not illustrate the project activities done.

0 No activity is recorded in log book.

Weekly activities

Supervis or signature s

No signature of verification of the supervisor.

Details

Neatness

Log book is exceptionall y detailed, provide an in-depth look into the project activities, and reflects the students commitmen t. The log book is exceptionall y neat. The pages are in very good condition, handwriting is neat and an obvious effort has been made to keep the log book presentable .

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, handwritin g is legible and some effort has been made to keep the logbook presentabl e.

The log book is relatively neat. The pages are in unsatisfactor y 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 unsatisfactor y 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 unsatisfactor y condition. It is in virtually unreadable condition. Handwriting is illegible. No effort has been made to keep the logbook presentable.