CS2212 Introduction to Software Engineering

CS2212
Introduction to
Software Engineering

Winter 2026
Course Syllabus

© Copyright Daniel Servos. Do not share or post to external sites. For Personal Use Only.
Some images and content from Software Engineering: A Practitioner's Approach 9th Edition By Roger Pressman and Bruce Maxim
Course Syllabus CS2212 Introduction to Software Engineering 2

Your Instructor
Daniel Servos
E-Mail: dservos5@[Link]
Office: MC387
Office Hours: By appointment
Appointment Link: [Link]
Course Syllabus CS2212 Introduction to Software Engineering 3

Middlesex College 3rd Floor

MC387
Course Syllabus CS2212 Introduction to Software Engineering 4

Course Description
Course Description:
Computer Science 2212 is an introduction to software engineering and its
application in team software projects. In this course, we will examine the
stages of the software engineering process, including requirements gathering,
specification, design, implementation, and testing. We will also cover the
practicalities of software engineering and a number of the key tools and
technologies leveraged in successful endeavours.
Course Syllabus CS2212 Introduction to Software Engineering 5

Course Description
Format:
Hybrid, in-class lectures with online components & videos

Tuesday Lecture Time: Friday Lecture Time:

• 10:30am to 12:30pm in NSC-145 • 11:30pm to 12:30pm in AHB-1R40
• Lectures • No in-person lecture.
• Tutorials • Time to watch online videos.
• Groupwork Activities • Time to meet with team for group
• Attendance & participation project.
during Tuesday lecture counts
towards final grade.
Course Syllabus CS2212 Introduction to Software Engineering 6

Course Sites
OWL Brightspace GitLab
• [Link] • [Link]
• Main course site • Project management tools for use
• Syllabus in the group project.
• Slides • Includes:
• Project details and resources • Git Repository
• Forums • Wiki
• Weekly readings, homework and tasks • Issue Tracker
• Announcements
• More details on this after groups
• Supplementary resources
are formed.
• Updated weekly
Course Syllabus CS2212 Introduction to Software Engineering 7

Course Sites

Let’s take a look at how the OWL

site is organized.
Course Syllabus CS2212 Introduction to Software Engineering 8

Recommended Textbook
Software Engineering A
Practitioner’s Approach
(9th Edition)
By Roger Pressman and Bruce Maxim

• Each week readings will be assigned from this

textbook.
• Both physical copies (UWO bookstore) and an
eTextbook (from Mc Graw Hil) are available.
• McGraw Hill connect will not be used (don’t need to
buy this).
Bookstore URL: [Link]
eTextbook URL: [Link]
Course Syllabus CS2212 Introduction to Software Engineering 9

Recommended Textbook
UML Distilled
(3rd Edition)
By Martin Fowler

• Optional text that will be helpful when we cover

UML.
• Great resource for you and your team when
working on the group project.
• Recommended that at least one member of
your team has a copy of this text.

Bookstore URL: [Link]

eTextbook URL: [Link]
Course Syllabus CS2212 Introduction to Software Engineering 10

Required Subscription
Kritik360
• You are required to have a subscription to
Kritik360 for this course.
• Peer-to-peer learning and evaluation platform
used for submitting and evaluating project
milestones.
• The cost of the subscription is $22.
• You cannot purchase or setup your subscription
until you receive this email invitation. This will be
sent out after the add/drop date.
Course Syllabus CS2212 Introduction to Software Engineering 11

Student Evaluation
Element Weight
Group Project 40%
Participation 10%
Group Peer Evaluations (2) 5%
Midterms (2)
45%
OR Final Exam
Course Syllabus CS2212 Introduction to Software Engineering 12

