Announcements
Team Repository Setup Now Available and Information about Project Final Deliverables, Posters/Demos Posted
We have posted the instructions for setting up your team repository. You can find them in the CI/CD Pipeline Activity. The repository will include the starter code for the final project. We recommend that you start this process as soon as possible to avoid any delays.
In addition, each team needs to work with their Mentor TA to choose one issue tracking software for their project. You will need to update your project work on github Projects, JIRA or something similar.
We have also published requirements for final project deliverables on the course website. This includes grading rubrics and other requirements related to the submission of the final project (i.e., code/testing, report). In addition, we have provided a list of expectations for the final demos / presentations with the grading rubric. Please be sure to review these quickly.
Canvas assignments for these are now published.
Finally, we have scheduled a number of ‘work on project’ sessions during our regular class meetings. Please check the calendar for your section. For those class meetings we will be taking attendance. Your attendance at these meetings will collectively count as 1 In-Class Activity.
Software Development Process
As part of the software development process, each team is expected to use a structured development process, including pull requests, code reviews, etc. Each team will also submit sprint reports, individual surveys, and have meetings with TA Mentor. The development process started earlier this week (as you started developing your project plan) and the required “process-related” submissions will start later this week.
These assignments are required for weeks 3-7 and count towards “project process” part of the project which is worth 20% of the overall project grade.
Here are important submissions to remember for upcoming weeks:
- Every week all members of a team are expected to meet with their mentor TA twice for a regularly scheduled meeting. Weekly Canvas assignments (called “TA Meeting”) will help track your attendance for these meetings.
- Every week each student is expected to complete one (Confidential, Peer Evaluation) Survey by Friday 6pm. The link can be found under the Canvas assignment (called “Peer Evaluations”) which will help track if you completed the survey or not.
- At the end of each sprint (Fridays for Week 3-6 and Tuesday for Week 7), each team will submit a sprint report (and retrospective) through a Canvas assignment (called “Sprint Report and Retrospective”). Sprint schedule can be found in the project plan handout.
- After the revised project plan is submitted, we will provide instructions to create project repos. During your development, each team member is expected to contribute to the project regularly and evenly (with minumum two commits per sprint). TAs will review your github commits, PRs, code reviews regularly and will keep an eye on appropriate division of labor within the project team. They will also provide you a weekly assessment of your work.
Please add these to your calendars as reminders.
Project Teams Announced
Project Team Assignments are now posted on piazza. Please coordinate with your assigned TA Mentors to schedule a kick-off meeting. The first team deliverable will be the preliminary project plan due on Friday, May 22nd. The requirements for the project plan can be found on the course website and the related Canvas assignment is also published.
If you have any questions about the project team assignment, please reach out to your instructor by email.
Team Formation Survey is Now Available + IP2 Published
Please complete this Team Formation Survey to help us organize you into a team for the term project. EVERY STUDENT must fill this form out by 6pm EST on Friday May 15th. Please fill out the form even if you don’t have any preference for team members. We would recommend that you check with other students in your section BEFORE filling out the survey.
Also, the second individual project deliverable is now released, and will be due on Wednesday, May 20th at 6pm EST. We strongly encourage you to read through the assignment soon, so that you can begin to formulate a plan of attack to complete this assignment.
Individual Project Deliverable 1 Posted
The first individual project deliverable is now posted. This deliverable will be due on Wednesday May 13th 6pm ET. Your code will be submitted through github Classroom. The link to your project repo will be submitted on Gradescope.
On Tuesday afternoon (i.e., before the first day of classes), we will be adding all enrolled students to our github organization (and you will be receving an invitation by email). Once you have accepted that, you will be be able to start working on IP1, which we would encourage you to do early. Feel free to use piazza to ask questions and use office hours if you need help.
The schedule of office hours is now posted on the staff page. We will start holding office hours from Wednesday May 6th. We have 25 hours of scheduled TA office hours per week.
Welcome to CS4530 - Summer 2026
On behalf of the entire instructional team (instructor and 5 TAs), welcome to the Summer 2026 edition of CS 4530! This website will contain all of the lectures, assignments, activities and tutorials for the class. Our Canvas site contains your gradebook as well as single-sign-on links to Piazza (for questions and discussion), instructions for submitting assignments and replicates much of the material from the class website.
In advance of the first week of class, we’ve shared the calendar for our section, the first two lectures (with related activities), and tutorials on installing your IDE, Typescript, Unit testing with Vitest, and API Requests. Please take a moment to review those. In addition, the first individual project deliverable will be posted at the start of the semester and it will be due a week later on Wednesday 5/13.
We are looking forward to meeting you all next week!