Embedded Files
Before writing any code, you need a detailed plan for how your program will work. In this stage, you’ll break down your project using abstraction and decomposition and create a development plan to guide your work. You’ll also design an IPO table, flowchart, and pseudocode, each representing a different key part of your program. These tools will help you structure your ideas and think through your logic before you start coding.
Requirements: Design & Development Planning
Requirements: Design & Development Planning
By the end of this stage, you must submit a Design & Development Plan that includes the following structured sections. Use these headlines in your document:
1. Development Plan
Break down the main features from your Project Brief into smaller, manageable tasks using abstraction and decomposition.
Outline the step-by-step order in which you will develop features (e.g., setting up a user interface first, then adding data processing).
Identify dependencies between different parts of the program (e.g., "Before implementing user authentication, I need to create a database to store login details").
Ensure that all 15 programming concepts from your Project Brief are accounted for in your plan. You don't need to list them, but you must include and highlight the key words in your development plan to show that you have considered them all in your proposal. You must include a clear idea of the objects
Format: Several well-structured paragraphs that explicitly connect to features from Stage 1: Project Brief & Initial Planning.
2. Planned Inputs, Processes, and Outputs (IPO)
Select one key part of your program from the Key Features section of your Project Brief and break it down using an IPO Table.
Clearly define the Inputs, Processes, and Outputs for that feature.
Ensure that the IPO matches what you described in Stage 1.
3. Flowchart
Create a flowchart to represent the logic of a different key part of your program than the IPO Table.
The flowchart should be based on one of the features you described in Stage 1.
It must follow standard flowchart symbols (lozenge, rectangle, diamond, parallelogram, arrows) and clearly show decision-making, loops, and processes where applicable.
Format: A properly formatted flowchart image or diagram.
4. Pseudocode
Write pseudocode for another key part of your program, ensuring it is different from the process covered in the IPO Table and Flowchart.
The pseudocode must be based on a critical algorithm or function planned in Stage 1 Key Features.
Ensure the logic matches the program structure outlined in your Development Plan.
Format: A structured pseudocode block that follows logical coding conventions.
5. Class Design & Object Relationships (150-200 words)
List the classes you plan to create in your program.
Describe the relationships between these classes (e.g., inheritance, composition, interactions).
Select two key classes and describe them in detail:
List their attributes (variables) and explain their purpose.
List their methods (functions) and describe what they do.
Format: A bulleted list for the classes that you will create, a well-structured paragraph for overall class relationships, followed by a bullet-point list for two key classes.
Rubric: Design & Development Planning
Rubric: Design & Development Planning
Development Plan
4 – Clearly breaks down the problem, outlines the development steps logically, and connects to Stage 1 features and programming concepts.
3 – Provides a good plan but lacks some connections to Stage 1 or detail in dependencies.
2 – Mentions steps but lacks clear links to Stage 1 or logical order.
1 – Minimal or unclear development plan with no clear progression from Stage 1.
Planned Inputs, Processes, and Outputs (IPO)
4 – Well-structured IPO table clearly based on a key feature from Stage 1.
3 – IPO table is mostly clear but missing some connection to Stage 1.
2 – IPO table lacks clarity, is incomplete / does not align with Stage 1.
1 – IPO table is unclear, missing / does not relate to Stage 1 features.
Flowchart
4 – Clear, well-structured flowchart representing a different key process from Stage 1.
3 – Mostly correct flowchart but missing some logical connections to Stage 1.
2 – Basic flowchart that lacks key elements or proper alignment with Stage 1.
1 – No flowchart or flowchart is unclear / does not relate to Stage 1.
Pseudocode
4 – Well-structured, logical pseudocode that reflects a different process from the IPO Table and Flowchart, clearly linked to Stage 1 features.
3 – Mostly clear pseudocode structure and logic / missing some link to Stage 1.
2 – Basic pseudocode with missing steps or unclear logic / not well-connected to Stage 1.
1 – No pseudocode or it is incomplete and unclear.
Class Design & Object Relationships
4 – Clearly lists all planned classes and explains relationships between them. Two key classes are described in detail, with clear attributes and methods.
3 – Lists most planned classes and describes relationships. Two key classes are included, but descriptions lack some detail.
2 – Some planned classes are listed, but relationships are unclear. Key class descriptions are incomplete.
1 – Little or no class design explanation, or the descriptions lack clear attributes and methods.
Total Score: /20
16-20 points – Complete and well-structured Design & Development Plan with strong connections to Stage 1.
11-15 points – Mostly complete but missing some details or links to Stage 1.
6-10 points – Basic outline but lacks key elements and clear progression from Stage 1.
0-5 points – Incomplete or unclear Design & Development Plan with little connection to Stage 1.
Page updated
Google Sites
Report abuse