Essential Requirements
To be eligible to obtain a passing mark (50% or over) in the course you must satisfy ALL of the
following requirements:
1. You must obtain a weighted Midterm/Final Exam grade of at least 40%.
2. You must attend and be present in-person at the acceptance testing meeting with your team and TA at the
end of the term (unless written permission is given from the course instructor for an excused absence).
3. You must attend and be an active participant in the group project which entails all of the following:
a) Obtain a grade of 40% or over on your team’s peer evaluation of your performance in your team
project.
b) Contribute in some way to each milestone in the group project (as shown by the edit, commit, and
issue history on GitLab).
c) Regularly attending both your team’s weekly meetings, and the biweekly stand-up meeting with your
team’s assigned TA. You must attend at least half of each type of meeting to pass the course.
Course Syllabus CS2212 Introduction to Software Engineering 13

Group Project
All students are required to be an active participant in a term long
group project that will involve the specification, design, and
implementation of a reasonably large-scale software system,
implemented using Java.
Course Syllabus CS2212 Introduction to Software Engineering 14

Important Group Project Rules

1. All team members are expected to contribute in some way to
every project component including requirements, design,
implementation, and testing.

2. All teams must make active use of the GitLab Software

throughout the whole project (not just upload files and create tasks
at the end).

3. All teams must hold and document weekly face-to-face

meetings. Minutes must be kept by the team. Starting the week of
Jan. 19th.
Course Syllabus CS2212 Introduction to Software Engineering 15

Project Topic
Typing Game
The main purpose of the project will be to design and implement a typing game
application. The goal is to make typing practice feel like play by turning typing drills
into a game loop with clear goals, feedback, and progression. Your game should help
players improve real typing fundamentals like accuracy and speed while also keeping
them engaged through mechanics such as scoring, combos, levels, challenges, or
time-based modes.

The game does not necessarily have to be graphically demanding but must have
a graphical user interface (GUI) and follow best practices for UI design and
software engineering in general.

Full project specification can be found on

OWL (in the Group Project Unit)
Course Syllabus CS2212 Introduction to Software Engineering 16

Project Topic
Typing Game

Let’s take a look at a basic demo.

Course Syllabus CS2212 Introduction to Software Engineering 17

Group Project
Group Responsibilities
Create teams of 4 or 5 students (5 preferred)
• Make your team request on OWL by joining an open team.
• If you do not request a team by January 14th, you will be added to one by the
course instructor.
• If you request a team with less than 5 students, more members may be added to
top it up.
• I will try to honor your requests, but I may need to rearranged some teams to
make groups of 5.
Course Syllabus CS2212 Introduction to Software Engineering 18

Group Project
Group Responsibilities
Meet with your group weekly starting week of January 19th
• You must meet weekly and keep minutes of your meeting.
• Weekly meetings can be in-person or online but must be face-to-face (e.g. use
Zoom if online). Can not be done over text-based chat or voice only.
• Meeting times must be arranged that work for everyone in the group (not on
holidays or reading week).
• Meeting length is up to you but a minimum of 1 hour is required.
Course Syllabus CS2212 Introduction to Software Engineering 19

Group Project
Group Responsibilities
Check-in meeting with your assigned TA every other week
• Each team will be assigned a teaching assistant (TA).
• You must work with your assigned TA to find a day and time to meet every other week.
• Meetings with the TA are at most 20 minutes in length.
• These meetings should act as a sort of scrum meeting where you discuss progress your
group has made in the last two weeks, create a plan for the tasks that will be completed
during the next two weeks, and work with the TA on any issues that have arisen.
• It is also your team's responsibility to take minutes of the stand-up meetings as you
would a general group meeting.
• The week you meet with a TA will be based on your team’s assigned team number.
Course Syllabus CS2212 Introduction to Software Engineering 20

Group Project
Group Responsibilities
Meet with your assigned TA every other week
TA Check-In Meeting Schedule
• Week 1 (Jan 5 - 11): No meeting this week.
• Week 2 (Jan 12 - 18): No meeting this week.
• Week 3 (Jan 19 - 25): Odd numbered team meet with TA
• Week 4 (Jan 26 – Feb 1): Even numbered team meet with TA
• Week 5 (Feb 2 - 8): Odd numbered team meet with TA
• Week 6 (Feb 9 - 15): Even numbered team meet with TA
• Reading Week (Feb 16 – 22): No meetings this week
• Week 7 (Feb 23 – Mar 1): Odd numbered team meet with TA
• Week 8 (Mar 2 - 8): Even numbered team meet with TA
• Week 9 (Mar 9 - 15): Odd numbered team meet with TA
• Week 10 (Mar 16 - 22): Even numbered team meet with TA
• Week 11 (Mar 23 - 29): No meetings this week
• Week 12 (Mar 30 – Apr 5): No meetings this week
• Week 13 (Apr 6 – Apr 9) Acceptance testing (all teams meet with TA)
Course Syllabus CS2212 Introduction to Software Engineering 21

