Open Source Society University
Path to a free self-taught education in Computer Science!
# Contents
# Summary
The OSSU curriculum is a complete education in computer science using online materials. It's not merely for career training or professional development. It's for those who want a proper, well-rounded grounding in concepts fundamental to all computing disciplines, and for those who have the discipline, will, and (most importantly!) good habits to obtain this education largely on their own, but with support from a worldwide community of fellow learners.
It is designed according to the degree requirements of undergraduate computer science majors, minus general education (non-CS) requirements, as it is assumed most of the people following this curriculum are already educated outside the field of CS. The courses themselves are among the very best in the world, often coming from Harvard, Princeton, MIT, etc., but specifically chosen to meet the following criteria.
Courses must:
- Be open for enrollment
- Run regularly (ideally in self-paced format, otherwise running multiple times per year)
- Be of generally high quality in teaching materials and pedagogical principles
- Match the curricular standards of the CS 2013: Curriculum Guidelines for Undergraduate Degree Programs in Computer Science
When no course meets the above criteria, the coursework is supplemented with a book. When there are courses or books that don't fit into the curriculum but are otherwise of high quality, they belong in extras/courses or extras/readings.
Organization. The curriculum is designed as follows:
- Intro CS: for students to try out CS and see if it's right for them
- Core CS: corresponds roughly to the first three years of a computer science curriculum, taking classes that all majors would be required to take
- Advanced CS: corresponds roughly to the final year of a computer science curriculum, taking electives according to the student's interests
- Final Project: a project for students to validate, consolidate, and display their knowledge, to be evaluated by their peers worldwide
Duration. It is possible to finish within about 2 years if you plan carefully and devote roughly 20 hours/week to your studies. Learners can use this spreadsheet (opens new window) to estimate their end date. If you make a personal copy you can enter your actual course completion dates in the Curriculum Data sheet and get updated completion estimates.
Cost. All or nearly all course material is available for free. However, some courses may charge money for assignments/tests/projects to be graded. Note that Coursera offers financial aid (opens new window).
Decide how much or how little to spend based on your own time and budget; just remember that you can't purchase success!
Process. Students can work through the curriculum alone or in groups, in order or out of order.
- We recommend doing all courses in Core CS, only skipping a course when you are certain that you've already learned the material previously.
- For simplicity, we recommend working through courses (especially Core CS) in order from top to bottom, as they have already been topologically sorted (opens new window) by their prerequisites.
- Courses in Advanced CS are electives. Choose one subject (e.g. Advanced programming) you want to become an expert in and take all the courses under that heading. You can also create your own custom subject, but we recommend getting validation from the community on the subject you choose.
Content policy. If you plan on showing off some of your coursework publicly, you must share only files that you are allowed to. Do NOT disrespect the code of conduct that you signed in the beginning of each course!
Getting help (Details about our FAQ and chatroom)
# Community
- We have a discord server!
(opens new window) This should be your first stop to talk with other OSSU students. Why don't you introduce yourself right now? Join the CS channel in OSSU Discord (opens new window) - You can also interact through GitHub issues (opens new window). If there is a problem with a course, or a change needs to be made to the curriculum, this is the place to start the conversation. Read more here.
- Subscribe to our newsletter (opens new window).
- Add Open Source Society University to your Linkedin (opens new window) profile!
- Note: There is an unmaintained and deprecated firebase app that you might find when searching OSSU. You can safely ignore it. Read more in the FAQ.
# Curriculum
Curriculum version: 8.0.0 (see CHANGELOG)
# Prerequisites
- Core CS assumes the student has already taken high school math (opens new window), including algebra, geometry, and pre-calculus.
- Advanced CS assumes the student has already taken the entirety of Core CS and is knowledgeable enough now to decide which electives to take.
- Note that Advanced systems assumes the student has taken a basic physics course (e.g. AP Physics in high school).
# Intro CS
# Introduction to Programming
If you've never written a for-loop, or don't know what a string is in programming, start here. This course is self-paced, allowing you to adjust the number of hours you spend per week to meet your needs.
Topics covered:
simple programs simple data structures
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Python for Everybody (opens new window) | 10 weeks | 10 hours/week | none | chat (opens new window) |
# Introduction to Computer Science
This course will introduce you to the world of computer science. Students who have been introduced to programming, either from the courses above or through study elsewhere, should take this course for a flavor of the material to come. If you finish the course wanting more, Computer Science is likely for you!
Topics covered:
computation imperative programming basic data structures and algorithms and more
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Introduction to Computer Science and Programming using Python (opens new window) (alt (opens new window)) | 9 weeks | 15 hours/week | high school algebra (opens new window) | chat (opens new window) |
# Core CS
All coursework under Core CS is required, unless otherwise indicated.
# Core programming
Topics covered:
functional programming design for testing program requirements common design patterns unit testing object-oriented design Java static typing dynamic typing ML-family languages (via Standard ML) Lisp-family languages (via Racket) Ruby and more
The How to Code courses are based on the textbook How to Design Programs (opens new window). The First Edition is available for free online and includes problem sets and solutions. Students are encouraged to do these assignments.
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| How to Code - Simple Data (opens new window) | 7 weeks | 8-10 hours/week | none | chat (opens new window) |
| How to Code - Complex Data (opens new window) | 6 weeks | 8-10 hours/week | How to Code: Simple Data | chat (opens new window) |
| Programming Languages, Part A (opens new window) | 5 weeks | 4-8 hours/week | How to Code (Hear instructor (opens new window)) | chat (opens new window) |
| Programming Languages, Part B (opens new window) | 3 weeks | 4-8 hours/week | Programming Languages, Part A | chat (opens new window) |
| Programming Languages, Part C (opens new window) | 3 weeks | 4-8 hours/week | Programming Languages, Part B | chat (opens new window) |
# Math Electives
Students must choose one of the following topics: calculus, linear algebra, logic, or probability.
# Calculus
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Calculus 1A: Differentiation (opens new window) | 13 weeks | 6-10 hours/week | high school math | chat (opens new window) |
| Calculus 1B: Integration (opens new window) | 13 weeks | 5-10 hours/week | Calculus 1A | chat (opens new window) |
| Calculus 1C: Coordinate Systems & Infinite Series (opens new window) | 6 weeks | 5-10 hours/week | Calculus 1B | chat (opens new window) |
# Linear Algebra
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Essence of Linear Algebra (opens new window) | - | - | high school math | chat (opens new window) |
| Linear Algebra (opens new window) | 14 weeks | 12 hours/week | Essence of Linear Algebra | chat (opens new window) |
# Logic
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Introduction to Logic (opens new window) | 10 weeks | 4-8 hours/week | set theory (opens new window) | chat (opens new window) |
# Probability
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Probability (opens new window) | 24 weeks | 12 hours/week | Differentiation and Integration (opens new window) | chat (opens new window) |
# Core Math
In addition to their math elective, students must complete the following course on discrete mathematics.
Topics covered:
discrete mathematics mathematical proofs basic statistics O-notation discrete probability and more
| Courses | Duration | Effort | Notes | Prerequisites | Discussion |
|---|---|---|---|---|---|
| Mathematics for Computer Science (opens new window) (alt (opens new window)) | 13 weeks | 5 hours/week | An alternate version with solutions to the problem sets is here (opens new window). Students struggling can consider the Discrete Mathematics Specialization (opens new window) first. It is more interactive but less comprehensive, and costs money to unlock full interactivity. | Calculus 1C | chat (opens new window) |
# CS Tools
Understanding theory is important, but you will also be expected to create programs. There are a number of tools that are widely used to make that process easier. Learn them now to ease your future work writing programs.
Topics covered:
terminals and shell scripting vim command line environments version control and more
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| The Missing Semester of Your CS Education (opens new window) | 2 weeks | 12 hours/week | - | chat (opens new window) |
# Core systems
Topics covered:
procedural programming manual memory management boolean algebra gate logic memory computer architecture assembly machine language virtual machines high-level languages compilers operating systems network protocols and more
# Core theory
Topics covered:
divide and conquer sorting and searching randomized algorithms graph search shortest paths data structures greedy algorithms minimum spanning trees dynamic programming NP-completeness and more
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Divide and Conquer, Sorting and Searching, and Randomized Algorithms (opens new window) | 4 weeks | 4-8 hours/week | any programming language, Mathematics for Computer Science | chat (opens new window) |
| Graph Search, Shortest Paths, and Data Structures (opens new window) | 4 weeks | 4-8 hours/week | Divide and Conquer, Sorting and Searching, and Randomized Algorithms | chat (opens new window) |
| Greedy Algorithms, Minimum Spanning Trees, and Dynamic Programming (opens new window) | 4 weeks | 4-8 hours/week | Graph Search, Shortest Paths, and Data Structures | chat (opens new window) |
| Shortest Paths Revisited, NP-Complete Problems and What To Do About Them (opens new window) | 4 weeks | 4-8 hours/week | Greedy Algorithms, Minimum Spanning Trees, and Dynamic Programming | chat (opens new window) |
# Core Security
Topics covered Confidentiality, Integrity, Availability Secure Design Defensive Programming Threats and Attacks Network Security Cryptography and more
Note: These courses are provisionally recommended. There is an open Request For Comment (opens new window) on security course selection. Contributors are encouraged to compare the various courses in the RFC and offer feedback.
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Information Security: Context and Introduction (opens new window) | 5 weeks | 3 hours/week | - | chat (opens new window) |
| Principles of Secure Coding (opens new window) | 4 weeks | 4 hours/week | - | chat (opens new window) |
| Identifying Security Vulnerabilities (opens new window) | 4 weeks | 4 hours/week | - | chat (opens new window) |
Choose one of the following:
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Identifying Security Vulnerabilities in C/C++Programming (opens new window) | 4 weeks | 5 hours/week | - | chat (opens new window) |
| Exploiting and Securing Vulnerabilities in Java Applications (opens new window) | 4 weeks | 5 hours/week | - | chat (opens new window) |
# Core applications
Topics covered:
Agile methodology REST software specifications refactoring relational databases transaction processing data modeling neural networks supervised learning unsupervised learning OpenGL raytracing and more
| Courses | Duration | Effort | Prerequisites | Discussion |
|---|---|---|---|---|
| Relational Databases and SQL (opens new window) | 2 weeks | 10 hours/week | core programming | chat (opens new window) |
| Databases: Modeling and Theory (opens new window) | 2 weeks | 10 hours/week | Relational Databases and SQL (opens new window) | chat (opens new window) |
| Databases: Semistructured Data (opens new window) | 2 weeks | 10 hours/week | core programming | chat (opens new window) |
| Machine Learning (opens new window) | 11 weeks | 4-6 hours/week | linear algebra | chat (opens new window) |
| Computer Graphics (opens new window) | 6 weeks | 12 hours/week | C++ or Java, linear algebra | chat (opens new window) |
| Software Engineering: Introduction (opens new window) | 6 weeks | 8-10 hours/week | Core Programming, and a sizable project | chat (opens new window) |
| Software Development Capstone Project (opens new window) | 6-7 weeks | 8-10 hours/week | Software Engineering: Introduction | chat (opens new window) |
# Advanced CS
After completing every required course in Core CS, students should choose a subset of courses from Advanced CS based on interest. Not every course from a subcategory needs to be taken. But students should take every course that is relevant to the field they intend to go into.
The Advanced CS study should then end with one of the Specializations under Advanced applications. A Specialization's Capstone, if taken, may act as the Final project, if permitted by the Honor Code of the course. If not, or if a student chooses not to take the Capstone, then a separate Final project will need to be done to complete this curriculum.
# Advanced programming
Topics covered:
debugging theory and practice goal-oriented programming parallel computing object-oriented analysis and design UML large-scale software architecture and design and more
| Courses | Duration | Effort | Prerequisites |
|---|---|---|---|
| Parallel Programming (opens new window) | 4 weeks | 6-8 hours/week | Scala programming |
| Compilers (opens new window) | 9 weeks | 6-8 hours/week | none |
| Introduction to Haskell (opens new window) | 14 weeks | - | - |
| Learn Prolog Now! (opens new window) | 12 weeks | - | - |
| Software Debugging (opens new window) | 8 weeks | 6 hours/week | Python, object-oriented programming |
| Software Testing (opens new window) | 4 weeks | 6 hours/week | Python, programming experience |
| Software Architecture & Design (opens new window) | 8 weeks | 6 hours/week | software engineering in Java |
# Advanced systems
Topics covered:
digital signaling combinational logic CMOS technologies sequential logic finite state machines processor instruction sets caches pipelining virtualization parallel processing virtual memory synchronization primitives system call interface and more
| Courses | Duration | Effort | Prerequisites |
|---|---|---|---|
| Computation Structures 1: Digital Circuits (opens new window) | 10 weeks | 6 hours/week | Nand2Tetris II (opens new window) |
| Computation Structures 2: Computer Architecture (opens new window) | 10 weeks | 6 hours/week | Computation Structures 1 |
| Computation Structures 3: Computer Organization (opens new window) | 10 weeks | 6 hours/week | Computation Structures 2 |
# Advanced theory
Topics covered:
formal languages Turing machines computability event-driven concurrency automata distributed shared memory consensus algorithms state machine replication computational geometry theory propositional logic relational logic Herbrand logic game trees and more
| Courses | Duration | Effort | Prerequisites |
|---|---|---|---|
| Theory of Computation (opens new window) (Lectures (opens new window)) | 8 weeks | 10 hours/week | discrete mathematics, logic, algorithms |
| Computational Geometry (opens new window) | 16 weeks | 8 hours/week | algorithms, C++ |
| Game Theory (opens new window) | 8 weeks | 3 hours/week | mathematical thinking, probability, calculus |
# Advanced applications
These Coursera Specializations all end with a Capstone project. Depending on the course, you may be able to utilize the Capstone as your Final Project for this Computer Science curriculum. Note that doing a Specialization with the Capstone at the end always costs money. So if you don't wish to spend money or use the Capstone as your Final, it may be possible to take the courses in the Specialization for free by manually searching for them, but not all allow this.
| Courses | Duration | Effort | Prerequisites |
|---|---|---|---|
| Modern Robotics (Specialization) (opens new window) | 26 weeks | 2-5 hours/week | freshman-level physics, linear algebra, calculus, linear ordinary differential equations (opens new window) |
| Data Mining (Specialization) (opens new window) | 30 weeks | 2-5 hours/week | machine learning |
| Big Data (Specialization) (opens new window) | 30 weeks | 3-5 hours/week | none |
| Internet of Things (Specialization) (opens new window) | 30 weeks | 1-5 hours/week | strong programming |
| Cloud Computing (Specialization) (opens new window) | 30 weeks | 2-6 hours/week | C++ programming |
| Fullstack Open (opens new window) | 12 weeks | 6 hours/week | programming |
| Data Science (Specialization) (opens new window) | 43 weeks | 1-6 hours/week | none |
| Functional Programming in Scala (Specialization) (opens new window) | 29 weeks | 4-5 hours/week | One year programming experience |
| Game Design and Development (Specialization) (opens new window) | 6 months | 5 hours/week | programming, interactive design |
# Final project
OSS University is project-focused. You are encouraged to do the assignments and exams for each course, but what really matters is whether you can use your knowledge to solve a real-world problem.
After you've gotten through all of Core CS and the parts of Advanced CS relevant to you, you should think about a problem that you can solve using the knowledge you've acquired. Not only does real project work look great on a resume, but the project will also validate and consolidate your knowledge. You can create something entirely new, or you can find an existing project that needs help via websites like CodeTriage (opens new window) or First Timers Only (opens new window).
Another option is using the Capstone project from taking one of the Specializations in Advanced applications; whether or not this makes sense depends on the course, the project, and whether or not the course's Honor Code permits you to display your work publicly. In some cases, it may not be permitted; do not violate your course's Honor Code!
Put the OSSU-CS badge in the README of your repository!
(opens new window)
- Markdown:
[](https://github.com/ossu/computer-science) - HTML:
<a href="https://github.com/ossu/computer-science"><img alt="Open Source Society University - Computer Science" src="https://img.shields.io/badge/OSSU-computer--science-blue.svg"></a>
# Evaluation
Upon completing your final project, submit your project's information to PROJECTS via a pull request and use our community channels to announce it to your fellow students.
Your peers and mentors from OSSU will then informally evaluate your project. You will not be "graded" in the traditional sense — everyone has their own measurements for what they consider a success. The purpose of the evaluation is to act as your first announcement to the world that you are a computer scientist and to get experience listening to feedback — both positive and negative — and taking it in stride.
The final project evaluation has a second purpose: to evaluate whether OSSU, through its community and curriculum, is successful in its mission to guide independent learners in obtaining a world-class computer science education.
# Cooperative work
You can create this project alone or with other students! We love cooperative work! Use our channels to communicate with other fellows to combine and create new projects!
# Which programming languages should I use?
My friend, here is the best part of liberty! You can use any language that you want to complete the final project.
The important thing is to internalize the core concepts and to be able to use them with whatever tool (programming language) that you wish.
# Congratulations
After completing the requirements of the curriculum above, you will have completed the equivalent of a full bachelor's degree in Computer Science. Congratulations!
What is next for you? The possibilities are boundless and overlapping:
- Look for a job as a developer!
- Check out the readings for classic books you can read that will sharpen your skills and expand your knowledge.
- Join a local developer meetup (e.g. via meetup.com (opens new window)).
- Pay attention to emerging technologies in the world of software development:
- Explore the actor model through Elixir (opens new window), a new functional programming language for the web based on the battle-tested Erlang Virtual Machine!
- Explore borrowing and lifetimes through Rust (opens new window), a systems language which achieves memory- and thread-safety without a garbage collector!
- Explore dependent type systems through Idris (opens new window), a new Haskell-inspired language with unprecedented support for type-driven development.
# Code of conduct
OSSU's code of conduct (opens new window).
# How to show your progress
- Create an account in Trello (opens new window).
- Copy this (opens new window) board to your personal account. See how to copy a board here (opens new window).
Now that you have a copy of our official board, you just need to pass the cards to the Doing column or Done column as you progress in your study.
We also have labels to help you have more control through the process. The meaning of each of these labels is:
Main Curriculum: cards with that label represent courses that are listed in our curriculum.Extra Resources: cards with that label represent courses that were added by the student.Doing: cards with that label represent courses the student is current doing.Done: cards with that label represent courses finished by the student. Those cards should also have the link for at least one project/article built with the knowledge acquired in such course.Section: cards with that label represent the section that we have in our curriculum. Those cards with theSectionlabel are only to help the organization of the Done column. You should put the Course's cards below its respective Section's card.
The intention of this board is to provide our students a way to track their progress, and also the ability to show their progress through a public page for friends, family, employers, etc. You can change the status of your board to be public or private.
# Team
- Eric Douglas (opens new window): founder of OSSU
- hanjiexi (opens new window): lead technical maintainer
- waciumawanjohi (opens new window): lead academic maintainer
- Contributors (opens new window)