Computer Science Honors
Course Progress
0/0
Learning Goals 3
→Form Teams of 2-3 (Wayfinding Game + Tooling)
→Draft Preliminary Abstract
→Initialize GitHub Repo / Kanban Board (Projects or Jira)
1 assignment due
Learning Goals 3
→Instructional Problem, Current & Desired State KSAs
→Gap Analysis + Research Questions
→Team Norms & Technical Ownership Roles
Learning Goals 4
→Review 3+ Existing Commercial/Open-Source/Academic Solutions
→Product Requirements Document (PRD) w/ Quantified Metrics
→Patent & Open-Source License Search (MIT, GPL, Apache)
→Peer Review: Trade Problem Statement + PRD with Another Team
1 assignment due
Learning Goals 3
→Present PRD to Industry Mentor for Feasibility Feedback
→Signed Mentor Agreement Form
→Initialize Engineering Portfolio
1 assignment due
Learning Goals 4
→Reflect on Sprint
→Self-Assessment
→Peer and Teacher Feedback
→Set Future Knowledge Goals
2 assignments due
Learning Goals 4
→Sketch 3+ Competing Design Concepts
→Score Concepts in a Decision/Design Matrix
→Concept Testing (Paper Prototype, Wireframe, or Spike)
→First Mentor Meeting: Present Concepts for Design Feedback
1 assignment due
Learning Goals 3
→Justify Design with Math/Science/CS Principles
→Technical Drawing / CAD / System Architecture Diagram
→Material List, Tool Selection & Tool Safety
1 assignment due
Learning Goals 3
→Assess Cost, Manufacturability & Technical Feasibility
→Vendor & Material Cost Sourcing / Bill of Materials Audit
→Prototype Timeline for Build & Test
1 assignment due
Learning Goals 4
→Mock-up / Concept Model
→Prototype Build (Assembly) Procedure
→Preliminary Design Review
→Build Working MVP + Log First Test Results vs. Sprint 1 PRD
1 assignment due
Learning Goals 4
→Second Mentor Meeting: Demo Prototype for Feasibility Feedback
→Define Testing Criteria & Testing Procedure
→Run Physical Testing & Record Data
→Critical Design Review → Redesign, Refine & Re-test
1 assignment due
Learning Goals 3
→Demo Prototype to Target Users / External Stakeholders
→Collect & Document Structured External Feedback
→Update Multimedia Display with Evaluation Findings
Learning Goals 3
→Post-Mortem on Technical Debt & Bugs
→Individual + Team Reflection on Trimester 1
→Finalize Sprint 1-3 Engineering Portfolio
1 assignment due
Learning Goals 3
→Element L: Draft Recommendations for Next Design Iteration
→Element M: Finalize Electronic Portfolio & Multimedia Display
→Element M: Night at the Museum (N@tM) — Defend Alpha to Judging Panel
1 assignment due
Learning Goals 3
→Log Trimester 1 Failures & Pivots in a Version-Controlled Changelog
→Root-Cause Analysis of N@tM Panel & Sprint 3 Issues
→Revise Problem Statement with Post-Alpha Evidence
1 assignment due
Learning Goals 3
→Build an FMEA Risk Matrix with Your Mentor
→Document & Analyze Your Trimester 1 Prototype as the 'Previous Solution'
→Rank Failure Modes by Severity, Occurrence & Detection
1 assignment due
Learning Goals 3
→Revise PRD to Stricter, Industry-Grade Quantified Specs
→Justify Each Spec Change Against FMEA + Mentor/User Feedback
→Peer Review the Revised PRD with Another Team
1 assignment due
Learning Goals 3
→Reflect on Redesign Decisions
→Reset Team Norms & Technical Ownership for the Build Phase
→Set Knowledge Goals for Sprint 5
1 assignment due
Learning Goals 3
→Generate Production-Fidelity Design/Architecture Options
→Decision Matrix v2 Against Revised PRD
→Select & Justify the Beta Design
1 assignment due
Learning Goals 3
→Full Sub-System Integration Plan
→Updated Technical Drawings / CAD / Architecture Diagrams
→Apply Advanced STEM Principles at Production Fidelity
Learning Goals 3
→Cost Out Manufacturing / Hosting at Scale
→Regulatory & Compliance Considerations
→Revised Timeline for Beta Build & Test
1 assignment due
Learning Goals 3
→Build Production-Grade Beta Prototype
→Fully Integrate All Sub-Systems
→Log Beta Build Results vs. Revised PRD
1 assignment due
Learning Goals 3
→Edge-Case, Load & Regulatory-Compliance Testing
→Record Data Against Revised PRD Targets
→Comparative Data Analysis: Beta vs. Alpha Prototype
1 assignment due
Learning Goals 3
→Run User Acceptance Testing with External Participants
→Document External/Mentor Evaluation of the Beta
→Redesign & Refine Based on UAT Findings
Learning Goals 3
→Write the Final Engineering Assessment
→Draft the Future Roadmap Beyond Capstone
→Individual + Team Reflection Across Both Iterations
1 assignment due
Learning Goals 3
→Element L: Final Designer's Recommendations Across Both Iterations
→Element M: Package Final Technical Portfolio (Repo, Docs, Testing Logs)
→Element M: Deliver Venture-Style Capstone Defense to Judging Panel
1 assignment due
Element F: Consideration of Design Viability
1 min read
•
Assignment
Week 7: Consideration of Design Viability
PLTW Element F — Consideration of Design Viability.
Assess Viability
Before you build, stress-test the design on paper across the dimensions that kill real projects:
- Cost viability — can this be built and (if applicable) deployed/hosted within budget?
- Manufacturability / buildability — can your team actually construct this with the time and skills available this trimester?
- Technical feasibility — are there any unproven assumptions (an API that may not support what you need, a sensor accuracy you haven’t verified) that need a spike before you commit?
Vendor & Material Cost / Bill of Materials
- Source real costs for every material, part, or paid service in your Material List (Element E). No placeholder numbers.
- Compile a Bill of Materials (BOM): item, vendor/source, quantity, unit cost, total cost.
- For software-only builds, this includes hosting tiers, API rate limits/costs, and any paid dependencies.
Timeline of Building & Testing
- Lay out a Prototype Timeline: what gets built in what order, and when testing checkpoints happen, through the end of Sprint 2 (Week 8) into Sprint 3.
- Turn the timeline into GitHub Issues on your Kanban board with due dates — this is your Engineering Journal timeline, not a static document.
Core Deliverables
- Design viability assessment (cost / manufacturability / feasibility).
- Bill of Materials with sourced costs.
- Build-and-test timeline reflected in your Kanban board.
Submit Assignment
Need to update a submission later? Open the submissions dashboard.
Course Timeline
Week 0 Chat click to open
No messages yet.
Week 1 Chat click to open
No messages yet.
Week 2 Chat click to open
No messages yet.
Week 3 Chat click to open
No messages yet.
Week 4 Chat click to open
No messages yet.
Week 5 Chat click to open
No messages yet.
Week 6 Chat click to open
No messages yet.
Week 7 Chat click to open
No messages yet.
Week 8 Chat click to open
No messages yet.
Week 9 Chat click to open
No messages yet.
Week 10 Chat click to open
No messages yet.
Week 11 Chat click to open
No messages yet.
Week 12 Chat click to open
No messages yet.
Week 13 Chat click to open
No messages yet.
Week 14 Chat click to open
No messages yet.
Week 15 Chat click to open
No messages yet.
Week 16 Chat click to open
No messages yet.
Week 17 Chat click to open
No messages yet.
Week 18 Chat click to open
No messages yet.
Week 19 Chat click to open
No messages yet.
Week 20 Chat click to open
No messages yet.
Week 21 Chat click to open
No messages yet.
Week 22 Chat click to open
No messages yet.
Week 23 Chat click to open
No messages yet.
Week 24 Chat click to open
No messages yet.