CSSE | CSP | CSA | Readme | About |
Computer Science and Software Engineering
Sprint1: Tools and Software Development Processes
By the end of Weeks 0-3, students will have gained practical experience in blogging, coding with Jupyter Notebooks, and GitHub Pages; learning will begin with Linux, 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 Articulation Credit and Game Development journey.
Illustration
+-----------------+ | Laptop, OS | | Tool Setup | +-----------------+ | | VS Code, Markdown, Jupyter Notebook, 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 - Bathroom pass |
|
1 |
- GitHub Pages Playground |
- Learning Habits |
|
2 |
- Frontend Development |
||
3 |
- SASS basics |
- Pair Showcase |
Sprint2: Introduction to Development with JavaScript
A key focus of this course is to make Web Games using JavaScript. These next few weeks we start covering object-oriented programming in JavaScript with game emphasis. Topics include control structures, data types, input/output, operators, classes, methods and parameters, basic inheritance, and documentation practices.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
4 |
- Sprint 2 - CSSE Objectives |
- Gaming Intro |
|
5 |
- JavaScript Data Types and Operators |
||
6 |
- JavaScript Variables, Input, Output |
- RPG Hacks |
|
7 |
- JavaScript For Loops and Sprites |
Sprint3: Building a blog with GitHub Pages for N@tM
Part of the process of becoming technically proficient is working on fundamentals and then taking on challenges while coding. These challenges with some vision, questions, and AI research, it will be amazing what can be done. Our goal is to participate in N@tM with the other CS classes and other classes from the Electives Department. We should have a blog, progress in a game, and a series of lesson hacks to show off.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
8 |
- Sprint 3 - CSSE Objectives |
- JavaScript Lessons |
|
9 | |||
10 | |||
11 | |||
12 |
Sprint4: Planning, Exploration, and OOP Programming
Students, in trios, will work on Platformer Game and study OOP. There will be a lot of code, some Tech Talks, and some Teaching assignments provided to learn the code.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
13 |
- Sprint 4 - CSSE Objectives |
- Agile Methodology Intro - OOP game levels, Part 1 files - OOP game levels, Part 2 coding |
|
14 |
- Animation Transitions - Enemies - Leaderboard - Parallax / Assets - Platforms - Player elements - Player preferences / Local Storage |
- Mario | Enemies | Student - Mario | Elevated Platforms | Student - Mario | Parallax | Student - Lopez | Animation | Student - Select | Local Storage | Student - Leaderboard | Student - Player | Student |
|
15 |
Sprint5: Prgramming Structures and Game Development
The Teacher will be providing topics. All teams will be doing hacks and forming a more complete Mario game.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
16 | |||
17 |
Sprint6: Create a Final Project, "Student Teaching Teams", and N@tM
Trimester 2 concludes with students presenting their project at N@tM. Each person within "Student Teams" will have their own specialty feature within the student project. Students should be able to talk about design, coding, and present features of their portion of the system.
Week | Issues | Code, Code, Code | Collaboration |
---|---|---|---|
18 | |||
19 | |||
20 | |||
21 | |||
22 | |||
23 | |||
24 | |||
25 |