Guideline 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.1Objective

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.2Credit 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.

1.3Project Scope

Page 1 of 73

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. Programmingii. Networkingiii.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 user’s 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 application such as a packet sniffer to demonstrate the security threats that he read in the literature can actually happen in real life.

Page 2 of 73

1.3.3 Game Development

The project titles may range from game development areas such as, stand-alone 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.4Procedures

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.

1.5Responsibility and Roles

1.5.1 Student

Once a the student’s 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,

Page 3 of 73

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 coordinator’s 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 reportii. Group Formationiii.project Registrationiv.evaluationg) 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.

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:

Page 4 of 73

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 student’s time management (based on weekly schedule given by project coordinator) and also encourage the student’s 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 project’s 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.

2.0

Page 5 of 73

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.

Table 2.1 : Teaching and Learning ProcessLeve

lCourse Context

HourTeaching & Learning Implementation

5 Project Analysis & Design

30 LECTURE30 PRACTICAL

2 hours – Theory (Lecturer)2 hours – Practical (Supervisor)

6 Project 15 LECTURE45 PRACTICAL

1 hour – Consultation3 hours – Practical (Students complete their project in lab)

2.2 Planner

Refer to Appendix Project Analysis & Design planner.

Page 6 of 73

2.3 Gantt Chart

Level

Week / Activity W1

W2

W3

W4

W5

W6

W7

W8

W9

W10

W11

W12

W13

W14

W15

5

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 √

6

Reviewed project and proposal √Guidance & Consultation √ √ √ √ √ √ √ √ √ √ √ √ √ √ √1st Demonstration √2nd Demonstration √3rd Demonstration √Submit Final draft √Presentation, and submit capstone project √

Figure 2.1: Project Analysis & Design Gantt Chart

Page 7 of 73

2.4 Project Flow (Level 5)

Flow Chart Explanation Outcome

Project coordinator briefs level 5 students

The project’s title may be proposed by lecturers or students.

The coordinator or supervisor will release the list of approved projects to the students.

Discuss project with supervisor and make any amendment that necessary.

Submit project proposal and deliver oral presentation to supervisor.

Make any amendment that necessary.

Submit project planning report to supervisor.

Submit project analysis report and delivers oral presentation to supervisor.

Submit project design report and deliverers oral presentation to supervisor.

Submit capstone project to supervisor.

Project Proposal

Project planning

report

Project Analysis report

Project Design report

Capstone Project and

Project Document

Figure 2.2 : Project Analysis and Design Flow Chart

2.5 Project Flow (Level 6)

Page 8 of 73

START

Project analysis and design briefing

No

Discuss project with supervisor

Yes

Yes

END

List of titles published for students to choose

Students propose title

Students choose titles from list

Amendment

Supervisor agrees

Submit capstone project

Project Design Report and oral presentation

Project Analysis Report and oral presentation

Submit Project Planning Report

Proposal preparation and oral presentation

Fill in registration form and submit

Coordinator publishes group title

Yes

No

Yes

No

No

Amendment

Flow Chart Explanation Outcome

Proposal and project review.

Discuss the progress of the project development with supervision.

Present the development stage to the supervisor

Make any amendment that necessary

Present the testing stage to the supervisor.


Present the implementation stage to the supervisor


Submit final draft to supervisor

Submit final report to the supervisor. Present final presentation to evaluators.

Demontration 1

Demontration 2

Demontration 3

Final draft report

Final report, Capstone Project, User Manual, End Product.

Figure 2.3: Project Flow Chart

Page 9 of 73

START

Final year project review

Consultation with supervisor

1st Progress demonstration

2nd Progress demonstration

3rd Progress demonstration

END

Final report and presentation

Submit final draft

Amendment

Amendment

Amendment

Yes

Yes

Yes

No

No

No

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

Level 5 Level 6Individual Group Individual Group

Peer Assessment √ (20%) - √ (10%) -Presentation √ (30%) - √ (25%) -Demonstration - - √ (15%) -Capstone

1. Proposal - √ (15%) - -2. Portfolio - √ (5%) - √ (5%)3. Logbook √ (10%) - √ (10%) -4. Analysis

Report√ (10%) - - -

5. Design Report √ (10%) - - -6. Final Report - - - √ (20%)7. End Product - - - √ (10%)8. User Manual - - - √ (5%)

Total 100% 100%

3.1.1 Peer Assessment

Each student will be assessed by his group members based on:Table 3.2 : Peer Assessment

Level 5 Level 6Knowledge Social skills & ResponsibilitiesCommunication Management & Entrepreneurial

SkillsLeadership LeadershipTeam work 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 73

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

FP521 (Level 5) FP621 (Level 6)1. Report

Proposal2. Portfolio3. Log book4. Report

Analysis5. Report Design

15%5%

10%10%10%

1. Portfolio2. Log book3. Final Report4. End Product5. User Manual

5%10%20%10%5%

d. Portfolio

A student portfolio is a systematic collection of student’s work and related material that depicts a student's activities, accomplishments and achievements in one or more subjects. The collection should include evidence of student’s reflection and self-

Page 11 of 73

evaluation, guidelines for selecting the portfolio contents, and criteria for judging the quality of the work.

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 73

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. Items Description1. Cover Page 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.

2. Paper and Size

Use only high quality white A4 70-gram or A4 80-gram paper, size 210mm X 297mm.

3. Margin For each page, the margin should be: Left: 40 mm Right, Top and Bottom: 25 mm Header and Footer: 15 mm

4. Typesetting 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

5. Figure and Table

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.

6. Project Proposal (Level 5)

Project Proposal must be written in minimum of 10 pages length. It is only considered text EXCLUDING front page, appendix and references.

7. Analysis and Design Report (Level 5)

Analysis and Design Report must be written in maximum of 5 pages length. It is only considered text EXCLUDING front page, appendix and references.

8. Final Project Report (Level 6)

Final Project Report must be written in not more than 100 pages length. It only considered text EXCLUDING front page, appendix and references.

9. Paging Bottom right10. References 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

Page 13 of 73

student final project report. The student must follow The American Psychological Association (APA) reference citations style for references in text. See Appendix C1.

11. Binding Semester 5: All report must be using “Black Tape Binding” with white cover.Semester 6: Report cover must be “Buckram” (hardcover), gold printing and 14–18 times New Roman font face. See Appendix B1 and Appendix B2.

4.2 Proposal

Supervisor and coordinator will check student’s 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

DescriptionTable of ContentsEach student’s contribution to the relevant chapters and section should clearly be indicated by chapter in the proposal.

1.0 IntroductionBriefly explain on introductory project that carried out together current issue related to project.2.0 Problem StatementBriefly explain the problems that arise which made project chosen to be conducted.3.0 ObjectiveList 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 ScopeStudent 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 SignificantBriefly explain the interest of implementing project that carried out.6.0 Literature ReviewBriefly 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

Page 14 of 73

technology 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 MethodologyBriefly 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 ConclusionBriefly summarize the whole chapters that were implemented for the project.ReferenceReferences 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 ChartCreate the timeline of the project progress to complete the project.

Page 15 of 73

