Category Final Year Project

Assessments (CSP 650)

Assessments


 Written report 45% – Chapter 1,2,3,4,5 – (Supervisor & Examiner)

  • 25% Supervisor (Project Report Evaluation) (Form F11) – Due date (1/2/2025)
  • 20% Examiner (Project Report Evaluation) (Form F11) – Due date (1/2/2025)

 Written report 10% – Chapter 4 – (Supervisor & Examiner)

  • 5% Supervisor (Project Report Evaluation) (Form F11) – Due date (1/2/2025)
  • 5% Examiner (Project Report Evaluation) (Form F11) – Due date (1/2/2025)

 Presentation 40% (Lecturer, supervisor & Examiner)

  • 10% Lecturer (Progress Project Presentation) (Form F9) – Duration (6/10/2025 – 1/2/2026)
  • 15% Supervisor (Final Project Presentation) (Form F10) – Due date (1/2/2025)
  • 15% Examiner (Final Project Presentation) (Form F10) – Due date (1/2/2025)

Business Model Canvas 5% (Lecturer)

  • 5% Lecturer (Lean Canvas Model Evaluation) (Form F13) – Due date (1/12/2025)

List all forms:

References:

  1. Joseph S. Valacich , Joey F. George, Modern Systems Analysis and Design, 9, Pearson Publication Inc, 2019, ISBN: 978-013517275
  2. Teun den Dekker, Design Thinking, Routledge, 2020, ISBN: 9781000358650
  3. Stephen Hartley, Project Management, n/a, ISBN: 9781760631789
  4. Joseph Heagney, Fundamentals of Project Management, 5th, Amacom, 2018, ISBN: 9780814437360

Course syllabus & Schema of work (CSP 650)

This course will enable the students to experience the planning, analysis, design and development phases in handling information technology project. The student develops solutions based on the formulated problem. Students should be able to compile, analyse and present the project carried out in the form of a thesis. Students also should be able to communicate the project outcome effectively through oral and presentation

At the end of the course, students should be able to:

  • Solve undertaken problem using appropriate technique and principles in the field of computing sciences (C5)
  • Present the undertaken project in written and orally in the field of computing sciences (A2)
  • Propose the commercial potential for the undertaken solution (A3)
  • Organize information and discussion relevant to the undertaken of project (A4)

Course Syllabus

TopicRemarks
WEEK 1 
(6/10 –10/10)

Project Foundation
• Project Formulation Refinement
• Recap Project Proposal (CSP600)
• Go through FYP process
Lecture 1
Introduction to CSP650

Lab 1: 
Correction of report (proposal)
WEEK 2 
(13/10 – 17/10)


Writing and Structuring Report
• Sections in Report
• Writing Approach


Start Entrance Survey (7 Oct – 3 Nov 2024)

Lecture 2



Lab 2: 
Present up-to-date project progress
Refine Chapter 1


WEEK 3
(20/10 – 24/10)


Chapter 1- Refining Introduction section
• Problem Statement 
• Objectives 

End Entrance Survey (7 Oct – 3 Nov 2024)
Submit Mutual Acceptance Form(F1)

Lecture 3


Lab 3: 
Present up-to-date project progress
Continue to refine Chapter 1
WEEK 4
(27/10 – 31/10)


Chapter 2- Refining Literature Review and References section
• Citation – The APA format
• Reference Management



Lecture 4


Lab 4: 
Present up-to-date project progress
Continue to refine Chapter 2
WEEK 5
(3/11 – 7/11)


Business Model Canvas / Lean Model Canvas
 • Introduction 



Lecture 5



Lab 5: 
Present up-to-date project progress
Continue to refine Chapter 2
WEEK 6
(10/11 – 14/11)


Business Model Canvas / Lean Model Canvas

• Entrepreneurship



Lecture 6
Draft Lean Model Canvas

Lab 6: 
Present up-to-date project progress
Continue to refine Chapter 3
WEEK 7
(17/11 – 21/11)




Chapter 3- Refining Methodology Section

• Project Framework
• Design & Coding








Lecture 7
Lean Model Canvas

Lab 7: 
Present up-to-date project progress
Continue to refine Chapter 3
Semester break
WEEK 8
(1/12 – 5/10)





Result and Findings

• Achievement of objectives
• Aligning to methodology activities

Submit Lean Model canvas (Due date 1/12/2025)


Lecture 8


Lab 8: 
Present up-to-date project progress
Draf Chapter 4
WEEK 9
(8/12 – 12/12)


 


Result and Findings

• Achievement of objectives
• Aligning to methodology activities 






Lecture 9




Lab 9: 
Chapter 5
Present up-to-date project progress
Draf Chapter 4
WEEK 10
(15/12 – 19/12)


Conclusions & Recommendation

• Summary of the project
• Strengths and limitations
Future work recommendation



Lecture 10


Lab 10: 
Present up-to-date project progress
Draf Chapter 5




(22/12 – 26/12)Semester Break
WEEK 11
(29/11 – 2/1)


 




Abstract
• Types of Abstract: Executive, Descriptive, Informative







Start Student Feedback Online (SuFO) (10 Jun – 14 July 2024)



Lecture 11


Lab 11: 
Present up-to-date project progress
Draf Chapter 5
WEEK 12
(5/1 -9/1)


Presentation
• Oral Presentation
• Poster presentation
Start Exit Survey (24 Jun -7 July 2024)

Lecture 12


Lab 12: 
Progress Presentation
WEEK 13
(12/1- 16/1)


Good Poster guideline
• Content
• Arrangement
• Font

Submission of report – First Draft (12 Jan 2025)


Lecture 13


Lab 13: 
Progress Presentation and
Plagiarism checking
WEEK 14
(19/1 – 23/1)


Poster Printing
• Briefing on exhibition and related procedures
Submit Final Proposal – Due (6/7/2025)

Start Student Feedback Online (SuFO)
Start Exit Survey


Lab 13: 
Progress Presentation and Poster

Final presentation 12/7/2025
(26/1 – 30/1)
Study week
(2/2 – 6/2)
End Student Feedback Online (SuFO)
End Exit Survey
Final Examination Week
(10/2 – 1/3)Semester Break

SESI OCT 2025 – FEB 2026

Game Development Lifecycle (GDLC)

The Game Development Life Cycle (GDLC) is a structured process for creating video games, similar to the Software Development Life Cycle (SDLC). It typically involves several stages, including initiation, pre-production, production, testing, beta, and release. GDLC provides a framework for managing the complex process of game development, from initial concept to release and beyond. 

Software Development Life Cycle (SDLC) 

Software development life cycle (SDLC) is a series of phases that provide a common understanding of the software building process. How the software will be realized and developed from the business understanding and requirements elicitation phase to convert these business ideas and requirements into functions and features until its usage and operation to achieve the business needs. A good software engineer should have enough knowledge on how to choose the SDLC model based on the project context and the business requirements.

Rapid

What is Rapid Application Development at its core? RAD is a development approach that emphasizes speed and flexibility in software development. It’s designed for teams and businesses that want to prioritize quick prototyping and feedback over lengthy planning phases. By focusing on rapid iterations, RAD ensures that apps are developed efficiently while meeting changing project requirements.

How it works? RAD minimizes complexity through modularized designs and iterative workflows. Teams work closely with stakeholders to define requirements early, enabling them to create a working prototype quickly. This prototype is refined through feedback loops, ensuring that the final product delivers a better experience to end users.

With RAD, the focus is on reducing development costs and shortening the development cycle, all while maintaining high quality — rather practical for modern business processes that demand speed, adaptability, and collaboration.