# VCE Software Development Unit 3 Outcome 2 ## Criterion 4: Generating Design Ideas and Developing Evaluation Criteria Guide This guide provides an in-depth breakdown of how to complete **Criterion 4 (Skills in generating design ideas and developing evaluation criteria)** for the School-assessed Task (SAT) in **VCE Software Development Unit 3 Outcome 2**. It incorporates specifications and requirements from the following official VCAA documents: * **VCE Software Development Administrative Information for School-based Assessment (2026)** (rubric & assessment indicators) * **VCE Applied Computing Study Design (From 2025)** (course structure, concepts & skills) * **VCE Applied Computing: Unit 3 and 4 Software Development: Software tools and functions and outcome-specific requirements** (ideation tools) --- ## 1. Criterion 4 Overview * **Assessment Task:** School-assessed Task (SAT) Unit 3 Outcome 2. * **Focus:** Students generate two to three different design ideas for their software solution using various ideation techniques. They then develop evaluation criteria based on the functional and non-functional requirements to evaluate these design ideas and justify the selection of the preferred design. * **Score Allocation:** Ranked from **0 to 10 marks** across five performance levels (Very Low, Low, Medium, High, Very High). * **Problem-Solving Methodology Stage:** **Design** (specifically ideation and evaluation criteria development). --- ## 2. Assessment Rubric Breakdown (Observation 4) To achieve a high score (9–10 marks), students must address two key indicators: | Performance Level | Marks | Indicator 1: Generating Design Ideas | Indicator 2: Developing & Applying Evaluation Criteria | | :--- | :--- | :--- | :--- | | **Very High** | **9–10** | Generates **feasible, original, and distinctive** design ideas using ideation tools that **fully represent the software solution**. Uses annotations to **describe and justify** appearance and functionality. | Uses the evaluation criteria to **justify** (using logical arguments and evidence) which elements of the design ideas should be further developed into detailed designs. | | **High** | **7–8** | Generates design ideas using **three or more** ideation tools and techniques. Uses annotations to **describe and justify** the appearance and functionality of the software solution. | Uses the evaluation criteria to **explain** (with reasons) which elements of the design ideas should be further developed into detailed designs. | | **Medium** | **5–6** | Generates design ideas using **two** ideation tools. Uses annotations to **explain** the appearance and functionality. | Develops and **applies** evaluation criteria to determine which elements of the design ideas should be further developed. | | **Low** | **3–4** | Illustrates design ideas using **one** ideation tool. Uses annotations to **identify** the appearance. | Outlines criteria to evaluate design ideas and the software solution, with reference to functional and non-functional requirements. | | **Very Low** | **1–2** | **Lists** design ideas for the software solution. | **Identifies measures** (e.g., simple questions) to evaluate design ideas or the software solution. | | **Not Shown** | **0** | Insufficient evidence. | Insufficient evidence. | --- ## 3. Required Ideation Tools & Techniques VCAA mandates specific ideation tools. To achieve a **Very High** score, students must generate **2 to 3 distinct design ideas** and utilize **at least three** of the following tools: ### A. Mood Boards * **Purpose:** Collates visual inspiration (imagery, color palettes, typography, UI layout structures) and code samples. It helps set the overall aesthetic and theme. * **VCAA Rule:** Samples must be annotated to explain their applicability to the proposed solution, what features will or won't be used, and the design rationale. ### B. Brainstorming * **Purpose:** Unstructured collation of ideas surrounding the core problem. * **VCAA Rule:** Can be a list or a diagram. If represented as a diagram, the central theme (the problem/solution name) is in a central shape (cloud, rectangle, ellipse) with related ideas connected via straight lines. ### C. Mind Maps * **Purpose:** Structured, hierarchical collation of related ideas. * **VCAA Rule:** A diagram with a central theme in a shape, branching out into main ideas (e.g., Database, UI, Security, Features) which then branch further into specific solutions or requirements. ### D. Sketches * **Purpose:** Quick, unrefined illustrations showing user interface layouts or demonstrating how components link and interact. * **VCAA Rule:** Can be hand-drawn or digitally drawn. Unlike mock-ups, these are rough and focus on quick conceptual layout exploration. --- ## 4. Crafting High-Quality Annotations Annotations are the key to scoring in the **High/Very High** bands. Annotations must not just point to an element; they must **describe** and **justify** both appearance and functionality. > [!IMPORTANT] > **Identify (1–4 Marks):** *"This is a blue submit button."* > **Explain (5–6 Marks):** *"This button is blue to fit the ocean theme, and clicking it submits the registration form data."* > **Describe & Justify (7–10 Marks):** *"The submit button uses a high-contrast dark blue (#1D3557) background with bold white text. This satisfies the design principle of **Contrast**, ensuring users with visual impairments can easily locate the primary action (appearance). When clicked, it validates all form inputs and writes a new record to the database (functionality). This is justified as it enforces data integrity before submission, minimizing runtime errors."* --- ## 5. Developing Evaluation Criteria (Efficiency & Effectiveness) Evaluation criteria are developed during the Design stage to determine how well the design ideas meet requirements. They must be developed with reference to the **functional and non-functional requirements** from the SRS (Criterion 3). The VCAA Study Design dictates that these criteria must focus on **Efficiency** and **Effectiveness**: ### A. Efficiency (How well the solution uses resources) * **Speed/Response Time:** How quickly does the algorithm run or load pages? * **Processing Power / Memory Usage:** How light is the solution on CPU and RAM? * **Developer Effort / Time:** How complex is the design to program within the timeframe? * **User Action Efficiency:** How few clicks or keystrokes does it take a user to complete a task? ### B. Effectiveness (How well the solution meets requirements and user needs) * **Accuracy:** Are the calculations and database writes correct and error-free? * **Usability:** Is the interface intuitive, clean, and accessible? * **Security:** Does the design protect user credentials and personal data? * **Relevance:** Does the solution actually solve the client's problem? --- ## 6. How to Apply and Justify the Preferred Design (Indicator 2) To secure **9–10 marks**, students must use their evaluation criteria to **justify** which elements of their design ideas are carried forward into the detailed designs. This is best done in two steps: ### Step 1: Create an Evaluation Matrix Create a table comparing the generated design ideas (e.g., Design Idea 1 vs. Design Idea 2) against the criteria. | ID | Criterion | Source (SRS Req) | Focus | Design Idea 1 | Design Idea 2 | | :--- | :--- | :--- | :--- | :--- | :--- | | **C1** | Can the user log in within 3 seconds? | Non-functional (Performance) | **Efficiency** | **High:** Uses simple text inputs with minimal script loading. | **Medium:** Uses animated transitions which may delay load times on older hardware. | | **C2** | Is user data protected from unauthorized views? | Non-functional (Security) | **Effectiveness** | **Low:** Plaintext database connection, local file storage. | **High:** Encrypted database hosting with secure password hashing. | | **C3** | Does the interface provide clear navigation pathways? | Non-functional (Usability) | **Effectiveness** | **High:** Side navigation bar with persistent links. | **Medium:** Drop-down menu that hides options. | ### Step 2: Write the Justification Statement Underneath the matrix, write a formal justification that explains why the preferred design was selected. > [!TIP] > **Example Justification:** > *"Based on the evaluation matrix, **Design Idea 2** has been selected as the preferred design to be developed into detailed designs. Although Design Idea 1 scored higher in load efficiency (due to its text-only interface), Design Idea 2 is significantly more effective at meeting the security constraint (C2) and usability requirement (C3). Design Idea 2 incorporates secure password hashing, which satisfies APP 11 (Security) and prevents unauthorized database access. Furthermore, its side navigation bar provides clear affordance for navigation, which outweighs the slight speed increase of Design Idea 1. Therefore, Design Idea 2 represents the most feasible and complete solution for the client."* --- ## 7. Student Checklist for a Very High Score (9–10 Marks) - [ ] **Folio of Design Ideas:** - [ ] Generated **at least 2–3 distinct design ideas** (e.g., contrasting layouts, navigation systems, or database architectures). - [ ] Used **at least three ideation tools** (Mood Board, Brainstorming, Mind Map, or Sketches) to document these ideas. - [ ] Design ideas are **original** (custom layouts, not direct copies of templates) and **feasible** (can be realistically programmed in the selected language). - [ ] **Detailed Annotations:** - [ ] Annotations are attached directly to the visual ideation tools. - [ ] Annotations **describe** the exact appearance and functionality of key elements. - [ ] Annotations **justify** design choices by explicitly referencing design principles (e.g., Alignment, Space, Contrast) or UX characteristics (e.g., Affordance, Usability). - [ ] **Evaluation Criteria Development:** - [ ] Developed a formal table of **evaluation criteria** directly linked to the SRS requirements. - [ ] Each criterion is explicitly classified as assessing **Efficiency** or **Effectiveness**. - [ ] Developed a grading scale (e.g., 1–5 or Low/Med/High) to measure the criteria. - [ ] **Justification & Selection:** - [ ] Applied the evaluation criteria to all design ideas within a matrix or table. - [ ] Provided a written **justification** explaining which design (or elements of both) is selected as the preferred design, supported by logical evidence from the evaluation matrix.