4.3 ReportTable 4.3: Project Outcome

Outcome DescriptionFinal 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.

Portfolio 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 non-technical 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.

Description

1. Cover & Report BackboneSee Appendix.

2. Plain paper3. Title Page

See Appendix.4. Declaration of Originality

Student makes declaration on their project originality, with the exclusion of quotations in the written report. See Appendix.

5. Approval for SubmissionSee Appendix

6. AcknowledgementsSee Appendix.

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

8. Table of ContentsEach student’s contribution to the relevant chapters and section should clearly beindicated by chapter in the project report I. See Appendix.

9. List of TablesList of table title with page numbers. The number sequence must follow the chapter. See Appendix.

10. List of Figures

Page 16 of 73

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.

11. List of AppendicesThis 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.

12. 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.13. 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.

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

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

16. Chapter 5 (Development and Testing)

Page 17 of 73

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.

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

18. ReferenceReferences 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 Contents of Analysis ReportAnalysis Report

A comprehensive analysis of a particular data using fact-finding t e chniques :1. Interviews2. Documentation review3. Observation4. Sampling5. 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 THR EE )

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 73

4.3.3 Project Design Report

Table 4.6: Design Report Content

Outcome Contents of Design ReportDesign 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 73

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 week2. FP621 – 1 hours theory and 3 hours practical in a week

4.6.4 Log Book Format

Forms and Conditions of the Log Book1. 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 73

POLYTECHNIC XXX

JABATAN PENGAJIAN POLITEKNIK

DIPLOMA OF INFORMATION TECHNOLOGY (PROGRAMMING)

INFORMATION TECHNOLOGY & COMMUNICATION DEPARTMENTJABATAN PENGJIAN POLITEKNIK

Page 21 of 73

FINAL PROJECT LOG BOOK

KPT LOGO POLYTECHNIC LOGO

INFORMATION TECHNOLOGY & COMMUNICATION DEPT.POLYTECHNIC XXX

KEMENTERIAN PENGAJIAN TINGGI MALAYSIA

STUDENT INFORMATION

YEAR / SESSION

STUDENT INFORMATION

NAME

REGISTRATION NUMBER

CLASS

COURSE PHONE NUMBER

ADDRESS

PROJECT INFORMATION

TITLE

SUPERVISOR

Student Signature,

…………………………… ( )

Page 22 of 73

Please insert photograph here

CONTENTS PAGE

1.0 Introduction2.0 Reminder to the Students3.0 Meeting Duration4.0 Format of Log Book5.0 Weekly Activities Report

Page 23 of 73

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

1) Design Order form interfaces2) Create following tables in Ms Access

database:a) Order tableb) Customer tablec) Stock table

3) Create tables relationships.4) Connect Order form and Order table

using PHP and SQL.

Weekly achievement

1) Completed2) All tasks are completed accept Stock

table still in progress.3) Completed4) Unsuccessful.

Reflective

1) I can’t complete item 4 because time limitation2) I understood how to create table relationship

Supervisor’s comment:

1) Order form - OK2) Data group in Order table is not fixed. Please modify where applicable.3) Please refer to suitable book for the connection above.

Verified by

Supervisor’s Signature: Date: 20/07/2012

………………………………

(Amyzah binti Ahmad)

Figure 4.1: Log Book Example

Page 24 of 73

Table 4.1: Reference List for BookBasic 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.

Calfee, R. C., & Valencia, R. R. (1991). APA guide to preparing manuscripts for journal publication. Washington, DC: American Psychological Association.

Edited Book, No Author

Duncan, G.J., & Brooks-Gunn, J. (Eds.). (1997). Consequences of growing up poor. New York: Russell Sage Foundation

Edited Book with an Author or Authors

Plath, S. (2000). The unabridged journals (K.V. Kukil, Ed.). New York: Anchor.

A Translation Note: When you cite a republished work in your text, it should appear with both dates: Laplace (1814/1951).

Laplace, P. S. (1951). A philosophical essay on probabilities. (F. W. Truscott & F. L. Emory, Trans.). New York: Dover. (Original work published 1814).

Edition Other Than the First

Helfer, M.E., Keme, R.S., & Drugman, R.D. (1997). The battered child (5th ed.). Chicago: University of Chicago Press

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.

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.

Multivolume Work Scruton, R. (1996). The eclipse of listening. The New Criterion, 15(30), 5-13.

Page 25 of 73

5.0 CONCLUSION

5.1 ReferencesTable 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), 5-13.

Article in a Magazine

Henry, W. A., III. (1990, April 9). Making the grade in today's schools. Time, 135, 28-31.

Article in a Newspaper

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.

Schultz, S. (2005, December 28). Calls made to strengthen state energy policies. The Country Today, pp. 1A, 2A.

Letter to the Editor

Moller, G. (2002, August). Ripples versus rumbles [Letter to the editor]. Scientific American, 287(2), 12.

Review 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 73

Table 5.2: Reference List for Other Print Sources

An Entry in an Encyclopedia

Bergmann, P. G. (1993). Relativity. In The new encyclopedia britannica (Vol. 26, pp. 501-508). Chicago: Encyclopedia Britannica.

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.

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

Dissertation Abstract

Yoshida, Y. (2001). Essays in urban transportation (Doctoral dissertation, Boston College, 2001). Dissertation Abstracts International, 62, 7741A.

Government Document

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.

Report from a Private Organization

American Psychiatric Association. (2000). Practice guidelines for the treatment of patients with eating disorders (2nd ed.). Washington, D.C.: Author.

Conference Proceedings

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.

Published Conference Paper

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

Page 27 of 73

Malaya.Unpublished Conference Paper

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.

Academic Exercise / Thesis (Unpublished)

Santini, S. N. (2008). Research methods for business: A skill building approach. Unpublished master’s thesis, University of Malaya, Kuala Lumpur.

Page 28 of 73

Table 5.3: Reference List for Electronic Sources

Article From an Online Periodical / Databases

Online articles follow the same guidelines for printed articles. Include all information the online host makes available, including an issue number in parentheses.

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/

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/cite living

Online Scholarly Journal Article

Author, A. A., & Author, B. B. (Date of publication). Title of article. Title of Journal, volume number. Retrieved month day, year, from http://www.someaddress.com/full /url/

Kenneth, I. A. (2000). A Buddhist response to the nature of human rights. Journal of Buddhist Ethics, 8.Retrieved 20 February 2001, from http://www.cac.psu.edu/jbe/twocont.html

Online Scholarly Journal Article with Printed Version Available

If the article appears as a printed version as well, the URL is not required. Use "Electronic version" in brackets after the article's title.

Whitmeyer, J.M. (2000). Power through appointment [Electronic version]. Social Science Research, 29, 535-555.

Article From a Database

