Welcome to CPSC 310!

Introduction to Software Engineering

UBC-CPSC 310 - 2023 W T1, 101, 102

ABSENCES | PIAZZA | CLASSY | GITHUB | LABS AND OFFICE HOURS

Instructor: Reid Holmes

Labs and Office Hours: Labs and Office Hours page

Lectures: 100% in person (no recordings)

Deadlines, Resources: Schedule page

ALL STUDENTS INCLUDING WAITLISTED STUDENTS: START CHECKPOINT 0 ON THE FIRST DAY OF SEMESTER!

It takes a lot of time to get setup and started. It will be graded before the add/drop date.

Lab sections - Course staff cannot move students between lab sections. Please watch the SSC for updates to the lab sections you wish to join if you want to move; lab composition is very dynamic as the add/drop deadline nears. Faculty/course staff cannot sign registrar forms, only the CS advisors can change lab/lecture composition.

Waitlist update - We have been told that the course will be overenrolled by the first lecture and the waitlists will be cleared at that time. Unfortunately, if you are not registered in the course by the first lecture, you will be unable to take the course this term.

Please do not contact the instructional staff about the waitlist - We do not have any information about it, and cannot tell you your position on it or the likelihood you will get into the class. Course staff cannot sign people into the class. Please contact CS advisors. More waitlist instructions.

We are prepared for students falling sick for some time during the term. Other life issues can always come up and the stress-level can become quite high; you may need a break. Here's what we're doing:

Quizzes will be taken in person in the CBTF (details below).
We will offer grade accommodations (not extensions) for the project to those who have suffered absences or for those who are experiencing longer running situations that are severely impacting their ability to do work (such as caring for unwell dependents); fill in the Absences form in the page header.
The ClientBot will provide sanitiy checking feedback on each branch commit, smoke test feedback on each merge-to-main, and full feedback on each checkpoint at the deadline.
If you're needing support because of personal reasons (like personal tragedy or crisis) please get in touch. We have more we can do for students in really difficult situations.

There's more information on each of the above in the sections below....

About Lectures

All lectures will take place in person. You can attend lecture in either section, regardless of where you are registered. Lectures will not be recorded, but the slides will be published by the end of the week the lecture took place in.

If a class has to be cancelled because the instructor is unable to come to class, the topic will be moved to a subsequent day. If this happens such that there is a squeeze, topics may be shortened and additional resources made available to preserve learning outcomes.

Entire semester schedule is on the Schedule page.

Section 101: Swing 222; Tu/Th 0800 - 0920
Section 102: MacMillan 360; Tu/Th 1400 - 1520

About Labs

Labs will all be online this term. The schedule is here. During the first week of the term, labs function as drop-in office hours.

After the Checkpoint 0 deadline labs are mandatory. You must attend a weekly Scrum with your mentor TA and submit a weekly progress report. If you are absent please contact the course admin at cpsc310-admin@cs.ubc.ca.

If you can't get into the lab you want, please just watch SSC for availability. We can't help with lab registration.

About Office hours

All TA/Project office hours will be in person, except if a TA chooses to hold them online. There is a queue system to process students fairly. Wait times can be long before deadlines, so plan accordingly.

There will be an explicit process to follow this term if you wish to show TAs your code in office hours, details to follow.

Instructor office hours will be in person. These office hours will focus on course content, not the project.

About Quizzes

There will be 4 quizzes, but we only count your top 3. Quizzes are cumulative and will cover all lecture material prior to the end of the Thursday before the quiz opens. Practice quizzes will not be available.

Quiz availability dates are on the Schedule page. Quizzes will be taken in person in special-purpose labs (ICCS 008 and 014) referred to as the Computer-Based Testing Facility (CBTF). You will self-schedule your quiz time by making a reservation in one of the sessions listed at ca.prairietest.com (PT). We will announce in advance when the PT reservation system is available for each quiz. Quizzes will not be returned but will be available for viewing in the CBTF at various points during the term and before the final exam.

CBTF sessions typically occur on Wed, Thu, and Fri and seats are first-come, first-served for all times. Please arrive at the CBTF approximately 10 min before your scheduled time, and bring your UBC ID card for checkin.

The CBTF is a secure, invigilated, testing site consisting of two neighboring rooms in the basement of ICCS. When you arrive for your quiz, you will be asked to place all of your personal belongings including all electronics (watches, phones, ear buds, etc.) on the shelves at the front of the room. After check-in you will take your seat, log in to PT, and begin your quiz when the invigilator gives the signal. When you’re finished, just submit your quiz, collect your things, and leave the room!

