Project Guidelines
Project Rubric
Project Proposal (week 3)
Project Report
Project Presentation (week 14)
Mini Project (10%)
• Form a group (min 2, max 4 persons)
• Project Proposal (submitted on week 3, submit correction not later than week 5.
• Project Progress (lecturer will check every 1 or 2 weeks, check algorithm, flow chart, coding, report)
• Project Presentation and Report Submission on week 14.
MINI PROJECT (10%)
(Group)
Submission Date:
Project Proposal Due Date: week 3 to week 5 (ask your lecturer)
Project Final Report: Week 14 (Submit Project Report & Presentation)
1. Proposal guidelines
Each group (min 2 - max 4) needs to submit a proposal to suggest a title and its detailed description. Do not write the program yet. Your proposed program must contain at least selection, repetition and functions.
Write a simple proposal that includes the following information:
• Frontpage (Color: RED)
• Project Name/Title
• Students’ Information (student id, student name, group (example: CS1112A/EC1102A)
• Summary of the project (some project detail)
• Pseudocode and flowchart
• Marks for the proposal will be given in your final report.
Your proposal will be rejected if any of the required information is not stated in the proposal. After the proposal is accepted, you may start coding the project.
Each group is required to submit a proposal to your lecturer (date discuss with your lecturer).
2. Project Guidelines
Project Details:
• Your project must apply selection, repetition and functions.
• Prepare the FINAL REPORT which includes the following:
• Frontpage (Color: BLUE)
• A brief explanation of the project in the executive summary.
• Complete program.
• All Variable/Constant, Input and Output involved.
• Sample of output.
• Send the softcopy and all related files of your program to your lecturer. State your group (example: CS1112A/EC1102A), matric number, name, and the title of your project in the folder (Discuss with your lecturer how to send your project - either through email, google drive, WhatsApp, ufuture, i-Learn, google classroom etc.)
• Scoring rubric (must be attached with the final report).
Each group is required to submit a project report to your lecturer by Week 14/Discuss with your lecturer
PROJECT PROPOSAL
Table of Contents
1. Project Summary
(Project details such as the flow of the system or user requirement – Students are encouraged to put diagrams)
2. Pseudocode and flowchart
(List of variables, selection, repetition and functions that will be used)
*It is okay if your actual project differs from your proposal. Lecturer just want to know if your proposed system is realistic (not too simple and not too complex)
*Please use this format:
Please use this format starting from Table of Content to Reference.
• Front Page Colour: Red
• Font Face: Arial
• Font size: 11-point
• Top Margin: 2.54cm
• Bottom Margin: 2.54cm
• Left Margin: 2.54cm
• Right Margin: 2.54cm
• Page Number: Bottom and centre of each page
PROJECT REPORT
Table of Contents
Acknowledgement
1. Executive Summary
2. Pseudocode and flowchart
3. List of Codes
4. Details of Input and Output
5. Screen Layout
6. References
*Please use this format:
Please use this format starting from Table of Content to Reference.
• Front Page Colour: Blue
• Font Face: Arial
• Font size: 11-point
• Top Margin: 2.54cm
• Bottom Margin: 2.54cm
• Left Margin: 2.54cm
• Right Margin: 2.54cm
• Page Number: Bottom and centre of each page
Rubric Category
- Proposal’s format and content: Include all the necessary information and it is well documented.
- Proposal’s pseudocode and flowchart: Pseudocode and flowchart’s logic match with the system implementation
- Proposal overall quality: The proposal is well written and documented. Clearly define the problems to be solved. Clearly define the objectives.
- Clarity of program’s (code) presentation: The program is clearly written (indented) as well as easy to understand. Each of the processes is well documented/commented on.
- Structure and algorithm of a program: The program can solve the problem completely. There is no syntax error, logic error and run-time error.
- Compulsory topics to be included: Apply selection, repetition and functions within the algorithm of the program.
- Result/Output: The program produced expected output with an accurate and presentable format.
- Report overall quality: The report is well written and documented. Clearly explains what the project is all about.
- Presentation: The presentation’s flow is in order. Able to answer technical questions. Confidence.
- Knowledge mastery: Project demonstrated achieves a level of artful engineering mastery marked by truly innovative, authentic and ideas, solutions and design.