When referencing material obtained from an online database (such as a database in the library), provide appropriate print citation information (formatted just like a "normal" print 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.

Smyth, A. M., Parker, A. L., & Pease, D. L. (2002). A study of enjoyment of peas. Journal of Abnormal Eating, 8(3). Retrieved 20 February 2003, from PsycARTICLES database.

Nonperiodical Web Document, Web Page, or Report

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.

Chapter or Section of a Web Document

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

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/

Page 29 of 73

http://www.someaddress.com/full /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.

mod_rewrite.html

Online Forum or Discussion Board Posting

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.

Frook, B. D. (1999, July 23). New inventions in the cyberworld of toylandia [Msg 25]. Message posted to http://groups.earthlink.com/forum/messages/00025.html

Computer Software

Ludwig, T. (2002). PsychInquiry [computer software]. New York: Worth.

Page 30 of 73

Table 5.4: Reference List for Other Non-Print Sources

Interview, Email, and Other Personal Communications

No personal communication is included in your reference list; instead, parenthetically cite the communicators name and the date of the communication in your main text only.

(E. Robbins, personal communication, January 4, 2001).A. P. Smith also claimed that many of her students had difficulties with APA style (personal communication, November 3, 2002).

Motion Picture 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).

A Motion Picture or Video Tape with International or National availability

Smith, J.D. (Producer), & Smithee, A.F. (Director). (2001). Really big disaster movie [ Motion picture]. United States: Paramount Pictures

A Motion Picture or Video Tape with Limited Availability

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)

Television Broadcast or Series Episode

Producer, P. P. (Producer). (Date of broadcast or copyright). Title of broadcast [ Television broadcast or Television series ]. City of origin: Studio or distributor.

Single Episode of a Television Series

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.

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.

Television Broadcast

Important, I. M. (Producer). (1990, November 1). The nightly news hour [Television broadcast]. New York: Central Broadcasting Service.

A Television Series

Bellisario, D.L. (Producer). (1992). Exciting action show [Television series]. Hollywood: American Broadcasting Company.

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

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 73

6.0 APPENDICESAPPENDIX A

Project Planner

LEVEL WEEK TASK OUTCOME

1 Student Registration

5

2

Divide students into groups of two-three.

Discuss project title. Assign each group to a

supervisor Discuss project development Create project capstone Discuss methodologies

Project registration form

3 Discuss and prepare proposal Draft proposal paper

4 Discuss project proposal Present proposal Get supervisor’s approval

5 Discuss Preliminary

Investigation Prepare fact-finding materials

6 Discuss the tasks in planning a

project Develop a plan

7 Discuss and construct Gantt

Chart Prepare a planning report

8 Discuss preliminary analysis Perform fact-finding Analyze the gathered

information

Presentation 1(Proposal Report)

9 Discuss detailed analysis Design data analysis

10 Discuss detailed analysis Design diagram

11 Discuss detailed analysis Design entity relationship

diagrams

12 Discuss and prepare analysis

report. Present analysis report

Presentation 2(Analysis Report)

13 Discuss project design Illustrate project Design

14 Discuss input design Design effective source

documents and input controls.

Page 32 of 73

15 Discuss output design Present project design

Presentation 3(Design report)

16 Compile the project

documentation Demonstrate initial prototype

for a new system

17Demonstration

Capstone ProjectProject document

LEVEL WEEK TASK OUTCOME6 1 Student registration

2 Project proposal review Review project plan and project

design

3 Discuss and develop problem

specification, design, and code the program

4 Report and discuss the progress

of the project development Develop the project

PEER ASSESSMENT 1


of the project development Develop the project Demonstration



DEMONSTRATION 1









11 Discuss testing Conduct unit testing,

integration testing and system testing

DEMONSTRATION 2

12 Discuss the findings of project testing

PEER ASSESSMENT 2

Page 33 of 73

Rectify the errors detected in the system

13 Review Outcome Perform implementation plan Demonstration

14 Review Outcome Perform implementation plan Demonstration

15 Compile project documentation Present the project DEMONSTRATION 3

16 Inter-polytechnic final project competition PEER ASSESSMENT 3

17 FINAL PRESENTATION

Page 34 of 73

APPENDIX BGantt Chart

Level WEEK / ACTIVITY W1

W2

W3

W4

W5

W6

W7

W8

W9

W10

W11

W12

W13

W14

W15

W16

W17

5

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 √

6 Reviewed project and proposal √Guidance & Consultation √ √ √ √ √ √ √ √ √ √ √ √ √ √ √1st Demonstration √2nd Demonstration √

Page 35 of 73

Level WEEK / ACTIVITY W1

W2

W3

W4

W5

W6

W7

W8

W9

W10

W11

W12

W13

W14

W15

W16

W17

3rd Demonstration √Submit Final draft √Presentation, and submit capstone project

√

Page 36 of 73

APPENDIX CLevel 5: RPP

POLITEKNIK XXXSEMESTER LESSON PLAN

DEPARTMENT OF INFORMATION AND COMMUNICATION TECHNOLOGY

SESSION: ________

LESSON PLAN

Lecturer’s Name : Session : Department / Unit : INFORMATION & COMMUNICATION TECHNOLOGY Class / Club : Code & Course Name : FP521 - PROJECT ANALYSIS AND DESIGN

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 community4. 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; and9. Demonstrate effective leadership and teamwork skills.

Page 37 of 73

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 )

Topics, General Outcomes, Specific Outcomes and Coursework Assessment

Implementation date Notes/Reflection

W1 STUDENT REGISTRATION WEEK

W2

1.0 INTRODUCTION1.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. Timeb. Costc. Scope

1.1.5 Demonstrate knowledge and understanding of intellectual properties

1.1.6 Explain common types of intellectual property:a. Patentb. Trademarksc. Trade secretsd. Copyrighte. 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, teamwork, leadership, and responsible ethical and moral behaviour in project development

Page 38 of 73

Week(Period )



W3

1.2 Explain System Development life Cycle (SDLC).1.2.1 Describe the activities in different phases of SDLC.

a. Planningb. Analyzec. Designd. Developmente. Testingf. Implementationg. Maintenance

1.2.2 Identify the various types of life cycle models such as:a. Waterfall modelb. Spiral modelc. Fountain modeld. Prototyping modele. Iterative and Incremental developmentf. Rapid Application Development (RAD)g. Joint Application Development (JAD)h. Extreme Programming (XP)i. Agile Model

1.3 Discuss project reports and documentation1.3.1 Describe types of reports:

a. Portfolio reportb. Planning reportc. Analysis reportd. Design report

1.3.2 Explain project documentation requirement , structures and styles.

1.3.3 Justify the importance of documentation.1.4 Demonstrate the use of project portfolio.

1.4.1 Create project portfolio that includes the following such as:a. Technical memob. User documentationc. Technical requirementd. Phases of project life cyclee. Matrix table comprises of Summary of referencesf. Self or peer evaluation statement

W4 1.5 Draft project proposal1.5.1 Define the purpose of a project proposal.

Page 39 of 73

Week(Period )



1.5.2 Determine the potential product or software that needs to be developed with high level programming language:a. Database programmingb. Web programmingc. Multimedia programmingd. Games programminge. 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 Synopsisb. Introduction / backgroundc. Problem Statementd. Objectivese. Project Significancef. Methodologyg. Conclusion

1.5.6 Prepare proposal paper and present the proposal.

W5

2.0 PLANNING2.1 Discuss Preliminary Investigation