Group Project
Group Responsibilities
Define clear roles and expectations for your team
• Documented in team contract.
• Who will do X, who is responsible for Y, etc.
• Minimum time requirements, meeting times/length, etc.

Decide on a common development environment and tools

• Teams must decide on what tools (IDE, third party libraires, etc.) they will be using.
• Note that some specific tools will be required by the project specification.

Demonstrate the project at the end of the term

• All team members must be present for this demonstration with the TA.

• All teams must create a video the shows off their project that will be peer reviewed by other students.

Complete peer-reviews individually

Course Syllabus CS2212 Introduction to Software Engineering 22

Group Project
Tentative Project Schedule:
Submission Kritik360 Peer
Due Date Assessment Due Date
Component Weight (by 11:59PM) (by 11:59PM)
Planning Documentation 4% Jan. 23rd Jan. 30th
Requirements Documentation 8% Feb. 6th Feb. 13th
Design Documentation 9% Mar. 6th Mar. 13th
Testing Documentation & Project Demo Video 9% Apr. 2nd Apr. 9th
Final Implementation & Delivery 9% Apr. 2nd N/A

Submission Stages:
• Stage 1: Groups submit a copy of their milestone via Kritik360 by the “Group Submission Due
Date”. This is one submission for the whole group.
• Stage 2: Each individual student (not as a group) will evaluate the work of another team via the
Kritik360 platform and give a peer review of their work.
• Stage 3: Within three days after the “Kritik360 Peer Assessment Due Date” you must evaluate
the quality of feedback you received from another team.
Course Syllabus CS2212 Introduction to Software Engineering 23

Group Project
Tentative Project Schedule:
Submission Kritik360 Peer
Due Date Assessment Due Date
Component Weight (by 11:59PM) (by 11:59PM)
Planning Documentation 4% Jan. 23rd Jan. 30th
Requirements Documentation 8% Feb. 6th Feb. 13th
Design Documentation 9% Mar. 6th Mar. 13th
Testing Documentation & Project Demo Video 9% Apr. 2nd Apr. 9th
Final Implementation & Delivery 9% Apr. 2nd N/A

Individual Grade for Each Peer Reviewed Component:

• 80% based on the peer evaluation of your group’s work.
• 15% based on the quality of the peer evaluation you completed of another group’s work.
• 5% for evaluating the feedback your group was given.

Note that the Final Implementation & Delivery component will be evaluated by your team’s TA.
Course Syllabus CS2212 Introduction to Software Engineering 24

Group Project
Tentative Project Schedule:
Submission Kritik360 Peer
Due Date Assessment Due Date
Component Weight (by 11:59PM) (by 11:59PM)
Planning Documentation 4% Jan. 23rd Jan. 30th
Requirements Documentation 8% Feb. 6th Feb. 13th
Design Documentation 9% Mar. 6th Mar. 13th
Testing Documentation & Project Demo Video 9% Apr. 2nd Apr. 9th
Final Implementation & Delivery 9% Apr. 2nd N/A

Other Important Dates:

• Teams requests due by January 14th at 11:59PM.
• Team lists posted by January 16th.
• Team meetings the week of January 19th.
• Project demonstrations with TA (Acceptance Testing) will be scheduled between April 6th –
April 9th (inclusive).
Course Syllabus CS2212 Introduction to Software Engineering 25

Group Project
Late Penalty Policy:
• This course uses a late coupon system.
• Each team is given 6 late coupons for the whole term (once they are used, they
are gone forever).

