Computer  Science I (COSC 071) 
 (Fall 2009)
 


 PROFESSORS:


Dr. Mahendran Velauthapillai
mahe@cs.georgetown.edu
(202) 687-5936 (Office)  
Department of Computer Science          
331 St. Mary's Hall

                                  

OFFICE HOURS:

 TR 1.30 - 2.30 PM or by appointment.


TEACHING ASSISTANTS:
   




NameOffice Hours Location   Email




Matt Dzaman 2:30-4:15 T, 5:30-7 R STM 347  mcd49@georgetown.edu




Nick  Williams 2-4 M, 6:30-8:30 W  STM 330  njw22@georgetown.edu




Jesse Muller 11-1 Mon, Sunday   STM 330  jessejmueller@gmail.com








NOTES:


 Sep 3, 2009:   readme   zero  one   two   three   four  five  six   seven 

 Sep 8, 2009:   readme   zero  one  two  three  four five 

 Sep 10, 2009:   readme   one  two  three  four  five   elevator1  elevator2  richter  tax 

 Sep 15, 2009:   readme   zero  one  two  three  four five six 

 Sep 17, 2009:   readme   zero  one  two  three  four five six 

 Sep 22, 2009:   readme  

 Sep 24, 2009:   readme   zero  one  two  three  four 

 Sep 29, 2009:   readme  

 Oct 6 , 2009:   readme  zero one two three 

 Oct 8 , 2009:   readme  zero one two three four  five 

 Oct 13 , 2009:   readme  zero one two three four  five 
 Oct 15 , 2009:   readme  zero one  

 Oct 20 , 2009:   readme   one two three four  five six seven eight  nine  
 Oct 22 , 2009:   readme   one two three four  five six seven   
 Oct 27 , 2009:   readme  
 Oct 29 , 2009:   readme   one two three four  five six seven   eight   
 Nov 03 , 2009:   readme  zero one  



TEXT:




   

      
 
      C++ for Everyone  by Cay S. Horstmann
   

   

      Publisher Wiley, John & Sons 
   

   

      ISBN:   978-0-470-38329-2 
   





COURSE REQUIREMENTS:

 2 Mid Terms,  Final and 15 programming projects (50%)



IMPORTANT DATES:

   Mid-Term 1: Oct 1  (R)  10% of your final grade (open books open notes) 
    
   Mid-Term 2: Nov 5  (R)  15% of your final grade (open books open notes) 

   Final:      Dec 19 Sat 4-6PM    25% of your final grade(open books open notes)







ProjsGiven Due   Points   Problem           






 


0 09/03  09/08 0 
 Install Dev C++ (goto www.download.com and search for dev C++)
and test it by running some C++ examples from your text books.
You don't have to turn anything to us. 



 1  09/08  09/10 10 
 Write a program to print out your favorite poem. Make sure each line is numbered.




 2  09/10  09/15 10  
Hw2      sol 




 3  09/15  09/17 10    
Hw3-1   sol      Hw3-2 
 sol  




 4  09/17  09/22 10  
Hw4-1   eggs    Hw4-2 
 beer 





 5  09/22  09/24 10    Hw5  
 sol  




 6  09/24  09/29 10   Hw6  
 sol  




 7  09/29  10/06 10   Hw7  
 sol  




 8  10/06  10/13 20  Hw8  
 sol  




 9  10/13  10/20 20  Hw9  
 sol  




 10  10/20  10/27 20   Hw10-1  
     sol  
 Hw10-2  
    sol  




 11  10/27  11/03 20   Hw11-1  
 Hw11-2   




 12  11/03  11/12 30   Hw12   




 13  11/12  11/19 30 




 14  11/19  12/01 40 




 15  12/01  12/08 40 







COURSE POLICY:

1. All  programming projects should be turned in 
   before the beginning of the class. You should
   email the appropriate program and the 

   It is your responsibility to always keep a backup.

2. Late projects will  not  be accepted. 
   If you cannot make it to class its your responsibility 
   to turn in the project prior to the due date.  No credit 
   will be given to programs that do not compile. If you 
   have not finished the whole project, 
   hand in  the portions which you have demonstrated  
   do work correctly for partial credit. Include a 
   note explaining what you have done.

3. To receive full credit for your program, you must strictly 
   follow the programming style outlined in the text.

4. Makeups and extensions will be given only for medical reasons.


                                   
COURSE ETHICS:

1. All course work has to be done individually. 
   Any person cheating will be reported to the 
   dean and is liable to fail the course. 
   Both cheater and the "cheatee" are considered 
   guilty and there will be no exceptions.

2. You may discuss the material presented in class 
   or the book with your classmates. You should not 
   discuss the solution of any programming projects. 
   You may discuss specific syntax errors.

3. Working together on the design of a program or 
   on coding any part of it is  not permitted.

4. When you seek help from  me in debugging a program, 
   you may encounter specific suggestions on how to 
   fix a program. You should understand the purpose 
   and operation of each statement, and every statement 
   should be your own work. Don't add statements into your 
   program because someone said: "here try his..."  
   Experience says that this is a major source of error.