2.1.1 Identify the steps in preliminary investigation:a. Understand the problem or opportunityb. Define the project scope and constraintsc. Perform fact-findingd. Evaluate feasibilitye. Estimate project development time and costf. 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.

W6 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 projecta. Objectives of planb. Develop a planc. Construct project planning diagram

Page 40 of 73

Week(Period )



d. Identify timing duration of each activity in planning diagrame. Identify costs and labor/personnel associated with each

activity

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

W8

3.0 ANALYSING3.1 Conduct Preliminary Analysis

3.1.1 Identify the following elements related to project requirements:a. Inputb. Outputc. Processd. Performancee. Control

3.1.2 Justify in depth the techniques used in fact-finding:a. Interviewsb. Documentation reviewc. Observationd. Questionnairese. Samplingf. Research

W9 3.1 Conduct Preliminary Analysis3.1.3 Use the appropriate technique of fact-finding.3.1.4Analyze the gathered information.

W103.2 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 Feasibilityb. Operational Feasibilityc. Economic Feasibility

W11 3.3 Construct Detailed Analysis3.3.1 Identify the techniques employed in analysing the information:

a. Entity Life Historyb. Relational Data Analysisc. Context Diagram

Page 41 of 73

Week(Period )



d. Data Flow Diagramse. Entity Relationship Diagrams

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

W13

4.0 DESIGNING4.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 controls4.2 Create Input Design

4.2.1 Differentiate data capture and data entry.4.2.2 List the objectives of input design.

W14

4.2.3 Explain the input and data entry methods:a. Batch inputb. 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.

W15

4.3 Create Output Design4.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 reportsb. Screens displayc. Audiod. E-maile. Computer microfilmf. Internet-based

4.3.4 Develop detail reports, exception reports and summary reports.

4.3.5 Explain general principles important to output design:a. Guidelinesb. Process

4.3.6 Perform output design for a new system as a case study.

Page 42 of 73

Week(Period )



W16

4.4 Create a prototype to validate the design4.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 project’s prototype.

4.5 Compile the project documentation.4.5.1 Prepare project documentation based on:

a. Introduction of the projectb. Literature reviewc. Methodology

Prepared by : ------------------------------------------ Signature of Course Lecturer Date :

Approved by : -------------------------------------------------- Signature of Deputy Director (Academic) / Head of Department / Programme Leader

Date :

APPENDIX D

Level 6: RPP

POLITEKNIK XXXSEMESTER LESSON PLAN

DEPARTMENT OF INFORMATION AND COMMUNICATION TECHNOLOGY

SESSION:_______

Page 43 of 73

LESSON PLAN

PROGRAMME : COURSE CODE : FP621COURSE NAME : PROGRAMMING PROJECTNAME OF LECTURER :

Week(Period )



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 STUDENT REGISTRATION WEEK

Page 44 of 73

Learning Domains (LD)LD1: Knowledge LD2: Practical Skills LD3: Communication SkillsLD4: Critical Thinking and Problem Solving

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

Week(Period )



W2

1.0PROJECT PROPOSAL REVIEW1.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.

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.

Briefing on the CLOs, Topics, assessments, SLT requirements of this course, etc.

Do Entrance Survey

W3

2.0DEVELOPMENT2.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.

W42.1.3 Develop the project application using an appropriate

programming language and development tools.PEER ASSESSMENT

W5 2.1.4 Apply secure coding and features by implementing the user controls, validation control etc.

W6 2.1.5 Review the system’s program and overall development.

2.1.6 Perform debugging. Identify the errors.

Page 45 of 73

Week(Period )



DEMONSTRATION 1W7 SEMESTER BREAK Hari Raya Aidilfitri (19 &

20.8.2012)

W8

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.W9 2.2.3 Maintain a change log for each new version or new

revision status.

W10 2.2.4 Keep track of work efforts individually (report time).

W11

2.2.5 Document and present the report of the progress development of the project.


i. Develop problem specification, design and code the program.

ii. Report the progress of the project development

DEMONSTRATION 2

Page 46 of 73

Week(Period )



W12

3.0TESTING3.1 Understand type of testing in IT related project.

3.1.1 Explain different types of software testing:a. Unit testingb. Integration testingc. 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 2W13 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.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 project’s requirement

specifications.


i. Understand type of testing in IT related project.ii. Conduct testing in a project.

Page 47 of 73

Week(Period )



DEMONSTRATION 2

W14

4.0IMPLEMENTATION4.1 Present Outcome for review.

4.1.1 Present the Time and Resource Plan:a. Milestones and Outcome for defined activitiesb. Persons responsible of each activity and deliverablec. Participants in each activityd. 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 requirementsb. 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 planb. Interim Reportc. Complete specification and design

Page 48 of 73

Week(Period )



W15

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.


i. Present Outcome for review.ii. Implement the project.

DEMONSTRATION 3

W16 5.0DOCUMENTATION5.1 Prepare project documentation.

5.1.1 Review the formalize and completed project documentation consist of:a. Project planb. Requirement specificationc. Final designd. Test description and resultse. Major findings and conclusionsf. Further work and recommendationsg. 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.5.1.4 Provide a compilation of the following:

Page 49 of 73

Week(Period )



a. Executable program or applicationb. Source code

PEER ASSESSMENT 3

W17

5.1.5 Present the final product.


i. Prepare project documentation.

PRESENTATION

Do Exit Survey

W18 STUDY WEEK

W19EXAMINATION WEEK

W20

Prepared by : ------------------------------------------ Signature of Course Lecturer Date :

Approved by : ---------------------------------------------------------- Signature of Deputy Director (Academic) / Head of Department / Programme Leader

Date :

Page 50 of 73

APPENDIX EAPA Format

GENERAL RULESSingle Author Last name first, followed by author

initials.Berndt, T. J. (2002). Friendship quality and social development. Current Directions in Psychological Science, 11, 7-10.

Two Authors List by their last names and initials. Use the ampersand (&) instead of "and."

Wegener, D. T., & Petty, R. E. (1994). Mood management across affective states: The hedonic contingency hypothesis. Journal of Personality & Social Psychology, 66, 1034-1048.

Three to Six Authors List by last names and initials; commas separate author names, while the last author name is preceded again by ampersand (&).

Kernis, M. H., Cornell, D. P., Sun, C. R., Berry, A., & Harlow, T. (1993). There's more to self-esteem than whether it is high or low: The importance of stability of self-esteem. Journal of Personality and Social Psychology, 65, 1190-1204.

More Than Six Authors

If there are more than six authors, list the first six as above and then "et al.," which stands for "and others." Remember not to place a period after "et" in "et al."

Harris, M., Karper, E., Stacks, G., Hoffman, D., DeNiro, R., Cruz, P., et al. (2001). Writing labs and the Hollywood connection. Journal of Film and Writing, 44(3), 213-245.

Author - Malay Names(without family names)

Omit bin/binti Asmah Binti OmarCite asAsmah Omar. (1991). Kemahiran berbahasa. Kuala Lumpur: Penerbitan Pustaka Antara.

Author - Chinese Names

First name first, followed by author initials.

