Information and Computer Science 52:
Introduction to Software Engineering

Spring Quarter, 2011

LectureDiscussion
Location: ICS 174
T Th 2:00 - 3:20
Course code: 36580
Location: ICS 174
MWF 2:00 - 2:50pm
Course code: 36581

Instructors

Add, Drop, and Grade Policies

Adds and drops should be done through WebReg through the end of second week. See me if you want to take the course Pass / Not Pass.

Textbook

You are responsible for learning the Windows and Java features you need in order to complete the ICS 52 assignments. Some basic information and guidance will be provided in the lectures and in the discussion section, but be prepared to learn whatever else you need on your own.

Keeping in Touch

The web page for the course is http://www.ics.uci.edu/~frost/ics52/   . Check your email (UCInetID account) frequently; we may need to get in touch with you by email. Please feel free to send email to the course staff: put ICS 52 in the beginning of the subject line, and your name and ID in the message body.

Academic Dishonesty

Be familiar with ICS policy, as well as the UCI official policy on academic honesty. In particular, all work you hand in for ICS 52 must be your own work. A single act of cheating will result in a grade of F.

Special Accommodations

Any student who feels he or she may need an accommodation based on the impact of a disability should contact me privately to discuss his or her specific needs. Also contact the Disability Services Center at (949) 824-7494 as soon as possible to better ensure that such accommodations are implemented in a timely fashion.

Computer Health and Safety

Even though you are young and reasonably healthy, as a student in a technology field and nascent software engineer you are at risk for several computer-related health problems, particularly RSI (repetitive-strain injury). Please read and follow the good advice linked to on the school's Computer Health and Safety web page.

Schedule

Week Dates  Lecture Discussion Assignments Readings
1 March 29
March 31 		Introduction
Principles and Processes 		(no disc. 4/28)
Java 1.6 & Lib
'' 		Library out
Requirements out 		1, 2 (skim), 3
2 April 5
April 7 		Principles and Processes
'' 		Interviews
''
'' 		 
Library due 		6, 9
Requirements example
3 April 12
April 14 		Requirements Engineering
'' 		Interviews
''
'' 		Requirements draft due
 
  		11, 12
4 April 19
April 21 		Architecture & Design
'' 		  Requirements due
Design out 		Scientific American article "Command and Control"
5 April 26
April 28 		Midterm
Module Design 		 
Design
Design 		 
 
Design draft due 		10
6 May 3
May 5 		Module Design
'' 		     
7 May 10
May 12 		QA & Testing
QA & Testing
  		Design due (5/10)
Implementation out (5/12) 		 
8 May 17
May 19 		QA & Testing
'' 		 
 
  		 
 
13
9 May 24
May 26 		TBD
TBD 		 
  		Implementation due
Testing out (5/26)
 Article (TBA)
 
10 May 31
June 2 		Special Topics & Review
'' 		 
  		 
Testing due 		 
F June 9 Final Exam, 1:30-3:30 pm
Subject to change! 



 Assignments and Grading



The Midterm and Final exams together count for 40% of the
course grade,
either 15% and 25% or 20% and 20%, whichever is better
for the student.
The Homeworks and Project are 60% of the course grade.
The homeworks count as follows:







 Homework				 Weight

 A. Library Maintenance 4%

 1. Requirements 16%

 2. Design  16%

 3. Implementation  12%

 4. Testing 12%






Homeworks and tests are scored on a point basis, usually 0 to 100.
This course requires a lot of work, and it is important that all
assignments be turned in on time.
Late work will be penalized.
The penalty is approximately 1 point for every 2 hours late, up to 10 points off.
The penalty then slows down to about 5 points per day.
Homeworks turned in more than a week late will not receive more than 50 points.





Grades are assigned after all work has been scored,
based on the weighted average of points.
The equivalencies are A or A- for 90 and up,
B+, B, or B- for 80 to 89,
C+, C, or C- for 70 to 79,
D for 60 to 69, and
F for averages below 60.
These ranges may be modified slightly.