Computer Science Honors

Course Progress 0/0
Week 6 Element E: Application of STEM Principles & Practices

Element E: Application of STEM Principles & Practices

1 min read

Week 6: Application of STEM Principles & Practices

PLTW Element E — Application of STEM Principles and Practices.

Justify the Design with STEM Principles

For a CS/software Capstone, “STEM principles” means the computer science, data structures, algorithms, or systems concepts that make your design work — not just that it works, but why it works. Document, for example:

  • The algorithmic or architectural approach and its complexity/scaling tradeoffs.
  • Any math/statistics underlying your solution (e.g. a scoring model, a cognitive-load metric, a signal-processing step).
  • Relevant CS principles from prior coursework you’re applying (data modeling, API design, security, concurrency, etc.).

Technical Drawing / Architecture Diagram

  • Produce a Technical Drawing appropriate to your build: for hardware, a dimensioned CAD drawing; for software, a system architecture diagram (components, data flow, API boundaries).
  • Diagrams belong in your engineering portfolio, versioned alongside your code — not as a one-off image nobody can trace back to a decision.

Material List, Tool Selection & Tool Safety

  • Draft a Material List — for software, this includes libraries, frameworks, APIs, and hosting/services you intend to depend on, each with its license noted.
  • Tool Selection — what you’re building with and why (language, framework, hardware platform).
  • Tool Safety — for physical builds, standard shop/tool safety sign-off; for software, note any tools with elevated access (deploy keys, admin APIs) and how you’re handling them safely.

Core Deliverables

  • STEM justification write-up.
  • Technical drawing or architecture diagram.
  • Material list with licenses noted.
  • Tool selection & safety notes.

Course Timeline