1 / 27

Project 1 (CPRB 413 / CGNB 413) Briefing

Project 1 (CPRB 413 / CGNB 413) Briefing. By: COIT Undergraduate Project Committee. Why do you need to do project?. Apply knowledge that has been learned in class. Gain experience in developing a system. Learn something new. To create a sample of your work. Requirement to get a degree.

kaiya
Télécharger la présentation

Project 1 (CPRB 413 / CGNB 413) Briefing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Project 1 (CPRB 413 / CGNB 413) Briefing By: COIT Undergraduate Project Committee

  2. Why do you need to do project? • Apply knowledge that has been learned in class. • Gain experience in developing a system. • Learn something new. • To create a sample of your work. • Requirement to get a degree.

  3. Project 1 Activities • Find and register for a project • Pick our project • Propose your own project • Submit an initial report • Keep a logbook • Set a meeting with supervisor every week • Discuss with examiner at least once • Write the draft report • Perform presentation • Write the final report

  4. Where to get the project titles? • Go to the following URL: • http://sephiroth/spmsv2 • After you have chosen the projects that you are interested in, go and see the lecturer who proposed the project for further discussion. • The lecturer will register you for the project.

  5. Project Guidelines • There are two guidelines that you need to obtain. • COIT Project Guidelines • Report Writing Guidelines • Both documents can be obtained from http://sephiroth/spmsv2

  6. Project Categories • There are four project categories: • Systems and Networking • Software Engineering • Graphics and Multimedia • Information Systems • Students may only take projects that belong to their specialization.

  7. How do you propose your own project? • Write a brief proposal containing the following information: • Project title • A brief description on what you are going to implement • Objectives and scopes • Outcome of the project • The proposed topic must be related to your specialization. • Find a lecturer who is willing to supervise your project. • Preferably a lecturer who belongs to your department

  8. Minimum Standard • All projects must at least achieve the minimum standard as outlined in Appendix A in the guideline. • Each project category has its own minimum standard. • Will be explained further in the breakout session after this.

  9. Initial Report • A small write up (around 2 to 3 page) that contain the plan for the whole project. • Should be agreed upon by both student and supervisor. • Contents: • Project title • Brief description • Objectives and scopes • Expected outcome • Gantt Chart

  10. Logbook • Each student is required to keep a logbook (can be obtained from http://sephiroth/spmsv2/). • All your progress must be written in the logbook. • Bring the logbook during your meeting with supervisor. • Supervisor need to read and sign your logbook. • At the end of the semester, if there are less than SIX signatures, your supervisor has the right to give you an E.

  11. Project 1 vs. Project 2 • The actual scope for project 1 and project 2 depends on the methodology used. • Example 1: Waterfall Model • Project 1: Literature review, user requirements, system design. • Project 2: Implementation, testing. • Example 2: Prototyping Model • Project 1: Literature review, system design (maybe partially), prototype 1, prototype testing. • Project 2: More design, prototype 2 (or more), final product, testing. • Discuss expected deliverables (for both Project 1 and 2) with your supervisor.

  12. Assessment Criteria Percentage Logbook and meeting attendance 10% Presentation 30% Report 60% Project 1 Evaluation • Marks will be given by your project supervisor and your examiner. • Marks allocation:

  13. Project Examiner • Each project will be assigned an examiner. • A lecturer who will evaluate your project together with your supervisor. • Examiners will choose the projects that he/she wants to examine. • You have no control over who your examiner will be. • It is COMPULSORY for you to discuss your project with your examiner at least once during the semester.

  14. Presentation • Will be done in supervisor’s room and evaluated by supervisor and examiner. • Duration around 30 minutes • Recommendation and suggestions should be taken seriously • Modify report if necessary

  15. Final Report • Read the COIT’s final year project guidelines to learn about the format. • Should roughly follow our suggested report contents. • Make sure grammar is correct. • Write with intention that somebody else who read this will be able to understand and implement your system. • Make sure all contents cited from other sources are referenced properly.

  16. Facilities • Money allocation • Each of you are allocated RM 400.00 for buying equipments. • Procedures: • Get form from lab technician. • Fill in the required information. • Get your supervisor to verify. • Bring back the form to lab technician. • The technician will buy the items for you.

  17. Facilities • You CANNOT buy: • Pirated software • Books • Software that is already available in the lab. • Remember that whatever you buy, they belong to the college. • Make sure you return them to the lab by the end of your project. • Failure to do so may cause your grade to be suspended.

  18. Facilities • Final year project lab • There is a computer lab dedicated for final year project students. • BW-4-R06. • You can use the lab for: • Research (browsing the Web, etc). • Development. • If you need to install any specific software, please contact the lab technicians.

  19. Project Workshops • Several workshop sessions will be conducted throughout the semester. • Aimed to help students in doing the project properly. • Cover key activities in final year project: • How to do research • Report writing

  20. Tasks Deadlines Confirm a project topic 17 July 2009 (One week from today) Submit an initial report to supervisor 24 July 2009 (One week after confirming your topic) Submission of draft report 25 September 2009 (4 weeks before end of semester) Presentation Between 28 September to 9 October 2009 (Around 2 or 3 weeks before end of semester) Submission of final report 16 October 2009 (1 week before end of semester) Deadlines

  21. FAQs • What happen if I cannot get a project? • Consult the project coordinator to see whether he can help you. • After a certain deadline, you need to drop the project. Otherwise, you will be given an E. • I cannot finish my project 1 in this semester. Can I extend? • Extension is only allowed until the first week of the next semester. Otherwise, you will be given an E.

  22. FAQs • What if I want to submit my report a little bit later than the deadline? • Yes, you can do so, but you need to seek permission from both your supervisor and examiner. • If you do not ask for permission, your supervisor and examiner has the right to give a 0.

  23. FAQs • Can I change my project in the middle of project 1? • Yes, with the permission of the supervisor. • Can I change my supervisor in the middle of project 1? • No. But if you are really desperate please see your project coordinator.

  24. FAQs • What if I don’t like my examiner? • Live with it… • What if my supervisor becomes unavailable? • If it can be planned (i.e. maternity leave), please make arrangement beforehand. • If it cannot be planned (i.e. death, hospitalization, lecturer got fired), please see the project coordinator.

  25. Common Problems • Fail to get a project before deadline. • Poor attendance to meeting with supervisor. • Do not meet examiner at the beginning of the project. • Late report submission. • Forget to submit report to examiner. • Plagiarism / cheating.

  26. Q & A

  27. Breakout Sessions • Systems and Networking: BW-G-R04 • Software Engineering: BW-G-R05 • Information Systems: BW-G-R06 • Graphics and Multimedia: BW-G-R14

More Related