Chu Chin NingCite asChu, C. N. (1995). Simulated counter-current adsorption processes; A comparison of modeling strategies. Chemical Engineering Journal, 56, 59-65.

Page 51 of 73

Author - Chinese Names with English Names

Family names followed by the initials of the English name and the author initials

Vincent Foo Hiap KhianCite asFoo, V. H. K. (1983). Sarawak: Mini episodes of the past. Petaling Jaya: Fajar Bakti.

Author-Indian & Sikh Names(without family names)

Omit d/o, s/o, a/l, a/p Narrayani a/p Jeganathan.Cite asNarrayani Jeganathan. (2009).

Inherited Names Cite as it is Raja Ahmad Niza.Cite asRaja Ahmad Niza. (2009).

Conferred titles Omit title Tun Mahathir MohamadCite asMahathir Mohamad

Local Government Institution as Author

Cite under state and followed by the name of department in Malay

Pahang, Jabatan Alam Sekitar. (2009).

Foreign Government Institution as Author

Cite under state or country and followed by the name of department in English

New Zealand, Department of External Affairs. (2009).

Unique Corporate Body Names

If the name starts with Foundation (Yayasan), Board (Lembaga), cite as it is given

Yayasan Sabah. (2009).

Organization as Author

American Psychological Association. (2003).

Conference Names with Numbers

Do not include the numbers Fifth Asia-Pacific Physics ConferenceCite asAsia-Pacific Physics Conference

Unknown Author Merriam-Webster's collegiate dictionary (10th ed.).(1993). Springfield, MA: Merriam-Webster.

Page 52 of 73

APPENDIX F

Level 5 : Proposal Report Rubric

CRITERIA 5 4 3 2 1 0Introduction 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

Unclear and incomplete understanding of the project to be taken

Vague about the project to be undertaken

Problem Statement

Always clearly explains the problems

Clearly explain the problems most of the time

Sometimes clearly explain the problems

Occasionally explains the problems faced

Vague explanations of the problems

No problem stated

Objectives The main objective is very clear during first submission.

The main objective is clear during first submission.

The main objective needs to be improved

The main objective is clear after review.

The main objective is clear with guidance.

The main objective is not clear

Scope Always clearly clarify system scope and user scope

Clearly clarify system scope and user scope most of the time

Most of the requiredsystem scope and user scope are included

Few of the requiredsystem scope and user scope are included

No clear clarification between system scope and user scope

Do not clarify user between system scope and user scope

Project Significant(cannot be measured)

Very clear explanation of the project significance

Clear explanation of the project significance

Somewhat clear explanations of project significant

Less clear about project significant

State very little about the project significance

Do Not state the project significance

Literature Review

The study carried out very clearly in evidence

The study carried out in few evidence

Less evidence of research done

No evidence of research done

Explanation is too general

Not state the explanation

Methodology Methodology associated with building projects.

Most methodology associated with building projects.

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.

References More than 5 from 5 from books or Less than 5 Have 5 reference Less than 5 Not have

Page 53 of 73

books or journals and follow APA styles. Not have website reference.

journals but not follow APA styles. Not have website reference.

references books or journals but follow APA styles. Not have website reference.

include books, journals and website. Follow APA styles.

reference include books, journals and website and not follow APA styles.

references.

Gantt ChartChart is accurate based on project schedule.

Chart is accurate based on project schedule but less specific.

Chart is accurate based on project schedule but not specific.

Chart is less accurate based on project schedule.

Chart is not accurate based on project schedule.

Not have chart.

CostMeets all normal requirements and reasonable

Meets most normal requirements and reasonable

Meet few normal requirements.

Meet very little normal requirements.

None meet the normal requirements.

Not cost specified.

ConclusionStudent concludes the presentation confidently

Student concludes the presentation

Student concludes the presentation with few point.

Conclusion is vague.

Inappropriate conclusion.

No conclusion.

Page 54 of 73

APPENDIX G

Level 5: Analysis Report Rubric

CRITERIA 5 4 3 2 1 0Fact finding technique

Questions are answered thoroughly with suitable techniques supported by data from the fact finding.

Demonstrate most techniques to answer the question.

Demonstrate many techniques to answer the question.

Demonstrate some suitable technique to answer the question.

Demonstrate little suitable technique to answer the question.

Demonstrate little or no suitable technique to answer the question.

Data Accurate representation of the data using suitable diagrams. Data is precise with accepted values.

Good representation of the data using suitable diagram s but data lacks precision.

Brief representation of the data using suitable diagrams but data lacks precision.

Contains only some data which use suitable diagrams.

Contains only little data or data is not accurate

Data is not presented.

Analysis Analysis is insightful. All data are logically analyzed.

Analysis is insightful. All data are most logically analyzed.

Analysis is general. Data are logically analyzed for the most part.

Contains only some data analysis

Contains only little data analysis

Analysis is not presented

Literature Review

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 literature’s relationship to the project.

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 55 of 73

APPENDIX HLevel 5: Design Report Rubric

CRITERIA 5 4 3 2 1 0Graphical User Interface (GUI)(exclude DNS Project)

Exemplary user interface, superior over GUI’s for similar purposes, many innovative ideas.

innovative ideas and user friendly.

Some innovative ideas, relatively user friendly.

Difficult to understand and only little effort have been spent to design the GUI.

GUI are poorly design

GUI is not shown.

Design problem solution

Clear and complete understanding of design goal and constraints for the whole project

Clear and complete understanding of design goal and constraints for the most part of the project

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

Diagram Reliability

All diagrams are constructed accurately based on information provided and calculated.

Most diagrams are accurately constructed based on information provided and calculated.

Some diagrams areaccurately constructed based on information provided and calculated.

Diagram are suitable based on information provided

Does not identify appropriate information to include in diagram.

Diagram not shown.

Problem Solving Using Diagram

All diagrams are effectively used to work towards a verifiable solution

Most of the diagrams are effectively used to work towards a verifiable solution

Identifies some items to include in the diagrams that will lead toward a solution

Diagrams are suitable that will lead toward a solution

Diagrams areinappropriate

No diagram used.

Page 56 of 73

APPENDIX ILevel 5: Peer Assessment Rubric

CRITERIA 5 4 3 2 1 0

KNO

WLE

DG

E

Comprehension

Very clear, comprehensive understanding of theoretical foundations.

Good grasp of theoretical foundations.

Fair grasp of theoretical foundations.

Vague conceptions, but lack of clarity of theories and/or models.

Lack of understanding of basic theories & models.

No understanding of basic theories & models.

ContentGreat knowledge in field of study.

Good amount of knowledge in field of study.

Fair amount of knowledge in field of study.

Very basic knowledge base.

Very limited knowledge.

Lack of knowledge.

COM

MU

NIC

ATI

ON

NonverbalLanguage

Excellent gestures and postures.

Good gestures and postures.

Good gestures. Weak gestures and postures.

Bad gestures and postures.

No gestures and postures.

Eye ContactGood eye contact with the audience.

Consistent use of direct eye contact with the audience.

Frequently looking at the audience.

Sometimes look at the audience.

Rarely look at the audience.

No eye contact (read the text).