Collaboration/communication with others (tutors, other students, anyone) is not allowed during the quizzes and while the quiz is open for other students. If detected, it will be considered academic misconduct.

Because we are allowing flexible quiz-taking, you are not allowed to post any content or question about any quiz to any forum (Piazza, reddit) or to communicate with any other student about a quiz. Any such communication is considered academic misconduct and will be treated seriously.

Misconduct on any quiz will result in a score of 0 for all quizzes for all students involved; quiz weight cannot be transferred to the final in these cases.

About the Project

The project has 4 checkpoints (C0..C3).

All project deadlines are on the Schedule page.

See the Project page for more details! The project is entirely about having a development-based experiential learning experience. No interim solutions will be posted, the value of the project is in ideating and evaluating your own strategies for systematically tackling larger-scale development challenges.

You will need a partner for Checkpoints 1-3, and that person must be in your lab. Teams are declared the week after the add/drop date. If you don't have a teammate at that time we will assign you to a team.

All checkpoints have set deadlines. These are given on the schedule page. AutoTest will provide full feedback (and a grade) for the highest commit on the main branch at the deadline. Smoke tests can be run on all commits on the main branch prior to the deadline. Sanity tests will be automatically run on your personal branches. You should be checking your own progress using your own tests, and using our AutoTest Smoke tests.

You may NOT use a tutor to help you with the project content. You may not look for project-specific help online. This will be considered academic misconduct.

For Checkpoints 1-3, you must also submit a weekly progress/work report individually.

Questions: Piazza

It is highly recommended that you sign up with your cs email (the r2d2 email address you are given) so that we can identify you in case we need to be in touch over Piazza.

Piazza is intended to be your mechanism to communicate with the teaching team.

There are no private posts available. To individually contact a TA you must attend lab or office hours.

If you can't get into Piazza, contact cpsc310-admin@cs.ubc.ca.

Join Piazza

Absences: Form

The project has some hard deadlines: Checkpoint 0 at the drop date, and the Checkpoint 1-3 deadlines during the semester. We won't be offering extensions on these deadlines for any reason, because of the way our grading works. But we will offer grade accommodations for the project to those who have suffered absences or for those who are experiencing conditions that are severely hurting their ability to do work (such as having kids home from school, caring for another person because they are unwell, etc). Fill out the absence form in the page header. You don't need to provide proof - just provide an explanation so we can assess the accommodation that's right for you. Forms must be submitted by December 7 @ 1800.

Accommodations: Course Coordinator

Please inform the Course Coordinator at cpsc310-admin@cs.ubc.ca of all accommodations from the Centre for Accessibility.

Admin Issues: Course Coordinator

For anything else related to the administration of the course, please contact the Course Coordinator at cpsc310-admin@cs.ubc.ca.

Cheating:

IMPORTANT: DO NOT CHEAT ON THE PROJECT. Do not copy code from others or the web. Do not share code. Do not look at old projects if you happen upon them while searching the web, and do not look at project code belonging to students in the class currently. Concrete details are given here. As in a corporate environment, you are responsible for every line of code you commit to your repository. Tutors can not help you do your project work. You must do all your own work. Cases will be referred to the dean and students have received 0 in the course, and been suspended for copying in past terms.

Respectful Environment:

Everyone involved with CPSC 310 is responsible for understanding and abiding by UBC's Respectful Environment Statement.

The Statement of Principle of UBC's Respectful Environment Statement is "The best possible environment for working, learning and living is one in which respect, civility, diversity, opportunity and inclusion are valued. Everyone at the University of British Columbia is expected to conduct themselves in a manner that upholds these principles in all communications and interactions with fellow UBC community members and the public in all University-related settings." More details can be found on the department's resource page.

License

The readings and pre-recorded videos for this course are licensed using CC-by-SA. However, it is important to note that the lecture videos, slides, deliverable descriptions, code implementing the deliverables, exams, and exam solutions are considered private materials. We go to considerable lengths to make the project an interesting and useful learning experience for this course. This is a great deal of work, and while future students may be tempted by your solutions, posting them does not do them any real favours. Please be considerate with these private materials and not pass them along to others, do not make your repos public or post them to other sites online.

Page updated

Google Sites

Report abuse