This stage is all about defining your project idea and setting clear goals. You’ll create a Project Brief that explains what your program will do, who it is for, and what problem it will solve. You’ll also outline the features your program will include and how you will use all 15 programming concepts in your project. This is your chance to plan your vision before you start coding, making sure you have a clear direction from the start.
By the end of this stage, you must submit a Project Brief that includes the following structured sections. Use these headlines in your document:
1. Project Overview (150-200 words)
Explain what your program will do.
Describe the problem it aims to solve or the need it addresses.
Identify the intended users of the program and how it will help them.
Format: A well-structured paragraph.
2. Key Features
List the planned features of the program.
Explain how each feature will work and its purpose.
Format: A bullet point list with short explanations.
3. Use of Programming Concepts
Identify all 15 programming concepts and explain how each will be used in the project.
Provide specific examples (e.g., "I will use loops to validate user input" instead of just "I will use loops").
Format: A numbered or bullet-point list with clear explanations for each concept.
4. Planned Inputs, Processes, and Outputs (IPO)
Define how data will be handled in the program.
Use a table format with three sections:
Inputs: What data the program will take from the user.
Processes: What the program will do with that data.
Outputs: What the user will see as a result.
Format: A structured table with three clear sections (Inputs, Processes, Outputs).
5. Challenges & Considerations (100-150 words)
Identify possible challenges in developing the program.
Consider factors such as usability, security, and accessibility.
Format: A well-structured paragraph or bullet points.
Each section is assessed on completion, clarity, and correctness.
Project Overview (150-200 words)
4 – Clearly explains the program’s purpose, problem, and users in detail.
3 – Provides a clear explanation but lacks some depth or clarity.
2 – Mentions the purpose but lacks detail or focus.
1 – Minimal or unclear explanation of the program’s purpose.
Key Features (100-150 words)
4 – Features are well-defined, realistic, and clearly explained.
3 – Features are mostly clear but missing some explanation.
2 – Features are vague or incomplete.
1 – Features are unclear or missing.
Use of Programming Concepts (200-250 words)
4 – All 15 concepts are identified with clear and specific explanations.
3 – Most concepts are identified but some lack explanation.
2 – Some concepts are identified but lack clarity.
1 – Few or no concepts are mentioned, or they lack detail.
IPO Table (100-150 words)
4 – Clearly structured IPO table with relevant details in each section.
3 – IPO table is mostly clear but missing some details.
2 – IPO table lacks clarity or is incomplete.
1 – IPO table is unclear, missing, or incorrect.
Challenges & Considerations (100-150 words)
4 – Identifies key challenges with thoughtful considerations.
3 – Identifies some challenges but lacks depth.
2 – Mentions a few challenges but lacks detail.
1 – No meaningful discussion of challenges.
Total Score: /20
16-20 points – Complete and well-structured Project Brief.
11-15 points – Mostly complete but missing some details.
6-10 points – Basic outline but lacks key elements.
0-5 points – Incomplete or unclear Project Brief.