Sonoma State University
Department of Computer Science
CS-370: Software Design and Development
Spring 2026

Course Description

Techniques of software design and development. Software lifecycle, requirements, formal specification, metrics, design, functional and structural testing, rapid prototyping, complexity, version control, and team management. Software metrics, tools for component-based software development. Team-based, agile, and scrum methodologies emphasized.

Prerequisites

Prerequisite: Grade of C- or better in CS 215 or consent of instructor.

Instructor

Robert Bruce

Learning Outcomes

Upon successful completion of this course, students will be able to:

1. Design a scalable, relational database schema in MySQL in third normal form.
2. Apply the MySQL database application programming interface in software applications.
3. Create dynamically-driven, server-side web page content in HTML5 using the Apache web server and the Common Gateway Interface.
4. Apply software engineering principles through the entire software development lifecycle from design, implementation, testing, release, and maintenance.
5. Employ effective skills and techniques to make team-based project management productive within the realm of software development.

Required Texts/Readings

• Beginning Software Engineering (Second Edition) by Rod Stephens

Course Requirements

Midterm Examination

The midterm exam will cover chapters 1, 2, 3, 4, 5, 6, 7, 8, 9, 13, 14, 15, 16, 17, 18, 19 of Stephen's Beginning Software Engineering. The exam will be closed-book. You may use one A4 sheet of paper (8.5 inches width by 11 inches length) for notes during the midterm examination. You may write notes on both sides of the sheet of paper.

Final Examination

The final exam will cover chapters 10, 11, 12, 20, and 21 of of Stephen's Beginning Software Engineering. The final exam will be comprised of open-ended questions. The exam will be closed-book. You may use one A4 sheet of paper (8.5 inches width by 11 inches length) for notes during the midterm examination. You may write notes on both sides of the sheet of paper.

Grading Information

Assignment	Percentage of Grade
In-class exercises†	15 %
Project Report†	10 %
Project Presentation†	10 %
Database Schema‡	5 %
Programming Assignment 1: Authenticate User‡	5 %
Programming Assignment 2: Display User Transactions‡	5 %
Programming Assignment 3: Bid or Sell‡	5 %
Programming Assignment 4: Display auctions‡	5 %
Midterm exam† Midterm exam study guide	20%
Final exam† Final exam study guide	20%
TOTAL	100%

† Graded as an individual
‡ Graded as a group (each member of the group gets the same grade)

Determination of Grades

Ultimately this course is graded A, B, C, D, or F. Percentage grades are rounded to the nearest whole number. For example, a grade of 92.4% will be rounded to 92% and result in a grade of "A minus". A grade of 92.5% will be rounded to 93% and result in a grade of "A".

Grading Scale

Percent range	Grade
93% to 100% inclusive	A
90% to 92% inclusive	A-
87% to 89% inclusive	B+
83% to 86% inclusive	B
80% to 82% inclusive	B-
77% to 79% inclusive	C+
73% to 76% inclusive	C
70% to 72% inclusive	C-
67% to 69% inclusive	D+
63% to 66% inclusive	D
60% to 62% inclusive	D-
Below 60%	F

Grading Policies

Late assignments

Absent extenuating circumstances (illness, family emergency), late submissions will be accepted under the late policy until the listed "Until" deadline on Canvas. The late policy is minus 10% per day, and never grows more than minus 50% markdown (as long as the assignment is submitted before the listed "Until" deadline on Canvas).

Late exams and quizzes

• There are no make-up exams.
• Official proof of emergency required for missing an exam, project, or project presentation.

Course Schedule