Mondays

Course Description:

Introduction to the concepts and techniques required to develop complex software systems and manage software projects. Emphasis on object-oriented methodologies and modeling via UML.

Prerequisite:

CS 240.

Grading:

The course grade will be based upon performance on two exams, several projects, and five homework assignments. The weighting of these factors will be as follows:

Five 20-Point Homework Assignments Each homework assignment will probe into the topics discussed in lecture and the texts. Your solutions must be word-processed, grammatically correct, and submitted on your dropbox by the designated deadline. You may collaborate with others to develop responses, but you must cite who assists you, and your responses must be in your own words..	100 points
Three 50-Point Individual Projects On these software development assignments, you are expected to work alone, with only the instructor seeing your work.	150 points
Two 100-Point Group Projects & One 200-Point Group Project On these software development assignments, you will be assigned a team of classmates with which to work, with only the instructor and your team seeing your work.	400 points
Two 100-Point Exams The exams, administered during class, closed book and closed notes, will consist primarily of essay questions, with some identification/short-answer items and perhaps a few multiple-choice items.	200 points
One 150-Point Comprehensive Final Exam The final exam will be administered as scheduled (in accordance with University policy). The exam will be structured like the other exams.	150 points
Total Possible Points	1000 points

Class Policies

Grading Scale

Academic Misconduct

Attendance

Late Assignments

900-1000	A
800-899	B
700-799	C
600-699	D
0-599	E

Collaboration is encouraged on the homework assignments, but you must cite any student, instructor, tutor, or resource that assists you. In any case, you are expected to write your own responses (i.e., no direct quotes or paraphrasing) in order to demonstrate your understanding of the concepts being explored.

Attendance is strongly encouraged, but not required.

The material covered during lectures and class discussions shall form the basis for the exams and the projects.

There will be no work accepted late and no unexcused absences from exams. No makeup exams shall be given for unexcused absences. Exceptions are granted only for documented medical problems.

Occasionally, students find that a couple of major exams fall on the same date. To reschedule an exam under such circumstances, arrangements must be made with the instructor at least one week in advance.

Teamwork

Teamwork is required on all group projects, with credit assigned according to individual contributions. Continued non-participation in group projects will result in removal from a team and no credit assigned to the removed individual for all remaining group projects.

	Tentative Syllabus
Tuesdays					Thursdays
Date		Topic	Reading	Due	Date	Topic	Reading	Due
1/15		Software Systems	Tsui Ch. 1-2		1/17	Software Engineering Intro	Tsui Ch. 3
1/22		Software Process Models	Tsui Ch. 4		1/23	Agile Development	Tsui Ch. 5
1/29		UML Introduction	Fowler Ch. 1-2	HW1	1/31	UML Class Diagrams	Fowler Ch. 3-4	IP1 (PSP0)
2/5		UML Use Cases	Fowler Ch. 5-9		2/7	UML Activity Diagrams	Fowler Ch. 10-11
2/12		PSP Intro	Humphrey Ch. 1-2	HW2	2/14	PSP Measuring & Estimating	Humphrey Ch. 3-5	IP2 (PSP0)
2/19		PSP Planning	Humphrey Ch. 6-7		2/21	Software Requirements	Tsui Ch. 6
2/26		EXAM #1 (Tsui 1-6; Fowler 1-11; Humphrey 1-7)