<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://sfi.opencodingsociety.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://sfi.opencodingsociety.com/" rel="alternate" type="text/html" /><updated>2026-11-20T01:19:07+00:00</updated><id>https://sfi.opencodingsociety.com/feed.xml</id><title type="html">SFI Foundation</title><subtitle>Standards for the quality assurance of specialty performance and racing equipment.</subtitle><entry><title type="html">D292 Task 1: Ideation for an E-Learning Solution</title><link href="https://sfi.opencodingsociety.com/wgu/d292/task1-ideation/" rel="alternate" type="text/html" title="D292 Task 1: Ideation for an E-Learning Solution" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d292/D292_Plagiarism-WGU-SGM2-Task1-Ideation-Higher-Level-Education_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d292/task1-ideation/"><![CDATA[<!-- Converted from: Plagiarism-WGU-SGM2-Task1-Ideation-Higher-Level-Education.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:03 -->
<!-- Images extracted: 0 -->

<h4 id="weaver-university-higher-education--ideates-solutions-to-an-instructional-problem"><strong>Weaver University Higher Education | Ideates Solutions to an Instructional Problem</strong></h4>

<h4 id="a-lxd-foundations-i--context"><strong>A. LXD Foundations I | Context</strong></h4>

<h4 id="a1-instructional-setting-and-target-learners"><strong>A1. Instructional Setting and Target Learners</strong></h4>

<p>As a member of the LxD team, I am assigned to improve the instructional problems at Weaver University in WR001.</p>

<p>My focus in the “Empathize” phase of Design Thinking was on two groups:</p>

<p>High-tech and diverse – Group D. This group consists of highly technical and diverse learners. They are active in e-learning, enjoy online options, and bring significant prior knowledge and work experience in their fields. These students are credentialing in the USA and are highly motivated, especially when given opportunities to share knowledge with peers.</p>

<p>Low-tech and diverse – Group H. This group is equally capable and motivated. They are pursuing education in their field of passion in a new country. These learners are dedicated but prefer low-tech approaches. They would rather read a book than engage with a mobile app. They often study in isolation, sometimes excessively, without guidance from more experienced peers.</p>

<h4 id="a2-instructional-problem"><strong>A2. Instructional Problem</strong></h4>

<ul>
  <li>WR001 data shows less than 82% mastery in several key skills:
    <ul>
      <li>APA citation (70%)</li>
      <li>Mini-research paper (74%)</li>
      <li>Coherency (75%)</li>
      <li>Style (78%)</li>
    </ul>
  </li>
  <li>
    <p>Discussion boards and peer activities are underutilized, even though peer collaboration (87%) is one of the stronger factors.</p>
  </li>
  <li><strong>Problem:</strong> Students are not mastering critical academic writing skills, partly due to weak engagement with collaborative tools that support writing and skill development.</li>
</ul>

<h4 id="a3-ksas-and-gap-analysis"><strong>A3. KSAs and Gap Analysis</strong></h4>

<p>High-tech learners (Group D):</p>

<ul>
  <li>
    <p>Knowledge (Current): Strong subject knowledge; understand the importance of academic integrity and proper citations. One student explained, “I know the importance of including the work of other scholars… I am very focused on making sure I follow the rules for proper citations and references.”</p>
  </li>
  <li>
    <p>Skills (Current): Highly skilled with technology and comfortable navigating digital tools to support writing. Knows the importance and rules for APA citations and references.</p>
  </li>
  <li>
    <p>Abilities (Current): Can mentor or collaborate with peers but currently lack structured opportunities or audiences to share expertise.</p>
  </li>
  <li>
    <p>Desired State: High-tech learners need opportunities to apply their skills by mentoring peers and reinforcing best practices in APA and research writing.</p>
  </li>
</ul>

<p>Low-tech learners (Group H):</p>

<ul>
  <li>
    <p>Knowledge (Current): Developing subject knowledge; some view APA as a one-time requirement rather than an ongoing academic standard. One student reflected, “Am I going to have to do more with APA? I thought it was just for this class.”</p>
  </li>
  <li>
    <p>Skills (Current): Dedicated but inefficient; prefer printed or traditional study methods over digital tools, often avoiding platforms like discussion boards.</p>
  </li>
  <li>
    <p>Abilities (Current): Desire to follow rules but struggle without explicit instruction and guidance. As one student noted, “It’s even better if I can print everything… I don’t really like using [technology] for school.”</p>
  </li>
  <li>
    <p>Desired State: Low-tech learners need structured, guided practice in APA and research writing, supported by clear expectations and accessible tools.</p>
  </li>
</ul>

<p>Gap:</p>

<ul>
  <li>
    <p>Current state: Students demonstrate uneven understanding and inconsistent application of APA citation and research writing skills. Group D has expertise but no structured outlet to share; Group H lacks clarity and avoids digital supports that could help them improve.</p>
  </li>
  <li>
    <p>Desired state: Both groups actively engage in collaborative, structured learning opportunities that improve mastery of APA citation, coherency, and research paper development.</p>
  </li>
</ul>

<p><strong>A4. Problem Statement</strong></p>

<ul>
  <li>
    <p>Learners in WR001 need structured ways to strengthen academic writing skills (APA citation, coherency, research paper development) because current performance data shows less than 82% mastery.</p>
  </li>
  <li>
    <p>Students are not consistently engaging in collaborative practices (e.g., drafts, discussion boards, peer review) that support writing growth.</p>
  </li>
  <li>
    <p>Low-tech learners, in particular, may avoid online tools, limiting their access to peer and instructor feedback.</p>
  </li>
  <li>
    <p>Without intervention, students will continue to underperform in key writing skills essential for success in higher education.</p>
  </li>
</ul>

<p><strong>B. Goal</strong></p>

<p>Students will demonstrate improved mastery of key academic writing skills (APA citation, coherency, research paper development), which are essential for avoiding plagiarism, maintaining academic integrity, and success in WR001.</p>

<p><strong>C. Objectives</strong></p>

<ul>
  <li>
    <p>Low-tech and high-tech students need opportunities aligned to their specific skill gap areas as identified in quantitative data.</p>
  </li>
  <li>
    <p>Students need collaborative tools and peer engagement processes (e.g., revised discussion boards) that foster deeper writing skill development and engagement.</p>
  </li>
  <li>
    <p>Teachers need to act as constructivists, using quantitative data to guide instructional decisions that help students close identified gaps and get engaged with recommended tools and platforms.</p>
  </li>
</ul>

<table>
  <tbody>
    <tr>
      <td>**B. Ideate</td>
      <td>Design Thinking Methods**</td>
    </tr>
  </tbody>
</table>

<p><strong>B1. Experience with the Ideation Process</strong></p>

<p>I engaged in the ideation process by brainstorming while walking and reflecting on both cognitive and social–emotional aspects of student learning. This process exemplified divergent thinking because I allowed myself to generate a wide range of possible solutions, not limited to traditional instruction.</p>

<p>I used “How Might We?” framing questions and connected ideas to theories such as Connectivism and Merrill’s Problem-Centered Approach. This helped me consider solutions that addressed both mastery of APA and writing skills, as well as the collaborative and motivational needs of students.</p>

<p><strong>B2. Artifact of Ideation</strong></p>

<p>Since most of my brainstorming took place during a walk, I captured my thinking in a sticky-notes style table. This table reflects the range of ideas I considered and how I framed them through lower levels of Bloom’s Taxonomy.</p>

<p>Sticky notes brainstorming</p>

<table>
  <thead>
    <tr>
      <th> </th>
      <th> </th>
      <th> </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Make a mock research paper(s) that help frame what needs to be done.</td>
      <td>Work in pairs to encourage active communication and memories.</td>
      <td>Create authentic opportunities for less experienced cohorts to work with more experienced cohorts.</td>
    </tr>
    <tr>
      <td>Be sure Teacher is guiding and setting up event that help achieve Goals to improve standards</td>
      <td>Try to include more “why” in the discussion like intellectual property rights.</td>
      <td>Help students understand the value of citations or be sure that learning value is graded and instructed in a way that they feel knowledge is transferred to future work.</td>
    </tr>
  </tbody>
</table>

<p>Framing questions using lower Bloom’s Taxonomy, Cognitive Approach to problem</p>

<table>
  <thead>
    <tr>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>How Might We?</td>
      <td>Idea #1 - Understand</td>
      <td>Idea #2 - Apply</td>
      <td>Idea #3 - Evaluate</td>
    </tr>
  </tbody>
</table>

<table>
  <tbody>
    <tr>
      <td>Learn rules for APA?</td>
      <td>Develop short outline on APA rules</td>
      <td>Create references in Mock paper and validate rules and references with AI</td>
      <td>Set up workshop or peer events where you review others references</td>
    </tr>
    <tr>
      <td>Learn in-text citations?</td>
      <td>Develop citation examples for review.</td>
      <td>Create mock research paper using proper APA and citations.</td>
      <td>Add citations to the APA workshop</td>
    </tr>
    <tr>
      <td>Avoid Plagiarism?</td>
      <td>Talk about content licensing and rules (ie creative commons, trademark, etc)</td>
      <td>Develop before and after examples plagiarism versus APA and citation.</td>
      <td>Discuss landmark cases of plagiarism and consequences.</td>
    </tr>
    <tr>
      <td>Improve Collaborative tools?</td>
      <td>Teacher circulates information on communities.</td>
      <td>Teacher sponsors and mandates attendance at some required events in communities on avoiding plagiarism</td>
      <td>The teacher nominates experienced students to lead cohort events and to capture assessment or analytics on attendees</td>
    </tr>
    <tr>
      <td>Increase coherency in research papers?</td>
      <td>A mock research paper(s) template is created with intention of citing sources and following APA guidelines. This is posted to e-learning or app.</td>
      <td>Students with a cohort are tasked to work together in live share workshop session to properly craft APA references and citations.</td>
      <td>Leaders of cohort engage with live share session of pair cohorts. They monitor, support, and then evaluate mastery.</td>
    </tr>
  </tbody>
</table>

<p><strong>B3. Three Distinct Ideas to Address the Instructional Problem</strong></p>

<p>The instructional problem is that learners in WR001 are not mastering critical academic writing skills (APA citation, coherency, and research paper development) because they are not consistently engaging in collaborative practices that support growth. From my ideation process, I generated three distinct ideas:</p>

<ol>
  <li><strong>APA Citation Workshops</strong>
    <ul>
      <li><strong>Description:</strong> Peer-led workshops where students bring drafts and practice inserting APA in-text citations and references.</li>
      <li><strong>Addresses the problem by:</strong> Providing structured opportunities for practice with immediate feedback.</li>
    </ul>
  </li>
  <li><strong>Plagiarism Case Studies</strong>
    <ol>
      <li><strong>Description:</strong> Group activities that examine real-world plagiarism cases, discuss consequences, and practice rewriting with proper citations.</li>
      <li><strong>Addresses the problem by</strong> Building conceptual understanding of academic integrity and the importance of correct citation.</li>
    </ol>
  </li>
  <li><strong>Mock Research Paper Live Share</strong>
    <ol>
      <li><strong>Description:</strong> Structured sessions pairing new learners with cohort experts to review and properly cite paper using a rubric.</li>
      <li><strong>Addresses the problem by:</strong> Increasing peer interaction and engagement in collaborative learning.</li>
    </ol>
  </li>
</ol>

<p><strong>C. Prototype One-Hour E-Learning Module</strong></p>

<p><strong>C1. Learning Objective</strong></p>

<p>Learners will apply correct APA citation techniques to revise a research paper that contains plagiarism errors, demonstrating mastery of academic integrity skills required for WR001.</p>

<p><strong>C2. Module Description</strong></p>

<p>The proposed one-hour e-learning module is the <strong>“APA Citation Workshop.”</strong> This session addresses a fundamental mastery challenge—avoiding plagiarism—by integrating two complementary strategies: direct instruction in APA citation and a <strong>Plagiarism Case Study</strong> to capture learner attention and increase relevance.</p>

<p>The workshop follows <strong>Merrill’s First Principles of Instruction</strong>:</p>

<ul>
  <li><strong>Activation</strong>
    <ul>
      <li>Present a research paper containing plagiarism.</li>
      <li>Discuss the academic and professional consequences of plagiarism.</li>
      <li>Equip learners with guidelines for correction.</li>
    </ul>
  </li>
  <li><strong>Demonstration</strong>
    <ul>
      <li>Instructor models correcting one example as a class activity.</li>
      <li>Advanced cohorts perform a live demonstration of revisions.</li>
      <li>A pre-recorded video is available for replay and reinforcement.</li>
    </ul>
  </li>
  <li><strong>Application</strong>
    <ul>
      <li>Learners revise the remaining plagiarism errors in the research paper.</li>
      <li>Provide a rubric detailing common citation fault.</li>
      <li>Small peer groups (1:8–10 ratio) give immediate feedback.</li>
    </ul>
  </li>
  <li><strong>Integration</strong>
    <ul>
      <li>Learners demonstrate mastery by earning a completion certificate.</li>
      <li>The module concludes by assigning the next scaffolded task: drafting a <strong>Mock Research Paper</strong>.</li>
    </ul>
  </li>
</ul>

<p><strong>C3. Learner Experience</strong></p>

<p>Learners will progress through the <strong>lower levels of Bloom’s Taxonomy</strong>:</p>

<ul>
  <li>
    <p><strong>“Remember</strong>:” The instructional video and presentation help learners recall citation rules.</p>
  </li>
  <li>
    <p><strong>“Understand”:</strong> Activation and demonstration phases build conceptual knowledge.</p>
  </li>
  <li>
    <p><strong>“Apply”</strong>: Learners immediately practice correcting citations using the rubric.</p>
  </li>
  <li>
    <p><strong>“Analyze”</strong>: Learners evaluate the research paper, identify errors, and justify corrections.</p>
  </li>
</ul>

<p>This hybrid design combines <strong>Merrill’s problem-centered approach</strong> with <strong>Fink’s Human Dimension</strong>, using real failure cases to promote deeper, personally meaningful learning.</p>

<p><strong>C4. Supporting Learning Theories</strong></p>

<ul>
  <li>
    <p><strong>Fink’s Taxonomy (Human Dimension)</strong>: By analyzing plagiarism in a real case, learners connect emotionally and socially to the problem, recognizing its impact on academic identity.</p>
  </li>
  <li>
    <p><strong>Connectivism</strong>: Advanced cohorts guide sessions, creating peer-to-peer learning opportunities and strengthening student connections to the wider learning community.</p>
  </li>
</ul>

<p><strong>C5. Assessment</strong></p>

<p>Learning will be assessed through:</p>

<ul>
  <li>
    <p>Performance on the rubric (accuracy of corrections).</p>
  </li>
  <li>
    <p>Recorded results (e.g., completion time, number of corrections).</p>
  </li>
  <li>
    <p>Peer and instructor feedback on accuracy and clarity.</p>
  </li>
</ul>

<p><strong>C6. Meeting Target Learner Needs</strong></p>

<p>The module is designed for both high-tech and low-tech learners:</p>

<ul>
  <li>
    <p><strong>Low-tech learners</strong>: Receive explicit, guided practice in a structured environment before being asked to produce their own paper.</p>
  </li>
  <li>
    <p><strong>High-tech learners</strong>: Serve as mentors or cohort leaders, reinforcing their expertise while contributing to peer learning.</p>
  </li>
</ul>

<p>By the end of the module, all learners will:</p>

<ul>
  <li>
    <p>Demonstrate confidence in “applying” APA citation.</p>
  </li>
  <li>
    <p>Qualify for the next level of learning, the <strong>Mock Research Paper</strong> assignment.</p>
  </li>
</ul>

<p><strong>D. Acknowledgment of Sources</strong></p>

<p>No sources used outside of WGU-provided materials.</p>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d292" /><summary type="html"><![CDATA[Plagiarism lesson. Students will brainstorm and outline their ideas for an e-learning solution, focusing on innovative approaches to instructional design.]]></summary></entry><entry><title type="html">D292 Task 2: Storyboard for an E-Learning Solution</title><link href="https://sfi.opencodingsociety.com/wgu/d292/task2-storyboard/" rel="alternate" type="text/html" title="D292 Task 2: Storyboard for an E-Learning Solution" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d292/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d292/task2-storyboard/"><![CDATA[<!-- Converted from: Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:03 -->
<!-- Images extracted: 9 -->

<table>
  <tbody>
    <tr>
      <td>**Weaver University Higher Education</td>
      <td>Creates a Storyboard for an E-Learning Solution**</td>
    </tr>
  </tbody>
</table>

<h4 id="a-context"><strong>A. Context</strong></h4>

<p><strong>A1. LxD Foundation 1</strong></p>

<h4 id="a1-instructional-setting-and-target-learners"><strong>A1. Instructional Setting and Target Learners</strong></h4>

<p>As a member of the LxD team, I am assigned to improve the instructional problems at Weaver University in WR001.</p>

<p>My focus in the “Empathize” phase of Design Thinking was on two groups:</p>

<p>High-tech and diverse – Group D. This group consists of highly technical and diverse learners. They are active in e-learning, enjoy online options, and bring significant prior knowledge and work experience in their fields. These students are credentialing in the USA and are highly motivated, especially when given opportunities to share knowledge with peers.</p>

<p>Low-tech and diverse – Group H. This group is equally capable and motivated. They are pursuing education in their field of passion in a new country. These learners are dedicated but prefer low-tech approaches. They would rather read a book than engage with a mobile app. They often study in isolation, sometimes excessively, without guidance from more experienced peers.</p>

<p><strong>B. Goal</strong></p>

<p>Students will demonstrate improved mastery of key academic writing skills (APA citation, coherency, research paper development), which are essential for avoiding plagiarism, maintaining academic integrity, and success in WR001.</p>

<p><strong>A2. LxD Foundation 2</strong></p>

<p><strong>C1. Learning Objective</strong></p>

<p>Learners will apply correct APA citation techniques to revise a research paper that contains plagiarism errors, demonstrating mastery of academic integrity skills required for WR001.</p>

<p><strong>C2. Module Description</strong></p>

<p>The proposed one-hour e-learning module is the <strong>“APA Citation Workshop.”</strong> This session addresses a fundamental mastery challenge—avoiding plagiarism—by integrating two complementary strategies: direct instruction in APA citation and a <strong>Plagiarism Case Study</strong> to capture learner attention and increase relevance.</p>

<p>The workshop follows <strong>Merrill’s First Principles of Instruction</strong>:</p>

<ul>
  <li><strong>Activation</strong>
    <ul>
      <li>Present a research paper containing plagiarism.</li>
      <li>Discuss the academic and professional consequences of plagiarism.</li>
      <li>Equip learners with guidelines for correction.</li>
    </ul>
  </li>
  <li><strong>Demonstration</strong>
    <ul>
      <li>Instructor models correcting one example as a class activity.</li>
      <li>Advanced cohorts perform a live demonstration of revisions.</li>
      <li>A pre-recorded video is available for replay and reinforcement.</li>
    </ul>
  </li>
  <li><strong>Application</strong>
    <ul>
      <li>Learners revise the remaining plagiarism errors in the research paper.</li>
      <li>Provide a rubric detailing common citation fault.</li>
      <li>Small peer groups (1:8–10 ratio) give immediate feedback.</li>
    </ul>
  </li>
  <li><strong>Integration</strong>
    <ul>
      <li>Learners demonstrate mastery by earning a completion certificate.</li>
      <li>The module concludes by assigning the next scaffolded task: drafting a <strong>Mock Research Paper</strong>.</li>
    </ul>
  </li>
</ul>

<p><strong>C3. Learner Experience</strong></p>

<p>Learners will progress through the <strong>lower levels of Bloom’s Taxonomy</strong>:</p>

<ul>
  <li>
    <p><strong>“Remember</strong>:” The instructional video and presentation help learners recall citation rules.</p>
  </li>
  <li>
    <p><strong>“Understand”:</strong> Activation and demonstration phases build conceptual knowledge.</p>
  </li>
  <li>
    <p><strong>“Apply”</strong>: Learners immediately practice correcting citations using the rubric.</p>
  </li>
  <li>
    <p><strong>“Analyze”</strong>: Learners evaluate the research paper, identify errors, and justify corrections.</p>
  </li>
</ul>

<p>This hybrid design combines <strong>Merrill’s problem-centered approach</strong> with <strong>Fink’s Human Dimension</strong>, using real failure cases to promote deeper, personally meaningful learning.</p>

<p><strong>B. Part I: Refining an E-Learning Solution</strong></p>

<p><strong>B1. Incorporating UDL Principles</strong></p>

<p>To refine the e-learning solution, each of the three <strong>Universal Design for Learning (UDL)</strong> principles—<strong>Engagement (The Why), Representation (The What), and Action &amp; Expression (The How)</strong>—can be intentionally integrated:</p>

<p><strong>Engagement (The Why)</strong></p>

<ul>
  <li>
    <p>Provide an authentic task by presenting a mock research paper containing plagiarism.</p>
  </li>
  <li>
    <p>Discuss the academic and professional consequences of plagiarism to capture interest and motivation.</p>
  </li>
  <li>
    <p>Foster community through small peer groups that review and revise mock papers together.</p>
  </li>
  <li>
    <p><em>Refinement</em>: Incorporate structured reflection activities so learners can connect new knowledge to personal goals and prior experiences.</p>
  </li>
</ul>

<p><strong>Representation (The What)</strong></p>

<ul>
  <li>
    <p>Present content through multiple modalities: instructor presentation, live demonstration, and recorded video for review.</p>
  </li>
  <li>
    <p><em>Refinement</em>: Strengthen connections to prior learning by explicitly linking plagiarism and citation instruction to earlier assignments in WR001.</p>
  </li>
</ul>

<p><strong>Action &amp; Expression (The How)</strong></p>

<ul>
  <li>
    <p>Support learning through small peer-mentor groups (1:8–10 ratio) that provide immediate, formative feedback.</p>
  </li>
  <li>
    <p>Allow learners to demonstrate progress by correcting plagiarism errors in a shared paper.</p>
  </li>
  <li>
    <p><em>Refinement</em>: Integrate assistive technologies (e.g., captions on video, citation management tools) to ensure accessibility for all learners.</p>
  </li>
</ul>

<p><strong>B2. Measurement for Learning Objective</strong></p>

<p>Learner progress toward the objective (“Apply correct APA citation techniques to revise a research paper”) can be measured using a structured rubric. The rubric provides clear expectations for performance, guides peer review, and allows for formative and summative assessment.</p>

<p><strong>Rubric for APA Citation Correction</strong></p>

<table>
  <thead>
    <tr>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Criterion</td>
      <td><strong>Proficient (3 pts)</strong></td>
      <td><strong>Developing (2 pts)</strong></td>
      <td><strong>Needs Work (1 pt)</strong></td>
    </tr>
    <tr>
      <td><strong>Quotation Formatting</strong></td>
      <td>All quotes are enclosed in quotation marks and punctuated correctly.</td>
      <td>Some quotes missing quotation marks or incorrect punctuation.</td>
      <td>Many quotes are missing quotation marks or incorrectly punctuated.</td>
    </tr>
    <tr>
      <td><strong>In-Text Citations</strong></td>
      <td>All quotes include proper APA in-text citation (author, year, page/line if applicable).</td>
      <td>Some quotes missing elements (e.g., year, page) or formatted incorrectly.</td>
      <td>Most or all quotes are missing or incorrectly cited.</td>
    </tr>
    <tr>
      <td><strong>Reference List</strong></td>
      <td>Complete reference list in correct APA format with all sources cited in-text.</td>
      <td>Partial reference list, some APA formatting errors.</td>
      <td>Reference list missing, incomplete, or incorrectly formatted.</td>
    </tr>
    <tr>
      <td><strong>Plagiarism Identification</strong></td>
      <td>Demonstrates clear correction of all plagiarism by citing original sources</td>
      <td>Corrects some plagiarism issues but leaves gaps.</td>
      <td>Fails to correct plagiarism; most sources uncited.</td>
    </tr>
  </tbody>
</table>

<p><strong>B3. Instructional Strategy Guiding the Storyboard</strong></p>

<p>The design of the storyboard is guided by <strong>Merrill’s First Principles of Instruction</strong>, which provide a structured framework for sequencing learner activities:</p>

<ol>
  <li>
    <p><strong>Activation</strong>: Learners are presented with a flawed research paper containing plagiarism.</p>
  </li>
  <li>
    <p><strong>Demonstration</strong>: The instructor and advanced cohorts model how to identify and correct citation errors.</p>
  </li>
  <li>
    <p><strong>Application</strong>: Learner’s practice correcting the remaining errors using a rubric, with peer mentors providing immediate feedback.</p>
  </li>
  <li>
    <p><strong>Integration</strong>: Learners reflect on the activity and apply their skills in the next scaffolded assignment (a Mock Research Paper).</p>
  </li>
  <li>
    <p>This strategy supports both high-tech and low-tech learners identified in the analysis (Part A). High-tech learners contribute as peer mentors, while low-tech learners benefit from guided, structured practice.</p>
  </li>
  <li>
    <p>By aligning Merrill’s principles with UDL, the solution not only scaffolds instruction but also ensures inclusivity and accessibility. My reflection shows that what began as a focus on <strong>problem-centered instruction</strong> in ideation now clearly intersects with <strong>UDL principles</strong> as I move into prototyping.</p>
  </li>
