Project 2 Briefing (CPRB423/CPRB424/CGNB424)

Slides:



Advertisements
Similar presentations
ECE FYP BRIEFING SEMESTER ii, 2014/2015
Advertisements

Project 1 (CGNB 413) Briefing
Major/Minor Projects 1. Why is this important?  Because it will make a big difference to your degree  A good 394 project mark can go a long way towards.
Course Outline Process Overview for Course Convenors.
Project Workshops Project Planning 1. Project planning proper management is essential the responsibility of the student with the advice of supervisor.
FINAL YEAR PROJECT I & II Week 1 – Introduction to the Course.
1 Google > Dave Inman > Projects Stages of a Final Year project.
School of Electrical Engineering & Computer Science Final Year Projects Final Year Project Coordinator – Newcastle Laboratory Manager - Newcastle Gunilla.
1 introduction to projects general information. 2 people lectures information systems/bit - Phil Clipsham computing programmes – Kevin Parrott multimedia.
School of Electrical Engineering & Computer Science
CS300 Planning and Executing a Project Terry Hinton Helen Treharne.
ECE FYP BRIEFING SEMESTER 1, 2014/2015 AUDITORIUM B KULLIYYAH of ENGINEERING 11 th September 2014.
1 Dissertation Process 4 process overview 4 specifics –dates, policies, etc.
1 introduction to mm/g/wt projects general information.
LECTURER-TASNUVA CHAUDHURY (TCY) TERM PROJECT SUMMER’15 MGT 321: Organizational Behavior.
Grant Writing/Comprehensive Workshop Paul R. Albert, Ph. D
ACADEMIC PROJECT Week 1 – Introduction to Academic Project.
School of Electrical Engineering & Computer Science Final Year Projects Final Year Project Coordinator – Newcastle Laboratory Manager - Newcastle Gunilla.
BRIEFING 1: FYP INTRODUCTION
Agenda Introduction Student Log Book Guidelines
EET 333 – ENGINEERING TEAM PROJECT 2 nd Semester, 2014/2015 Session.
EKT 445 FINAL YEAR PROJECT 1 SEM I 2014/2015
Z26 Project Management Introduction lecture 1 13 th January 2005
CISB594 – Business Intelligence
Electronic Engineering Department Final Year Projects September 2008.
MSc conference briefing Mike Spann Project coordinator
BSc Honours Project Introduction CSY4010 Amir Minai Module Leader.
BSc Honours Project Introduction CSY4010 Amir Minai Module Leader.
IMSS005 Computer Science Seminar 2014/15 Lecture 1 This course is normally offered in every semester. If you are not planning to give a presentation in.
FINAL YEAR PROJECT (FYP) ERT 423 SESSION 2010/2011 “INTRODUCTION” MISMISURAYA MEOR AHMAD
Thesis Format and Submission
BSc Final Year Projects in Computing Computer Science, Creative Computing, Games Programming, Business Computing Dr Rodger Kibble.
©Dr I M Bradley Doing the project and other things.
Final Year Project 2 Systems and Networking Department.
Final Year Project (FYP) 1
Final Year Project 1 (FYP 1)
Final Year Project 2 Systems and Networking Department.
Introduction to Academic Project. INTRODUCTION No Academic Project Course CodeCreditsSemesterPrerequisites 2 Academic Project II 1.WAES3182 Academic.
Project 1 (CGNB 413) Briefing
Association of Accounting Technicians Portfolio Building 1 Introduction.
The Draft and Formal Project Proposal
Now what? 1.  I have short-listed projects I am interested in  I know the types of projects I would like to pursue  I have an idea of the resources.
King Saud University- College of Engineering- Dept of Chemical Engineering GUIDELINES AND RECOMMANDATIONS FOR THE PREPARATION OF GRADUATE PROJECT I AND.
Mini Project Guidelines & Evaluation. Project Objectives This mini project objective is to create a complete and working interactive web-based / disc-based.
LECTURER-TASNUVA CHAUDHURY (TCY) TERM PROJECT SPRING’16 MGT 321: Organizational Behavior.
INFO 3: Use of ICT In The Digital World Topic 7: Developing ICT Solutions Factors that contribute to the success and failure of ICT Systems.
PRACTICAL TRAINING GUIDELINES Department of Accounting 1 PRACTICAL TRAINING COORDINATOR Dr. Suaniza Mamat Room: A338, Level 3, KENMS Office Tel:
3P SYSTEM Better, Faster, More Meaningful Grades.
Preparation of the Self-Study and Documentation
Electronic Eng. FYP Coordinator - Rizalafande Che Ismail -
Technical Business Consultancy Project
ECE FYP BRIEFING SEMESTER i, 2016/2017
University of Haifa MA program in English Literature
Approval of Assessments
EEE368 Coordinators: 1. Mdm Norhidayatul Hikmee bt Mahzan
Systems and Networking Department
MDM ROHAZITA BAHARI FYP Coordinator
Annual Assessment of Progress 2017/18 Briefing for Research Students Research Student Registry Mar/Apr 2018.
ECE FYP BRIEFING SEMESTER iI, 2017/2018
Foundation Degree IT Project
ECE FYP BRIEFING SEMESTER i, 2018/2019
ECE FYP BRIEFING SEMESTER iI, 2016/2017
ECE FYP BRIEFING SEMESTER i, 2017/2018
COMS 161 Introduction to Computing
Approval of Assessments
Project Workshops Introduction.
FINAL YEAR PROJECT 2 (FYP) BRIEFING PLT 440/6
University of Haifa MA program in English Literature
ECE FYP BRIEFING SEMESTER I, 2019/2020
Presentation transcript:

Project 2 Briefing (CPRB423/CPRB424/CGNB424) COIT Final Year Project Committee Azimah Abd Ghapar – Head of Committee T.J. Iskandar Abd Aziz – Coordinator Project 2 Salman Yussof – Coordinator Project 1 Nazrita Ibrahim Yunus Yusoff Zailani Ibrahim Sharifah Junainah Syed Aziz Alan Cheah Kah Hoe

What do you need to do in Project 2? Start Immediately  Continue where you left off at the end of project 1 (you should have developed something by now) Student must achieve all the objectives that have been set in Project 1. Those objectives that cannot be achieved must be properly documented and justified

You are required to: Keep a logbook The log book contain the list of (weekly or bi-weekly) work scopes agreed between the supervisor and students See your supervisor regularly to report your progress The supervisor has the right to disallow the student from taking part in the presentation if the student fails to come and see him/her at least 6 times throughout the semester Write and submit draft thesis Perform presentation Submit final thesis

Deliverables A complete, working system as mentioned in your objectives and scopes If your objective is not to develop a system, then you must deliver whatever it is that has been agreed upon with your supervisor Presentation and system demo Final report A CD/DVD containing the source code and compiled system of your project Attach the disc at the back of your report. Do NOT put source codes inside your report!!

Project 2 Evaluation Assessment Criteria Percentage Thesis 30 Final Presentation 50 Log Book 5 Implementation 15

Project 2 Evaluation : Thesis (30%) Assessment Criteria Percentage Introduction, Objectives and Scopes 2 Research, methodology and analysis Proposed system / solution System Implementation 10 Results and discussion Format and presentation 4

Project 2 Evaluation : Presentation (50%) Assessment Criteria Percentage Introduction 5 Design Result Presentation Style Demonstration 20 Project Quality 10

Project 2 Evaluation : Log Book (5%) & Implementation (15%) Assessment Criteria Percentage Frequency of meeting with supervisor 5 Implementation – 15% This section is reserved for the supervisor to give his/her own evaluation on the result of the project. It mostly reflects the satisfaction of the supervisor on the outcome of the project and the performance of his/her student regarding the project.

Presentation Objective of the project presentation: To measure the ability of student to present his/her project Before you can present, your supervisor needs to approve that your project is ready to be presented Once your name is submitted, you CANNOT pull back (You must present your project)

Presentation Presentation contents: Total presentation time: 50 minutes 5 minutes: preparation 15 minutes: slide presentation 15 minutes: demo 10 minutes: Q&A 5 minutes: copy system to server Presentation contents: Introduction (what the project is all about) Objectives and scopes (what should be achieved) Design / solution (what has been done to achieve the objectives) Result (what was obtained at the end of the project) System Demo

Presentation DO NOT spend too much time talking about literature review and methodology You should concentrate on your work (things that you did during Project 2) You are advised to bring your own computer for the demo You are required to bring the source code/source file of your project to the presentation Failure to bring the source codes can be interpreted that you have committed plagiarism