• Each late coupon adds a grace period of 24 hours per ticket (up to a maximum
of 3 tickets per project component).

• No action is required by a team to use a late coupon. Simply submit late,

and the correct number of late coupons will be used.
• If insufficient late coupons remain or the component is more than 3 days late, a
zero grade will be given.
• Late coupons can only be used on the group submission (stage 1) they cannot
be used on individual work, tests, or your acceptance testing date.
Course Syllabus CS2212 Introduction to Software Engineering 26

Group Project
Appealing a Project Component Grade

If you feel that your project component was evaluated unfairly, you must take these
steps within 1 week of receiving the grade back:

1. Contact the teaching assistant assigned to your team via their email and
explain in detail why you feel your work was incorrectly evaluated.

2. If your teaching assistant agrees with your appeal, they can adjust the grade.

3. If you disagree with your teaching assistant’s determination or they fail to

respond in one week, you may escalate your appeal to the course instructor
by emailing them.
Course Syllabus CS2212 Introduction to Software Engineering 27

Group Member Evaluations

At two times during the course, you will be asked to provide evaluations of your team
members:

• This will occur at approximately halfway through the course and at the end of
the semester.

• Tentative dates: Monday February 13th and Thursday April 2nd

• Will use Kritik360 (same system and stages as project components).

• You must obtain a grade of 40% or higher on these evaluations

(combined) to pass the course.
Course Syllabus CS2212 Introduction to Software Engineering 28

A Quick Word on Academic Dishonesty

• Groups are encouraged to discuss the project together and ask questions about the
project on the course forums.

• No code or documentation should be shared between groups. Only post code

fragments (small bits of code and not whole files) when asking for help publicly.

• If you use code or documentation from another source (e.g. something you found online
or generated with a tool) it must be clearly indicated and correctly citied.

• Only you and your group members can work on your project. No tutors, friends who
are not group members, outside services, etc.

• Can not use pre-existing work from other courses, past years, past attempts at this
course, etc. in the project without written permission from the course instructor.

• There are restrictions on generative AI use in this course, please see the course
syllabus for a full breakdown.
Course Syllabus CS2212 Introduction to Software Engineering 29

Participation
How Will It Work?
• A points system will be used to track participation.
• Points can be earned in a number of ways, both inside and outside of class.
• The number of participation points you have at the end of the course will determine your
participation grade.
• Each week will have at least 100 points from in-class activities.
• Points can also be earned by:
• Attending check-in meetings with your TA
• Completing the weekly participation quiz on OWL (with a grade of at least 80%)
• Watching lecture videos on OWL (must make sure the page is marked as completed)
• Certain types of forum posts
• See the course syllabus for a complete list of ways to earn participation points.
Course Syllabus CS2212 Introduction to Software Engineering 30

Participation
How Will It be Graded?
Level Grade (out of 10%) Minimum Participation Points
Required
0 0% 0
1 1% 300
2 2% 375
3 3% 490
4 4% 610
5 5% 750
6 6% 960
7 7% 1200
8 8% 1480
9 9% 1850
10 10% 2225

No fraction of percentages will be granted for participation. You must make it to the next level
to increase your participation grade. For example, 955 points would still be a level 5, worth 5%.
Course Syllabus CS2212 Introduction to Software Engineering 31

Participation
How Will It be Graded?
Level Grade (out of 10%) Minimum Participation Points
Required
0 0% 0
1 1% 300
2 2% 375
3 3% 490
4 4% 610
5 5% 750
6 6% 960
7 7% 1200
8 8% 1480
9 9% 1850
10 10% 2225
Example:
If you obtain 1150 points, you would bet at level 6 and receive a grade of 6% (out of 10) for your
participation grade. You would need at least 1200 points to move up to level 7.
Course Syllabus CS2212 Introduction to Software Engineering 32

Participation
Keep in mind that:

• There are more points available then needed to obtain a full participation
grade.

• You can make up for missed lectures/quizzes/etc. by doing other activities

that earn points.

• Your current points will not be calculated or shown live. They will only be
calculated at the end of the term.