</ol>

<p><strong>B4. Storyboard to Objectives Planning</strong></p>

<p>The storyboard will be organized to align directly with the instructional strategy from B3 and the learning objective from Part A: Learners will apply correct APA citation techniques to revise a research paper that contains plagiarism errors. The storyboard will detail personas, mock content, and the sequence of e-learning materials so that both high-tech and low-tech learners can achieve mastery.</p>

<p><strong>Preparation of Content</strong></p>

<ol>
  <li>
    <p><strong>Instructor or administrator uploads the flawed research paper, rubric, and instructional video into the LMS.</strong></p>
  </li>
  <li>
    <p><strong>Persona roles are integrated into the storyboard to ensure scaffolding for both high-tech (mentor roles) and low-tech learners (guided practice).</strong></p>
  </li>
</ol>

<p><strong>Demonstration of Content</strong></p>

<ol>
  <li>
    <p><strong>The advanced cohorts (mentor roles) present citation correction through live demonstrations and share references to recorded examples and rubric.</strong></p>
  </li>
  <li>
    <p><strong>The storyboard will emphasize design features (clear visuals, chunked steps, replayable videos) that support diverse learner needs.</strong></p>
  </li>
</ol>

<p><strong>Application and Assessment</strong></p>

<ol>
  <li>
    <p><strong>Learner’s practice correcting citations and building an APA reference list within the mock paper.</strong></p>
  </li>
  <li>
    <p><strong>The rubric is embedded as both a guide and an assessment tool, with peer mentors providing immediate feedback.</strong></p>
  </li>
  <li>
    <p><strong>Assessment data (rubric scores, completion, feedback) is captured to document progress toward the objective.</strong></p>
  </li>
  <li>
    <p><strong>This storyboard plan ensures that instruction flows logically from preparation to demonstration to application, reinforcing Merrill’s First Principles of Instruction while incorporating UDL principles for inclusivity and accessibility.</strong></p>
  </li>
</ol>

<p><strong>C. Part II: Storyboard Prototype</strong></p>

<p>The LxD storyboard approach below uses GitHub Pages, Markdown, and HTML. It is published on the internet <a href="https://jm1021.github.io/student/english/plagiarism">here</a>, but all relevant elements for this assignment are captured within the document in slide-like visuals.</p>

<p><strong>C1a. Why Plagiarism Matters</strong></p>

<p>Page 1: Key questions and content, this would likely be personalized by the instructor.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_image9.png" alt="Image 9" /></p>

<p><strong>C1b. Introduction</strong></p>

<p>Page 2: Insight provided to the learner on the training objectives. This is Merril’s 1st principle with slight modifications to meet objectives of this assignment.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_imagea.png" alt="Image a" /></p>

<p><strong>C2a. The Importance of Plagiarism</strong></p>

<p>Page 3: Grab learners’ attention with plagiarism cases.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_imageb.png" alt="Image b" /></p>

<p><strong>C2c. Practice correcting errors</strong></p>

<p>Page 4: This is where the citation learning happens.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_imagec.png" alt="Image c" /></p>

<p>Workshop Tool</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_imaged.png" alt="Image d" /></p>

<p>Tool Sample</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_imagee.png" alt="Image e" /></p>

<p><strong>C2d Group Workshop</strong></p>

<p>Page 5: Group meeting to correct paper that lacks citations and references.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_imagef.png" alt="Image f" /></p>

<p><strong>C3a. Assessment of Workshop</strong></p>

<p>Page 6: Instructor assessment.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_image10.png" alt="Image 10" /></p>

<p><strong>C3b. Summary</strong></p>

<p>Page 7: Student learning outcome.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task2-Storyboard-Higher-Level-Education_image11.png" alt="Image 11" /></p>

<p><strong>D. Acknowledgment of Sources</strong></p>

<p>No sources used outside of WGU-provided materials. Sources used in visuals are self-contained and managed outside of this document.</p>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d292" /><summary type="html"><![CDATA[Plagiarism lesson. Students will create a storyboard for their e-learning solution, outlining the key components and flow of the instructional materials.]]></summary></entry><entry><title type="html">D292 Task 3: Prototype Mockup for an E-Learning Solution</title><link href="https://sfi.opencodingsociety.com/wgu/d292/task3-mockup/" rel="alternate" type="text/html" title="D292 Task 3: Prototype Mockup for an E-Learning Solution" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d292/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d292/task3-mockup/"><![CDATA[<!-- Converted from: Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:04 -->
<!-- Images extracted: 21 -->

<p><strong>Prototype Mockup for an E-Learning Solution on Plagiarism Avoidance</strong></p>

<h4 id="a-context"><strong>A. Context</strong></h4>

<p>Section ‘A.’ contains LXD Foundations materials to provide context for plagiarism instructional problem evaluated in a Weaver University case study:</p>

<p><strong>Task 1 - C1. Learning Objective</strong></p>

<p>Learners will apply correct APA citation techniques to revise a research paper that contains plagiarism errors, demonstrating mastery of academic integrity skills required for WR001.</p>

<p><strong>Task 2 - C. Storyboard</strong></p>

<p>The LxD storyboard uses GitHub Pages, Markdown, and HTML. It is published on the internet <a href="https://jm1021.github.io/student/english/plagiarism/storyboard/">here</a>, but all relevant elements for this assignment are captured within the document in slide-like visuals.</p>

<p><strong>Task 2 - C1a. Why Plagiarism Matters</strong></p>

<p>Page 1: Key questions and content; this would likely be personalized by the instructor.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image9.png" alt="Image 9" /></p>

<p><strong>Task 2 - C1b. Introduction</strong></p>

<p>Page 2: Insight provided to the learner on the training objectives. This is Merril’s 1st principle with slight modifications to meet objectives of this assignment.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_imagea.png" alt="Image a" /></p>

<p><strong>Task 2 - C2a. The Importance of Plagiarism</strong></p>

<p>Page 3: Grab learners’ attention with plagiarism cases.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_imageb.png" alt="Image b" /></p>

<p><strong>Task 2 - C2c. Practice correcting errors</strong></p>

<p>Page 4: This is where the citation learning happens.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_imagec.png" alt="Image c" /></p>

<p>Workshop Tool</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_imaged.png" alt="Image d" /></p>

<p>Tool Sample</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_imagee.png" alt="Image e" /></p>

<p><strong>Task 2 - C2d Group Workshop</strong></p>

<p>Page 5: Group meeting to correct paper that lacks citations and references.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_imagef.png" alt="Image f" /></p>

<p><strong>Task 2 - C3a. Assessment of Workshop</strong></p>

<p>Page 6: Instructor assessment.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image10.png" alt="Image 10" /></p>

<p><strong>Task 2 - C3b. Summary</strong></p>

<p>Page 7: Student learning outcomes.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image11.png" alt="Image 11" /></p>

<p><strong>B. Original E-Learning Training Module</strong></p>

<p>This plagiarism workshop system is a <strong>sophisticated, multi-module e-learning solution</strong> that far exceeds the basic mockup requirements. Instead of 6-10 screens, I have prototyped a <strong>6-module learning system.</strong></p>

<p><strong>This document is intended to cover requirements. However, the system is online and is at:</strong></p>

<p><a href="https://pages.opencodingsociety.com/plagiarism"><strong>https://pages.opencodingsociety.com/plagiarism</strong></a></p>

<p><strong>Generative AI features require a login (user: hop, password: 123Hop!) at:</strong></p>

<p><a href="https://pages.opencodingsociety.com/login"><strong>https://pages.opencodingsociety.com/login</strong></a></p>

<p><strong>Return to link on plagiarism (above) after login.</strong></p>

<ul>
  <li>
    <p>User navigation with progress tracking and introduction</p>
  </li>
  <li>
    <p>Cross-module data integration, progression to support tracking</p>
  </li>
  <li>
    <p>Plagiarism case studies C1</p>
  </li>
  <li>
    <p>Mastery modules C2, C3, C4, each formative, but as whole they are summative</p>
  </li>
  <li>
    <p>Assessment Module C5</p>
  </li>
  <li>
    <p>Student Mastery Certificate</p>
  </li>
  <li>
    <p>Generative AI support in C2 (API citation generator is a must try)</p>
  </li>
  <li>
    <p>Generative AI support (Plagiarism detection, Thesis building, 5-paragraph essay, Research paper)</p>
  </li>
  <li>
    <p>Instructor assessment tools</p>
  </li>
  <li>
    <p>Certificate generation</p>
  </li>
  <li>
    <p>UI/UX/LxD design to meet Task 3 requirements</p>
  </li>
  <li>
    <p>Contains the Test Mode buttons to support quick module transitions.<img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image12.png" alt="Image 12" /></p>
  </li>
</ul>

<p><strong>B1a. Navigation and Tracking Page (clipped 2/6)</strong></p>

<p>The landing page serves as the central navigation point to launch the “Why Source?” Introduction.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image13.png" alt="Image 13" /></p>

