Wednesday, May 18, 2011

Final Project Supervisor (HOD approved special cases)

Mr Foong
1. Darryl Shawn Miranda
2. Ashvind Jude
3. Jervenne Yong

Meet me every Monday from 12.00-3.00.

Monday, March 7, 2011

Supervisor Allocation for Final Project (Jan - May 2011 semester)

The following is the list of students with their corresponding supervisors for the IT299 Project.

Ms Mohgana
1. Arun Kumar Mohan
2. Chong Li Jun
3. Chow HungKee Amos

Mr Foong
1. Chu Teck Seng
2. Danny Chin Kim Yuan
3. Hiew Yong Shing

Ms Kameni
1. Jaeson Martin
2. Lee King Han
3. Lee Yik Chee
4. Lim Cheng Yong

Ms Hiew
1. Okoye Innocent Ezenna
2. Safura Hanis Musa
3. Simon Chow Samuel
4. Tey Teck Wey

Please see your supervisors on a weekly basis.

Friday, May 15, 2009

Project Deliverables

The following is the list of deliverables:
  1. Terms of Reference (TOR) - by week 4
  2. Project Schedule (Gantt Chart) - by week 4
  3. Project Report - by week 14
  4. CD containing compiled program (.exe file) and source code and/or other relevant files (database, report files, pictures and etc) - by week 14

Friday, May 8, 2009

Project Report

The report is a major part of the project. It is a clear and accurate description of all aspects of the project.

Suggested Framework for the Project Report
  1. Title page
    - Project title
    - Author
    - Course
    - Date
  2. Summary
    - An extract of the main points of your report
    - What was achieved and what remains to be done
    - Any change in emphasis or direction during the project
  3. Contents
  4. Introduction
    - A brief overview of the nature of the project, what has to be attempted and the deliverables to be produced.
    - Acknowledgements
  5. Product Development
    - Main body of the report in which the work carried out is described in detail.
    - The approach adopted
    - Resources and facilities used
    - The problems encountered and their solutions
    - Setbacks
    - What has been achieved
    - A description of the deliverables
    - How it was established that the deliverables meet the objectives
  6. Conclusion
  7. Appendices
    - any relevant material to support the report
    - terms of reference
    - schedule
    - design and program documentation
    - trial plan, test data and expected results
    - user guide
    - operating instructions


Thursday, May 7, 2009

Project Process

The project process is a combination of many of the skills and techniques that you have developed during the diploma programme and before, and one of which you may be using in your job.

Tasks to be achieved:
  • researching the problem
  • analysing the problem
  • designing a solution
  • implementing a solution
  • documenting your solution

Wednesday, May 6, 2009

Project Planning

Project Terms of Reference

One of the first tasks of the student once they have chosen a project topic is to define clear and comprehensive terms of reference (TOR). The TOR is a critical element of the project and act as a yardstick against which the project will be measured. A framework for the TOR will be given below.

Well-defined terms of reference are helpful in the following ways:
  • they prevent a student tackling a project that is over ambitious.
  • they form a 'contract' with the student as to what is to be achieved in the project.
  • negotiation of the terms of reference with the supervisor clarifies issues in the project and is an important learning experience.

The TOR form a basis for the project, but they may be subject to modification if the progress of the project justifies it, and modifications are agreed between all parties concerned with the project.

Framework for Terms of Reference

Format:

Heading - to include project title, student name, date of production and version.

Overview - this outlines the reasons for undertaking the work.

Objectives - the aims of the work, in terms of the major tasks, are stated here.

Constraints - define the boundaries of the work.

Resources - such as equipment, services, or software are identified.

Project Scheduling

Next you should prepare a schedule of tasks and target dates. Your project will normally be split into phases such as:

  • background research
  • investigation of requirements
  • analysis
  • design
  • familiarisation with software tools
  • implementation
  • testing
  • user and system documentation
  • report writing

Once the phases and tasks have been determined then the time required for their completion must be estimated.

A Gantt Chart must be produced for this scheduling purpose.

Tuesday, May 5, 2009

Project Selection

It is important to decide on a project title as soon as possible so that the work on the project can be started. If you generate your own project please submit the topic area to your lecturer in printed form for approval.

Alternatively, you may be able to choose a project from a list prepared by your lecturer.