Visual AidsAttractive, big and clear.

Big and clear. Small but clear. Big but unclear. Small and unclear. Unclear.

LEAD

ERSH

IP

Working withOthers

Listens to, shares with, and supports the efforts of others.

Always listens to, shares with, and supports the efforts of others.

Usually listens to, shares with, and supports the efforts of others.

Often listens to, shares with, and supports the efforts of other.

Rarely listens to, shares with, and supports the efforts of others.

Does not listen to, shares with, and supports the efforts of others.

ContributionsA definite leader who contributes a lot of effort.

A good group member who tries hard.

A strong group member who tries hard.

A satisfactory group member who does what is required.

Rarely participate. Refuse to participate.

Focus on the Task

Consistently stays focuses.

Always stays focuses.

Stays focuses most of the time.

Stays focuses some of the time.

Rarely focuses. Lost focuses.

Problem-solving

Actively looks for and suggests solutions to problems.

Always looks for and suggests solutions to problems.

Most of the time looks for and suggests solutions to

Refines solutions suggested by others.

Does not suggest or refine solutions.

Does not try to solve problems.

Page 57 of 73

problems.TE

AM W

ORK

ParticipationFully participated. Always participate. Most of the time

participated.Some of the time participated.

Rarely participated. Does not participate.

ListeningListens carefully to others’ ideas.

Always listens to others’ ideas.

Usually listens to others’ ideas.

Sometimes listens to others’ ideas.

Rarely listens to others and often interrupts them.

Does not listen to others and often interrupts them.

FeedbackOffered detailed, constructive feedback when appropriate.

Offered constructive feedback when appropriate.


Occasionally offered constructive feedback.

Rarely offered constructive or useful feedback.

Did not offer constructive or useful feedback.

Cooperation

Treated others respectfully and shared the workload fairly.

Usually treated others respectfully.

Usually shared the workload fairly.

Sometimes treated others disrespectfully or did not share the workload fairly.

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

Treated others disrespectfully or did not share the workload fairly.

Time Management

Completed assigned tasks on time.

Always completed assigned tasks on time.

Usually completed assigned tasks on time.

Sometimes completed assigned tasks on time.

Often did not complete assigned tasks on time.

Did not complete most of the assigned tasks on time.

Page 58 of 73

APPENDIX J

Level 5 And 6: Soft Skill Presentation/Demonstration Rubric

Criteria 5 4 3 2 1 0

Communication

Communicates and interacts with audience with a high degree of effectiveness and ideas

Communicates and interacts with audience with a moderate degree of effectiveness and ideas

Communicates and interacts with audience with some effective ideas

Communicates and interacts with audience with considerable ideas

Communicates and interacts with audience with limited ideas

Little to no communication or interaction with audience

Answering Ability

Accurately answer all questions posed with high confidence.

Accurately answer almost all questions posed with high confidence.

Accurately answer a few questions posed with confidence.

Able to answer some questions with lack of confidence

Able to answer some questions posed but lacks of confident

Unable to answer all questions posed and has no confident.

Posture and Eye Contact

Hold attention of entire audience with the use of direct eye contact, student displays relaxed, self-confident with no mistakes.

Hold attention of entire audience with the use of direct eye contact, student displays relaxed, self-confident with few mistakes.

Consistent use of direct eye contact with audience, displays no nervousness and stress.

Consistent use of direct eye contact with audience, displays modest nervousness and stress.

Displayed minimal eye contact with audience, show nervousness and stress.

No eye contact with audience, show nervousness and stress.

Enthusiasm

Demonstrates a strong, positive feeling about topic during entire presentation

Demonstrates a positive feeling about topic during entire presentation.

shows some positive feelings towards the topic.

Occasionally Shows interest towards the topic presented.

Shows lack of interest in the topic presented.

Shows no interest at all in topic presented

Leadership & Team work

Good leadership role and works as a cohesive unit to make the presentation

Assume leadership role and works as a cohesive unit to make the presentation

Assist in coordinating task and works together to make the presentation

Minimum contribution coordinating task and work together to make presentation

Minimum contribution to the presentation

No contribution to the presentation

Self Appearance Shows an excellent attitude during the

Shows presentable attitude during the

Shows a good attitude along the

Shows a mild attitude along the

Shows a poor attitude along the

Does not show a good attitude in the

Page 59 of 73

presentation session. Dresses nicely & appropriately (tie, student’s card, jacket, shoes)



presentation session. Dressing appropriately (tie, student’s card, jacket, shoes).

presentation session. Dressing appropriately (tie, matric card, jacket, shoes).

presentation session. Dressing inappropriately.

Material and Added Tools

Used full effectively material and new technology to explain and organized information along the presentation session.

Used effectively material and new technology to explain and organized information along the presentation session.

Used effectively material and added tools to explain and organized information along the presentation session

Used with moderate effectiveness material and added tools to explain and organized information along the presentation session

Minimal using of material and added tools to explain and organized information along the presentation session

Does not use any material or tools to explain and organized information along the presentation session

Intonation and volume

Intentionally adjusts intonation and volume to achieve purpose.

Adjusts intonation and volume appropriately to make the presentation attractive.

Voice and the intonation is slow. Not enough to impede understanding.

Speaks too fast or slow in a way that impedes understanding. Voice and the intonation is slow.

Voice and the intonation is not clear.

Voice and intonation are not heard.

Page 60 of 73

APPENDIX KLevel 6: Peer Assessment Rubric

SOCI

AL S

KILL

S &

RES

PON

SIBI

LITI

ES


Self Expression

Integrates own feelings, ideas and experiences with those of others.

Always integrates own feelings, ideas and experiences with those of others.

Regularly and accurately expresses own feelings, ideas and experiences.

Sometimes expresses personal feelings, ideas and experiences.

Rarely expresses personal feelings, ideas and experiences.

Does not express personal feelings, ideas and experiences.

Response to Others

Listens actively to others.

Always listens actively to others.

Regularly listens actively to others.

Sometimes listens attentively to others.

Rarely listens to others.

Does not listen to others.

CooperationShows consideration for others.

Always shows consideration for others.

Regularly shows consideration for others.

Sometimes shows consideration for others.

Rarely shows consideration for others.

Does not show consideration for others.

RespectUses appropriate language when talking with peers.

Always uses appropriate language when talking with peers.

Regularly uses appropriate language when talking with peers.

Sometimes uses appropriate language when talking with peers.

Rarely uses appropriate language when talking with peers.

Does not use appropriate language when talking with peers.

Group Interaction

Works well with others.

Always works well with others.

Regularly works well with others.

Sometimes works well with others.

Rarely works well with others.

Does not work well with others.

Group Decision-making

Participate in the decision-making process.

Always participate in the decision-making process.

Regularly participate in the decision-making process.

Sometimes participate in the decision-making process.

Rarely participate in the decision-making process.

Does not participate in the decision-making process.

MAN

AGEM

ENT

&

ENTE

RPRE

NEU

RAL

SKIL

LS

Planning

Sets challenging goals with a step-by-step plan and time frame for achieving them.

Sets realistic, attainable goals; uses a process for achieving them.

