Design and implementation of novel software solutions. Problem identification and definition; idea generation and evaluation; and software implementation, testing, and deployment. Emphasizes software development best practices including framework selection, code review, documentation, appropriate library usage, project management, continuous integration and testing, and teamwork.
Working together enhances your learning and problem-solving abilities. It's a chance to share ideas, pool skills, and have a rewarding experience. Whether you're teaming up with friends or making new connections, this collaborative approach will enrich your time in CS222.
For these reasons, group work is a core part of this course and the majority of your grade will be based on your team project (completed in groups of exactly four).
|Monday||No OH this week!|
|Tuesday||No OH this week!|
|Wednesday||No OH this week!|
|Thursday||No OH this week!|
|Friday||No OH this week!|
|Saturday||No office hours|
All office hours are hosted on Campuswire. Please join using the Campuswire link posted on Canvas.
|8/25||Course Introduction [Recording] [Slides]|
|9/1||Git Basics [Recording] [Excalidraw]|
|9/8||Git Advanced [Recording] [GitHub Resources]|
|9/15||Software Engineering Overview [Recording] [Slides]|
|9/22||Successful Projects [Recording] [Slides]|
|9/29||Frontend Development [Recording] [Slides]|
|10/6||Backend Development [Recording] [Slides]|
|10/13||Code Commenting [Recording] [Slides]|
|10/20||Cloud Computing [Recording] [Slides]|
|10/27||Databases [Recording] [Slides]|
|11/3||Security [Recording] [Slides]|
|11/10||Networks [Recording] [Slides]|
|11/17||Wrapping up - Post Mortems [Recording] [Slides]|
|11/24||FALL BREAK - ENJOY YOUR VACATION|
|12/1||Mastering Presentation Skills [Recording]|
|TBD (Finals Week)||Final Project Presentations!|
As the semester progresses, we will continue to update the schedule.
Lectures: Attendance is not required, however we will post a short quiz on the content of each lecture. This is much easier if you go to lecture, but we'll post recordings and/or slides. Unless otherwise specified, any assignments announced during lecture (i.e. the quizzes) are due at the start of the following lecture.
Grading PolicyPlease see the Canvas gradebook!
Your group members are the only ones permitted to develop and debug all work submitted unless otherwise directed in the course.
You may have high-level discussions or discuss rules of language syntax with students outside of your group. However, the source code for your project may only be shown to people outside of your group or course staff until after the current semester has concluded.
Your group may consult resources that help you attain a better conceptual understanding of a given problem and the techniques to solve it. However, you must clearly cite whatever outside material you introduce or adapt into your submission. For each coding check-in, any source code in your repository may contain up to 25% code from external sources. This code must be cited appropriately. This policy applies to any code copied from sites like StackOverflow and GeeksForGeeks and placed directly into your source code. It does not include the usage of open source libraries as project dependencies (e.g. web frameworks, JSON parsing libraries, etc.).
The CS department expects you to be familiar with the CS department's Honor Code and the University expects you all to be familiar with Rule 33 in the Code of Policies and Regulations Applying to All Students. All parties involved in a violation of this policy will receive a 0 on that check-in and their final course grade reduced by one letter (e.g., A->B, B->C, etc.). A second offense will result in a failing grade for the class.
In the event of an academic integrity violation, we will attempt to separately establish each personâ€™s involvement and appropriate sanctions separately. However, by default, all group members will receive the same penalty.
General Software Engineering
Git and GitHub
Mental Health and Inclusivity
- College of Engineering Syllabus Statements
- Statement on anti-racism and inclusivity
The intent of this section is to raise student and instructor awareness of the ongoing threat of bias and racism and of the need to take personal responsibility in creating an inclusive learning environment.
The Grainger College of Engineering is committed to the creation of an anti-racist, inclusive community that welcomes diversity along a number of dimensions, including, but not limited to, race, ethnicity and national origins, gender and gender identity, sexuality, disability status, class, age, or religious beliefs. The College recognizes that we are learning together in the midst of the Black Lives Matter movement, that Black, Hispanic, and Indigenous voices and contributions have largely either been excluded from, or not recognized in, science and engineering, and that both overt racism and micro-aggressions threaten the well-being of our students and our university community.
The effectiveness of this course is dependent upon each of us to create a safe and encouraging learning environment that allows for the open exchange of ideas while also ensuring equitable opportunities and respect for all of us. Everyone is expected to help establish and maintain an environment where students, staff, and faculty can contribute without fear of personal ridicule, or intolerant or offensive language. If you witness or experience racism, discrimination, micro-aggressions, or other offensive behavior, you are encouraged to bring this to the attention of the course director if you feel comfortable. You can also report these behaviors to the Bias Assessment and Response Team (BART) (https://bart.illinois.edu). Based on your report, BART members will follow up and reach out to students to make sure they have the support they need to be healthy and safe. If the reported behavior also violates university policy, staff in the Office for Student Conflict Resolution may respond as well and will take appropriate action.
- Statement on CS CARES and CS Values and Code of Conduct (Approved by CS CARES Committee, January 13, 2022)
All members of the Illinois Computer Science department - faculty, staff, and students - are expected to adhere to the CS Values and Code of Conduct. The CS CARES Committee is available to serve as a resource to help people who are concerned about or experience a potential violation of the Code. If you experience such issues, please contact the CS CARES Committee. The Instructors of this course are also available for issues related to this class.
- Statement on mental health
Diminished mental health, including significant stress, mood changes, excessive worry, substance/alcohol abuse, or problems with eating and/or sleeping can interfere with optimal academic performance, social development, and emotional well-being. The University of Illinois offers a variety of confidential services including individual and group counseling, crisis intervention, psychiatric services, and specialized screenings at no additional cost. If you or someone you know experiences any of the above mental health concerns, it is strongly encouraged to contact or visit any of the University's resources provided below. Getting help is a smart and courageous thing to do -- for yourself and for those who care about you.
Counseling Center: 217-333-3704, 610 East John Street Champaign, IL 61820
McKinley Health Center:217-333-2700, 1109 South Lincoln Avenue, Urbana, Illinois 61801
University wellness center: https://wellness.illinois.edu/