<p><strong>B2a. Introduction Page (Intro at top, fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image14.png" alt="Image 14" /></p>

<p><strong>B2a. Introduction Page (Rubric, fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image15.png" alt="Image 15" /></p>

<p><strong>B. C1 Content – Plagiarism Case Studies (fragment)</strong></p>

<p>Includes Video and Audio players.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image16.png" alt="Image 16" /></p>

<p><strong>B. C2 Content – API Reference Instruction (clipped)</strong></p>

<p>Includes Generative AI and formative assessment data that is passed to C5.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image17.png" alt="Image 17" /></p>

<p><strong>B. C3 Content – Reference Correction Practice (fragment)</strong></p>

<p>Includes formative assessment data that is passed to C5.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image18.png" alt="Image 18" /></p>

<p><strong>B. C4 Content – Plagiarism Avoidance Workshop (fragment)</strong></p>

<p>Includes Generative AI to support plagiarism checks and summative assessment data that is passed to C5.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image19.png" alt="Image 19" /></p>

<p><strong>B. C5-1 Instructor Review (clipped)</strong></p>

<p>Displays key learning achievements by students from C2, C3, C4. Supports grading and comments.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image1a.png" alt="Image 1a" /></p>

<p><strong>B. C5-2 Instructor Assessment (fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image1b.png" alt="Image 1b" /></p>

<p><strong>B. C6-1 Student Master Completed (clipped)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image1c.png" alt="Image 1c" /></p>

<p><strong>B. C6-2 Student Master Completed (fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task3-Mockup-Higher-Level-Education_image1d.png" alt="Image 1d" /></p>

<p><strong>C. Explain Sensory and Interactive Elements</strong></p>

<p>Review of learning achievements.</p>

<p><strong>Visuals and Graphic Design Principles</strong></p>

<ul>
  <li>
    <p>The navigation page provides custom SVG icons for each module</p>
  </li>
  <li>
    <p>Progress bar shows progressions</p>
  </li>
  <li>
    <p>Status badges (locked/available/completed)</p>
  </li>
  <li>
    <p>Card hover effects with shimmer animations</p>
  </li>
</ul>

<p><strong>Interactivity:</strong></p>

<ul>
  <li>
    <p>Click-to-progress module unlocking</p>
  </li>
  <li>
    <p>Interactive form submissions with real-time validation</p>
  </li>
  <li>
    <p>Auto-loading data between modules</p>
  </li>
  <li>
    <p>Quick comment template buttons for instructors</p>
  </li>
  <li>
    <p>Frontend/Backend Generative AI API presentations</p>
  </li>
</ul>

<p><strong>Videos:</strong></p>

<ul>
  <li>
    <p>Working link embedded in C1 Plagiarism Cases card</p>
  </li>
  <li>
    <p>Video links staged for Navigation elements (TBD)</p>
  </li>
  <li>
    <p>Framework ready for audio narration (video links support this)</p>
  </li>
</ul>

<p>Audio:</p>

<ul>
  <li>Audio player integration on C1</li>
</ul>

<p><strong>How This Meets Academic Requirements</strong></p>

<p><strong>C1. Visual &amp; Graphic Design Principles:</strong></p>

<ul>
  <li>
    <p>White Space: Clean card layouts with proper padding, breathing room between elements</p>
  </li>
  <li>
    <p>Visual Hierarchy: Clear typography scales (h2, h3), color-coded status system, logical information flow</p>
  </li>
  <li>
    <p>Alignment: Grid-based layout, consistent button alignment, centered progress elements</p>
  </li>
  <li>
    <p>Movement: Smooth transitions, hover animations, progress bar fills, card lifting effects</p>
  </li>
</ul>

<p><strong>C2. Usability Best Practices:</strong></p>

<ul>
  <li>
    <p>Effectiveness: Sequential learning path ensures goal achievement</p>
  </li>
  <li>
    <p>Efficiency: Auto-loading eliminates manual data entry, quick templates speed instructor feedback</p>
  </li>
  <li>
    <p>Engagement: Interactive exercises, visual progress tracking, achievement system</p>
  </li>
  <li>
    <p>Error Tolerance: Graceful localStorage fallbacks, clear error messages, retry mechanisms</p>
  </li>
  <li>
    <p>Ease of Learning: Intuitive navigation, consistent interface patterns, clear status indicators</p>
  </li>
</ul>

<p><strong>C3. Universal Design for Learning (UDL):</strong></p>

<ul>
  <li>
    <p><strong>Engagement:</strong> Multiple learning modalities (video, text, interactive exercises), progress gamification</p>
  </li>
  <li>
    <p><strong>Representation:</strong> Text + visual + interactive content, self-pacing through module system</p>
  </li>
  <li>
    <p><strong>Action &amp; Expression:</strong> Multiple assessment formats, instructor feedback options, student choice in completion order</p>
  </li>
</ul>

<p><strong>C4. Accessibility:</strong></p>

<ul>
  <li>
    <p><strong>Perceivability:</strong> High contrast design, clear typography, meaningful color coding beyond color alone</p>
  </li>
  <li>
    <p><strong>Operability:</strong> Keyboard navigation support, touch-friendly buttons, logical tab order</p>
  </li>
  <li>
    <p><strong>Understandability:</strong> Consistent navigation patterns, clear status messages, predictable interactions</p>
  </li>
</ul>

<p><strong>D. Acknowledgment of Sources</strong></p>

<p>No sources used outside of WGU-provided materials. Sources used in visuals are self-contained and managed outside of this document.</p>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d292" /><summary type="html"><![CDATA[Plagiarism lesson. Students will create a prototype mockup for an e-learning solution, demonstrating their understanding of instructional design principles and user experience.]]></summary></entry><entry><title type="html">D292 Task 4: Test Plan for an E-Learning Solution</title><link href="https://sfi.opencodingsociety.com/wgu/d292/task4-test-plan/" rel="alternate" type="text/html" title="D292 Task 4: Test Plan for an E-Learning Solution" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d292/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d292/task4-test-plan/"><![CDATA[<!-- Converted from: Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:04 -->
<!-- Images extracted: 15 -->

<p><strong>Usability Test Plan for an E-Learning Solution on Plagiarism Avoidance</strong></p>

<h4 id="a-context"><strong>A. Context</strong></h4>

<p>This document provides a Test Plan on the E-Learning prototype developed for the problems which were identified in the Weaver University case study.</p>

<p><strong>A1. Learning Objective</strong></p>

<p>Learners will apply correct APA citation techniques to revise a research paper that contains plagiarism errors, demonstrating mastery of academic integrity skills required for WR001.</p>

<p><strong>A2. Original E-Learning Training Module</strong></p>

<p>This plagiarism workshop system is a <strong>sophisticated, multi-module e-learning solution</strong> that far exceeds the basic mockup requirements. Instead of 6-10 screens, I have prototyped a <strong>6-module learning system.</strong></p>

<p><strong>This document is intended to cover requirements. However, the system is online and is at:</strong></p>

<p><a href="https://pages.opencodingsociety.com/plagiarism"><strong>https://pages.opencodingsociety.com/plagiarism</strong></a></p>

<p><strong>Generative AI features require a login (user: hop, password: 123Hop!) at:</strong></p>

<p><a href="https://pages.opencodingsociety.com/login"><strong>https://pages.opencodingsociety.com/login</strong></a></p>

<p><strong>Return to link on plagiarism (above) after login.</strong></p>

<ul>
  <li>
    <p>User navigation with progress tracking and introduction</p>
  </li>
  <li>
    <p>Cross-module data integration, progression to support tracking</p>
  </li>
  <li>
    <p>Plagiarism case studies C1</p>
  </li>
  <li>
    <p>Mastery modules C2, C3, C4, each formative, but as whole they are summative</p>
  </li>
  <li>
    <p>Assessment Module C5</p>
  </li>
  <li>
    <p>Student Mastery Certificate</p>
  </li>
  <li>
    <p>Generative AI support in C2 (API citation generator is a must try)</p>
  </li>
  <li>
    <p>Generative AI support (Plagiarism detection, Thesis building, 5-paragraph essay, Research paper)</p>
  </li>
  <li>
    <p>Instructor assessment tools</p>
  </li>
  <li>
    <p>Certificate generation</p>
  </li>
  <li>
    <p>UI/UX/LxD design to meet Task 3 requirements</p>
  </li>
  <li>
    <p>Contains the Test Mode buttons to support quick module transitions.<img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image12.png" alt="Image 12" /></p>
  </li>
</ul>

<p><strong>A2a. Navigation and Tracking Page (clipped 2/6)</strong></p>

<p>The landing page serves as the central navigation point to launch the “Why Source?” Introduction.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image13.png" alt="Image 13" /></p>

<p><strong>A2b. Introduction Page (Intro at top, fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image14.png" alt="Image 14" /></p>

<p><strong>A2 . Introduction Page (Rubric, fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image15.png" alt="Image 15" /></p>

<p><strong>A2d. C1 Content – Plagiarism Case Studies (fragment)</strong></p>

<p>Includes Video and Audio players.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image16.png" alt="Image 16" /></p>

<p><strong>A2e. C2 Content – API Reference Instruction (clipped)</strong></p>

<p>Includes Generative AI and formative assessment data that is passed to C5.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image17.png" alt="Image 17" /></p>

<p><strong>A2f. C3 Content – Reference Correction Practice (fragment)</strong></p>

<p>Includes formative assessment data that is passed to C5.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image18.png" alt="Image 18" /></p>

<p><strong>A2g. C4 Content – Plagiarism Avoidance Workshop (fragment)</strong></p>

<p>Includes Generative AI to support plagiarism checks and summative assessment data that is passed to C5.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image19.png" alt="Image 19" /></p>

<p><strong>A2h. C5-1 Instructor Review (clipped)</strong></p>

<p>Displays key learning achievements by students from C2, C3, C4. Supports grading and comments.</p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image1a.png" alt="Image 1a" /></p>

<p><strong>A2i. C5-2 Instructor Assessment (fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image1b.png" alt="Image 1b" /></p>

<p><strong>A2j. C6-1 Student Master Completed (clipped)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image1c.png" alt="Image 1c" /></p>

<p><strong>A2k. C6-2 Student Master Completed (fragment)</strong></p>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image1d.png" alt="Image 1d" /></p>

<h4 id="b-purpose-of-testing-and-potential-benefits"><strong>B. Purpose of Testing and Potential Benefits</strong></h4>

<p>Primary Purpose</p>

<p>The usability testing for the Plagiarism Prevention Quest serves a dual educational and developmental purpose, utilizing Test-Driven Development (TDD) methodology to rapidly improve the e-learning solution while simultaneously teaching students essential user experience design principles.</p>

<p>The dual purpose of timing aligns with my academic instruction, and testing this turned out to be a significant help in my students starting their own ideation and prototyping. This plan was executed on October 15, 2025.</p>

<p>Specific Benefits</p>

<p><strong>For the E-Learning Solution:</strong></p>

<ul>
  <li>
    <p><strong>Rapid Iteration:</strong> TDD approach enables quick identification and resolution of critical usability issues</p>
  </li>
  <li>
    <p><strong>User-Centered Design:</strong> Direct feedback from target audience (high school students) ensures age-appropriate design decisions</p>
  </li>
  <li>
    <p><strong>Cross-Platform Validation:</strong> Testing on both mobile and laptop devices identifies platform-specific issues</p>
  </li>
  <li>
    <p><strong>Performance Optimization:</strong> Real-world usage patterns reveal system bottlenecks and AI tool response time issues</p>
  </li>
</ul>

<p><strong>For Student Learning:</strong></p>

<ul>
  <li>
    <p><strong>Experiential Learning:</strong> Students gain hands-on experience with usability testing methodologies they can apply to their own projects</p>
  </li>
  <li>
    <p><strong>Design Thinking Development:</strong> Participants learn to think critically about user experience and interface design</p>
  </li>
  <li>
    <p><strong>Collaborative Skills:</strong> Group testing format develops teamwork and communication abilities</p>
  </li>
  <li>
    <p><strong>Transfer Learning:</strong> Testing experience directly supports students’ final quest-building projects</p>
  </li>
</ul>

<p><strong>For Instructional Design:</strong></p>

<ul>
  <li>
    <p><strong>Evidence-Based Improvements:</strong> Quantifiable feedback data drives prioritized development sprints</p>
  </li>
  <li>
    <p><strong>Learning Objective Validation:</strong> Testing confirms whether educational goals are being met effectively</p>
  </li>
  <li>
    <p><strong>Scalability Assessment:</strong> Determines if the quest format of plagiarism learning can be successfully applied to other subject areas</p>
  </li>
</ul>

<h4 id="c-parts-of-e-learning-solution-to-be-tested"><strong>C. Parts of E-Learning Solution to be Tested</strong></h4>

<p>Core Module Components</p>

<p><strong>C1: Case Studies Module</strong></p>

<ul>
  <li>
    <p>Navigation through plagiarism scenarios</p>
  </li>
  <li>
    <p>Video content functionality and engagement</p>
  </li>
  <li>
    <p>Audio integration and accessibility</p>
  </li>
  <li>
    <p>Interactive case study activities</p>
  </li>
  <li>
    <p>Content comprehension and retention</p>
  </li>
</ul>

<p><strong>C2: APA Reference &amp; Citation Training</strong></p>

<ul>
  <li>
    <p>Quote Finder tool usability</p>
  </li>
  <li>
    <p>Interactive citation building interface</p>
  </li>
  <li>
    <p>Auto-fill functionality and accuracy</p>
  </li>
  <li>
    <p>Reference generation workflow</p>
  </li>
  <li>
    <p>Practice exercises and immediate feedback</p>
  </li>
</ul>

<p><strong>C3: Error Correction Practice</strong></p>

<ul>
  <li>
    <p>Error identification interface</p>
  </li>
  <li>
    <p>Correction workflow and guidance</p>
  </li>
  <li>
    <p>Feedback mechanisms and validation</p>
  </li>
  <li>
    <p>Exercise progression and difficulty scaling</p>
  </li>
</ul>

<p><strong>C4: Build Your Own Document</strong></p>

<ul>
  <li>
    <p>AI-powered content creation tools</p>
  </li>
  <li>
    <p>Citation integration during writing</p>
  </li>
  <li>
    <p>Real-time plagiarism detection features</p>
  </li>
  <li>
    <p>Document export and submission functionality</p>
  </li>
</ul>

<p><strong>C5: Instructor Evaluation Interface</strong></p>

<ul>
  <li>
    <p>Data transfer from C1-C4 modules to instructor dashboard</p>
  </li>
  <li>
    <p>Automated grading and assessment compilation</p>
  </li>
  <li>
    <p>Instructor comment and feedback system</p>
  </li>
  <li>
    <p>Student progress tracking and analytics</p>
  </li>
  <li>
    <p>Grading efficiency and speed evaluation</p>
  </li>
</ul>

<p><strong>C6: Student Certification Award</strong></p>

<ul>
  <li>
    <p>Certificate generation based on completed modules</p>
  </li>
  <li>
    <p>Student achievement recognition system</p>
  </li>
  <li>
    <p>Progress visualization and completion status</p>
  </li>
  <li>
    <p>Instructor feedback display and accessibility</p>
  </li>
  <li>
    <p>Student motivation and engagement through recognition</p>
  </li>
</ul>

<p>System-Wide Features</p>

<p><strong>Navigation and Progress Tracking</strong></p>

<ul>
  <li>
    <p>Main page quest progression interface</p>
  </li>
  <li>
    <p>Module unlock mechanisms</p>
  </li>
  <li>
    <p>Progress indicators and completion status</p>
  </li>
  <li>
    <p>Cross-module navigation flow</p>
  </li>
</ul>

<p><strong>Authentication and Access Control</strong></p>

<ul>
  <li>
    <p>Login/registration process</p>
  </li>
  <li>
    <p>Guest access capabilities</p>
  </li>
  <li>
    <p>Session management</p>
  </li>
  <li>
    <p>Security and privacy controls</p>
  </li>
</ul>

<p><strong>Mobile Responsiveness</strong></p>

<ul>
  <li>
    <p>Touch interface optimization</p>
  </li>
  <li>
    <p>Screen size adaptability</p>
  </li>
  <li>
    <p>Performance on mobile devices</p>
  </li>
  <li>
    <p>Accessibility features</p>
  </li>
</ul>

<p><strong>Performance and Reliability</strong></p>

<ul>
  <li>
    <p>Page load times</p>
  </li>
  <li>
    <p>AI tool response speeds</p>
  </li>
  <li>
    <p>Error handling and recovery</p>
  </li>
  <li>
    <p>System stability under concurrent usage</p>
  </li>
</ul>

<p><strong>D. Test Objectives and Specific Learning Goal</strong>s</p>

<p>Primary Learning Objectives</p>

<p><strong>Objective 1: Validate Educational Effectiveness</strong></p>

<ul>
  <li>
    <p><strong>Learning Goal:</strong> Confirm students successfully learn plagiarism prevention concepts</p>
  </li>
  <li>
    <p><strong>Assumption to Validate:</strong> Quest-based learning is more engaging than traditional instruction</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> 90%+ of participants demonstrate understanding of plagiarism consequences and proper citation methods</p>
  </li>
</ul>

<p><strong>Objective 2: Assess Usability and User Experience</strong></p>

<ul>
  <li>
    <p><strong>Learning Goal:</strong> Identify specific interface elements that enhance or hinder learning</p>
  </li>
  <li>
    <p><strong>Assumption to Validate:</strong> Current navigation flow supports learning progression</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> 80%+ task completion rate with minimal assistance</p>
  </li>
</ul>

<p><strong>Objective 3: Evaluate Cross-Platform Compatibility</strong></p>

<ul>
  <li>
    <p><strong>Learning Goal:</strong> Determine if mobile and laptop experiences are equivalent</p>
  </li>
  <li>
    <p><strong>Assumption to Validate:</strong> Mobile-responsive design provides adequate functionality</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> No significant performance or usability differences between platforms</p>
  </li>
</ul>

<p><strong>Objective 4: Test Technical Infrastructure</strong></p>

<ul>
  <li>
    <p><strong>Learning Goal:</strong> Assess system performance under realistic usage conditions</p>
  </li>
  <li>
    <p><strong>Assumption to Validate:</strong> AI tools and backend services can support classroom-scale concurrent usage</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> &lt;5 second response times for all interactive features</p>
  </li>
</ul>

<p><strong>Objective 5: Validate Design Transfer Learning</strong></p>

<ul>
  <li>
    <p><strong>Learning Goal:</strong> Confirm students absorb instructional design principles for their own projects</p>
  </li>
  <li>
    <p><strong>Assumption to Validate:</strong> Observing well-designed quest teaches design thinking</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Participants can articulate specific design elements to implement in their own quests</p>
  </li>
</ul>

<p><strong>E. Usability Metrics to be Gathered</strong></p>

<p>Quantitative Metrics</p>

<p><strong>Task Completion Metrics</strong></p>

<ul>
  <li>
    <p>Completion rate for each module (C1-C6)</p>
  </li>
  <li>
    <p>Time to complete each module</p>
  </li>
  <li>
    <p>Error rate during interactive exercises</p>
  </li>
  <li>
    <p>Success rate for citation building tasks</p>
  </li>
  <li>
    <p>Abandonment points and drop-off rates</p>
  </li>
  <li>
    <p>Understanding rate for instructor interface demonstration (C5)</p>
  </li>
  <li>
    <p>Engagement rate with certification system (C6)</p>
  </li>
</ul>

<p><strong>Performance Metrics</strong></p>

<ul>
  <li>
    <p>Page load times across devices</p>
  </li>
  <li>
    <p>AI tool response times</p>
  </li>
  <li>
    <p>Video loading and playback success rates</p>
  </li>
  <li>
    <p>System error frequency and types</p>
  </li>
  <li>
    <p>Concurrent user capacity testing</p>
  </li>
</ul>

<p><strong>Navigation Metrics</strong></p>

<ul>
  <li>
    <p>Time spent navigating between modules</p>
  </li>
  <li>
    <p>Number of back-and-forth navigation actions</p>
  </li>
  <li>
    <p>Progress indicator usage and understanding</p>
  </li>
  <li>
    <p>Help-seeking behavior frequency</p>
  </li>
</ul>

<p>Qualitative Metrics</p>

<p><strong>User Experience Ratings</strong></p>

<ul>
  <li>
    <p>5-point Likert scale ratings for visual appeal</p>
  </li>
  <li>
    <p>Difficulty rankings (0-5 scale) for each module</p>
  </li>
  <li>
    <p>Engagement level self-assessments</p>
  </li>
  <li>
    <p>Frustration indicators and pain points</p>
  </li>
</ul>

<p><strong>Content Effectiveness Measures</strong></p>

<ul>
  <li>
    <p>Comprehension check performance</p>
  </li>
  <li>
    <p>Retention test scores</p>
  </li>
  <li>
    <p>Practical application success rates</p>
  </li>
  <li>
    <p>Knowledge transfer demonstration</p>
  </li>
</ul>

<p><strong>Design Learning Assessment</strong></p>

<ul>
  <li>
    <p>Ability to identify effective design elements</p>
  </li>
  <li>
    <p>Understanding of quest architecture principles</p>
  </li>
  <li>
    <p>Transfer learning articulation quality</p>
  </li>
  <li>
    <p>Design critique sophistication</p>
  </li>
</ul>

<p><strong>Visual Analytics and Data Representation</strong></p>

<ul>
  <li>
    <p>Chart generation for preference distributions (pie charts, bar graphs)</p>
  </li>
  <li>
    <p>Trend analysis visualizations for completion rates across modules</p>
  </li>
  <li>
    <p>Cross-platform comparison matrices (mobile vs. laptop performance)</p>
  </li>
  <li>
    <p>Priority mapping visualizations combining impact, frequency, and severity scores</p>
  </li>
  <li>
    <p>Progress flow diagrams showing user journey through C1-C6 modules</p>
  </li>
</ul>

<p><strong>F. Usability Performance Goals</strong></p>

<p>Critical Performance Thresholds</p>

<p><strong>Task Success Goals</strong></p>

<ul>
  <li>
    <p>95% completion rate for C1 (Case Studies)</p>
  </li>
  <li>
    <p>90% completion rate for C2 (APA Training)</p>
  </li>
  <li>
    <p>85% completion rate for C3 (Error Correction)</p>
  </li>
  <li>
    <p>90% completion rate for C4 (Document Building)</p>
  </li>
  <li>
    <p>95% completion rate for C5 (Instructor Evaluation - demonstration)</p>
  </li>
  <li>
    <p>90% completion rate for C6 (Student Certification - demonstration)</p>
  </li>
  <li>
    <p>80% completion rate for full quest sequence (C1-C6)</p>
  </li>
</ul>

<p><strong>Efficiency Goals</strong></p>

<ul>
  <li>
    <p>Average module completion time: 5-7 minutes</p>
  </li>
  <li>
    <p>Total quest completion time: 25-30 minutes</p>
  </li>
  <li>
    <p>Navigation between modules: &lt;30 seconds</p>
  </li>
  <li>
    <p>AI tool response time: &lt;5 seconds</p>
  </li>
  <li>
    <p>Video loading time: &lt;10 seconds</p>
  </li>
</ul>

<p><strong>User Satisfaction Goals</strong></p>

<ul>
  <li>
    <p>Visual appeal rating: &gt;3.5/5</p>
  </li>
  <li>
    <p>Difficulty rating: 2.5-3.5/5 (appropriately challenging)</p>
  </li>
  <li>
    <p>Engagement level: &gt;4/5</p>
  </li>
  <li>
    <p>Likelihood to recommend: &gt;80%</p>
  </li>
  <li>
    <p>Design learning transfer: &gt;85% can articulate specific principles</p>
  </li>
</ul>

<p><strong>Technical Performance Goals</strong></p>

<ul>
  <li>
    <p>System uptime: 99.5% during testing periods</p>
  </li>
  <li>
    <p>Error rate: &lt;5% for all interactive features</p>
  </li>
  <li>
    <p>Mobile performance parity: &lt;10% difference from laptop</p>
  </li>
  <li>
    <p>Concurrent user support: 50+ simultaneous users</p>
  </li>
  <li>
    <p>Cross-browser compatibility: 95% functionality across major browsers</p>
  </li>
</ul>

<p><strong>G. Usability Tasks and Scenarios</strong></p>

<p>Pre-Test Scenario Setup</p>

<p><strong>Scenario:</strong> “You are part of a design team tasked with evaluating an educational quest system. Your goal is to experience the learning content while thinking like a UX designer. You’ll be testing both the educational effectiveness and the user interface design.”</p>

<p>Module-Specific Tasks</p>

<p><em>Note: Each task is performed by the 3-person testing group structure (Mobile Tester, Laptop Tester, Group Recorder) as detailed in Section H, ensuring comprehensive cross-platform evaluation and systematic feedback capture.</em></p>

<p><strong>C1: Case Studies Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Navigate to Case Studies module and complete all scenarios</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “Review each plagiarism case and identify the consequences. Pay attention to how the information is presented and how easy it is to understand.”</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Complete all case studies and demonstrate understanding of consequences</p>
  </li>
  <li>
    <p><strong>Design Focus:</strong> Evaluate video functionality, audio integration, and content layout</p>
  </li>
  <li>
    <p><strong>Group Role Application:</strong></p>
    <ul>
      <li><strong>Mobile Tester:</strong> Focus on video playback, touch navigation, and mobile content readability</li>
      <li><strong>Laptop Tester:</strong> Assess full video functionality, audio controls, and detailed interface elements</li>
      <li><strong>Recorder:</strong> Document which platform handles multimedia content more effectively</li>
    </ul>
  </li>
</ol>

<p><strong>C2: APA Training Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Use Quote Finder tool to locate relevant quotes for a given topic</p>
  </li>
  <li>
    <p><strong>Task:</strong> Build complete APA citations using the interactive tools</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “Imagine you’re writing a research paper on climate change. Use the tools to find appropriate quotes and create proper citations.”</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Successfully generate accurate APA citations</p>
  </li>
  <li>
    <p><strong>Design Focus:</strong> Assess tool usability, workflow efficiency, and learning support</p>
  </li>
  <li>
    <p><strong>Group Role Application:</strong></p>
    <ul>
      <li><strong>Mobile Tester:</strong> Test touch interactions with citation tools, mobile form usability</li>
      <li><strong>Laptop Tester:</strong> Evaluate full tool functionality, auto-fill features, complex workflows</li>
      <li><strong>Recorder:</strong> Compare efficiency and accuracy between platforms</li>
    </ul>
  </li>
</ol>

<p><strong>C3: Error Correction Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Identify citation errors in provided examples</p>
  </li>
  <li>
    <p><strong>Task:</strong> Correct errors using system guidance</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “You’ve been given examples of student work with citation mistakes. Find and fix the errors using the available tools.”</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Correctly identify and fix 80% of errors</p>
  </li>
  <li>
    <p><strong>Design Focus:</strong> Evaluate feedback quality, error highlighting, and correction workflow</p>
  </li>
  <li>
    <p><strong>Group Role Application:</strong></p>
    <ul>
      <li><strong>Mobile Tester:</strong> Assess error highlighting visibility, correction interface usability on small screens</li>
      <li><strong>Laptop Tester:</strong> Test detailed feedback mechanisms, comprehensive error detection features</li>
      <li><strong>Recorder:</strong> Document which platform provides clearer error guidance</li>
    </ul>
  </li>
</ol>

<p><strong>C4: Document Building Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Create original content using AI-powered tools</p>
  </li>
  <li>
    <p><strong>Task:</strong> Integrate proper citations during the writing process</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “Write a short paragraph on a topic of your choice, using the AI tools to help generate content and ensure proper citations.”</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Produce original content with appropriate citations</p>
  </li>
  <li>
    <p><strong>Design Focus:</strong> Test AI integration, real-time feedback, and writing workflow</p>
  </li>
  <li>
    <p><strong>Group Role Application:</strong></p>
    <ul>
      <li><strong>Mobile Tester:</strong> Evaluate mobile writing experience, AI tool responsiveness, touch typing efficiency</li>
      <li><strong>Laptop Tester:</strong> Test full AI feature set, real-time citation integration, comprehensive writing tools</li>
      <li><strong>Recorder:</strong> Compare AI performance and writing workflow effectiveness across platforms</li>
    </ul>
  </li>
</ol>

<p><strong>C5: Instructor Evaluation Interface Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Observe how student data from C1-C4 transfers to instructor dashboard</p>
  </li>
  <li>
    <p><strong>Task:</strong> Review automated grading compilation and assessment summaries</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “As students, observe how your completed work from C1-C4 automatically appears in the instructor’s grading interface. Notice how this speeds up the grading process.”</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Understand data flow from student modules to instructor evaluation</p>
  </li>
  <li>
    <p><strong>Design Focus:</strong> Evaluate data transfer clarity, grading efficiency demonstration, instructor feedback visibility</p>
  </li>
  <li>
    <p><strong>Group Role Application:</strong></p>
    <ul>
      <li><strong>Mobile Tester:</strong> Assess mobile display of instructor feedback and grading interface</li>
      <li><strong>Laptop Tester:</strong> Evaluate full instructor dashboard functionality and data presentation</li>
      <li><strong>Recorder:</strong> Document understanding of data flow and grading automation benefits</li>
    </ul>
  </li>
</ol>

<p><strong>C6: Student Certification Award Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> View personalized certificate generation based on completed modules</p>
  </li>
  <li>
    <p><strong>Task:</strong> Access instructor comments and feedback through certification system</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “Receive your completion certificate and review instructor feedback. Notice how your progress through C1-C4 is recognized and how instructor comments are integrated.”</p>
  </li>
  <li>
    <p><strong>Success Criteria:</strong> Successfully access certificate and understand achievement recognition system</p>
  </li>
  <li>
    <p><strong>Design Focus:</strong> Test motivation through recognition, feedback accessibility, progress visualization</p>
  </li>
  <li>
    <p><strong>Group Role Application:</strong></p>
    <ul>
      <li><strong>Mobile Tester:</strong> Evaluate mobile certificate display, feedback readability, achievement visualization</li>
      <li><strong>Laptop Tester:</strong> Test full certification interface, detailed feedback access, progress tracking</li>
      <li><strong>Recorder:</strong> Document motivational impact and feedback accessibility across platforms</li>
    </ul>
  </li>
</ol>

<p>Cross-System Tasks</p>

<p><strong>Navigation and Progress Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Navigate through all modules using the main quest interface</p>
  </li>
  <li>
    <p><strong>Task:</strong> Track progress and understand completion status</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “Experience the full quest progression, paying attention to how you know what to do next and how to track your progress.”</p>
  </li>
</ol>

<p><strong>Mobile Experience Tasks</strong></p>

<ol>
  <li>
    <p><strong>Task:</strong> Complete at least one full module on mobile device</p>
  </li>
  <li>
    <p><strong>Task:</strong> Compare mobile and laptop experiences</p>
  </li>
  <li>
    <p><strong>Scenario:</strong> “Test the system on your phone and compare it to the laptop experience. Note any differences in functionality or usability.”</p>
  </li>
</ol>

<p>Expected Feedback Examples</p>

<p><em>Based on actual testing results from 100+ students, participants typically provide feedback like:</em></p>

<p><strong>Improvement Priority Responses:</strong> - <em>“My team suggested editing the layout of the page to be extra visually appealing. Such as adding visuals like diagrams, editing font colors and sizes, etc. Just appealing for kids our age in general.”</em> - <em>“We would improve the UI because we found it difficult to keep going back to the main page to proceed to the next stage.”</em> - <em>“Maybe include like check marks when each section of the module is finished, so when we move on, we know that the next module is unlocked and we can progress.”</em> - <em>“Have a next button after each section so we don’t have to go back to the main page and switch.”</em></p>

<p><strong>Learning Transfer Evidence:</strong> - <em>“I learned the progression system and how it locks features and we can implement that into our own design.”</em> - <em>“We learned to make our quest progressive and include elements of ‘leveling up’ to make it a more interactive and genuine experience.”</em> - <em>“I learned to break up the quest into different sections ranging from activation, demonstration, practice, application, assessment, and integration.”</em> - <em>“The integration of AI was something that we could integrate into our own design.”</em></p>

<p><strong>Usability Challenge Identification:</strong> - <em>“Our team didn’t find any major issues, but one minor problem that occurred was that each feature, such as the ‘Analyzing text’ feature took a while to load would end up not working.”</em> - <em>“It was a little difficult to understand what each of the settings can be used for, so at the top there could be more explanation on the purpose of the different tools and their applications”</em> - <em>“For the phone, some instructions are hard to read because they did not fit onto the screen.”</em></p>

<p><strong>H. Test Methodology</strong></p>

<p>Test Type Components</p>

<p><strong>In-Person Testing</strong></p>

<ul>
  <li>
    <p><strong>Rationale:</strong> Direct observation enables capture of non-verbal cues, immediate clarification of confusion, and real-time collaborative discussion</p>
  </li>
  <li>
    <p><strong>Setting:</strong> Classroom environment with multiple testing stations</p>
  </li>
  <li>
    <p><strong>Benefits:</strong> Natural collaborative learning environment, immediate instructor support, authentic usage context</p>
  </li>
  <li>
    <p><strong>Critical Group Structure:</strong> Groups of 3 with clearly defined roles to ensure comprehensive testing coverage:</p>
    <ul>
      <li><strong>Mobile Tester:</strong> Tests all modules on smartphone/tablet to identify touch interface issues, responsive design problems, and mobile-specific functionality gaps</li>
      <li><strong>Laptop Tester:</strong> Tests all modules on personal laptop (Windows/macOS/Chromebook) to evaluate full feature functionality, detailed workflows, and comprehensive user interface elements</li>
      <li><strong>Group Recorder:</strong> Uses structured Google Form to systematically capture both testers’ feedback, observations, and recommendations while facilitating group discussion</li>
    </ul>
  </li>
</ul>

<p><strong>Assessment Testing</strong></p>

<ul>
  <li>
    <p><strong>Purpose:</strong> Evaluate current system performance against established usability criteria</p>
  </li>
  <li>
    <p><strong>Focus:</strong> Identify specific pain points, measure task completion rates, and assess learning effectiveness</p>
  </li>
  <li>
    <p><strong>Approach:</strong> Structured tasks with defined success criteria and measurable outcomes</p>
  </li>
</ul>

<p><strong>Moderated Testing</strong></p>

<ul>
  <li>
    <p><strong>Structure:</strong> Instructor and student observers guide testing process</p>
  </li>
  <li>
    <p><strong>Benefits:</strong> Ensures consistent procedures, captures detailed qualitative feedback, enables immediate follow-up questions</p>
  </li>
  <li>
    <p><strong>Interaction:</strong> Facilitators encourage think-aloud protocol and collaborative discussion</p>
  </li>
</ul>

<p>Participant Components</p>

<p><strong>Number of Participants</strong></p>

<ul>
  <li>
    <p><strong>Target:</strong> 100+ students across 4 classes</p>
  </li>
  <li>
    <p><strong>Group Structure:</strong> 33-34 groups of 3 students each</p>
  </li>
  <li>
    <p><strong>Statistical Power:</strong> Large sample size enables reliable identification of patterns and statistically significant findings</p>
  </li>
  <li>
    <p><strong>Coverage:</strong> Multiple classes ensure diverse perspectives and usage patterns</p>
  </li>
</ul>

<p><strong>Eligibility Requirements</strong></p>

<ul>
  <li>
    <p><strong>Academic Level:</strong> High school students (grades 9-12)</p>
  </li>
  <li>
    <p><strong>Technical Prerequisites:</strong> Basic computer and internet navigation skills</p>
  </li>
  <li>
    <p><strong>Educational Context:</strong> Currently enrolled in computer science or related technical courses</p>
  </li>
  <li>
    <p><strong>Availability:</strong> Able to participate in 30-minute testing sessions during class time</p>
  </li>
</ul>

<p><strong>Participant Qualifications</strong></p>

<ul>
  <li>
    <p><strong>Technical Skills:</strong> Comfortable using both laptop and mobile devices</p>
  </li>
  <li>
    <p><strong>Collaboration Ability:</strong> Capable of working effectively in small groups</p>
  </li>
  <li>
    <p><strong>Communication Skills:</strong> Able to provide verbal and written feedback</p>
  </li>
  <li>
    <p><strong>Academic Standing:</strong> Regular attendance and engagement in coursework</p>
  </li>
</ul>

<p><strong>Required Skills</strong></p>

<ul>
  <li>
    <p><strong>Digital Literacy:</strong> Proficient with web browsers, form submission, basic troubleshooting</p>
  </li>
  <li>
    <p><strong>Academic Writing:</strong> Understanding of research and citation concepts (even if basic)</p>
  </li>
  <li>
    <p><strong>Critical Thinking:</strong> Ability to evaluate and critique user interface elements</p>
  </li>
  <li>
    <p><strong>Design Awareness:</strong> Basic understanding of what makes websites and apps easy or difficult to use</p>
  </li>
</ul>

<p>Participant Training</p>

<p><strong>Pre-Testing Orientation (5-7 minutes)</strong></p>

<ul>
  <li>
    <p><strong>Mindset Preparation:</strong> “You are testing the system, not being tested by it”</p>
  </li>
  <li>
    <p><strong>Role Clarification:</strong> Participants are UX evaluators and co-designers, not passive learners</p>
  </li>
  <li>
    <p><strong>Testing Approach:</strong> Introduction to thinking aloud and providing constructive feedback</p>
  </li>
  <li>
    <p><strong>Collaboration Guidelines:</strong> How to work effectively in testing groups</p>
  </li>
</ul>

<p><strong>Procedural Training</strong></p>

<ul>
  <li>
    <p><strong>Form Usage:</strong> How to complete feedback forms efficiently and accurately</p>
  </li>
  <li>
    <p><strong>Device Management:</strong> Proper handling of mobile and laptop testing stations</p>
  </li>
  <li>
    <p><strong>Time Management:</strong> Understanding of module time limits and pacing</p>
  </li>
  <li>
    <p><strong>Question Protocol:</strong> When and how to ask for clarification or assistance</p>
  </li>
</ul>

<p><strong>Quality Assurance Training</strong></p>

<ul>
  <li>
    <p><strong>Feedback Standards:</strong> Examples of helpful vs. unhelpful feedback</p>
  </li>
  <li>
    <p><strong>Observation Skills:</strong> What to look for when watching partner’s testing experience</p>
  </li>
  <li>
    <p><strong>Documentation:</strong> How to capture specific examples and quotes</p>
  </li>
  <li>
    <p><strong>Objectivity:</strong> Distinguishing between personal preference and usability issues</p>
  </li>
</ul>

<p>Testing Procedures</p>

<p><strong>Test Setting</strong></p>

<ul>
  <li>
    <p><strong>Environment:</strong> Regular classroom with multiple laptop testing stations</p>
  </li>
  <li>
    <p><strong>Equipment:</strong> Student personal laptops (Windows/macOS/Chromebook) and mobile devices</p>
  </li>
  <li>
    <p><strong>Layout:</strong> Groups of 3 with adequate space for collaboration and observation</p>
  </li>
  <li>
    <p><strong>Technical Setup:</strong> Pre-tested devices with reliable internet connectivity</p>
  </li>
</ul>

<p><strong>Participant Steps</strong></p>

<ol>
  <li>
    <p><strong>Group Formation:</strong> Self-select into groups of 3 students</p>
  </li>
  <li>
    <p><strong>Role Assignment:</strong> Designate mobile tester, laptop tester, and recorder</p>
  </li>
  <li>
    <p><strong>Initial Orientation:</strong> Review testing goals and feedback form structure</p>
  </li>
  <li>
    <p><strong>Module Testing:</strong> Complete C1-C4 modules with continuous feedback capture</p>
  </li>
  <li>
    <p><strong>System Evaluation:</strong> Assess overall navigation and quest experience</p>
  </li>
  <li>
    <p><strong>Instructor Interface Demonstration:</strong> Observe C5 instructor evaluation interface and data transfer from completed modules</p>
  </li>
  <li>
    <p><strong>Certification Experience:</strong> Experience C6 student certificate award and instructor feedback access</p>
  </li>
  <li>
    <p><strong>Wrap-up Discussion:</strong> Share key insights and improvement suggestions, including observations about data flow and grading efficiency</p>
  </li>
</ol>

<p><strong>Observer Steps</strong></p>

<ol>
  <li>
    <p><strong>Setup Verification:</strong> Ensure all groups have necessary materials and understand procedures</p>
  </li>
  <li>
    <p><strong>Process Monitoring:</strong> Circulate to answer questions and ensure consistent methodology</p>
  </li>
  <li>
    <p><strong>Data Collection:</strong> Note patterns, technical issues, and emergent insights</p>
  </li>
  <li>
    <p><strong>Time Management:</strong> Keep groups on schedule while allowing thorough testing</p>
  </li>
  <li>
    <p><strong>Documentation:</strong> Capture photos of completed forms and overall session notes</p>
  </li>
</ol>

<p><strong>I. Roles of Individuals Involved in Testing</strong></p>

<p>Primary Roles</p>

<p><strong>Lead Facilitator (Instructor)</strong></p>

<ul>
  <li>
    <p><strong>Responsibilities:</strong> Overall test coordination, opening presentation, procedural guidance, final wrap-up</p>
  </li>
  <li>
    <p><strong>Specific Tasks:</strong> Introduce testing goals, demonstrate modules, manage timing, address technical issues</p>
  </li>
  <li>
    <p><strong>Qualifications:</strong> Deep knowledge of system functionality, experience with user testing, group management skills</p>
  </li>
  <li>
    <p><strong>During Testing:</strong> Available for complex questions, monitoring overall progress, capturing high-level observations</p>
  </li>
</ul>

<p><strong>Student Observers/Recorders</strong></p>

<ul>
  <li>
    <p><strong>Responsibilities:</strong> Document testing process, capture detailed feedback, assist with form completion</p>
  </li>
  <li>
    <p><strong>Specific Tasks:</strong> Record group discussions, note technical issues, help struggling participants</p>
  </li>
  <li>
    <p><strong>Selection:</strong> Volunteers from testing groups who rotate through observation role</p>
  </li>
  <li>
    <p><strong>Training:</strong> Brief orientation on observation techniques and documentation standards</p>
  </li>
</ul>

<p><strong>Technical Support</strong></p>

<ul>
  <li>
    <p><strong>Responsibilities:</strong> Address device issues, connectivity problems, system errors</p>
  </li>
  <li>
    <p><strong>Specific Tasks:</strong> Reset devices between groups, troubleshoot login issues, document technical failures</p>
  </li>
  <li>
    <p><strong>Availability:</strong> On-call during testing sessions to minimize disruption</p>
  </li>
  <li>
    <p><strong>Documentation:</strong> Maintain log of technical issues for post-test analysis</p>
  </li>
</ul>

<p>Testing Group Roles</p>

<p><strong>Mobile Tester</strong></p>

<ul>
  <li>
    <p><strong>Primary Task:</strong> Complete quest modules using mobile device</p>
  </li>
  <li>
    <p><strong>Focus Areas:</strong> Touch interface usability, responsive design effectiveness, mobile-specific functionality</p>
  </li>
  <li>
    <p><strong>Documentation:</strong> Note mobile-specific issues, compare to laptop experience</p>
  </li>
  <li>
    <p><strong>Collaboration:</strong> Share observations with group, participate in discussions</p>
  </li>
</ul>

<p><strong>Laptop Tester</strong></p>

<ul>
  <li>
    <p><strong>Primary Task:</strong> Complete quest modules using personal laptop (Windows/macOS/Chromebook)</p>
  </li>
  <li>
    <p><strong>Focus Areas:</strong> Full interface functionality, detailed feature assessment, comprehensive workflow evaluation</p>
  </li>
  <li>
    <p><strong>Documentation:</strong> Capture detailed usability observations, test all interactive elements</p>
  </li>
  <li>
    <p><strong>Collaboration:</strong> Compare experiences with mobile tester, provide laptop perspective</p>
  </li>
</ul>

<p><strong>Group Recorder</strong></p>

<ul>
  <li>
    <p><strong>Primary Task:</strong> Document group’s collective feedback and observations</p>
  </li>
  <li>
    <p><strong>Focus Areas:</strong> Synthesize group discussion, complete feedback forms, capture specific quotes</p>
  </li>
  <li>
    <p><strong>Documentation:</strong> Maintain detailed notes, ensure all perspectives captured, submit completed forms</p>
  </li>
  <li>
    <p><strong>Facilitation:</strong> Guide group discussion, ensure all voices heard, manage time efficiently</p>
  </li>
</ul>

<p><strong>J. Impact, Frequency, and Severity Ranking System</strong></p>

<p>Problem Classification Framework</p>

<p><strong>Impact Scale (Task Completion Effect)</strong></p>

<ul>
  <li><strong>Critical (4):</strong> Prevents task completion entirely
    <ul>
      <li>Example: Broken video links preventing module progression</li>
      <li>Response: Immediate fix required, halt testing if necessary</li>
    </ul>
  </li>
  <li><strong>High (3):</strong> Significantly impairs task completion
    <ul>
      <li>Example: Slow AI tool response causing workflow disruption</li>
      <li>Response: Priority fix in next sprint</li>
    </ul>
  </li>
  <li><strong>Medium (2):</strong> Causes minor delays or workarounds
    <ul>
      <li>Example: Unclear instructions requiring help-seeking</li>
      <li>Response: Address in current sprint cycle</li>
    </ul>
  </li>
  <li><strong>Low (1):</strong> Cosmetic or preference issues
    <ul>
      <li>Example: Color scheme preferences</li>
      <li>Response: Consider for future iterations</li>
    </ul>
  </li>
</ul>

<p><strong>Frequency Scale (Occurrence Rate)</strong></p>

<ul>
  <li><strong>Universal (4):</strong> Affects 75%+ of users
    <ul>
      <li>Example: Mobile navigation issues reported by most groups</li>
      <li>Response: Critical priority regardless of severity</li>
    </ul>
  </li>
  <li><strong>Common (3):</strong> Affects 50-74% of users
    <ul>
      <li>Example: Confusion about progress indicators</li>
      <li>Response: High priority for sprint planning</li>
    </ul>
  </li>
  <li><strong>Occasional (2):</strong> Affects 25-49% of users
    <ul>
      <li>Example: Specific content comprehension issues</li>
      <li>Response: Medium priority, investigate patterns</li>
    </ul>
  </li>
  <li><strong>Rare (1):</strong> Affects &lt;25% of users
    <ul>
      <li>Example: Individual technical difficulties</li>
      <li>Response: Low priority unless severe impact</li>
    </ul>
  </li>
</ul>

<p><strong>Severity Scale (User Experience Disruption)</strong></p>

<ul>
  <li><strong>Severe (4):</strong> Causes significant frustration or abandonment
    <ul>
      <li>Example: Authentication barriers preventing access</li>
      <li>Response: Emergency fix required</li>
    </ul>
  </li>
  <li><strong>Moderate (3):</strong> Notable disruption but users continue
    <ul>
      <li>Example: Need to repeatedly navigate back to main page</li>
      <li>Response: Sprint 1 priority</li>
    </ul>
  </li>
  <li><strong>Minor (2):</strong> Slight annoyance or inefficiency
    <ul>
      <li>Example: Font size too small on mobile</li>
      <li>Response: Sprint 2-3 priority</li>
    </ul>
  </li>
  <li><strong>Trivial (1):</strong> Barely noticeable issues
    <ul>
      <li>Example: Minor visual alignment problems</li>
      <li>Response: Sprint 4 or future iteration</li>
    </ul>
  </li>
</ul>

<p>Composite Priority Calculation</p>

<p><strong>Priority Score = (Impact × 3) + (Frequency × 2) + Severity</strong></p>

<ul>
  <li>
    <p>Maximum Score: 36 (Critical impact, universal frequency, severe disruption)</p>
  </li>
  <li>
    <p>Minimum Score: 6 (Low impact, rare frequency, trivial severity)</p>
  </li>
</ul>

<p><strong>Priority Thresholds:</strong></p>

<ul>
  <li>
    <p><strong>P0 (Score 30-36):</strong> Drop everything and fix immediately</p>
  </li>
  <li>
    <p><strong>P1 (Score 24-29):</strong> Critical sprint 1 priority</p>
  </li>
  <li>
    <p><strong>P2 (Score 18-23):</strong> High sprint 2 priority</p>
  </li>
  <li>
    <p><strong>P3 (Score 12-17):</strong> Medium priority for sprint 3</p>
  </li>
  <li>
    <p><strong>P4 (Score 6-11):</strong> Low priority for sprint 4 or future</p>
  </li>
</ul>

<p>Response Protocol by Priority Level</p>

<p><strong>P0 Response (Emergency)</strong></p>

<ul>
  <li>
    <p><strong>Timeline:</strong> Fix within 24 hours</p>
  </li>
  <li>
    <p><strong>Resources:</strong> All available developers</p>
  </li>
  <li>
    <p><strong>Communication:</strong> Immediate notification to stakeholders</p>
  </li>
  <li>
    <p><strong>Testing:</strong> Hot fix deployed with immediate validation</p>
  </li>
</ul>

<p><strong>P1 Response (Critical)</strong></p>

<ul>
  <li>
    <p><strong>Timeline:</strong> Fix within 1 week (Sprint 1)</p>
  </li>
  <li>
    <p><strong>Resources:</strong> Primary development team</p>
  </li>
  <li>
    <p><strong>Communication:</strong> Daily standup tracking</p>
  </li>
  <li>
    <p><strong>Testing:</strong> Full regression testing before deployment</p>
  </li>
</ul>

<p><strong>P2 Response (High)</strong></p>

<ul>
  <li>
    <p><strong>Timeline:</strong> Fix within 2 weeks (Sprint 2)</p>
  </li>
  <li>
    <p><strong>Resources:</strong> Scheduled development capacity</p>
  </li>
  <li>
    <p><strong>Communication:</strong> Weekly progress updates</p>
  </li>
  <li>
    <p><strong>Testing:</strong> Standard QA procedures</p>
  </li>
</ul>

<p><strong>P3/P4 Response (Medium/Low)</strong></p>

<ul>
  <li>
    <p><strong>Timeline:</strong> Fix within 3-4 weeks or next major release</p>
  </li>
  <li>
    <p><strong>Resources:</strong> Available development time</p>
  </li>
  <li>
    <p><strong>Communication:</strong> Sprint planning inclusion</p>
  </li>
  <li>
    <p><strong>Testing:</strong> Batch testing with other improvements</p>
  </li>
</ul>

<p><strong>K. Post-Test Process for Results Management</strong></p>

<p>Reporting and Describing Results</p>

<p><strong>Immediate Data Compilation (Within 24 hours)</strong></p>

<ul>
  <li>
    <p><strong>Quantitative Summary:</strong> Aggregate completion rates, average times, error frequencies across all modules</p>
  </li>
  <li>
    <p><strong>Qualitative Synthesis:</strong> Categorize feedback themes, identify recurring issues, extract representative quotes</p>
  </li>
  <li>
    <p><strong>Priority Matrix Creation:</strong> Apply severity/frequency/impact scoring to create actionable priority rankings</p>
  </li>
  <li>
    <p><strong>Cross-Platform Analysis:</strong> Compare mobile vs. laptop performance and user experience differences</p>
  </li>
</ul>

<p><strong>Comprehensive Report Structure</strong></p>

<ul>
  <li>
    <p><strong>Executive Summary:</strong> Key findings, critical issues, recommended immediate actions</p>
  </li>
  <li>
    <p><strong>Visual Data Analysis:</strong> Charts and graphs showing user preferences, satisfaction ratings, and completion patterns</p>
    <ul>
      <li>Pie charts for UI element preferences (e.g., Page layout: 54.5%, Audio: 36.4%, Video: 9.1%)</li>
    </ul>
  </li>
</ul>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image1e.png" alt="Image 1e" /></p>

<ul>
  <li>
    <ul>
      <li>Bar charts for satisfaction ratings distribution across 1-5 scale (showing 72.7% at levels 4-5)</li>
      <li>Educational effectiveness validation charts (e.g., Quest understanding: 86.4% “Yes”, 13.6% “Somewhat”, 0% “No”)</li>
      <li>Completion rate comparisons across C1-C6 modules</li>
      <li>Cross-platform performance visualizations (mobile vs. laptop)</li>
      <li>Heat maps showing problem frequency and severity clusters</li>
    </ul>
  </li>
  <li>
    <p><strong>Detailed Findings:</strong> Module-by-module analysis with supporting data and user quotes</p>
  </li>
  <li>
    <p><strong>Technical Issues Log:</strong> Complete inventory of bugs, performance problems, and system failures</p>
  </li>
  <li>
    <p><strong>User Experience Insights:</strong> Patterns in navigation behavior, engagement levels, and satisfaction ratings</p>
  </li>
  <li><strong>Design Transfer Learning:</strong> Evidence of students absorbing instructional design principles</li>
</ul>

<p><strong>Stakeholder Communication</strong></p>

<ul>
  <li>
    <p><strong>Student Feedback:</strong> Share how their input directly influences improvements, demonstrate impact of their testing</p>
  </li>
  <li>
    <p><strong>Administrative Report:</strong> Summary of educational effectiveness and technical requirements for scaling</p>
  </li>
  <li>
    <p><strong>Development Team Brief:</strong> Prioritized backlog with clear specifications and user story context</p>
  </li>
</ul>

<p>Evaluating Metrics and Goals</p>

<p><strong>Goal Achievement Assessment</strong></p>

<ul>
  <li>
    <p><strong>Task Completion Analysis:</strong> Compare actual completion rates to target thresholds (95% C1, 90% C2, etc.)</p>
  </li>
  <li>
    <p><strong>Performance Benchmarking:</strong> Measure actual response times against &lt;5 second goals for AI tools</p>
  </li>
  <li>
    <p><strong>User Satisfaction Evaluation:</strong> Assess whether &gt;3.5/5 visual appeal and &gt;80% recommendation rates achieved</p>
  </li>
  <li>
    <p><strong>Learning Objective Validation:</strong> Determine if 90%+ demonstrated plagiarism prevention understanding</p>
  </li>
  <li>
    <p><strong>Visual Dashboard Creation:</strong> Generate executive-level charts and graphs for stakeholder presentation</p>
    <ul>
      <li>Module completion funnel charts showing drop-off points</li>
      <li>Satisfaction rating histograms with statistical distribution analysis (showing 72.7% positive ratings at 4-5 levels)</li>
      <li>UI preference pie charts (based on actual data: Page layout 54.5%, Audio 36.4%, Video 9.1%)</li>
      <li>Quest concept understanding validation (demonstrating 86.4% “Yes” responses for educational approach effectiveness)</li>
      <li>Performance benchmark comparison charts (actual vs. target metrics)</li>
      <li>Cross-platform performance radar charts comparing mobile and laptop experiences</li>
      <li>Educational effectiveness pie charts showing learning objective achievement rates</li>
    </ul>
  </li>
</ul>

<p><strong>Gap Analysis Process</strong></p>

<ul>
  <li>
    <p><strong>Identify Shortfalls:</strong> Specific areas where performance didn’t meet established goals</p>
  </li>
  <li>
    <p><strong>Root Cause Investigation:</strong> Analyze why certain metrics underperformed (technical, design, or content issues)</p>
  </li>
  <li>
    <p><strong>Impact Assessment:</strong> Determine which gaps represent critical barriers vs. optimization opportunities</p>
  </li>
  <li>
    <p><strong>Resource Requirements:</strong> Estimate development effort needed to address each performance gap</p>
  </li>
</ul>

<p><strong>Success Pattern Recognition</strong></p>

<ul>
  <li><strong>High-Performing Elements:</strong> Identify features, modules, or designs that exceeded expectations
    <ul>
      <li><em>Example: Quest architecture understanding - “I learned the progression system and how it locks features and we can implement that into our own design”</em></li>
    </ul>
  </li>
  <li>
    <p><strong>Transferable Insights:</strong> Extract principles that can be applied to underperforming areas</p>
  </li>
  <li>
    <p><strong>User Preference Patterns:</strong> Understand what design elements resonate most with target audience</p>
  </li>
  <li><strong>Scalability Indicators:</strong> Assess which successes can be replicated across other quest topics
    <ul>
      <li><em>Evidence: Students absorbed sophisticated design principles - “break up the quest into different sections ranging from activation, demonstration, practice, application, assessment, and integration”</em></li>
    </ul>
  </li>
</ul>

<p>Discussing Subjective Findings</p>

<p><strong>Qualitative Theme Analysis</strong></p>

<ul>
  <li><strong>Student Voice Synthesis:</strong> Organize feedback into coherent themes while preserving authentic student language
    <ul>
      <li><em>Example theme: Navigation frustration - “We found it difficult to keep going back to the main page to proceed to the next stage”</em></li>
      <li><em>Example theme: Age-appropriate design - “Just appealing for kids our age in general”</em></li>
    </ul>
  </li>
  <li>
    <p><strong>Preference vs. Usability Distinction:</strong> Separate personal taste feedback from genuine usability issues</p>
  </li>
  <li>
    <p><strong>Age-Appropriate Design Insights:</strong> Extract specific guidance about teenage user interface expectations</p>
  </li>
  <li><strong>Engagement Factor Identification:</strong> Understand what elements truly motivate vs. merely satisfy users</li>
</ul>

<p><strong>Contextual Interpretation Process</strong></p>

<ul>
  <li>
    <p><strong>Educational Environment Consideration:</strong> Frame findings within classroom learning constraints and opportunities</p>
  </li>
  <li>
    <p><strong>Technical Limitation Acknowledgment:</strong> Distinguish between fixable issues and platform/resource constraints</p>
  </li>
  <li>
    <p><strong>Instructor Perspective Integration:</strong> Balance student feedback with pedagogical goals and content requirements</p>
  </li>
  <li>
    <p><strong>Cultural and Generational Factors:</strong> Consider how findings reflect broader generational technology expectations</p>
  </li>
</ul>

<p><strong>Recommendation Validation</strong></p>

<ul>
  <li>
    <p><strong>Feasibility Assessment:</strong> Evaluate which suggestions can be realistically implemented within resource constraints</p>
  </li>
  <li>
    <p><strong>Educational Value Analysis:</strong> Ensure proposed changes support rather than detract from learning objectives</p>
  </li>
  <li>
    <p><strong>Unintended Consequence Consideration:</strong> Anticipate how changes might affect other user groups or system components</p>
  </li>
  <li>
    <p><strong>Implementation Priority Justification:</strong> Provide clear rationale for why certain subjective findings warrant development resources</p>
  </li>
</ul>

<p>Making Recommendations for Addressing Problems</p>

<p><strong>Immediate Action Plan (Sprint 1 - Week 1)</strong></p>

<ul>
  <li><strong>Critical Fixes:</strong> Address P0/P1 issues that prevent core functionality
    <ul>
      <li>Video system repair and testing</li>
      <li>Authentication barrier resolution</li>
      <li>Performance optimization for AI tools</li>
    </ul>
  </li>
  <li><strong>Quick Wins:</strong> Implement high-impact, low-effort improvements
    <ul>
      <li>Add “Next” buttons for navigation flow</li>
      <li>Basic mobile responsiveness fixes</li>
    </ul>
  </li>
  <li><strong>Communication Strategy:</strong> Update all users on progress and expected resolution timelines</li>
</ul>

<p><strong>Short-Term Development Plan (Sprints 2-3 - Weeks 2-3)</strong></p>

<ul>
  <li><strong>User Experience Enhancements:</strong> Systematic improvement of identified pain points
    <ul>
      <li>Mobile experience overhaul</li>
      <li>Visual design modernization</li>
      <li>Progress tracking implementation</li>
    </ul>
  </li>
  <li><strong>Content Refinement:</strong> Address specific module feedback
    <ul>
      <li>C3 module redesign based on user confusion</li>
      <li>Instruction clarity improvements</li>
      <li>Enhanced learning connections between modules</li>
    </ul>
  </li>
</ul>

<p><strong>Long-Term Enhancement Strategy (Sprint 4+ - Week 4 and beyond)</strong></p>

<ul>
  <li><strong>Advanced Features:</strong> Implement sophisticated improvements that emerged from testing
    <ul>
      <li>Synthesis and reflection elements</li>
      <li>Enhanced accessibility features</li>
      <li>Social sharing and collaboration tools</li>
    </ul>
  </li>
  <li><strong>Scalability Preparation:</strong> Develop framework for applying lessons to other quest topics
    <ul>
      <li>Template creation for ML-Learning and AI Impacts modules</li>
      <li>Best practices documentation for future quest development</li>
      <li>Instructor training materials for TDD methodology</li>
    </ul>
  </li>
</ul>

<p>Prototype-to-Development Decision Framework</p>

<p>Based on the comprehensive testing data collected from 100+ students across multiple classes, the following factors indicate readiness to transition from prototype mockup to full development phase:</p>

<p><strong>Quantitative Success Indicators Supporting Development</strong></p>

<ul>
  <li><strong>Educational Effectiveness Validation:</strong> 86.4% of students demonstrated clear understanding of the quest concept and learning approach, with 0% complete rejection</li>
</ul>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image1f.png" alt="Image 1f" /></p>

<ul>
  <li><strong>User Satisfaction Threshold Achievement:</strong> 72.7% of participants rated their experience at satisfaction levels 4-5 out of 5, exceeding the 60% minimum threshold for development approval</li>
</ul>

<p><img src="/images/docx/D292_Plagiarism-WGU-SGM2-Task4-Test-Plan-Higher-Level-Education_image20.png" alt="Image 20" /></p>

<ul>
  <li>
    <p><strong>Task Completion Viability:</strong> Core module functionality demonstrated sufficient usability for students to complete learning objectives</p>
  </li>
  <li>
    <p><strong>Cross-Platform Feasibility:</strong> Both mobile and laptop testing confirmed technical infrastructure can support intended user base</p>
  </li>
  <li>
    <p><strong>Instructor Interface Validation:</strong> C5 and C6 modules successfully demonstrated automated grading and certification workflows, confirming scalability for classroom implementation</p>
  </li>
</ul>

<p><strong>Qualitative Evidence Supporting Development</strong></p>

<ul>
  <li>
    <p><strong>Design Learning Transfer Success:</strong> Students absorbed sophisticated instructional design principles, evidenced by quotes like <em>“break up the quest into different sections ranging from activation, demonstration, practice, application, assessment, and integration”</em></p>
  </li>
  <li>
    <p><strong>Age-Appropriate Engagement:</strong> Feedback confirmed the approach resonates with target demographic, with specific requests for <em>“appealing for kids our age in general”</em></p>
  </li>
  <li>
    <p><strong>Problem Identification Clarity:</strong> Issues identified are implementation challenges rather than fundamental concept flaws - students requested better navigation and visual appeal, not different educational approaches</p>
  </li>
  <li>
    <p><strong>Positive-to-Negative Feedback Ratio:</strong> Constructive improvement suggestions (navigation flow, visual design) vastly outnumber fundamental objections to the quest methodology</p>
  </li>
</ul>

<p><strong>Development Readiness Criteria Met</strong></p>

<ul>
  <li>
    <p><strong>Proof of Concept Validation:</strong> Core educational hypothesis confirmed through measurable learning outcomes</p>
  </li>
  <li>
    <p><strong>Technical Infrastructure Viability:</strong> AI tools, multimedia integration, and cross-platform functionality demonstrated sufficient stability for production development</p>
  </li>
  <li>
    <p><strong>User Acceptance Foundation:</strong> Strong user engagement and comprehension rates provide solid foundation for feature expansion</p>
  </li>
  <li>
    <p><strong>Instructor Workflow Validation:</strong> C5/C6 modules proved the instructor evaluation and student certification systems can streamline classroom implementation</p>
  </li>
  <li>
    <p><strong>Scalability Evidence:</strong> Student feedback includes specific design elements they want to <em>“implement into our own design,”</em> confirming the quest framework can be replicated across subjects</p>
  </li>
</ul>

<p><strong>Development Phase Priorities Based on Testing</strong></p>

<p>The transition to development should prioritize backend infrastructure supporting: - <strong>User Role Management:</strong> Student and instructor authentication with appropriate access controls - <strong>Data Persistence:</strong> Student progress tracking, instructor feedback systems, and certification workflows - <strong>Performance Optimization:</strong> Addressing identified AI tool response times and mobile experience improvements - <strong>Navigation Enhancement:</strong> Implementing the frequently requested “next button” functionality and progress indicators - <strong>Visual Design Refinement:</strong> Age-appropriate interface improvements that emerged as top priority from student feedback</p>

<p><strong>Decision Rationale</strong></p>

<p>The positive-to-negative feedback ratio, combined with 86.4% educational concept validation and 72.7% user satisfaction ratings, provides clear evidence that the Plagiarism Prevention Quest prototype has successfully validated its core educational approach and user experience framework. All identified issues represent implementation optimizations rather than fundamental design flaws, making this an ideal candidate for full development phase with backend infrastructure integration.</p>

<p><strong>Economic Justification for Development Transition</strong></p>

<p>Further prototype testing would yield diminishing returns at this stage, as the core usability and educational effectiveness have been validated. The cost-benefit analysis strongly favors moving to development:</p>

<ul>
  <li>
    <p><strong>Testing Limitations:</strong> Prototype testing cannot adequately validate role-based authentication, data persistence, or instructor workflow efficiency - all critical for production viability</p>
  </li>
  <li>
    <p><strong>C3 Module Optimization:</strong> Identified weaknesses in the Error Correction module (C3) require real-time data updates and dynamic content delivery that can only be properly tested in a production environment with live databases</p>
  </li>
  <li>
    <p><strong>Backend Infrastructure Dependencies:</strong> Key features like automated grading (C5) and certification systems (C6) require full database integration and user role management that cannot be meaningfully tested in prototype form</p>
  </li>
  <li>
    <p><strong>Real-World Data Requirements:</strong> Effective testing of citation tools and error correction functionality requires access to current academic databases and dynamic content that prototype testing cannot simulate</p>
  </li>
  <li>
    <p><strong>Development Efficiency:</strong> Resources are better allocated to building production infrastructure rather than conducting additional prototype testing that cannot address the identified technical limitations</p>
  </li>
</ul>

<p><strong>Production Testing Strategy</strong></p>

<p>The transition to development enables more effective testing approaches: - <strong>Incremental Feature Testing:</strong> Real system allows testing of individual components as they are built - <strong>Live Data Validation:</strong> C3 error correction can be refined using actual academic content and citation databases - <strong>User Role Testing:</strong> Authentic instructor and student role testing with real data persistence - <strong>Performance Optimization:</strong> True load testing and system performance evaluation under realistic conditions</p>

<p><strong>Success Measurement Framework</strong></p>

<ul>
  <li>
    <p><strong>Follow-Up Testing Protocol:</strong> Plan for validation testing of implemented improvements</p>
  </li>
  <li>
    <p><strong>Continuous Feedback Mechanism:</strong> Establish ongoing channels for user input and system monitoring</p>
  </li>
  <li>
    <p><strong>Iteration Planning:</strong> Create framework for regular improvement cycles based on usage data</p>
  </li>
  <li>
    <p><strong>Knowledge Transfer Documentation:</strong> Capture lessons learned for application to future educational technology projects</p>
  </li>
</ul>

<p><strong>Risk Mitigation Strategy</strong></p>

<ul>
  <li>
    <p><strong>Implementation Risks:</strong> Identify potential issues with proposed changes and develop contingency plans</p>
  </li>
  <li>
    <p><strong>Resource Allocation:</strong> Ensure development capacity matches ambitious improvement timeline</p>
  </li>
  <li>
    <p><strong>User Adoption:</strong> Plan for introducing changes in ways that don’t disrupt ongoing educational use</p>
  </li>
  <li>
    <p><strong>Quality Assurance:</strong> Establish testing protocols to prevent new issues from emerging during improvement process</p>
  </li>
</ul>

<p>This comprehensive post-test process ensures that valuable user feedback translates into concrete improvements while maintaining focus on educational effectiveness and user experience excellence.</p>

<p><strong>L. Acknowledgment of Sources</strong></p>

<p>No sources used outside of WGU-provided materials. Sources used in visuals are self-contained and managed outside of this document.</p>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d292" /><summary type="html"><![CDATA[Plagiarism lesson. Students will develop a comprehensive test plan to evaluate the effectiveness and usability of their e-learning solution, ensuring it meets learning objectives and user needs.]]></summary></entry><entry><title type="html">Questofcode WGU Assessments E Learning</title><link href="https://sfi.opencodingsociety.com/docx/QuestOfCode-WGU-Assessments-E-Learning/" rel="alternate" type="text/html" title="Questofcode WGU Assessments E Learning" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/docx/D295_QuestOfCode-WGU-Assessments-E-Learning_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/docx/QuestOfCode-WGU-Assessments-E-Learning/"><![CDATA[<!-- Converted from: QuestOfCode-WGU-Assessments-E-Learning.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:03 -->
<!-- Images extracted: 0 -->

<h2 id="d295-task-4-e-learning---assessments-and-feedback">D295 Task 4: E-Learning - Assessments and Feedback</h2>

<h3 id="i-introduction">I. Introduction</h3>

<p><strong>This assessment and feedback plan supports the collaborative quest-based e-learning experience outlined in Task 3, where students design and build a web application using JavaScript, APIs, AI (Gemini), and databases. The goal is to integrate authentic formative and summative assessment checkpoints that reinforce teamwork, accountability, and mastery of computational and collaborative skills.</strong></p>

<p><strong>The assessment framework combines structured team-based checkpoints with individualized performance checks. Team Checks focuses on Scrum-based collaboration, design quality, and prototype functionality. Individual Checks assess personal contributions through GitHub analytics, issue tracking, and live review feedback. This dual-layer model ensures both collaborative competence and individual accountability.</strong></p>

<h3 id="ii-e-learning-experience-plan">II. E-Learning Experience Plan</h3>

<h4 id="a1-components">A1. Components</h4>

<ul>
  <li>
    <p><strong>Topic:</strong> Collaborative Quest Development with JavaScript APIs, AI, and Databases</p>
  </li>
  <li>
    <p><strong>Description:</strong> In this e-learning experience, we, the class, worked together to design and build a quest-based web application. We use JavaScript to connect to APIs (microblog), integrate AI (Gemini), and learn to store data with a database. Our project is collaborative: we share code, debug together, and help each other design a great user experience.</p>
  </li>
  <li>
    <p><strong>Grade:</strong> High School (Grades 10–12)</p>
  </li>
  <li><strong>Learning Goal:</strong> Work as a team to create a functional, ethical, and engaging quest app using real-world coding and collaboration skills.
    <ul>
      <li>Team 1: West Coast Quest
        <ul>
          <li>Food, Travel, Sports guided by AI</li>
        </ul>
      </li>
      <li>Team 2: Digital Famine Quest
        <ul>
          <li>Inter-planet restoration of Microblogging, Digital Literacy, AI, etc</li>
        </ul>
      </li>
    </ul>
  </li>
  <li><strong>Learning Objectives:</strong>
    <ol>
      <li>Use JavaScript to fetch data from APIs and handle responses with promises in User presented API.</li>
      <li>Integrate AI (Gemini) to enhance the quest experience.</li>
      <li>Implement database CRUD operations for quest progress and rewards.</li>
      <li>Design user experiences that are fun, accessible, and meaningful.</li>
      <li>Apply digital citizenship principles in all project work.</li>
    </ol>
  </li>
  <li><strong>Academic Standards:</strong>
    <ul>
      <li>ISTE Standard 1.4: Innovator Designer</li>
      <li>ISTE Standard 1.5: Computational Thinker</li>
      <li>ISTE Standard 1.7: Global Collaborator</li>
    </ul>
  </li>
</ul>

<h3 id="iii-formative-assessments">III. Formative Assessments</h3>

<p><strong>B. Learning Objective Selected: Implement CRUD database operations for tracking user progress and rewards.</strong></p>

<ul>
  <li>
    <p>Checkpoint 1 - Scrum Master Live review. Reviewing Design, which is composed of Ideation and Storyboard.</p>
  </li>
  <li>
    <p>Checkpoint 2 - Assistant Scrum Master Live Review. First integrations, which focus on Navigation and Classroom Integrations</p>
  </li>
</ul>

<h4 id="b1-formative-assessment">B1. Formative Assessment</h4>

<p><strong>Students complete Team Checkpoint 2: Assistant Scrum Master Live Review, where they demonstrate their first working integration of navigation flow, database connections, and classroom features. Each team presents its implementation during a live code review session.</strong></p>

<p><strong>Assessment Activity: The Assistant Scrum Master leads the live review while teammates demonstrate their part of the integration. The instructor observes teamwork, evaluates CRUD operations, and the recorder gathers immediate feedback through GitHub issues.</strong></p>

<h4 id="b2-technology-tool">B2. Technology Tool</h4>

<p><strong>Technology: GitHub (Pull Requests, Issues, and Project Kanban)</strong></p>

<p><strong>Justification: GitHub’s collaborative features support formative assessment by allowing real-time code inspection, commenting, and progress tracking. Using Issues and Pull Requests, the instructor can pinpoint logic errors, comment on database design, and provide targeted feedback linked directly to the relevant code.</strong></p>

<h4 id="b3-feedback-process">B3. Feedback Process</h4>

<p><strong>Feedback Strategy: Feedback is given both live during the review (verbal and on-screen walkthroughs) and asynchronous through GitHub issue threads. Each student receives feedback within 24 hours, referencing commit IDs and PR comments for precision. Teams are encouraged to reply to feedback comments or mark issues as ‘resolved’ once addressed.</strong></p>

<p><strong>Technology for Feedback: GitHub + VSCode Live Share</strong></p>

<p><strong>Explanation: Live Share enables real-time code collaboration while GitHub anchors written feedback in the repository. Students can instantly apply instructor or peer suggestions and verify improvements collaboratively. This combination ensures timely, traceable, and authentic feedback.</strong></p>

<h3 id="iv-summative-assessment">IV. Summative Assessment</h3>

<p><strong>The</strong> <em>Night at the Museum</em> Prototype Presentation serves as the summative <strong>team</strong> assessment. Teams present their quest application prototype in an <strong>open review walk-through</strong>, where teachers, peers, and local tech mentors visit each team’s station, explore the app, and discuss its features. The focus is on usability, design quality, data functionality, and teamwork.</p>

<p>For the <strong>Individual Final</strong>, each student participates in a live review using Issues from the Kanban board and GitHub Analytics data—including commits, pull requests, and issue activity.</p>

<p>Both events require a <strong>functional</strong> prototype demonstrating CRUD, API, and AI features, professional presentation and GitHub documentation, and clear evidence of iteration based on formative assessments and prior feedback.</p>

<h4 id="c1-accommodations-for-demonstrating-competency">C1. Accommodations for Demonstrating Competency</h4>

<ol>
  <li>
    <p>Video Submission Alternative: Students who prefer not to present live may submit a recorded demo of their app with voiceover explaining their code and features.</p>
  </li>
  <li>
    <p>Written Technical Reflection: Students who struggle with verbal presentation may submit a reflection paper summarizing their contributions, challenges, and how they applied instructor feedback.</p>
  </li>
</ol>

<h3 id="v-reflection-opportunities">V. Reflection Opportunities</h3>

<p>D1. Mid-Project Reflection (Formative): During Checkpoints 1 &amp; 2, the Scrum Master or Assistant Scrum Master conducts a Live Review, and students write a short reflection in a GitHub Issue and design choices, identifying what worked well and what needs revision.</p>

<p>D2. End-of-Project Reflection (Summative): After Night at the Museum, each student completes an individual reflection post on their GitHub Pages Blog. They summarize their learning growth, teamwork contributions, and feedback-guided improvement.</p>

<h3 id="vi-references">VI. References</h3>

<ul>
  <li>
    <p>International Society for Technology in Education (ISTE). (2021). ISTE Standards for Students. <a href="https://www.iste.org/standards/iste-standards-for-students">https://www.iste.org/standards/iste-standards-for-students</a></p>
  </li>
  <li>
    <p>GitHub Docs. (2025). <a href="https://docs.github.com/">https://docs.github.com/</a></p>
  </li>
  <li>
    <p>Microsoft. (2025). VSCode Live Share. <a href="https://visualstudio.microsoft.com/services/live-share/">https://visualstudio.microsoft.com/services/live-share/</a></p>
  </li>
  <li>
    <p>Google AI. (2025). Gemini API Documentation. <a href="https://ai.google.dev/docs">https://ai.google.dev/docs</a></p>
  </li>
</ul>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d295" /><summary type="html"><![CDATA[Converted from QuestOfCode-WGU-Assessments-E-Learning.docx]]></summary></entry><entry><title type="html">Questofcode WGU Collaborative E Learning</title><link href="https://sfi.opencodingsociety.com/docx/QuestOfCode-WGU-Collaborative-E-Learning/" rel="alternate" type="text/html" title="Questofcode WGU Collaborative E Learning" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/docx/D295_QuestOfCode-WGU-Collaborative-E-Learning_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/docx/QuestOfCode-WGU-Collaborative-E-Learning/"><![CDATA[<!-- Converted from: QuestOfCode-WGU-Collaborative-E-Learning.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:03 -->
<!-- Images extracted: 0 -->

<p>D295 Task 3: Collaborative E-Learning Experience Outline</p>

<p>2025-10-28</p>

<h2 id="d295-task-3-designing-collaborative-e-learning-experiences">D295 Task 3: Designing Collaborative E-Learning Experiences</h2>

<h3 id="i-introduction">I. Introduction</h3>

<p>This collaborative e-learning experience is designed for students to work together on a quest-based web application. The focus is on using JavaScript to connect to APIs, integrate AI (Gemini), and manage microblog (feedback) data in a database. Students share code, debug together, and help each other design a great user experience.</p>

<h3 id="ii-e-learning-experience-plan">II. E-Learning Experience Plan</h3>

<h4 id="a1-components">A1. Components</h4>

<ul>
  <li>
    <p><strong>Topic:</strong> Collaborative Quest Development with JavaScript APIs, AI, and Databases</p>
  </li>
  <li>
    <p><strong>Description:</strong> In this e-learning experience, we, the class, work together to design and build a quest-based web application. We use JavaScript to connect to APIs (microblog), integrate AI (Gemini), and learn to store data with a database. Our project is collaborative: we share code, debug together, and help each other design a great user experience.</p>
  </li>
  <li>
    <p><strong>Grade:</strong> High School (Grades 10–12)</p>
  </li>
  <li><strong>Learning Goal:</strong> Work as a team to create a functional, ethical, and engaging quest app using real-world coding and collaboration skills.
    <ul>
      <li>Team 1: West Coast Quest
        <ul>
          <li>Food, Travel, Sports guided by AI</li>
        </ul>
      </li>
      <li>Team 2: Digital Famine Quest
        <ul>
          <li>Inter-planet restoration of Microblogging, Digital Literacy, AI, etc</li>
        </ul>
      </li>
    </ul>
  </li>
  <li><strong>Learning Objectives:</strong>
    <ol>
      <li>Use JavaScript to fetch data from APIs and handle responses with promises in User presented API.</li>
      <li>Integrate AI (Gemini) to enhance the quest experience.</li>
      <li>Implement database CRUD operations for quest progress and rewards.</li>
      <li>Design user experiences that are fun, accessible, and meaningful.</li>
      <li>Apply digital citizenship principles in all project work.</li>
    </ol>
  </li>
  <li><strong>Academic Standards:</strong>
    <ul>
      <li>ISTE Standard 1.4: Innovator Designer</li>
      <li>ISTE Standard 1.5: Computational Thinker</li>
      <li>ISTE Standard 1.7: Global Collaborator</li>
    </ul>
  </li>
</ul>

<h4 id="a2-digital-tools-for-collaboration-two-provided">A2. Digital Tools for Collaboration (Two provided)</h4>

<ul>
  <li>
    <p><strong>GitHub:</strong> For sharing code, tracking changes, and reviewing each other’s work.</p>
  </li>
  <li>
    <p><strong>VSCode Live Share:</strong> For real-time pair programming and group debugging.</p>
  </li>
</ul>

<h5 id="how-tools-support-collaboration">How tools support collaboration</h5>

<ul>
  <li>
    <p>GitHub lets us work on the same codebase, suggest improvements, and merge our ideas safely.</p>
  </li>
  <li>
    <p>VSCode Live Share allows us to code together, ask questions, and solve problems as a team—even if we’re not in the same room.</p>
  </li>
</ul>

<h4 id="a3-collaborative-activities-two-provided">A3. Collaborative Activities (Two provided)</h4>

<ul>
  <li>
    <p><strong>Activity 1:</strong> Pair up to implement a new API feature (e.g., fetch quest data or integrate Gemini AI). One student builds the activity, writes the code, the other reviews, tests it, and coordinates “pull request”.<br />
<em>Alignment:</em> JavaScript API Consumption, AI Integration, Computational Thinker.</p>
  </li>
  <li>
    <p><strong>Activity 2:</strong> In small groups, design and test a new quest challenge. Each group presents their UX design and explains how they used UX design principles and digital citizenship principles.<br />
<em>Alignment:</em> Database API Usage, Digital Citizenship, Quest UX Design, Global Collaborator.</p>
  </li>
</ul>

<h4 id="a4-facilitation-strategies">A4. Facilitation Strategies</h4>

<ul>
  <li>
    <p><strong>Daily stand-ups:</strong> Use daily stand-up meetings (in-person or online) to set goals, share progress, and ask for help.</p>
  </li>
  <li>
    <p><strong>Debugging/support channel:</strong> Set up a shared “debugging channel” (Slack/Discord) where anyone can post questions or bugs for group support.</p>
  </li>
</ul>

<h5 id="how-strategies-support-collaboration">How strategies support collaboration</h5>

<ul>
  <li>
    <p>Stand-ups keep everyone on track and make sure no one is stuck alone.</p>
  </li>
  <li>
    <p>The debugging channel encourages us to help each other and learn from different solutions.</p>
  </li>
</ul>

<h4 id="a5-accessibility-considerations">A5. Accessibility Considerations</h4>

<ul>
  <li>
    <p>Make sure all code and documentation use clear language and comments.</p>
  </li>
  <li>
    <p>Use color-blind–friendly palettes and readable fonts in the quest for UI.</p>
  </li>
  <li>
    <p>Provide alternative text for images and ensure keyboard navigation works.</p>
  </li>
  <li>
    <p>Use different modalities in lesson (audio, video, speech to text)</p>
  </li>
</ul>

<h4 id="a6-differentiation-strategies-two-provided">A6. Differentiation Strategies (Two Provided)</h4>

<ul>
  <li>
    <p>Allow students to choose roles (e.g., Scrum Master, Scrummer, Designer, Tester, Presenter) based on their strengths and interests.</p>
  </li>
  <li>
    <p>Offer extra challenges (like advanced API design and Database integration) for students who want to go further and provide templates or code snippets for those who need more support.</p>
  </li>
</ul>

<h3 id="iii-iste-standards-alignment">III. ISTE Standards Alignment</h3>

<h4 id="b1a-list-of-relevant-iste-standards">B1a. List of relevant ISTE standards</h4>

<ul>
  <li>
    <p>ISTE Standard 1.4: Innovator Designer</p>
  </li>
  <li>
    <p>ISTE Standard 1.5: Computational Thinker</p>
  </li>
  <li>
    <p>ISTE Standard 1.7: Global Collaborator</p>
  </li>
</ul>

<h4 id="b1b-how-alignment-improves-student-learning">B1b. How alignment improves student learning</h4>

<p>By aligning with these ISTE standards, we learn to design, break down complex coding problems, work together globally, and use technology responsibly. This prepares us for real-world teamwork and problem-solving in tech careers.</p>

<h3 id="iv-references">IV. References</h3>

<ul>
  <li>
    <p>International Society for Technology in Education (ISTE). (2021). ISTE Standards for Students. https://www.iste.org/standards/iste-standards-for-students</p>
  </li>
  <li>
    <p>GitHub Docs. (2025). https://docs.github.com/</p>
  </li>
  <li>
    <p>Microsoft. (2025). VSCode Live Share. https://visualstudio.microsoft.com/services/live-share/</p>
  </li>
  <li>
    <p>Google AI. (2025). Gemini API Documentation. https://ai.google.dev/docs</p>
  </li>
</ul>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d295" /><summary type="html"><![CDATA[Converted from QuestOfCode-WGU-Collaborative-E-Learning.docx]]></summary></entry><entry><title type="html">D295 Task 2: Quest-Based Learning</title><link href="https://sfi.opencodingsociety.com/wgu/d295/task2-demonstration/" rel="alternate" type="text/html" title="D295 Task 2: Quest-Based Learning" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d295/D295_QuestOfCode-WGU-Demonstrating-Essential-Concepts_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d295/task2-demonstration/"><![CDATA[<!-- Converted from: QuestOfCode-WGU-Demonstrating-Essential-Concepts.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:04 -->
<!-- Images extracted: 0 -->

<p>D295 Task 2: Quest-Based Learning - Demonstrating Essential Concepts for K–12 E-Learning</p>

<p>John Mortensen</p>

<p>2025-10-23</p>

<h2 id="d295-task-2-quest-based-learning---demonstrating-essential-concepts-for-k12-e-learning">D295 Task 2: Quest-Based Learning - Demonstrating Essential Concepts for K–12 E-Learning</h2>

<h3 id="introduction">Introduction</h3>

<p><strong>In this task, I design an e-learning activity that introduces K–12 students to key concepts, skills, and tasks involved in JavaScript API integration. The activity serves as a demonstration of what students will learn and accomplish through a quest-based learning approach. It highlights how digital tools and interactive strategies can be used to illustrate clear learning outcomes and includes a description of the activity design, technologies employed, and methods of assessment.</strong></p>

<h3 id="a-unit-of-study-identification">A. Unit of Study Identification</h3>

<h4 id="topic-of-the-lesson">Topic of the Lesson</h4>

<p><strong>JavaScript API Integration for Quest-Based Digital Citizenship Applications</strong></p>

<h4 id="essential-concepts-skills-and-tasks">Essential Concepts, Skills, and Tasks</h4>

<p>Students will demonstrate mastery of the following essential concepts through their <strong>Quest of Code</strong> projects:</p>

<ol>
  <li>
    <p><strong>JavaScript API Consumption</strong> - Using promise-based fetch() with .then() chains and functional programming patterns</p>
  </li>
  <li>
    <p><strong>AI Integration via APIs</strong> - Designing purposeful Gemini AI prompts and formatting responses for quest UX</p>
  </li>
  <li>
    <p><strong>Database API Usage</strong> - Implementing CRUD operations with promise chaining for quest progression and rewards</p>
  </li>
  <li>
    <p><strong>Digital Citizenship Implementation</strong> - Applying ethical technology practices in real-world projects</p>
  </li>
  <li>
    <p><strong>Quest UX Design</strong> - Formatting API inputs/outputs into engaging, narrative-driven user experiences</p>
  </li>
</ol>

<h3 id="b-demonstration-strategy-and-implementation">B. Demonstration Strategy and Implementation</h3>

<h4 id="b1-instructional-strategy-quest-based-learning-with-api-integration">B1. Instructional Strategy: <strong>Quest-Based Learning with API Integration</strong></h4>

<p><strong>Primary Strategy</strong>: <strong>Instructor Introduction and Demonstration</strong></p>

<ul>
  <li>
    <p><strong>Show Examples</strong> - Instructor demonstrates live API calls using browser console and development tools</p>
  </li>
  <li>
    <p><strong>Format Modeling</strong> - Teacher shows how to transform raw API responses into quest-friendly formats</p>
  </li>
  <li>
    <p><strong>Error Handling Demonstration</strong> - Live troubleshooting of common API integration issues and solutions</p>
  </li>
  <li>
    <p><strong>Reading Materials</strong> - Comprehensive API documentation and integration guides provided for student reference</p>
  </li>
  <li>
    <p><strong>Step-by-Step Walkthroughs</strong> - Instructor guides students through initial API discovery and integration process</p>
  </li>
</ul>

<p><strong>Secondary Strategy</strong>: <strong>Learn-by-Doing with Collaborative Problem-Solving</strong></p>

<ul>
  <li>
    <p>Students work on their actual <strong>Quest of Code</strong> capstone projects after demonstration</p>
  </li>
  <li>
    <p>API integration serves their specific quest narrative and functionality needs</p>
  </li>
  <li>
    <p>Team-based quest development with shared API resources and peer debugging</p>
  </li>
  <li>
    <p>Real-time problem-solving within the context of preparing for <strong>Night at the Museum</strong></p>
  </li>
  <li>
    <p>Community-focused development preparing for public showcase</p>
  </li>
</ul>

<h4 id="b1a-strategy-implementation">B1a. Strategy Implementation</h4>

<p>The lesson follows a <strong>demonstration-first, quest-driven approach</strong> where students:</p>

<ol>
  <li>
    <p><strong>Observe</strong> - Watch instructor demonstrate live API integration techniques</p>
  </li>
  <li>
    <p><strong>Discover</strong> - Explore existing Flask APIs through guided interactive testing</p>
  </li>
  <li>
    <p><strong>Design</strong> - Plan how APIs will enhance their quest user experience with instructor support</p>
  </li>
  <li>
    <p><strong>Implement</strong> - Integrate Gemini AI and database APIs into their projects using demonstrated patterns</p>
  </li>
  <li>
    <p><strong>Test</strong> - Validate API integration with guest login functionality</p>
  </li>
  <li>
    <p><strong>Showcase</strong> - Present working prototypes to community at Night at the Museum</p>
  </li>
</ol>

<p><strong>Demonstration Integration Process</strong>:</p>

<ul>
  <li>
    <p>Instructor models how AI and data APIs serve quest narrative development</p>
  </li>
  <li>
    <p>Students follow demonstrated patterns with real-time instructor feedback</p>
  </li>
  <li>
    <p>Continuous scaffolding with demonstrated examples and troubleshooting techniques</p>
  </li>
  <li>
    <p>Progressive complexity building from demonstrated foundations toward independent implementation</p>
  </li>
</ul>

<h4 id="b2-digital-tools-for-quest-development-environment">B2. Digital Tools for Quest Development Environment</h4>

<p><strong>Primary Development Tools</strong>:</p>

<ul>
  <li>
    <p><strong>VSCode Live Share</strong> - Collaborative quest team development</p>
  </li>
  <li>
    <p><strong>GitHub Pages</strong> - Hosting and deployment for quest prototypes</p>
  </li>
  <li>
    <p><strong>Browser Developer Tools</strong> - API testing and debugging in real-time</p>
  </li>
</ul>

<p><strong>API Integration Tools</strong>:</p>

<ul>
  <li>
    <p><strong>Postman Client</strong> - Testing Flask API endpoints before JavaScript integration</p>
  </li>
  <li>
    <p><strong>Browser Console</strong> - Real-time JavaScript debugging and API response inspection</p>
  </li>
  <li>
    <p><strong>Network Tab</strong> - Monitoring API calls and troubleshooting connectivity issues</p>
  </li>
</ul>

<p><strong>Quest Development Platform</strong>:</p>

<ul>
  <li>
    <p><strong>GitHub</strong> - Quest project repositories and team collaboration</p>
  </li>
  <li>
    <p><strong>Jekyll/GitHub Pages</strong> - Quest website hosting with integrated backends</p>
  </li>
  <li>
    <p><strong>Slack</strong> - Real-time team communication during development sprints</p>
  </li>
</ul>

<p><strong>Community Showcase Tools</strong>:</p>

<ul>
  <li>
    <p><strong>Guest Login Systems</strong> - Simple authentication for Night at the Museum visitors</p>
  </li>
  <li>
    <p><strong>Data Visualization</strong> - Charts and graphs to display quest interaction data</p>
  </li>
  <li>
    <p><strong>Mobile-Responsive Design</strong> - Ensuring quest accessibility across devices</p>
  </li>
</ul>

<h4 id="b3-practice-and-feedback-mechanisms">B3. Practice and Feedback Mechanisms</h4>

<p><strong>Instructor-Led Demonstrations</strong>:</p>

<ul>
  <li>
    <p><strong>Live API Integration Examples</strong> - Teacher demonstrates real-time API calls and response handling</p>
  </li>
  <li>
    <p><strong>Error Simulation and Resolution</strong> - Instructor shows common mistakes and debugging techniques</p>
  </li>
  <li>
    <p><strong>Format Transformation Modeling</strong> - Step-by-step conversion of API data into quest elements</p>
  </li>
</ul>

<p><strong>Guided Practice Activities</strong>:</p>

<ul>
  <li>
    <p><strong>API Discovery Exercises</strong> - Students explore available endpoints with instructor guidance</p>
  </li>
  <li>
    <p><strong>Scaffolded Implementation</strong> - Graduated complexity following demonstrated patterns</p>
  </li>
  <li>
    <p><strong>Peer Collaboration</strong> - Students apply demonstrated techniques in team settings</p>
  </li>
</ul>

<p><strong>Feedback Delivery</strong>:</p>

<ul>
  <li>
    <p><strong>Real-time Instructor Support</strong> - Immediate guidance during API integration attempts</p>
  </li>
  <li>
    <p><strong>Demonstrated Best Practices</strong> - Teacher shows effective coding patterns and debugging strategies</p>
  </li>
  <li>
    <p><strong>Progressive Assessment</strong> - Building from demonstrated examples to independent implementation</p>
  </li>
</ul>

<h4 id="b4-assessment-methods">B4. Assessment Methods</h4>

<p><strong>Demonstration-Based Assessment</strong>:</p>

<ul>
  <li>
    <p><strong>Functional Quest Prototypes</strong> - Working applications with API integration following demonstrated patterns</p>
  </li>
  <li>
    <p><strong>Digital Citizenship Portfolio</strong> - Documentation of ethical technology decisions using provided frameworks</p>
  </li>
  <li>
    <p><strong>Night at the Museum Presentation</strong> - Live demonstration to community audience</p>
  </li>
</ul>

<p><strong>Technical Implementation Assessment</strong>:</p>

<ul>
  <li>
    <p><strong>Promise-Based API Integration</strong> - Functional fetch() chains with .then() following demonstrated examples</p>
  </li>
  <li>
    <p><strong>Purposeful API Design</strong> - Strategic use of APIs for quest lessons, rewards, and progression mechanics</p>
  </li>
  <li>
    <p><strong>UX-Focused Data Formatting</strong> - Transforming API inputs/outputs using demonstrated techniques</p>
  </li>
  <li>
    <p><strong>Error Handling and Validation</strong> - Robust promise chains with proper .catch() based on instructor examples</p>
  </li>
</ul>

<p><strong>Assessment Components</strong>:</p>

<ul>
  <li>
    <p><strong>Quest Functionality</strong> (40%) - APIs enhance the quest user experience using demonstrated patterns</p>
  </li>
  <li>
    <p><strong>Digital Citizenship</strong> (25%) - Ethical implementation and user data protection following provided guidelines</p>
  </li>
  <li>
    <p><strong>Community Presentation</strong> (20%) - Effective communication to authentic audience</p>
  </li>
  <li>
    <p><strong>Technical Quality</strong> (15%) - Clean, maintainable JavaScript code following demonstrated best practices</p>
  </li>
</ul>

<p><strong>Authentic Assessment Context</strong>:</p>

<ul>
  <li>
    <p><strong>Real Community Audience</strong> - Night at the Museum provides genuine user feedback</p>
  </li>
  <li>
    <p><strong>Industry Professional Reviews</strong> - CTE pathway mentors evaluate technical implementation</p>
  </li>
  <li>
    <p><strong>Peer Quest Testing</strong> - Students validate each other’s work before public showcase</p>
  </li>
</ul>

<h3 id="c-accessibility-considerations">C. Accessibility Considerations</h3>

<h4 id="universal-design-for-learning-udl-implementation">Universal Design for Learning (UDL) Implementation</h4>

<p><strong>Visual Accessibility</strong>:</p>

<ul>
  <li>
    <p><strong>High contrast code themes</strong> for students with visual impairments</p>
  </li>
  <li>
    <p><strong>Scalable text</strong> in all development environments</p>
  </li>
  <li>
    <p><strong>Screen reader compatibility</strong> with descriptive code comments</p>
  </li>
  <li>
    <p><strong>Alternative text</strong> for all diagrams and visual materials</p>
  </li>
</ul>

<p><strong>Motor Accessibility</strong>:</p>

<ul>
  <li>
    <p><strong>Voice-to-code</strong> integration for students with limited mobility</p>
  </li>
  <li>
    <p><strong>Customizable keyboard shortcuts</strong> in development environments</p>
  </li>
  <li>
    <p><strong>Alternative input methods</strong> (trackpad, stylus, eye-tracking)</p>
  </li>
</ul>

<p><strong>Cognitive Accessibility</strong>:</p>

<ul>
  <li>
    <p><strong>Chunked learning modules</strong> to prevent cognitive overload</p>
  </li>
  <li>
    <p><strong>Multiple representation formats</strong> (visual, auditory, kinesthetic)</p>
  </li>
  <li>
    <p><strong>Scaffolded complexity</strong> with clear progression indicators</p>
  </li>
  <li>
    <p><strong>Memory aids</strong> through consistent naming conventions and patterns</p>
  </li>
</ul>

<p><strong>Language and Communication</strong>:</p>

<ul>
  <li>
    <p><strong>Multilingual code comments</strong> for ESL students</p>
  </li>
  <li>
    <p><strong>Clear, jargon-free explanations</strong> with technical term glossary</p>
  </li>
  <li>
    <p><strong>Visual code flow diagrams</strong> to supplement verbal explanations</p>
  </li>
</ul>

<h3 id="d-differentiation-strategies">D. Differentiation Strategies</h3>

<h4 id="strategy-1-quest-complexity-tiers">Strategy 1: <strong>Quest Complexity Tiers</strong></h4>

<p><strong>Novice Quest Developers</strong>:</p>

<ul>
  <li>
    <p><strong>Template-based integration</strong> with pre-built API call examples from demonstrations</p>
  </li>
  <li>
    <p><strong>Simple AI interactions</strong> using basic prompt-response patterns shown in class</p>
  </li>
  <li>
    <p><strong>Basic data display</strong> from database APIs with provided styling templates</p>
  </li>
  <li>
    <p><strong>Guided quest narrative</strong> with structured story templates and demonstrated examples</p>
  </li>
</ul>

<p><strong>Intermediate Quest Developers</strong>:</p>

<ul>
  <li>
    <p><strong>Custom API integrations</strong> designed around their unique quest themes using demonstrated patterns</p>
  </li>
  <li>
    <p><strong>Dynamic AI conversations</strong> with context-aware prompt engineering following instructor examples</p>
  </li>
  <li>
    <p><strong>Interactive data visualizations</strong> using charts and user-generated content with provided libraries</p>
  </li>
  <li>
    <p><strong>Original quest mechanics</strong> with personalized user engagement features built on demonstrated foundations</p>
  </li>
</ul>

<p><strong>Advanced Quest Developers</strong>:</p>

<ul>
  <li>
    <p><strong>Complex API orchestration</strong> combining multiple services for rich experiences beyond basic demonstrations</p>
  </li>
  <li>
    <p><strong>AI-powered quest generation</strong> where Gemini creates dynamic content using advanced prompt techniques</p>
  </li>
  <li>
    <p><strong>Advanced data analytics</strong> tracking user behavior and quest completion rates with custom implementations</p>
  </li>
  <li>
    <p><strong>Innovative accessibility features</strong> and multi-modal interaction design extending demonstrated concepts</p>
  </li>
</ul>

<h4 id="strategy-2-progressive-quest-development-phases">Strategy 2: <strong>Progressive Quest Development Phases</strong></h4>

<p><strong>Phase 1: Design Thinking (Days 1-2)</strong>:</p>

<ul>
  <li>
    <p><strong>Empathy mapping</strong> for quest target audience and community showcase visitors</p>
  </li>
  <li>
    <p><strong>Problem definition</strong> identifying how APIs can enhance quest narrative and engagement</p>
  </li>
  <li>
    <p><strong>Ideation sessions</strong> brainstorming quest mechanics that leverage AI and data APIs</p>
  </li>
  <li>
    <p><strong>Storyboard creation</strong> connecting user journey to technical implementation needs</p>
  </li>
</ul>

<p><strong>Phase 2: Skeletal Organization (Days 3-4)</strong>:</p>

<ul>
  <li>
    <p><strong>Quest architecture planning</strong> with wireframes and user flow diagrams</p>
  </li>
  <li>
    <p><strong>API integration points</strong> identified within quest progression and reward systems</p>
  </li>
  <li>
    <p><strong>Technical feasibility validation</strong> ensuring chosen APIs support quest vision</p>
  </li>
  <li>
    <p><strong>Team role distribution</strong> for collaborative development and API specialization</p>
  </li>
</ul>

<p><strong>Phase 3: API Learning and Integration (Days 5-9)</strong>:</p>

<ul>
  <li>
    <p><strong>Promise-based API consumption</strong> with functional programming patterns following demonstrations</p>
  </li>
  <li>
    <p><strong>Purposeful AI prompt design</strong> for quest characters, hints, and dynamic content using shown examples</p>
  </li>
  <li>
    <p><strong>Database API integration</strong> for user progress, scoring, and personalization with instructor support</p>
  </li>
  <li>
    <p><strong>UX-focused data formatting</strong> transforming API responses into quest experiences using demonstrated techniques</p>
  </li>
</ul>

<p><strong>Phase 4: Prototype Refinement (Days 10-15)</strong>:</p>

<ul>
  <li>
    <p><strong>Cross-team testing</strong> with focus on API responsiveness and user experience</p>
  </li>
  <li>
    <p><strong>Community showcase preparation</strong> ensuring APIs enhance rather than distract from quest narrative</p>
  </li>
  <li>
    <p><strong>Performance optimization</strong> of promise chains and API call efficiency using demonstrated best practices</p>
  </li>
  <li>
    <p><strong>Final polish</strong> for Night at the Museum demonstration readiness</p>
  </li>
</ul>

<h3 id="e-digital-citizenship-best-practices">E. Digital Citizenship Best Practices</h3>

<h4 id="practice-1-ethical-ai-integration-and-transparency">Practice 1: <strong>Ethical AI Integration and Transparency</strong></h4>

<p><strong>Implementation in Quest Development</strong>:</p>

<ul>
  <li>
    <p>Students must <strong>document AI assistance</strong> in their quest development process</p>
  </li>
  <li>
    <p><strong>Attribution requirements</strong> for AI-generated content, code, or quest narrative elements</p>
  </li>
  <li>
    <p><strong>Critical evaluation</strong> of AI responses for bias, accuracy, and appropriateness</p>
  </li>
  <li>
    <p><strong>Responsible prompt design</strong> that respects user privacy and cultural sensitivity</p>
  </li>
</ul>

<p><strong>Quest-Specific Applications</strong>:</p>

<ul>
  <li>
    <p>Quest characters powered by AI must include <strong>transparency disclaimers</strong></p>
  </li>
  <li>
    <p>Students evaluate <strong>AI-generated quest content</strong> for educational value and bias</p>
  </li>
  <li>
    <p><strong>User consent mechanisms</strong> when quest interactions involve AI processing</p>
  </li>
  <li>
    <p>Discussion of <strong>AI limitations</strong> in quest design and user experience</p>
  </li>
</ul>

<h4 id="practice-2-data-privacy-and-user-protection">Practice 2: <strong>Data Privacy and User Protection</strong></h4>

<p><strong>Implementation in Quest Projects</strong>:</p>

<ul>
  <li>
    <p><strong>Guest login systems</strong> designed with minimal data collection</p>
  </li>
  <li>
    <p><strong>Clear privacy policies</strong> explaining how quest interaction data is used</p>
  </li>
  <li>
    <p><strong>User consent</strong> for data storage, especially for Night at the Museum visitors</p>
  </li>
  <li>
    <p><strong>Data minimization</strong> principles - collect only data necessary for quest functionality</p>
  </li>
</ul>

<p><strong>Community Showcase Considerations</strong>:</p>

<ul>
  <li>
    <p><strong>Anonymous interaction options</strong> for public demonstrations</p>
  </li>
  <li>
    <p><strong>Parent/guardian consent</strong> for any data collection from minor participants</p>
  </li>
  <li>
    <p><strong>Secure data handling</strong> practices when community members interact with quests</p>
  </li>
  <li>
    <p><strong>Right to be forgotten</strong> - easy data deletion for quest participants</p>
  </li>
</ul>

<h4 id="practice-3-inclusive-and-accessible-quest-design">Practice 3: <strong>Inclusive and Accessible Quest Design</strong></h4>

<p><strong>Implementation in Community Presentation</strong>:</p>

<ul>
  <li>
    <p><strong>Universal design principles</strong> ensuring quest accessibility for diverse abilities</p>
  </li>
  <li>
    <p><strong>Multiple interaction methods</strong> (keyboard, mouse, touch, voice) for quest navigation</p>
  </li>
  <li>
    <p><strong>Clear language and instructions</strong> accommodating different literacy levels</p>
  </li>
  <li>
    <p><strong>Cultural sensitivity</strong> in quest narratives and character design</p>
  </li>
</ul>

<p><strong>Community Engagement Focus</strong>:</p>

<ul>
  <li>
    <p><strong>Diverse representation</strong> in quest characters and storylines</p>
  </li>
  <li>
    <p><strong>Multilingual support</strong> considerations for diverse community members</p>
  </li>
  <li>
    <p><strong>Accessibility testing</strong> with community members having different abilities</p>
  </li>
  <li>
    <p><strong>Feedback mechanisms</strong> that welcome diverse perspectives and experiences</p>
  </li>
</ul>

<h3 id="f-quest-development-timeline-and-activities">F. Quest Development Timeline and Activities</h3>

<h4 id="week-1-api-discovery-and-quest-planning">Week 1: API Discovery and Quest Planning</h4>

<ul>
  <li>
    <p><strong>Day 1-2</strong>: Instructor demonstrates API exploration; students follow with guided testing</p>
  </li>
  <li>
    <p><strong>Day 3-4</strong>: Design quest user stories incorporating demonstrated AI and data features</p>
  </li>
  <li>
    <p><strong>Day 5</strong>: Create quest wireframes and technical implementation plan using provided templates</p>
  </li>
</ul>

<h4 id="week-2-javascript-api-integration">Week 2: JavaScript API Integration</h4>

<ul>
  <li>
    <p><strong>Day 1-2</strong>: Implement Gemini AI integration following demonstrated patterns</p>
  </li>
  <li>
    <p><strong>Day 3-4</strong>: Add database API calls for user progress using shown examples</p>
  </li>
  <li>
    <p><strong>Day 5</strong>: Integrate guest login system with instructor-provided authentication templates</p>
  </li>
</ul>

<h4 id="week-3-quest-refinement-and-community-preparation">Week 3: Quest Refinement and Community Preparation</h4>

<ul>
  <li>
    <p><strong>Day 1-2</strong>: User testing within quest teams following demonstrated testing protocols</p>
  </li>
  <li>
    <p><strong>Day 3-4</strong>: Polish user experience using demonstrated UX enhancement techniques</p>
  </li>
  <li>
    <p><strong>Day 5</strong>: <strong>Night at the Museum</strong> - Community showcase and authentic feedback</p>
  </li>
</ul>

<h4 id="assessment-checkpoints">Assessment Checkpoints</h4>

<ul>
  <li>
    <p><strong>End of Week 1</strong>: Quest concept with technical feasibility validation using provided rubric</p>
  </li>
  <li>
    <p><strong>End of Week 2</strong>: Functional API integration demonstrating core features following class examples</p>
  </li>
  <li>
    <p><strong>End of Week 3</strong>: Complete quest ready for community presentation meeting demonstrated standards</p>
  </li>
</ul>

<h4 id="quest-showcase-framework">Quest Showcase Framework</h4>

<p>Students prepare their <strong>Quest of Code</strong> projects for authentic community engagement, demonstrating both technical skill and digital citizenship principles through interactive experiences designed for diverse audiences, following the frameworks and examples provided throughout instruction.</p>

<h3 id="g-api-integration-templates-and-usage-documentation">G. API Integration Templates and Usage Documentation</h3>

<h4 id="g1-promise-based-api-call-templates">G1. Promise-Based API Call Templates</h4>

<h5 id="template-1-gemini-ai-integration-for-quest-characters">Template 1: Gemini AI Integration for Quest Characters</h5>

<p>// Quest AI Character Interaction Template<br />
function questAIResponse(userInput, questContext) {<br />
 return fetch(‘/gemini’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({ <br />
 message: userInput, <br />
 context: <code class="language-plaintext highlighter-rouge">Quest context: ${questContext}. Respond as a helpful quest guide.</code> <br />
 })<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(data =&gt; formatAIForQuest(data.response))<br />
 .catch(error =&gt; handleQuestError(error));<br />
}</p>

<p>// Check if Gemini API is available<br />
function checkGeminiHealth() {<br />
 return fetch(‘/gemini/health’)<br />
 .then(response =&gt; response.json())<br />
 .then(status =&gt; status.healthy)<br />
 .catch(() =&gt; false);<br />
}</p>

<h5 id="template-2-microblog-api-for-quest-interactions">Template 2: Microblog API for Quest Interactions</h5>

<p>// Create quest post or achievement share<br />
function createQuestPost(questTitle, achievement, topic) {<br />
 return fetch(‘/microblog’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({<br />
 title: questTitle,<br />
 content: achievement,<br />
 topic: topic<br />
 })<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(post =&gt; displayQuestAchievement(post))<br />
 .catch(error =&gt; showPostError(error));<br />
}</p>

<p>// Get quest-related posts for a specific page/topic<br />
function getQuestPosts(pageKey) {<br />
 return fetch(<code class="language-plaintext highlighter-rouge">/microblog/page/${pageKey}</code>)<br />
 .then(response =&gt; response.json())<br />
 .then(posts =&gt; formatQuestFeed(posts))<br />
 .catch(error =&gt; showFeedError(error));<br />
}</p>

<p>// Add reaction to quest achievement<br />
function reactToQuestPost(postId, reactionType) {<br />
 return fetch(‘/microblog/reaction’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({<br />
 post_id: postId,<br />
 reaction: reactionType<br />
 })<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(reaction =&gt; updateReactionUI(reaction))<br />
 .catch(error =&gt; handleReactionError(error));<br />
}</p>

<h4 id="g2-complete-quest-integration-examples">G2. Complete Quest Integration Examples</h4>

<h5 id="example-1-ai-powered-quest-hint-system">Example 1: AI-Powered Quest Hint System</h5>

<p>// Quest hint system using Gemini API<br />
function getQuestHint(currentStep, playerProgress) {<br />
 const hintPrompt = <code class="language-plaintext highlighter-rouge">Player is stuck on ${currentStep}. Progress: ${playerProgress}.   
 Provide a helpful hint without giving away the answer.</code>;</p>

<p>return fetch(‘/gemini’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({ message: hintPrompt })<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(data =&gt; {<br />
 // Format AI response for quest UI<br />
 return {<br />
 hint: data.response,<br />
 timestamp: Date.now(),<br />
 step: currentStep<br />
 };<br />
 })<br />
 .then(formattedHint =&gt; displayHintModal(formattedHint))<br />
 .catch(error =&gt; showFallbackHint(currentStep));<br />
}</p>

<h5 id="example-2-quest-achievement-sharing-with-microblog">Example 2: Quest Achievement Sharing with Microblog</h5>

<p>// Share quest completion with community<br />
function shareQuestAchievement(questName, completionTime, difficulty) {<br />
 // First create a post about the achievement<br />
 return fetch(‘/microblog’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({<br />
 title: <code class="language-plaintext highlighter-rouge">Quest Completed: ${questName}</code>,<br />
 content: <code class="language-plaintext highlighter-rouge">Finished in ${completionTime} on ${difficulty} difficulty!</code>,<br />
 topic: ‘quest-achievements’<br />
 })<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(post =&gt; {<br />
 // Then get recent achievements to display leaderboard<br />
 return fetch(‘/microblog/page/quest-achievements’)<br />
 .then(response =&gt; response.json())<br />
 .then(achievements =&gt; updateLeaderboard(achievements, post));<br />
 })<br />
 .catch(error =&gt; handleSharingError(error));<br />
}</p>

<h5 id="example-3-dynamic-quest-topic-creation">Example 3: Dynamic Quest Topic Creation</h5>

<p>// Auto-create topic for new quest and populate with intro post<br />
function initializeQuestTopic(questId, questTitle, questDescription) {<br />
 return fetch(‘/microblog/topics/auto-create’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({<br />
 topic_name: <code class="language-plaintext highlighter-rouge">quest-${questId}</code>,<br />
 description: <code class="language-plaintext highlighter-rouge">Discussion and progress for ${questTitle}</code><br />
 })<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(topic =&gt; {<br />
 // Create welcome post for the quest<br />
 return fetch(‘/microblog’, {<br />
 method: ‘POST’,<br />
 headers: { ‘Content-Type’: ‘application/json’ },<br />
 body: JSON.stringify({<br />
 title: <code class="language-plaintext highlighter-rouge">Welcome to ${questTitle}!</code>,<br />
 content: questDescription,<br />
 topic: topic.name<br />
 })<br />
 });<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(welcomePost =&gt; setupQuestEnvironment(welcomePost))<br />
 .catch(error =&gt; handleQuestSetupError(error));<br />
}</p>

<h4 id="g3-ux-focused-data-formatting-examples">G3. UX-Focused Data Formatting Examples</h4>

<p><strong>Gemini AI Response Formatting for Quest Narrative</strong>:</p>

<ul>
  <li>
    <p><strong>Quest Character Dialogue</strong>: Transform Gemini responses into NPC speech bubbles with character avatars</p>
  </li>
  <li>
    <p><strong>Interactive Hints</strong>: Format AI suggestions as mysterious scroll reveals or glowing text overlays</p>
  </li>
  <li>
    <p><strong>Dynamic Story Content</strong>: Use Gemini to generate quest flavor text that adapts to player choices</p>
  </li>
  <li>
    <p><strong>Smart Help System</strong>: Convert AI responses into contextual tooltips and progressive disclosure</p>
  </li>
</ul>

<p><strong>Microblog API Integration for Community Features</strong>:</p>

<ul>
  <li>
    <p><strong>Achievement Gallery</strong>: Display quest completions as visual cards with reaction counts</p>
  </li>
  <li>
    <p><strong>Progress Feed</strong>: Format microblog posts into timeline showing community quest progress</p>
  </li>
  <li>
    <p><strong>Collaborative Hints</strong>: Transform microblog replies into peer-to-peer help system</p>
  </li>
  <li>
    <p><strong>Quest Leaderboards</strong>: Use topic-filtered posts to create dynamic ranking displays</p>
  </li>
</ul>

<p><strong>Promise Chain UX Patterns</strong>:</p>

<p>// Smooth loading states with promise chains<br />
function loadQuestWithFeedback(questId) {<br />
 showLoadingSpinner(“Preparing your quest…”);</p>

<p>return checkGeminiHealth()<br />
 .then(healthy =&gt; {<br />
 if (!healthy) showOfflineMode();<br />
 updateLoadingText(“Loading quest data…”);<br />
 return fetch(<code class="language-plaintext highlighter-rouge">/microblog/page/quest-${questId}</code>);<br />
 })<br />
 .then(response =&gt; response.json())<br />
 .then(questData =&gt; {<br />
 updateLoadingText(“Initializing quest environment…”);<br />
 return formatQuestInterface(questData);<br />
 })<br />
 .then(questUI =&gt; {<br />
 hideLoadingSpinner();<br />
 return displayQuest(questUI);<br />
 })<br />
 .catch(error =&gt; {<br />
 hideLoadingSpinner();<br />
 showQuestLoadError(error);<br />
 });<br />
}</p>

<h4 id="g4-api-documentation-structure-for-students">G4. API Documentation Structure for Students</h4>

<p><strong>Available API Endpoints Reference</strong>:</p>

<p><strong>Gemini AI Endpoints</strong>:</p>

<ul>
  <li>
    <p>POST /gemini - Send messages to AI for quest interactions</p>
  </li>
  <li>
    <p>GET /gemini/health - Check if AI service is available</p>
  </li>
  <li>
    <p>GET /gemini/debug - Development endpoint for troubleshooting</p>
  </li>
</ul>

<p><strong>Microblog Data Endpoints</strong>:</p>

<ul>
  <li>
    <p>POST /microblog - Create quest posts and achievements</p>
  </li>
  <li>
    <p>POST /microblog/reply - Reply to quest discussions</p>
  </li>
  <li>
    <p>POST /microblog/reaction - React to quest posts (likes, etc.)</p>
  </li>
  <li>
    <p>GET/POST /microblog/topics - Manage quest topic categories</p>
  </li>
  <li>
    <p>GET /microblog/page/&lt;page_key&gt; - Get posts for specific quest pages</p>
  </li>
  <li>
    <p>POST /microblog/topics/auto-create - Auto-generate topics for new quests</p>
  </li>
</ul>

<p><strong>Required Documentation Components for Students</strong>:</p>

<ol>
  <li>
    <p><strong>Promise Chain Examples</strong> - Functional programming patterns for each endpoint</p>
  </li>
  <li>
    <p><strong>Error Handling Patterns</strong> - .catch() implementations for robust user experience</p>
  </li>
  <li>
    <p><strong>UX Integration Guides</strong> - Formatting API responses for quest engagement</p>
  </li>
  <li>
    <p><strong>Testing Templates</strong> - Browser console scripts for API validation</p>
  </li>
  <li>
    <p><strong>Quest Integration Strategies</strong> - When and how to use each API in quest design</p>
  </li>
</ol>

<p><strong>Student-Created Documentation</strong>:</p>

<ul>
  <li>
    <p><strong>Quest API Usage Journal</strong> - Personal documentation of API integration decisions</p>
  </li>
  <li>
    <p><strong>Promise Pattern Library</strong> - Reusable code snippets for team sharing</p>
  </li>
  <li>
    <p><strong>UX Transformation Examples</strong> - Before/after showing raw API data vs. quest presentation</p>
  </li>
  <li>
    <p><strong>Community Integration Showcase</strong> - Examples of microblog features enhancing quest experience</p>
  </li>
</ul>

<h3 id="h-resources-and-references">H. Resources and References</h3>

<h4 id="technical-documentation">Technical Documentation</h4>

<ul>
  <li>
    <p>Flask Documentation. (2025). <em>Flask Web Development Framework</em>. Retrieved from <a href="https://flask.palletsprojects.com/">https://flask.palletsprojects.com/</a></p>
  </li>
  <li>
    <p>Google AI. (2025). <em>Gemini API Documentation</em>. Retrieved from <a href="https://ai.google.dev/docs">https://ai.google.dev/docs</a></p>
  </li>
  <li>
    <p>SQLAlchemy Documentation. (2025). <em>Python SQL Toolkit</em>. Retrieved from <a href="https://sqlalchemy.org/">https://sqlalchemy.org/</a></p>
  </li>
</ul>

<h4 id="code-repository">Code Repository</h4>

<ul>
  <li>
    <p>Open Coding Society. (2025). <em>GitHub Pages: Unify the frontend for full-stack apps</em> [Source code]. GitHub. <a href="https://github.com/Open-Coding-Society/pages">https://github.com/Open-Coding-Society/pages</a></p>
  </li>
  <li>
    <p>Open Coding Society. (2025). <em>Flask Portfolio Starter</em> [Source code]. GitHub. <a href="https://github.com/Open-Coding-Society/flask">https://github.com/Open-Coding-Society/flask</a></p>
  </li>
</ul>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d295" /><summary type="html"><![CDATA[WGU D295 assessment demonstrating essential concepts through quest-based e-learning design]]></summary></entry><entry><title type="html">D295 Task 1: Digital Citizenship Ideation</title><link href="https://sfi.opencodingsociety.com/wgu/d295/task1-ideation/" rel="alternate" type="text/html" title="D295 Task 1: Digital Citizenship Ideation" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d295/D295_QuestOfCode-WGU-Digital-Citizenship_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d295/task1-ideation/"><![CDATA[<!-- Converted from: QuestOfCode-WGU-Digital-Citizenship.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:04 -->
<!-- Images extracted: 0 -->

<p>Quest Of Code</p>

<p>WGU D295 Task1 – Digital Citizenship</p>

<h2 id="the-quest-of-code">The Quest of Code</h2>

<h3 id="a1-requirement-brief">A1. Requirement Brief</h3>

<p><strong>Course Details:</strong> - <strong>Grade Level:</strong> 9–12</p>

<p><strong>Content Area:</strong> Computer Science / Career and Technical Education (Information Technology Pathway)</p>

<p><strong>Course Standards:</strong> <strong>National:</strong> CTE (CSTA/IT Pathway)</p>

<p><strong>College Board Requirements:</strong> AP Computer Science Principles - Create Performance Task</p>

<p><strong>ISTE Standards</strong> for Students: International Society for Technology in Education (2016)</p>

<h3 id="a2-learning-goal">A2. Learning Goal</h3>

<p>Students will collaboratively design and develop a full-stack web application modeled as a <em>quest-based learning game</em> that demonstrates understanding of front-end, back-end, and API integration. Students will apply digital citizenship, computational thinking, and ethical technology practices while creating, deploying, and presenting their prototypes to an authentic community audience.</p>

<h4 id="a2a-an-elaboration-on-goals">A2a. An Elaboration on Goals</h4>

<p>In the evolving landscape of computer science education, The Quest of Code transforms programming instruction into an immersive, quest-based experience that merges creativity, collaboration, and technical mastery. Students move beyond routine coding tasks to embark on a narrative-driven project—one that mirrors real-world software development and promotes computational thinking, design, and digital citizenship.</p>

<p>This experience emphasizes both individual mastery and team-based innovation. Students work in collaborative teams to design a functional full-stack application that embodies key software development principles and ethical computing practices. Through this approach, they engage with authentic challenges, applying both technical and creative problem-solving in a quest-ified and meaningful context.</p>

<h4 id="a2b-prerequisites">A2b. Prerequisites</h4>

<p>Classroom students are familiar with GitHub Pages, HTML, CSS, JavaScript, and Python. They actively participate in an SDLC (Software Development Life Cycle) that includes code commits, GitHub pushes, integration with team members, and pull requests (PRs) to the instructor’s repository.</p>

<h4 id="a2c-background">A2c. Background</h4>

<p>Prior to engaging in this project, the students were introduced to a project consisting of six modules: activation, demonstration, practice, application, assessment, and integration. They are to create a project that mimics this project’s techniques while learning Full-Stack development (JavaScript interacting with Python/Flask) and utilizing APIs—focusing on login, data storage, retrieval, and Gemini APIs. This learning is modeled as a quest or adventure, with students tracking through the modules as part of an ongoing “Quest of Code” experience.</p>

<h4 id="a2d-learning-phases">A2d. Learning Phases</h4>

<p>This new phase begins with <em>Ideation</em>, where students conceptualize their projects (shown below), which then moves into <em>Storyboarding</em> and <em>Prototyping</em>. Each team’s prototype will debut during the school’s <strong>“Night at the Museum”</strong>—an Electives Department showcase attended by families and community members, many of whom are professionals in the technology sector. During this event, students will present their prototypes and gather feedback from the audience.</p>

<p>The general plan includes a simplified <em>guest login</em> that allows visitors to traverse through different stages of each project, where interactions capture and log data. This authentic public feedback experience helps student teams test usability and determine whether their prototype is ready to enter the <em>Development Phase</em> of the Agile Scrum SDLC.</p>

<h4 id="a3a-ap-standards-alignment-college-board-2024">A3a. AP Standards Alignment [College Board, 2024]</h4>

<p><strong>AP Computer Science Principles - Create Performance Task:</strong> <a href="https://apcentral.collegeboard.org/media/pdf/ap-csp-student-task-directions.pdf">Student Task Directions</a></p>

<p>“Programming is a collaborative and creative process that brings ideas to life through the development of software. In the Create performance task, you will design and implement a program that might solve a problem, enable innovation, explore personal interests, or express creativity.”</p>

<h4 id="a3b-cte-national-standards-csta-2017">A3b. CTE National Standards [CSTA, 2017]</h4>

<ul>
  <li>
    <p><strong>CSTA 3A-AP-13:</strong> Decompose problems and subproblems into parts to facilitate design, implementation, and review of programs</p>
  </li>
  <li>
    <p><strong>CSTA 3A-AP-17:</strong> Systematically design and develop programs for broad audiences by incorporating feedback from users</p>
  </li>
  <li>
    <p><strong>CSTA 3A-AP-22:</strong> Design and develop computational artifacts working in team roles using collaborative tools</p>
  </li>
</ul>

<h4 id="a3c-digital-citizenship-principles-iste-2016">A3c. Digital Citizenship Principles [ISTE, 2016]</h4>

<ul>
  <li>
    <p><strong>Empowered Learner:</strong> Students design their learning pathways</p>
  </li>
  <li>
    <p><strong>Digital Citizen:</strong> Ethical use of tools, privacy, and data responsibility</p>
  </li>
  <li>
    <p><strong>Knowledge Constructor:</strong> AI and media literacy integration</p>
  </li>
  <li>
    <p><strong>Computational Thinker:</strong> Efficient and creative problem-solving</p>
  </li>
  <li>
    <p><strong>Innovative Designer:</strong> Iterative design, prototyping, and testing</p>
  </li>
</ul>

<h3 id="a4-technology-tools">A4. Technology Tools</h3>

<p>The students will continue to build and grow existing skills; they will begin to develop skills in Digital Literacy and Citizenship related to AI and API usage in coding.</p>

<h4 id="a4a-technical-samples">A4a. Technical Samples</h4>

<table>
  <thead>
    <tr>
      <th> </th>
      <th> </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Core Domains</td>
      <td>Skill Threads</td>
    </tr>
    <tr>
      <td>Front-End</td>
      <td>HTML, CSS, JS, media presentation</td>
    </tr>
    <tr>
      <td>Back-End</td>
      <td>CRUD operations, database management</td>
    </tr>
    <tr>
      <td>AI / API Integration</td>
      <td>Internet, Deployment, JSON,</td>
    </tr>
    <tr>
      <td>Data Literacy</td>
      <td>Authentic sources, secure data handling, access tokens</td>
    </tr>
    <tr>
      <td>Communication</td>
      <td>Blogging, storytelling, web publishing, and presentation</td>
    </tr>
  </tbody>
</table>

<h4 id="a4b-learning-activity">A4b. Learning Activity</h4>

<h5 id="group-1-game-board-progression">Group 1: Game Board Progression</h5>

<p>Theme: Learning to Code Through Life’s Analogies — ‘Roll your way from traveler to full-stack developer.’</p>

<table>
  <thead>
    <tr>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Lesson</strong></td>
      <td><strong>Skill or Concept (Exit)</strong></td>
      <td><strong>Learning Activity</strong></td>
      <td><strong>Assessment</strong></td>
      <td><strong>Technology Resource</strong></td>
      <td><strong>Digital Citizenship Principle</strong></td>
    </tr>
    <tr>
      <td><strong>1. Front-End: “Travel” Module</strong></td>
      <td>HTML/CSS, UI/UX planning</td>
      <td>Design a landing page (User View) that guides users on their quest; include buttons, links, and styled interface elements.</td>
      <td>Working, responsive interface mock-up</td>
      <td>VS Code, GitHub Pages, Chrome DevTools</td>
      <td><strong>Digital Citizen</strong>: Ethical design of user interfaces and accessibility considerations</td>
    </tr>
    <tr>
      <td><strong>2. Back-End: “Food / Database Kitchen” Module</strong></td>
      <td>CRUD operations, database schema</td>
      <td>Create a small data model to store user progress, awards, or tokens; connect to front-end</td>
      <td>Functional CRUD (Create/Read/Update/Delete) implementation</td>
      <td>Python Flask, SQLite, Postman API Testing</td>
      <td><strong>Knowledge Constructor</strong>: Secure data handling and privacy protection</td>
    </tr>
    <tr>
      <td><strong>3. Integration: “Sports / API Arena” Module</strong></td>
      <td>Fetch, async data handling</td>
      <td>Create a module that GETs/POSTs live user data (XP, tokens, progress)</td>
      <td>Working API connection and visible data flow</td>
      <td>JavaScript Fetch API, JSON, GitHub Actions</td>
      <td><strong>Computational Thinker</strong>: Efficient data processing and API security</td>
    </tr>
    <tr>
      <td><strong>4. Reflection &amp; AI: “AI / Code Coach” Module</strong></td>
      <td>AI-assisted debugging, optimization</td>
      <td>Use AI tools to identify and resolve code issues or improve features and insure credibility</td>
      <td>Reflection report + improved code commit</td>
      <td>GitHub Copilot, ChatGPT, AI Code Review Tools</td>
      <td><strong>Empowered Learner</strong>: Responsible AI usage and source verification</td>
    </tr>
  </tbody>
</table>

<h5 id="group-2-data-famine-progression">Group 2: Data Famine Progression</h5>

<p>Theme: Rebuilding Digital Civilization — ‘Your planet has lost its data and knowledge. Restore the civilization through quests of technology and truth.’</p>

<table>
  <thead>
    <tr>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
      <th> </th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Planet</strong></td>
      <td><strong>Theme / Analogy</strong></td>
      <td><strong>Skill Focus</strong></td>
      <td><strong>Technology Resource</strong></td>
      <td><strong>Learning Activity</strong></td>
      <td><strong>Digital Citizenship Principle</strong></td>
    </tr>
    <tr>
      <td>AI Planet</td>
      <td>Awakening</td>
      <td>AI tools for problem-solving and digital literacy</td>
      <td>ChatGPT, GitHub Copilot, Gemini API</td>
      <td>Build AI-assisted code solutions and evaluate AI responses for accuracy</td>
      <td><strong>Empowered Learner</strong>: Critical evaluation of AI-generated content and responsible AI usage</td>
    </tr>
    <tr>
      <td>Media Literacy Planet</td>
      <td>Awareness</td>
      <td>Identifying misinformation, scams, and bias</td>
      <td>Python Beautiful Soup, JSON APIs, Fact-checking websites</td>
      <td>Create a web scraper to analyze news sources and media libraries to build a truth verification tool</td>
      <td><strong>Digital Citizen</strong>: Information literacy, source verification, and ethical fact-checking practices</td>
    </tr>
    <tr>
      <td>Secure Data Planet</td>
      <td>Rebuilding Infrastructure</td>
      <td>Secure database creation and CRUD operations</td>
      <td>SQLite, Python Flask, JWT tokens, bcrypt hashing</td>
      <td>Design encrypted user authentication system with secure password storage</td>
      <td><strong>Knowledge Constructor</strong>: Data privacy protection and secure coding practices</td>
    </tr>
    <tr>
      <td>Microblogging Planet</td>
      <td>Communication</td>
      <td>APIs, posting, and sharing securely</td>
      <td>RESTful APIs, JavaScript Fetch, OAuth 2.0</td>
      <td>Build a secure social media platform with user authentication and content moderation</td>
      <td><strong>Computational Thinker</strong>: Secure communication protocols and data transmission</td>
    </tr>
    <tr>
      <td>Vault Planet</td>
      <td>Completion</td>
      <td>Synthesis of all skills</td>
      <td>Git version control, GitHub Pages, Jekyll deployment</td>
      <td>Create final portfolio showcasing all planet achievements with live demonstrations</td>
      <td><strong>Innovative Designer</strong>: Digital portfolio curation and professional presentation</td>
    </tr>
  </tbody>
</table>

<h4 id="a4c-assessments">A4c. Assessments</h4>

<p>This project will have several built-in checkpoints and reviews. T<em>he Quest of Code represents a transformative approach to computer science education, combining technical skill development with creative problem-solving and ethical technology practices. All these events are recorded on Canvas, LMS.</em></p>

<ul>
  <li>
    <p><strong>Checkpoint 1:</strong> Ideation finalization – sync on above</p>
  </li>
  <li>
    <p><strong>Checkpoint 2:</strong> Storyboard review – story sync before code start</p>
  </li>
  <li>
    <p><strong>Checkpoint 3:</strong> Pre-review Prototype – progress in GitHub</p>
  </li>
  <li>
    <p><strong>Checkpoint 4: Event</strong> Participation - feedback collection</p>
  </li>
  <li>
    <p><strong>Summation:</strong> Reflection of feedback with Instructor</p>
  </li>
</ul>

<h4 id="a4d-technology-resource">A4d. Technology Resource</h4>

<p>Each lesson’s technology resources directly support the main learning goal of “collaboratively designing and developing a full-stack web application modeled as a quest-based learning game that demonstrates understanding of front-end, back-end, and API integration.”</p>

<p><strong>Learning Goal Component → Technology Resource Alignment:</strong></p>

<ul>
  <li>
    <p><strong>Front-End Development</strong>: VS Code, GitHub Pages, Chrome DevTools enable students to create and deploy user interfaces that guide users through their quest-based game</p>
  </li>
  <li>
    <p><strong>Back-End Development</strong>: Python Flask, SQLite, Postman API Testing allows students to build server-side logic and databases that store game progress and user data</p>
  </li>
  <li>
    <p><strong>API Integration</strong>: JavaScript Fetch API, JSON, GitHub Actions provide the tools needed to connect front-end and back-end components with live data exchange</p>
  </li>
  <li>
    <p><strong>Collaborative Development</strong>: VS Code, GitHub Copilot, ChatGPT support team-based coding and peer feedback essential for collaborative software development</p>
  </li>
  <li>
    <p><strong>Quest-Based Learning</strong>: All tools work together to enable students to create quest-ified learning experiences that engage authentic community audiences during presentations</p>
  </li>
</ul>

<h4 id="a4e-digital-citizenship-principles">A4e. Digital Citizenship Principles</h4>

<p>In build this lesson we have considered many topics in</p>

<ol>
  <li>
    <p>Digital Access is directly correlated to the entire lesson.</p>
  </li>
  <li>
    <p>Digital Communication is the core requirement of the lesson, specifically blogging and building secure chat.</p>
  </li>
  <li>
    <p>All coding projects are published to the Open Coding Society <strong>[OCS, 2025]</strong> GitHub repository which contains an Apache <a href="https://github.com/Open-Coding-Society/pages/blob/main/LICENSE">license</a>.</p>
  </li>
  <li>
    <p>Two AP [College Board, 2024] topics will be covered in these workshops: “5.5 Legal and Ethical Concerns” and “Safe Computing”.</p>
  </li>
</ol>

<h3 id="b-implementation---e-learning-environment">B. Implementation - E-Learning Environment</h3>

<h4 id="selected-activity-front-end-travel-module-implementation">Selected Activity: Front-End “Travel” Module Implementation</h4>

<p><strong>Activity Selected:</strong> Lesson 1 - Front-End “Travel” Module where students design a landing page that guides users on their coding quest.</p>

<p><strong>E-Learning Implementation Process:</strong></p>

<p>This activity is implemented entirely in an online, collaborative environment where students work remotely or in hybrid settings. Students begin by accessing the lesson materials through the Open Coding Society web portal, where they find tutorial videos, code examples, and project templates.</p>

<p><strong>Step-by-Step E-Learning Implementation:</strong></p>

<ol>
  <li>
    <p><strong>Initiation</strong>: Students access the lesson through GitHub Pages links sent via Canvas LMS, Online Classroom Calendar, and Slack messaging platform.</p>
  </li>
  <li>
    <p><strong>Tutorial Phase</strong>: Students read lesson and watch embedded video tutorials on HTML/CSS fundamentals</p>
  </li>
  <li>
    <p><strong>Practice Phase</strong>: Students use GitHub in conjunction with VS Code on laptop (or cloud-based VS Code) to write and test code, using VSCode live share students can work collaboratively</p>
  </li>
  <li>
    <p><strong>Collaboration</strong>: Students use GitHub pull requests to share work and receive peer and instructor feedback</p>
  </li>
  <li>
    <p><strong>Assessment</strong>: Students deploy their landing pages to GitHub Pages for live demonstration</p>
  </li>
  <li>
    <p><strong>Reflection</strong>: Students document their learning process through GitHub Issues and blog posts</p>
  </li>
</ol>

<p><strong>E-Learning Benefits</strong>: This approach allows students to work at their own pace, access materials 24/7, collaborate asynchronously with teammates, and build a portfolio of work that’s immediately shareable with potential employers or college admissions.</p>

<h3 id="b1-digital-tools">B1. Digital Tools</h3>

<h4 id="tool-1-github-projects--issue-with-canvas-integrations">Tool 1: GitHub Projects + Issue with Canvas integrations</h4>

<p><strong>Purpose</strong>: Project management, assignment distribution, and progress tracking</p>

<p><strong>Implementation</strong>:</p>

<ul>
  <li>
    <p><strong>Setup</strong>: Teacher creates GitHub Projects with milestone-based task boards for each lesson phase</p>
  </li>
  <li>
    <p><strong>Student Access</strong>: Students receive GitHub Issues invitations through Canvas assignment links, automatically creating tracked tasks</p>
  </li>
  <li>
    <p><strong>Development Environment</strong>: Students work on personal laptops using Visual Studio Code with extensions (Live Server, GitLens) or KASM cloud workspaces for Chromebook users</p>
  </li>
  <li>
    <p><strong>Collaboration</strong>: Students use GitHub Issues for peer code review, bug reporting, and feature requests</p>
  </li>
  <li>
    <p><strong>Progress Tracking</strong>: Teachers monitor individual and team progress through GitHub Project boards and Issue completion</p>
  </li>
  <li>
    <p><strong>Assessment</strong>: Teachers review code commits, comment on Issues, and track milestone achievements through integrated dashboards</p>
  </li>
</ul>

<p><strong>E-Learning Advantage</strong>: GitHub integration, real-time progress visibility, authentic project management experience, accessible on any device.</p>

<h4 id="tool-2-local-development-stack--github-pages-deployment">Tool 2: Local Development Stack + GitHub Pages Deployment</h4>

<p><strong>Purpose</strong>: Full-stack development environment with live deployment pipeline</p>

<p><strong>Implementation</strong>:</p>

<ul>
  <li><strong>Local Setup</strong>: Students install and configure complete development environment on personal laptops:
    <ul>
      <li><strong>Visual Studio Code</strong> with essential extensions (Live Server, GitLens, Python, Ruby)</li>
      <li><strong>Ruby + Jekyll</strong> for static site generation and local testing</li>
      <li><strong>Python + Pip packages</strong> (Flask, SQLite3, Beautiful Soup) for backend development</li>
      <li><strong>Git version control</strong> for code management and collaboration</li>
    </ul>
  </li>
  <li>
    <p><strong>Chromebook Alternative</strong>: KASM cloud workspaces provide identical development environment in browser</p>
  </li>
  <li>
    <p><strong>Development Workflow</strong>: Students code locally, test using Jekyll serve, commit changes via Git</p>
  </li>
  <li>
    <p><strong>Deployment Pipeline</strong>: GitHub Pages automatically deploys student repositories to live websites</p>
  </li>
  <li>
    <p><strong>Portfolio Building</strong>: Each project becomes part of student’s professional portfolio with live demonstrations</p>
  </li>
  <li><strong>Community Showcase</strong>: Live projects shared during “Night at the Museum” events for authentic audience feedback</li>
</ul>

<p><strong>E-Learning Advantage</strong>: Industry-standard development workflow, professional portfolio creation, immediate live deployment, authentic learning environment that mirrors real-world software development.</p>

<h4 id="c-references">C. References</h4>

<p>[CSTA, 2017] Computer Science Teachers Association. (2017). CSTA K–12 Computer Science Standards. Retrieved from <a href="https://www.csteachers.org/page/standards">https://www.csteachers.org/page/standards</a></p>

<p>[ISTE, 2016] International Society for Technology in Education (ISTE). (2016). ISTE Standards for Students. Retrieved from <a href="https://www.iste.org/standards/for-students">https://www.iste.org/standards/for-students</a></p>

<p>[College Board, 2024] College Board. (2024). AP Computer Science Principles Create Performance Task. Retrieved from <a href="https://apcentral.collegeboard.org/">https://apcentral.collegeboard.org/</a></p>

<p><strong>[OCS, 2025]</strong> Open Coding Society. (2025). <em>Open Coding Society Curriculum Portal.</em> Retrieved from <a href="https://pages.opencodingsociety.com/">https://pages.opencodingsociety.com</a></p>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d295" /><summary type="html"><![CDATA[WGU D295 assessment focusing on digital citizenship education ideation phase]]></summary></entry><entry><title type="html">D296 Task 1: Designing for the Whole Child</title><link href="https://sfi.opencodingsociety.com/wgu/d296/task1-design-whole-child/" rel="alternate" type="text/html" title="D296 Task 1: Designing for the Whole Child" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d296/D296_Design-for-Whole-Child-WGU-E-learning_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d296/task1-design-whole-child/"><![CDATA[<!-- Converted from: Design-for-Whole-Child-WGU-E-learning.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:04 -->
<!-- Images extracted: 2 -->

<p>Designing for the Whole Child in K–12 E-Learning</p>

<h3 id="a1-introduction">A1. Introduction</h3>

<p>Designing meaningful online learning experiences requires an understanding of the real challenges that K–12 students face when learning in digital environments.<br />
While WGU materials emphasize empathy for the learner, much of my perspective comes from daily experience teaching <strong>Computer Science and Web Development</strong> through both <strong>in-person and online modalities</strong>.</p>

<p>Over the past 1.5 years of online teaching, I have witnessed the differences between: - <strong>In-class hybrid instruction</strong>, where students collaborate, receive immediate feedback, and build together. - <strong>Fully online learning</strong>, where motivation, structure, and emotional engagement must be deliberately designed into the experience.</p>

<p>Understanding these differences is essential for instructional designers, because <em>effective digital design is not merely content delivery — it is the architecture of engagement, emotion, and equity.</em></p>

<h4 id="modes-of-teaching-comparison">Modes of Teaching Comparison</h4>

<p><img src="/images/docx/D296_Design-for-Whole-Child-WGU-E-learning_image.png" alt="Image " /></p>

<h3 id="a2-challenges-and-contrasts">A2. Challenges and Contrasts</h3>

<p>The WGU lessons organize e-learning challenges across social, emotional, learning, and external dimensions. In my own practice, I have encountered these same themes, often through real examples in coding and project-based instruction. Below, I highlight how WGU’s theory aligns or contrasts with my classroom experiences.</p>

<h4 id="a2a-social-challenges">A2a. Social Challenges</h4>

<p>WGU Emphasis: Providing time for communication and routine feedback.</p>

<p>My Experience: In my coding classes, collaboration is central. Students learn GitHub workflows, peer review, and agile communication. In contrast, online learners often miss spontaneous collaboration—chat threads and delayed feedback lack the social immediacy that fosters peer learning.</p>

<p>Contrast: Where WGU suggests scheduling structured interaction, I have learned to integrate asynchronous community touchpoints such as comments on Issue threads, GitHub PRs, or breakout room updates. These allow students to “see” each other’s progress in authentic, project-based contexts.</p>

<h4 id="a2b-emotional-challenges">A2b. Emotional Challenges</h4>

<p>WGU Emphasis: Integrating opportunities to cultivate emotional intelligence.</p>

<p>My Experience: Emotional regulation is critical in programming. Students frequently encounter frustration during debugging. In person, I can read body language and intervene early. Online, those cues disappear, so I use reflection forms and “checkpoint” meetings and journaling to surface emotions.</p>

<p>Contrast: WGU’s guidance aligns with my practice, but I find success in tying emotional awareness to technical problem-solving — teaching students that frustration is a normal data point, not a failure. Sharing a work product in an authentic problem surfaces emotional intelligence.</p>

<h4 id="a2c-learning-challenges">A2c. Learning Challenges</h4>

<p>WGU Emphasis: Using UDL (Universal Design for Learning) as a foundation for course development.</p>

<p>My Experience: UDL principles — multiple modalities of representation, engagement, and expression — naturally align with project-based computer science outcomes. Students learn differently: some prefer visual diagrams of systems; others need code examples or tutorials. I often use live coding sessions side-by-side so learners can observe their expected path.</p>

<p>By contrast: While WGU emphasizes structural design, I focus on fluid scaffolding: dynamic adaptation based on student progress, rather than fixed course architecture.</p>

<h4 id="a2d-learning-distractions-external-challenges">A2d. Learning Distractions (External Challenges)</h4>

<p>WGU Emphasis: Explicitly teaching life skills such as time management and organization.</p>

<p>My Experience: Self-management is the make-or-break factor in online learning. In computer science, deadlines for commits or sprint tasks can teach real-world time discipline. I embedded agile tools like Kanban boards and burndown lists to make progress visible and self-directed.</p>

<p>By contrast, WGU’s recommendation feels broad, while my experience shows that project management tools themselves can teach life skills more effectively than separate lessons. Tasks, deadlines, and individual accountability help students engage in a timely manner.</p>

<h4 id="a2e-experiential-challenges">A2e. Experiential Challenges</h4>

<p>WGU Extension: Having authentic learning and outcomes.</p>

<p>My Experience: Authentic projects — student-built websites, Flask apps, or GitHub Pages portfolios — drive intrinsic motivation far better than quizzes. Students see their work hosted publicly, connected to professional skills. Having an end-of-trimester showcase, online or in person with parents, helps drive professional and authentic feedback.</p>

<p>By contrast: WGU emphasizes structure and routine; I emphasize ownership and relevance. Authentic learning transforms routine tasks into personal narratives of capability.</p>

<h4 id="a3-teacher-response-table">A3. Teacher Response Table</h4>

<table>
  <thead>
    <tr>
      <th>WGU Focus Area</th>
      <th>Summary of Concept</th>
      <th>My Teaching Response</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>A2a. Social</strong></td>
      <td>Provide time for communication and routine feedback.</td>
      <td>I prioritize community through structured peer code reviews, GitHub collaboration, and open feedback sessions. Students post daily updates on our Kanban boards and share progress through standups. This mirrors real-world development communication.</td>
    </tr>
    <tr>
      <td><strong>A2b. Emotional</strong></td>
      <td>Integrate opportunities to cultivate emotional intelligence.</td>
      <td>Students participate in reflective prompts after sprints to discuss frustrations, breakthroughs, and teamwork dynamics. This builds emotional awareness and self-regulation as part of agile iteration.</td>
    </tr>
    <tr>
      <td><strong>A2c. Learning Challenges</strong></td>
      <td>Apply UDL (Universal Design for Learning) as the foundation for course development.</td>
      <td>Each sprint includes multimodal resources—text tutorials, demos, and interactive examples—to meet diverse learner needs. Students can choose to submit evidence of learning through video walkthroughs, GitHub commits, or written reflections.</td>
    </tr>
    <tr>
      <td><strong>A2d. Learning Distractions</strong></td>
      <td>Explicitly teach life skills such as time management and organization.</td>
      <td>I use GitHub Projects and milestone planning to teach prioritization. Students learn to break down complex tasks into manageable issues and to maintain focus across competing classes and responsibilities. Students are encouraged to work in the moment and use classroom time as the largest part of their 5-hour commitment to build projects and code.</td>
    </tr>
    <tr>
      <td><strong>A2e. Experiential</strong></td>
      <td>Design authentic learning and outcomes.</td>
      <td>Students develop real-world full-stack projects connected to their interests (e.g., “Night at the Museum,” “Gamify-FinTech, Facial Recognition, Quest based adventure games”). They deploy applications using Flask, GitHub Pages, and Docker—mirroring professional software workflows.</td>
    </tr>
  </tbody>
</table>

<h4 id="a4-conclusion">A4. Conclusion</h4>

<p>Addressing the five core challenges in K–12 e-learning—social, emotional, learning, distraction, and experiential—through intentional, evidence-based strategies leads to more engaged, resilient, and successful students. By fostering community, supporting emotional growth, differentiating instruction, teaching self-management, and promoting authentic learning, we create digital environments where every learner can thrive.</p>

<p><img src="/images/docx/D296_Design-for-Whole-Child-WGU-E-learning_image2.png" alt="Image 2" /></p>

<h4 id="b-acknowledgment-of-sources">B. Acknowledgment of Sources</h4>

<p>No sources used outside of WGU-provided materials.</p>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d296" /><summary type="html"><![CDATA[WGU D296 assessment focusing on designing for the Whole Child in K–12 E-Learning]]></summary></entry><entry><title type="html">D296 Task 2: Flask Server Crash Course</title><link href="https://sfi.opencodingsociety.com/wgu/d296/task2-flask-crash-course/" rel="alternate" type="text/html" title="D296 Task 2: Flask Server Crash Course" /><published>2026-11-20T01:18:15+00:00</published><updated>2026-11-20T01:18:15+00:00</updated><id>https://sfi.opencodingsociety.com/wgu/d296/D296_Flask-Server-Crash-Course-WGU-E-learning_DOCX_</id><content type="html" xml:base="https://sfi.opencodingsociety.com/wgu/d296/task2-flask-crash-course/"><![CDATA[<!-- Converted from: Flask-Server-Crash-Course-WGU-E-learning.docx -->
<!-- File creation date: 2026-11-20 01:18:15 -->
<!-- Conversion date: 2026-11-20 01:19:04 -->
<!-- Images extracted: 1 -->

<p>SPM2 – Task2 - Crash Course on Building a Flask Server</p>

<h3 id="a-unit-description">A. Unit Description</h3>

<h4 id="csp-trimester-2-full-stack-development--sprint-4">CSP Trimester 2: Full Stack Development — Sprint 4</h4>

<p><strong>Overview:</strong></p>

<p>This sprint moves beyond the prototype phase of your Moving West Coast Travel or Digital Famine project. You will transition from a front-end demo to a fully functional full-stack application, integrating a live backend using Python Flask.</p>

<p>The goal is to demonstrate your ability to design, develop, and deploy a web application that includes:</p>

<ul>
  <li>
    <p>Persistent data management</p>
  </li>
  <li>
    <p>User interaction and authentication</p>
  </li>
  <li>
    <p>Dynamic content and performance tracking</p>
  </li>
</ul>

<p>These components will fulfill your APCSP Create Performance Task requirements, including code, video, and written reflection.</p>

<p><strong>Subject and Grade:</strong><br />
Computer Science, Grades 10–12</p>

<p><strong>Delivery Model:</strong></p>

<ul>
  <li>
    <p>Teacher-led demonstrations of Flask server setup and coding</p>
  </li>
  <li>
    <p>Students follow along on their own devices, building each component step-by-step</p>
  </li>
  <li>
    <p>Peer collaboration and live troubleshooting occur during demonstration</p>
  </li>
  <li>
    <p>Formative checkpoints and group discussions after each major milestone</p>
  </li>
</ul>

<h5 id="visual-timelines">Visual Timelines</h5>

<p><img src="/images/docx/D296_Flask-Server-Crash-Course-WGU-E-learning_image.png" alt="Image " /></p>

<h4 id="major-deliverables">Major Deliverables</h4>

<p>The following systems and deliverables will guide your progress through the sprint and ensure alignment with APCSP Create Performance Task requirements:</p>

<h5 id="1-flask-login-system-foundational">1. Flask Login System (Foundational)</h5>

<p><strong>Focus:</strong> Understanding and using authentication (cookies, sessions), user identification, and authorization as a foundation for all other deliverables.</p>

<p><strong>Usage:</strong></p>

<ul>
  <li>
    <p>Students will use Flask’s login-required features to ensure users are identified and authorized before accessing or modifying quest and API/Admin features.</p>
  </li>
  <li>
    <p>The login system is critical for enabling personalized quest experiences and secure data management.</p>
  </li>
</ul>

<p><strong>Tasks:</strong></p>

<ul>
  <li>
    <p>Demonstrate and practice user registration, login, and logout using Flask sessions.</p>
  </li>
  <li>
    <p>Apply login-required decorators to protect quest and admin routes.</p>
  </li>
  <li>
    <p>Store and retrieve user data (e.g., profile details, quest progress, and achievements) as part of the quest and admin deliverables.</p>
  </li>
</ul>

<p><strong>Deliverable:</strong> A demonstrated understanding and correct usage of authentication and authorization, supporting secure and individualized quest and admin features.</p>

<h5 id="2-quest-simplification--experience-design">2. Quest Simplification &amp; Experience Design</h5>

<p><strong>Focus:</strong> Refine your quest flow and enhance usability and motivation.</p>

<p><strong>Tasks:</strong></p>

<ul>
  <li>
    <p>Simplify or redesign your existing quest structure, reducing 20+ steps into 6–8 meaningful stages for your team.</p>
  </li>
  <li>
    <p>Apply your best UI/UX ideas to improve the clarity and engagement of the user/learner.</p>
  </li>
  <li>
    <p>Convert static lessons or activities into interactive challenges — such as code races, timed events, or live competitions.</p>
  </li>
  <li>
    <p>Record user performance and outcomes into your database for analytics or leaderboard features.</p>
  </li>
</ul>

<p><strong>Deliverable:</strong> An interactive, engaging, and data-driven quest experience that demonstrates thoughtful design and backend integration.</p>

<h5 id="3-api--database-design--admin-interface">3. API / Database Design &amp; Admin Interface</h5>

<p><strong>Focus:</strong> Data modeling, CRUD operations, and administrative management tools.</p>

<p><strong>Tasks:</strong></p>

<ul>
  <li>
    <p>Design a database schema for storing quests, user progress, and results.</p>
  </li>
  <li>
    <p>Build Flask routes and API endpoints for data access and updates.</p>
  </li>
  <li>
    <p>Create an Admin Dashboard (using Python/Jinja) to view and manage users, quests, and progress.</p>
  </li>
  <li>
    <p>Ensure data integrity and security across all operations.</p>
  </li>
</ul>

<p><strong>Deliverable:</strong> A fully operational backend with a simple yet functional admin UI for managing application data.</p>

<h5 id="instructor-requirements--guidance">Instructor Requirements / Guidance</h5>

<p>By the end of this sprint, each student should be able to:</p>

<ul>
  <li>
    <p>Explain their individual contribution and its impact on the full system.</p>
  </li>
  <li>
    <p>Show how that individual contribution meets College Board requirements.</p>
  </li>
  <li>
    <p>Demonstrate understanding of how frontend and backend communicate.</p>
  </li>
  <li>
    <p>Prepare to record a 1-minute silent video showing their individual contribution, user features, and data management.</p>
  </li>
</ul>

<h3 id="b-standards-based-evaluation--improvements">B. Standards-Based Evaluation &amp; Improvements</h3>

<h4 id="1-standard-b-content-indicator-b3">1. Standard B: Content, Indicator B3</h4>

<p><em>Source:</em> <a href="https://nsqol.org/the-standards/quality-online-courses/"><em>NSQOL Standards</em></a></p>

<p><strong>Digital literacy and communication skills are incorporated and taught as an integral part of the curriculum.</strong></p>

<p>a. <strong>Current Alignment:</strong></p>

<ul>
  <li>
    <p>In-person, students practice digital literacy by using command-line tools, GitHub, and VS Code, but communication is mostly verbal or via in-class collaboration.</p>
  </li>
  <li>
    <p><em>Example:</em> Students clone a repo and run Flask locally but may not document their process or communicate progress online effectively.</p>
  </li>
</ul>

<p>b. <strong>Improvement for E-Learning (Aligned to Deliverables):</strong></p>

<ul>
  <li>
    <p>For the <strong>Login System</strong>, students will review authentication and user management features in GitHub Issues, practicing technical communication and feature review.</p>
  </li>
  <li>
    <p>For <strong>Quest Design</strong>, students will collaborate on UI/UX improvements and interactive features, sharing progress and feedback in Slack and GitHub Issue discussions.</p>
  </li>
  <li>
    <p>For <strong>API/Admin</strong>, students will use Kanban boards and PRs to coordinate backend/API implementation, and code admin screens and dashboards.</p>
  </li>
  <li>
    <p>All phases require digital communication, peer review, and portfolio blogging in Jupyter Notebooks and GitHub.</p>
  </li>
</ul>

<p>c. <strong>Supporting Tool:</strong></p>

<ul>
  <li>Slack, VSCode, GitHub Issues, Kanban Board, Pull Requests, and Jupyter Notebooks. All elements practice synchronous or asynchronous communication and digital literacy.</li>
</ul>

<h4 id="2-standard-c-instructional-design-indicator-c8"><strong>2. Standard C: Instructional Design, Indicator C8</strong></h4>

<p><em>Source:</em> <a href="https://nsqol.org/the-standards/quality-online-courses/"><em>NSQOL Standards</em></a></p>

<p><strong>The course design provides opportunities for learner-instructor interaction, including opportunities for regular feedback about learner progress.</strong></p>

<p>a. <strong>Current Alignment:</strong></p>

<ul>
  <li>
    <p>In-person feedback is immediate and informal during coding sessions.</p>
  </li>
  <li>
    <p><em>Example:</em> The teacher and the Teacher Aide circulate and give real-time help until table teams have the ability to progress independently.</p>
  </li>
</ul>

<p>b. <strong>Improvement for E-Learning (Aligned to Deliverables):</strong></p>

<ul>
  <li>
    <p><strong>Login System:</strong> Formative checkpoints for understanding of registration, login, and user data features, with students submitting screenshots or code for instructor and peer feedback.</p>
  </li>
  <li>
    <p><strong>Quest Design:</strong> Checkpoint feedback on quest flow, UI/UX, and engagement features, with group check-ins and peer review of interactive challenges.</p>
  </li>
  <li>
    <p><strong>API/Admin:</strong> Checkpoint reviews of API endpoints, database design, and admin dashboard functionality, with feedback cycles at each milestone.</p>
  </li>
  <li>
    <p>Synchronous and asynchronous feedback is provided via Jupyter Notebooks, Slack, and GitHub PRs.</p>
  </li>
</ul>

<p>c. <strong>Supporting Tool:</strong></p>

<ul>
  <li>Jupyter Notebooks with embedded formative tasks, Slack for group check-ins, and GitHub PRs for code review and feedback.</li>
</ul>

<h4 id="3-standard-d-learner-assessment-indicator-d3"><strong>3. Standard D: Learner Assessment, Indicator D3</strong></h4>

<p><em>Source:</em> <a href="https://nsqol.org/the-standards/quality-online-courses/"><em>NSQOL Standards</em></a></p>

<p><strong>Assessment practices provide frequent and varied opportunities for self-monitoring and reflection of learning.</strong></p>

<p>a. <strong>Current Alignment:</strong></p>

<ul>
  <li>
    <p>In-person, students reflect verbally or in journals, but not always consistently.</p>
  </li>
  <li>
    <p><em>Example:</em> End-of-lesson reflections or group discussions/checkpoints where verbal communication assist instructor to see if standards are being achieved.</p>
  </li>
</ul>

<p>b. <strong>Improvement for E-Learning (Aligned to Deliverables):</strong></p>

<ul>
  <li>
    <p><strong>Login System:</strong> Self-checks and reflection prompts after implementing authentication and user data features into Quest, with peer review of code and user experience design.</p>
  </li>
  <li>
    <p><strong>Quest Design:</strong> Milestone-based self-assessment for quest simplification, UI/UX, and engagement, with peer and instructor feedback on interactive elements.</p>
  </li>
  <li>
    <p><strong>API/Admin:</strong> Reflection and review of database design, API endpoints, and admin dashboard, with self-monitoring of progress via checklists and GitHub Issues.</p>
  </li>
  <li>
    <p>Project is broken into a Sprint with four checkpoints, each mapped to a major deliverable and formative assessment.</p>
  </li>
</ul>

<p>c. <strong>Supporting Tool:</strong></p>

<ul>
  <li>Embedded Microblog Forms, Jupyter Notebook markdown cells, and GitHub Issues for reflection, self-assessment, and milestone tracking.</li>
</ul>

<h4 id="4-standard-f-course-technology-indicator-f3"><strong>4. Standard F: Course Technology, Indicator F3</strong></h4>

<p><em>Source:</em> <a href="https://nsqol.org/the-standards/quality-online-courses/"><em>NSQOL Standards</em></a></p>

<p><strong>The course technology allows for customization and personalization.</strong></p>

<p>a. <strong>Current Alignment:</strong></p>

<ul>
  <li>
    <p>In-person, students can choose project topics but follow the same technical steps.</p>
  </li>
  <li>
    <p><em>Example:</em> All students build the same basic Flask app, but build or adapt APIs to meet their prototype project from Trimester 1 (i.e. Digital Famine or West Coast Quest frontend).</p>
  </li>
  <li>
    <p>Additionally, students are expected to build a project according to requirements to meet the College Board performance task.</p>
  </li>
</ul>

<p>b. <strong>Improvement for E-Learning (Aligned to Deliverables):</strong></p>

<ul>
  <li>
    <p><strong>Login System:</strong> Students can personalize user profiles and authentication flows, adding custom fields or features.</p>
  </li>
  <li>
    <p><strong>Quest Design:</strong> Teams and individuals can redesign quest stages, UI, and challenges to reflect their interests and creativity.</p>
  </li>
  <li>
    <p><strong>API/Admin:</strong> Students can extend the backend with unique endpoints, admin features, or analytics tailored to their project vision.</p>
  </li>
  <li>
    <p>Project regrouping and mashups encourage reduction to favorite concepts and delivery of smaller, more personalized projects.</p>
  </li>
</ul>

<p>c. <strong>Supporting Tool:</strong></p>

<ul>
  <li>GitHub branching, project templates, PRs, and GitHub Pages blogs for customization, collaboration, and final submission.</li>
</ul>

<h4 id="5-additional-standard-eg-standard-e-accessibility-indicator-e2"><strong>5. Additional Standard (e.g., Standard E: Accessibility, Indicator E2)</strong></h4>

<p><em>Source:</em> <a href="https://nsqol.org/the-standards/quality-online-courses/"><em>NSQOL Standards</em></a></p>

<p><strong>The course provides alternative means of access to course materials.</strong></p>

<p>a. <strong>Current Alignment:</strong></p>

<ul>
  <li>In-person, the instructor provides help as needed, but materials may not be accessible to all learners.</li>
</ul>

<p>b. <strong>Improvement for E-Learning (Aligned to Deliverables):</strong></p>

<ul>
  <li>
    <p><strong>Login System:</strong> Ensure authentication and user features are accessible (e.g., clear forms, keyboard navigation, alt text for avatars).</p>
  </li>
  <li>
    <p><strong>Quest Design:</strong> Provide alternative formats for quest content, captions for videos, and accessible UI for interactive challenges.</p>
  </li>
  <li>
    <p><strong>API/Admin:</strong> Admin dashboards and data tools should be screen reader compatible and support high-contrast modes.</p>
  </li>
  <li>
    <p>All deliverables require adherence to web accessibility guidelines and accessible documentation.</p>
  </li>
</ul>

<p>c. <strong>Supporting Tool:</strong></p>

<ul>
  <li>Accessible Jupyter Notebooks, web accessibility best practices, and inclusive design in all deliverables.</li>
</ul>

<h3 id="c-sources">C. Sources</h3>

<ul>
  <li>National Standards for Quality Online Courses. <a href="https://nsqol.org/the-standards/quality-online-courses/">NSQOL Standards</a></li>
</ul>]]></content><author><name>John Mortensen</name></author><category term="WGU" /><category term="wgu" /><category term="d296" /><summary type="html"><![CDATA[WGU D296 assessment on building a Flask server for e-learning applications]]></summary></entry></feed>