• It is up to you to keep track if you want a current total before the end of
the term.
Course Syllabus CS2212 Introduction to Software Engineering 33

Midterms OR Final Exam

You are given the choice of either:

1) Writing 2 midterms, worth 22.5% each during the term.

2) Writing a final exam worth 45% during the final exam period.
3) Some combination of 1 and 2:
• If you write all three, your test grade will be the either the final exam or
midterms, whichever is higher.

• If you write one midterm and the final exam, the final exam will be worth 22.5%
and the midterm 22.5% or all the weight will be place on the final exam
(whichever is higher).
Course Syllabus CS2212 Introduction to Software Engineering 34

Midterms
• Will be conducted in-person.
• The length of each midterm is 2 hours.
• Closed book, no notes, references, electronic devices, etc.
• Content may cover any course material covered (in-class, in videos, or
the project) up until that point in the course. More exact content will be
announced before the quiz.
• Tentative midterm dates (subject to change):

Exam Date
Midterm 1 Saturday February 7th
Midterm 2 Friday March 20th
Course Syllabus CS2212 Introduction to Software Engineering 35

Final Exam
• You are not required to write the final exam if you wrote both
midterms, but doing so can only help your grade.
• During final exam period.
• 3 hours, closed book, comprehensive.
Course Syllabus CS2212 Introduction to Software Engineering 36

Weekly Time Requirements

• In-Person Lectures: 2 Hours a week.
• Videos: Most weeks will have a few videos to watch. Aiming for no
more than 2 hours on average a given week.
• Weekly Group Meeting: At least one hour per week.
• TA Check-in Meeting: 20 minutes, every other week.
• Readings: 2 chapters on average.
• Participation Quiz: 1 short quiz for participation points per week.
• Project Work: Minimal work for first weeks, growing to significant near
end of term (plan for this!)
 CS2212 Introduction to Software Engineering

CS2212
Introduction to
Software Engineering

Week 1 In-Class Activity

© Copyright Daniel Servos. Do not share or post to external sites. For Personal Use Only.
Some images and content from Software Engineering: A Practitioner's Approach 9th Edition By Roger Pressman and Bruce Maxim
Course Syllabus CS2212 Introduction to Software Engineering 38

Week 1 In-Class Activity

To get to know each other and meet other students that could be in
your group we will do an “ice breaker” activity:
1. Navigate to our course site and click this link:
Course Syllabus CS2212 Introduction to Software Engineering 39

Week 1 In-Class Activity

To get to know each other and meet other students that could be in
your group we will do an “ice breaker” activity:
2. With the persons sitting next to you fill out the form (each
person should fill in their own form) and discuss these topics:
• What year and program are you in?
• Why are you taking this course?
• One non-school thing or hobby you are into lately.
• If you already have a team in mind or if you are looking for a team.
• The "project vibe" you prefer (examples: start early, steady weekly
work, last-minute sprint, lots of meetings, mostly async).
Course Syllabus CS2212 Introduction to Software Engineering 40

Week 1 In-Class Activity

To get to know each other and meet other students that could be in
your group we will do an “ice breaker” activity:
3. Make sure you fill in the form on Gradescope and submit your
answers before the end of class.

If you are having any technical issues or don’t have a laptop/phone

see me at the front before you leave the classroom.
 CS2212 Introduction to Software Engineering

CS2212
Introduction to
Software Engineering

For Next Week

© Copyright Daniel Servos. Do not share or post to external sites. For Personal Use Only.
Some images and content from Software Engineering: A Practitioner's Approach 9th Edition By Roger Pressman and Bruce Maxim
Course Syllabus CS2212 Introduction to Software Engineering Group Work Code: 42

For Next Week How to sign up for a team:

Before text Tuesday:
• Watch the week 1 videos.
• Read chapters 1 and 2.
• Complete the week 1
participation quiz.
• Try to find a team and sign up
for a team on OWL Brightspace.
• Come to class with ready to Remember:
work on an activity (bring a laptop No class on Friday!
if possible).