Information and Computer Science 52:
Introduction to Software Engineering

Fall Quarter, 2009

LectureDiscussion
Location: ICS 174
MWF 1:00 - 1:50
Course code: 36620
Location: SSL 228
MWF 2:00-2:50
Course code: 36621

Instructors

Add, Drop, and Grade Policies

Add 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.

Flu

Excepts from a Sept. 17, 2009, email from Michael Gottfredson, Executive Vice Chancellor and Provost:
The H1N1 flu is quite contagious and its symptoms resemble those of the seasonal flu. The health of the members of the University community is our number one concern, and we are also concerned that widespread illness could disrupt the academic activity of the University.

Communication with students at the beginning of class on H1N1 and seasonal flu is critical. If any student feels even mildly sick with flu-like symptoms, they should stay home and if appropriate, seek medical attention. Students should return to work and school only after fever and symptoms have abated for 24 hours. It is recommended that faculty allow flexibility in class attendance policies so that students who do the right thing by staying away from campus with flu symptoms are not penalized.

I encourage you to have conversations with your colleagues and students during the first week of classes and outline in writing how instruction can continue with students who cannot attend class and how students can make up missed classes, assignments, and exams if they become ill. Also, please consider an alternate plan if you yourself become ill.

If you are ill with the flu or any other ailment, please contact me by email as soon as possible.

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
0 Sep. 25 Introduction (no disc. 9/25) Library out  
1 Sep. 28
Sep. 30
Oct. 2 		Software Engineering
Principles and Processes
'' 		Java 1.6 & Lib
''
(no disc. 10/2) 		 
 
 
1, 2 (skim), 3
2 Oct. 5
Oct. 7
Oct. 9 		Principles and Processes
''
'' 		Interviews
''
'' 		Requirements out
Library due
  		6, 9
Requirements example
3 Oct. 12
Oct. 14
Oct. 16 		Requirements Engineering
''
'' 		Interviews
''
'' 		Requirements draft due
 
  		11, 12
4 Oct. 19
Oct. 21
Oct. 23 		Architecture & Design
''
Midterm #1 		  Requirements due
Design out
  		Scientific American article
5 Oct. 26
Oct. 28
Oct. 30 		Module Design
''
'' 		Design
Design
  		 
 
Design draft due 		10
6 Nov. 2
Nov. 4
Nov. 6 		Module Design
''
'' 		   
Design due (11/6)
Implementation out (11/6) 		 
7 Nov. 9
Nov. 11
Nov. 13 		QA & Testing
(No lecture)
QA & Testing
  		   
8 Nov. 16
Nov. 18
Nov. 20 		QA & Testing
''
'' 		 
 
  		 
 
Implementation due 		13
9 Nov. 23
Nov. 25
Nov. 27 		Midterm #2
(No lecture)
(No lecture) 		Lecture
 
  		Testing out
 
  		Article (TBA)
10 Nov. 30
Dec. 2
Dec. 11 		Special Topics & Review
''
'' 		 
 
  		 
Testing due
  		 
F Dec. 9 Final Exam, 1:30-3:30 pm
Subject to change! 



 Assignments and Grading



The two Midterms together count for 25% of the course grade;
the midterm with a lower score will count 10% and
the midterm with a higher score will count 15%.
The Final Exam will be 25% of the course grade.
The Homeworks and Project are 50% of the course grade.
The homeworks count as follows:







 Homework				 Weight

 A. Library Maintenance 3%

 1. Requirements 15%

 2. Design  12%

 3. Implementation  10%

 4. Testing 10%






Homeworks and tests are scored on a point basis, usually 0 to 100.
All homeworks must be turned in and be scored at
40 or above to receive a grade of C or better for the class.
(Turning in all the homeworks does not guarantee you a grade of C or better.)
This course requires a lot of work, and it is important that all
assignments be turned in on time.
Late work will be penalized.
All homeworks must be turned in, at the very latest, before the
end of tenth week on Friday, December 11.





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.