CSSE | CSP | CSA | Readme | About |
Computer Science Principles
Sprint1: Tools and Software Development Processes
By the end of these, students will have gained practical experience in blogging, coding with Jupyter Notebooks, and GitHub Pages; learning will begin with Linux tool Setup, Markdown, HTML, and JavaScript. Students will establish a foundation using essential tools and software development processes to support their coding journey. Weeks 0-3 will provide a quick foundation, prior to students starting their College Board Create Task and Full Stack Web Development with Python journey.
Illustration
+-----------------+ | Laptop, OS | | Tool Setup | +-----------------+ | | VS Code, Markdown, Jupyter Notebook (.ipynb), JavaScript (.md, .html) v +-----------------+ | VS Code, Develop| | Code Editor | +-----------------+ | | Write code, make, run localhost, test, debug v +-----------------+ | VS Code, Git | | Version Control | | +-----------------+ | | Commit local versions, comment, show changes, reset branch v +-----------------+ | VS Code, Project| | GitHub Sync | +-----------------+ | | Push changes to GitHub cloud Repository (repo v +-----------------+ | GitHub, Collab | | Shared Code | +-----------------+ | | Tracking GitHub pages Actions, understanding Jekyll build files v +-----------------+ | GitHub Pages | -> Highlight languages, coding, and course skills, with Awesome Style | Showcase Project| -> Share project with the world +-----------------+
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
0 |
- Sprint 1 - Objectives |
- Tools and Equipment |
|
1 |
- GitHub Pages Playground |
- Learning Habits |
|
2 | |||
3 |
- Javascript Project Playground |
- Pair Showcase |
|
4 |
- Agile Methodology Intro |
Sprint2: Web Development Layers
During these weeks, students will delve into the frontend and backend layers used in Web Development. They will learn about the key components that make up the backend, including persistent data (SQL Database). The main focus of this sprint is to empower students to explore the development and deployment of a simple website. Throughout this period, there will be several student-led lectures (student teaching) that provide foundational concepts and help students learn programming and key principles required by the College Board.
Illustration
+---------------+ | GitHub Pages | | Design, Layout| | Frontend | +---------------+ | | User presentation, style | Actions v +--------------+ | JavaScript | | Logic/Events | +--------------+ | | JS Functionality, interactivity | Sends API request/response v +----------------+ | AWS EC2 Server | | Python / Flask | | Backend | +----------------+ | | Python Server-Side Processing | Analysis, Computation, and Models | Communicate with Data Services v +----------------+ | AWS Services | | Store Data | +----------------+
Sprint3: Web Application, Data, and N@tM
Student teams need to build their own Website, and individuals need to blog their learnings. The team Website should include interests but also requires the use of Python Flask and JavaScript programming. By the end of the Sprint, students will be ready to start many of the technical coding aspects of Web Development; having established a Deployed Website, Frontend, and Backend. In November, the Trimester will end by presenting the team project at the Electives Department "Night at the Museum" (N@tM).
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
9 |
- Sprint 3 - CSP Objectives |
- Flask Debug Walk-Through |
|
10 |
- Flocker Start APIs - Flocker Start APIs |
||
11 | |||
12 |
Sprint4: Warm-up Create Performance Task, Data Abstraction, Computer Systems, Networks, Impact of Computing
Trimester 2 will begin with advancement of Social Media Project, CPT learning and ideation. Great projects contain frontend style and backend data. Ideation for your CPT project should contain frontend using SASS; JavaScript interacting with user events; and a database with personal data structures. Student Teaching during this period will be preparing for College Board MCQ, topics will be assigned.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
13 |
- Sprint 4 - CSP Ideation and Objectives |
||
14 |
- BI 4.1 Internet - Web Server - BI 2 | Data | Binary Logic |
- BI 1 | Creative Development | Team Test - 1.1-1.4 Team Test - BI 4 | Computing Systems and Networks | AWS Deployment |
|
15 | |||
16 |
Sprint5: Create Performance Task (CPT) kickoff, CPT design and development
Trimester 2 continues with CPT project design and development. The big focus is on frontend/backend for data, databases, and login.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
17 | |||
18 | |||
19 | |||
20 | |||
21 |
Sprint6: N@tM and Create Performance Task (CPT) video and presentations. MCQ Exam Practice.
Trimester 2 concludes with students presenting their CPT project at N@tM. Each person within "Student Teams" will have their own specialty within the student project that satisfies all their Create Performance Task requirements. Students should be able to talk about design, coding, iteration, and present features of their portion of the system.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
22 | |||
23 | |||
24 |
Sprint7: Data Structures and Data Science
This is the beginning of a college course following the outline of CS113 Data Structures from Mira Costa CC. Topics, using Python, include searching, sorting, hashing, algorithms, analysis, object-oriented design, collections, lists, stacks, queues, trees, sets, dictionaries, and graphs.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
25 | |||
26 | |||
27 | |||
28 | |||
29 |
Sprint8: AP Weeks
Activities will be focused on supporting students in test preparations, including student teaching. Days that are not focused on test preparation will be focused on planning for year-end project/portfolio.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
30 | |||
31 | |||
32 | |||
33 |
Sprint9: Passion Project and N@tM
Presenting accomplishments for the year by creating a passion project for N@tM. This project will serve as the year-end final exam.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
34 | |||
35 | |||
36 |