Routinely sets goals; requires assistance to establish a process for achieving goals.

Occasionally sets goals; does not have a process for achieving goals.

Rarely sets goals; does not have a process for achieving goals.

Does not set goals; does not have a process for achieving goals.

Accountability

Sets goals, and achieves them ahead of schedule; offers to mentor others.

Sets and achieves goals on schedule.

Sets and achieves goals, or has reasonable explanation for not doing so.

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.

Renewed Commitmen

t

Sets new and challenging goals independently.

Sets challenging goals independently.

Sets new goals independently.

Requires assistance to set new goals.

Lacks motivation to set new goals.

Does not have motivation to set new goals.

Tolerance Of Others’

Ideas

Gives and encourages a variety of points of view.

Encourages a variety of points of view.

Evaluates differing points of view.

Considers differing points of view.

Occasionally demonstrates intolerance towards differing

Demonstrates intolerance towards differing points of view.

Page 61 of 73

points of view.LE

ADER

SHIP

Working with

Others

Listens to, shares with, and supports the efforts of others.

Always listens to, shares with, and supports the efforts of others.

Usually listens to, shares with, and supports the efforts of others.

Often listens to, shares with, and supports the efforts of other.

Rarely listens to, shares with, and supports the efforts of others.

Does not listen to, shares with, and supports the efforts of others.

Contributions

A definite leader who contributes a lot of effort.

A good group member who tries hard.

A strong group member who tries hard.

A satisfactory group member who does what is required.

Rarely participate. Refuse to participate.

Focus on the Task

Consistently stays focuses.

Always stays focuses.

Most of the time. Some of the time. Rarely focuses. Lost focuses.

Problem-solving

Actively looks for and suggests solutions to problems.

Always looks for and suggests solutions to problems.

Most of the time looks for and suggests solutions to problems.

Refines solutions suggested by others.

Does not suggest or refine solutions.

Does not try to solve problems.

TEAM

WO

RK

Participation

Fully participated. Always participate. Most of the time participated.

Some of the time participated.

Rarely participated.

Does not participate.

ListeningListened carefully to others’ ideas.

Always listen to others’ ideas.

Usually listened to others’ ideas.

Sometimes did not listen to others’ ideas.

Rarely listen to others and often interrupted them.

Did not listen to others and often interrupted them.

FeedbackOffered detailed, constructive feedback when appropriate.



Occasionally offered constructive feedback.

Rarely offered constructive or useful feedback.

Did not offer constructive or useful feedback.

Cooperation

Treated others respectfully and shared the workload fairly.

Usually treated others respectfully.

Usually shared the workload fairly.

Sometimes treated others disrespectfully or did not share the workload fairly.

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

Treated others disrespectfully or did not share the workload fairly.

Time Managemen

t

Completed assigned tasks on time.

Always completed assigned tasks on time.

Usually completed assigned tasks on time.

Sometimes completed assigned tasks on time.

Often did not complete assigned tasks on time.

Did not complete most of the assigned tasks on time.

Page 62 of 73

APPENDIX L

Level 6: End Product


Achieve the objectives

All objectives are achieved and exceeded expectation.

Most of the objectives are achieved.

A few of the objectives are achieved.

only two objectives are not achieved.

Only one objective is achieved

No objective.

Construction and functionally

Always describes effectively how the system was constructed and how it functions.

Most of the time describes how the system was constructed and how it functions.

Sometimes describes how the system was constructed and how it functions.

Occasionally describes how the system was constructed and how it functions.

Least attempts are made to describe how the system was constructed and how it functions.

No attempt is made to describe construction or functionally.

Feasibility

Always clearly communicated feasibility of construction and implementation. No errors with notification.

Clearly communicated feasibility of construction and implementation most of the time. Minor error.

Sometimes communicated feasibility of construction and implementation. Minor error.

Occasionally communicated feasibility of construction and implementation. Minor error.

Least communicated feasibility of construction and implementation. Major error.

No meaningful attempt was made to develop a solution. Major error.

User Interface Layout

Exceptionally attractive and usable layout. It is easy to locate all important elements. organize material effectively.

Almost usable layout, but may appear busy or boring. It is easy to locate most of the important elements.

Moderately usable layout, but may appear busy or boring. It is easy to locate most of the important elements.

Slightly usable layout, but may appear busy or boring. It is easy to locate most of the important elements.

Least usable layout, but may appear busy or boring. It is easy to locate most of the important elements.

Cluttered looking or confusing. It is often difficult to locate important elements.

Testing

test procedures are clear and well documented. Results are excellently documented, valid, and reliable.

attempt is made to document test procedures most of the time. Results are well documented , valid and reliable.

Moderately attempt is made to document test procedures. Results are very well documented but not 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.

Marketability project attempt is made to Moderate attempt is Slight attempt is Least attempt is No meaningful

Page 63 of 73

marketability is clearly communicated as to how this design is different, better, set apart from what already exists.

communicate the device’s marketability most of the time as to , how this design is different, better, set apart from what already exists.

made to communicate the device’s marketability as to how this design is different, better, set apart from what already exists.

made to communicate the device’s marketability, how this design is different, better, set apart from what already exists.

made to communicate the device’s marketability, how this design is different, better, set apart from what already exists.

attempt is made to communicate the project‘s marketability, how this design is different, better, set apart from what already exists.

OriginalityProduct shows an excellent original thought.

Product shows a good original thought.

Product shows a moderate amount of original thought.

Uses other people's ideas but there is little reference of original thinking.

Uses other people's ideas.

No originality and plagiarism.

CreativityExcellent ideas, creative and inventive.

Good ideas, creative and inventive.

Moderate ideas, creative and inventive.

Fairly creative ideas and inventive

Lack of ideas, creativity and invention.

No creativity

Page 64 of 73

APPENDIX M

Level 6: Final Report Rubric


Abstract

Describe excellent and specific sentence for main purpose, scope, method, result, recommendation and conclusion of project without grammatical errors.

Describe good sentence for main purpose, scope, method, result, recommendation and conclusion of project without grammatical errors.

Describe clear sentence for main purpose, scope, method, result, recommendation and conclusion of project without grammatical errors.

Describe moderate sentence for main purpose, scope, method, result, recommendation and conclusion of project with moderate grammatical errors.

Describe less sentence for main purpose, scope, method, result, recommendation and conclusion of project with many grammatical errors.

Sentence is not for main purpose, scope, method, result, recommendation and conclusion of project with many grammatical errors.

Introduction

Very good explanations of the project

Clear explanations of the project

Moderate explanations of the project

Not clear explanations of the project

Vague explanations of the project.

No explanation of the project.

Methodology

Methodology is clearly presented, relevant and appropriate ly applied to project development.

Methodology is clearly presented, relevant and appropriately applied to project development.

Methodology is clearly presented, but not appropriately or adequately applied to project development.

Methodology is moderately presented but not appropriately or adequately applied to project development.

Methodology is not clearly presented, not appropriately or adequately applied to project development.

No methodology is presented.

Literature review

Excellent literature review . Sources are cited when specific statements are made and significant to the project.

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.

Only two sources of literature review are covered without citation but related to the project.