Presentation Evaluation is done by a panel of evaluators (consists of lecturers) Two types of assessment are given: Presentation marks (based on overall presentation). Demo on the system developed (Pass or Fail)

Common cause of failure Your project does not meet the minimum standards/requirements of a degree project Read the Minimum Standards Document (get from http://sephiroth/spmsv2 ) You are not able to explain code or any other parts of the system (can be interpreted as committing plagiarism) What happen if you were given a fail during presentation? You will be given an E grade for your project

What To Do If Given a “FAIL” grade If you fail because your system is below the minimum standard If you are not satisfied with the panel decision, you can apply for remarking During the remarking session, you will present the same system in front of a new panel appointed by the committee

What To Do If Given a “FAIL” grade If you fail because you are not able to explain code (or any other part of the system) PLAGIARISM You are not allowed to go for remarking. If you are not satisfied with the panel decision, you can write an appeal letter to the Dean of COIT An investigation committee will be formed to investigate this matter If successful in your appeal, you are allowed to go for remarking If not, disciplinary action will be taken on you (because you commit plagiarism)

During presentation, bear in mind that… You must wear formal attire The medium of communication is English Be at the college early BEFORE your presentation time The panel has the right to fail you if you are not present during your presentation time The panel has the right to ask you anything that is related to your project Explain coding Open database Modify/debug your code on the spot Demo/create element (multimedia-based).

During presentation, bear in mind that… Bring all the materials related to the development of your project: Program codes Databases Required development tools Multimedia elements created  Graphics / images / animation /video Failure to prove that the project is developed by you may cause you to be given an E grade

Deadlines Deliverables Deadline Demo project output to supervisor (to confirm for presentation) 16/10/2009 - Friday (1 week before end of class) Submission of final draft thesis to supervisor 23/10/2009 - Friday (last day of class) Presentation 17/11/2009 – 19/11/2009 (1 week after final exam ends ) Submission of final thesis (Hard Cover) + system 24/11/2009 (1 week after presentation)

Deadlines The completion of project 2 is marked by your project presentation and submission of final thesis ALL STUDENT MUST PRESENT their project at the end of the semester Starting Sem 1 2009/2010, There will be no time extension or BS status given

Advice to students Do not procrastinate ! Don’t start after final exams.. Meet your supervisor on a regular basis. Do not come just towards the end Failure to see the supervisor has been identified as one of the major reason for the failure of the project Verify expected output (objectives) with your supervisor

Advice to students If you were in any doubt on what to do, check with your supervisor or the committee Keep several backup copies of your project in case something goes wrong with your computer You are ultimately responsible for the success of your project Your supervisor role is to supervise but you have to do all the works and be accountable of the results

Interesting Facts & Figures Students registered in Sem 2, 2007/2008 = 159 Presented in Sem 2 0708 = 159-109 = 50 (31.44%) Total BS = 109 (68.55%) *Presented in Sem 1, 0809 = 86 (78.89%) *Did not present in Sem 1, 0809 (automatic fail) = 23 (21.1%) Students registered in Sem 1, 2008/2009 = 202 CPRB 423 = 12, CPRB 424 = 187 & CGNB 424 = 3 Presented in Sem 1 0809 = 57 (28.21%) Total BS = 145 (71.78%)

Interesting Facts & Figures Students Presented Sem 1, 2008/2009 = 86 + 57 = 143 Total Passed = 105 (73.42%) Pending Presentation (Medical) = 1 (0.7%) Absent During Presentation (Auto Fail) = 5 (3.49%) Fails During Presentation = 32 (22.37%) Registered Sem 1 0809 – 14 failed Registered Sem 2 0708 - 23 Specialization Total Software Engineering 27 Systems & Networking 22 Information Systems 64 Graphics & Multimedia 30

Interesting Facts & Figures Students Presented Sem 2, 2008/2009 (June 09)= 103 Total number failed automatically/did not confirm/not allowed to present  = 28 ( 27.18%)  Total number confirmed for presentation = 75 (72.82%) Confirm, present and passed = 51 students  (68%) Confirm, present and failed = 12 students (16%) Confirm, absent and auto failed = 12 students (16 %)  Overall total of failures = 28 + 24 = 52/103 = 50.485% Students Registered Sem 1 2009/2010 = 147 CGNB424 = 85, CPRB423=7, CPRB424=55 Passed =%? And Failed=%?

Which category will you falls into ? YOU Decide !!! Good Luck..!!