Only one sources of literature review is covered without citation and not related to the project.

No literature review is presented.

Analysis

Excellent ,demonstrates clear understanding and elaboration of diagrams and flow charts.

Good ,demonstrates clear understanding and elaboration of diagrams and flow charts.

Clear analysis and demonstrates good deal of understanding of diagrams.

Moderate analysis and demonstrates good deal of understanding diagrams.

Not very clear analysis and no understanding of diagrams.

No analysis is presented.

DesignExcellently defines and shows process in design

Very well defines and shows process in design

Clearly shows and elaborates the design process.

Moderately shows and elaborates the design process.

Not clearly shows and elaborate the design process.

Not shown and elaborate design process.

Page 65 of 73

Implementation & testing

Use good testing technique and suitable data. Good result elaboration.

Use good testing technique and show clear result after testing.

Use suitable testing technique and show clear result after testing.

Use suitable testing technique but not show clear result after testing.

Use unsuitable testing technique.

no testing technique.

ConclusionSpecific and good conclusion. Objectives are achieved.

Specific and clear but only shows a few objectives are achieved.

Clear but does not show the objectives are achieved.

Moderate conclusion. No specific and clear conclusion.

No conclusion.

Arrangement

Information is excellently organized with well-constructed paragraphs and subheadings.

Information is very well organized, and paragraphs are well-constructed.

Information is well organized, but paragraphs are not well-constructed.

Information is moderately organized, but paragraphs are not well-constructed.

Lack of information Not organized.

Diagram & illustration

Diagrams and illustrations are excellent, neat and accurate.

Diagrams and illustrations are good, neat and accurate.

Diagrams and illustrations are moderate and accurate.

Diagrams and illustrations are less accurate.

Diagrams and illustrations are not accurate.

No diagrams and illustrations are presented.

References

References are significant to project and very organized with well-constructed using APA format.

References are organized and significant to project and follow APA format.

references are significant to project and follow APA format.

Reference are not significant to the project but follow APA format.

Reference does not follow APA format.

No references

WritingGood writing and no grammatical , spelling or punctuation errors.

Clear writing and no grammatical spelling, or punctuation errors.

No grammatical spelling or punctuation errors in writing.

Moderate grammatical spelling, or punctuation errors in writing.

Few grammatical, spelling, or punctuation errors in writing.

Many grammatical, spelling, or punctuation errors.

Page 66 of 73

APPENDIX N

Level 6: Development Demonstration Rubric

CRITERIA 5 4 3 2 1 0Input Development

Input Form – 100% completeSuitable data – 100% can be added using this form.

Input Form – More than 90% completeSuitable data – More than 90% can be added using this form.



Input Form – Less than 50% completeSuitable data – Less than 50% can be added using this form.

0% develope the input form of the system.

Output Development

100% develop More than 90% develop

More than 80% develop


Less than 50% develop

0% develope the output of the system

User Interface Development

Layout - Exceptionally attractive and user-friendlyImportant elements -Easy to locate Material - Organized effectively

Layout –Almost exceptionally attractive and user-friendly layout.Important elements –Easy to locateMaterial -Almost effectively organized

Layout –Attractive and user-friendly layout

Important elements –Easy to locate

Material -Moderately organized

Layout –Not user-friendly

Important elements –Easy to locate most of the important elements.


Important elements –Difficult to locate most of the important elements.

Layout –Clutter and confuse

Important elements –Cannot locate important elements.

Project Application Development

100% develop More than 90% develop



Less than 50% develop

0% develop the project application

System Security and Features

Implement 100%. Implement up to 90%

Implement up to 80%

Implement more than 50%

Implement less than 50%

0% apply user controls and validation controls

Page 67 of 73

Progress of Project Development

100% complete. More than 90% complete

More than 80% complete


Less than 50% complete

0% complete the progress of project development

Page 68 of 73

APPENDIX O

Level 6: Testing Demonstration Rubric


Testing Plan100% complete testing plan

More than 90% complete testing plan



Less than 50% complete testing plan

0% complete testing plan

Unit Testing100% complete unit testing

More than 90% complete unit testing



Less than 50% complete unit testing

0% complete unit testing

Integration Testing

100% complete integration testing

More than 90% complete integration testing



Less than 50% complete integration testing

0% complete integration testing

System Testing

100% complete system testing

More than 90% complete system testing



Less than 50% complete system testing

0% complete system testing

Page 69 of 73

APPENDIX P

Level 6: Implementation Demonstration Rubric


Feasibility / functionality

100% complete More than 90% completeMinor Errors

More than 80% completeMinor Errors

More than 50% completeMinor Errors

Less than 50% completeMajor Errors

0% complete

Major ErrorsMarketability(commercial value)

100% complete More than 90% complete




No meaningful attempt is made to communicate the projects’ marketability.

Objective Achievement

100% complete More than 90% complete




Do not achieve bjectives at all.

Originality

100% original Ideas, creative and inventive



More than 50% original Ideas, creative and inventive

Less than 50% original Ideas, creative and inventive

Uses other people’s ideas but does not give them credit.

User interface (layout)

Layout - Exceptionally attractive and user-friendlyImportant elements -Easy to locate Material - Organized effectively

Layout –Almost exceptionally attractive and user-friendly layout.Important elements –Easy to locateMaterial -Almost effectively organized

Layout –Attractive and user-friendly layout

Important elements –Easy to locate

Material -Moderately organized


Important elements –Easy to locate most of the important elements.


Important elements –Difficult to locate most of the important elements.

Layout –Clutter and confuse

Important elements –Cannot locate important elements.

Page 70 of 73

APPENDIX Q

Level 6: Portfolio Rubric


Required items

All required items are included, with a significant number of additions.

All required items are included, with a few additions.

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

Overall Organization

Items are clearly introduced, well organized, and creatively displayed, showing connection between items.

Items are introduced and well organized, showing connection between items.

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 71 of 73

APPENDIX R

Level 6: Log Book RubricCriteria 5 4 3 2 1 0

Weekly activities

All 15 weeks of activities are recorded in the log book.

More than 12 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.

Supervisor signatures

Supervisor’s signature of verification is shown for all 15 weeks.

Supervisor’s signature of verification is shown for more than 10 weeks.



Supervisor’s signature of verification is shown for less than 5 weeks.

No signature of verification of the supervisor.

Details

Log book is exceptionally detailed, provide an in-depth look into the project activities, and reflects the student’s commitment.

Log book is exceptionally detailed, provide an in-depth look into the project activities.

An appropriate amount of detail is used to explain the project activities done.

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.

Neatness

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.

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 72 of 73

APPENDIX S

Portfolio Checklist Project Title : ................................................................

No.Registrati

on Number Student Name

Level 5 Level 6

Proj

ect

Prop

osal

Pa

per

Anal

ysis

Repo

rt

Desig

n Re

port

Log

book

Fina

l rep

ort

End

prod

uct

User

man

ual

Log

book

Verified by:

______________________( Level 5 Supervisor Name )Date :

Verified by:

______________________( Level 6 Supervisor Name )

Page 73 of 73

Documents

Guideline Content