CSCI 3328 Object
Oriented Programming in C#
Fall 2012
Instructor: Xiang Lian
Office:
ENGR 3.275
Web: http://faculty.utpa.edu/lianx/
Email: lianx@utpa.edu
Course:
CSCI 3328 Object
Oriented Programming in C#
Prerequisites:
Students are expected to be enrolled in or have
completed CSCI 1380 or Programming Experience in another language and Ability
to develop algorithms
Time: MW, 13:10pm ~ 14:25pm.
Locations: ENGR 1.272 (Monday and Wednesday)
Course Webpage: http://faculty.utpa.edu/lianx/old_courses/CSCI3328_2012fall.html
Instructor's office hour: Monday and Wednesday (9:00 am ~ 11:00 am); or by appointment
Teaching Assistant: Dave Salinas
Office: ENGR 2.240
E-mail: dsalinasez@broncs.utpa.edu
Phone: TBD
Office Hours: Tuesday
11:30 am - 1:00 pm, Thursday 9:10 am - 10 25 am, or by appointment
Textbook
Paul Deitel and Harvey
Deitel. Visual C# 2008 How to Program, 3/E. Copyright 2009
Catalog Description
The
C# programming language and .NET environment will be introduced with an
emphasis on widows-based, event driven programming and the use of objects, LINQ
and XML. Topics may include UML, generic collections, database connections,
XML, inheritance and polymorphism, exception handling, event driven
programming, concurrent programming, windows forms, files and streams,
databases, and Web Services
Learning Outcomes
1. Use the .NET IDE
environment
2. Declare and use
various data types in the C# environment.
3. Properly use the
different looping structures available in C#.
4. Write an
amortization schedule or the future value of monthly investment program to
demonstrate the capabilities of looping.
5. Develop and use
classes, objects, methods and attributes.
6. Write programs
involving single and multidimensional arrays.
7. Write object
based programs showing proper use of inheritance and polymorphism.
8. Use GUIs
available in C#.
9. Write multi-form
programs.
10. Write multi-threaded programs
11. Write programs using different types of
file structures available to C#.
12. Link C# to a database.
C Sharp programming
requires a great deal of time working with the forms and tools. Students need to spend a minimum of 2
hours a day outside the classroom working in the lab. If you do not have the time, please do
not sign up for this course.
Tentative Schedule
|
Week |
Topic |
Notes1 |
|
Week 1 (Aug. 27) |
|
|
|
Week 1 (Aug. 29) |
Assignment
1 (Due on Sept. 5) |
|
|
Week 2 (Sept. 3) |
-- |
Labor Day Holiday, No Classes |
|
Week 2 (Sept. 5) |
Assignment
2 (Due on Sept. 12) |
|
|
Week 3 (Sept. 10) |
Assignment
3 (Due on Sept. 24) |
|
|
Week 3 (Sept. 12) |
|
|
|
Week 4 (Sept. 17) |
Assignment
4 (Due on Oct. 1) |
|
|
Week 4 (Sept. 19) |
|
|
|
Week 5 (Sept. 24) |
|
|
|
Week 5 (Sept. 26) |
Q/A |
|
|
Week 6 (Oct. 1) |
EXAM I |
|
|
Week 6 (Oct. 3) |
|
|
|
Week 7 (Oct. 8) |
Assignment
5 (Due on Oct. 22) |
|
|
Week 7 (Oct. 10) |
|
|
|
Week 8 (Oct. 15) |
Assignment
6 (Due on Oct. 29) |
|
|
Week 8 (Oct. 17) |
|
|
|
Week 9 (Oct. 22) |
[ |
|
|
Week 9 (Oct. 24) |
Q/A |
|
|
Week 10 (Oct. 29) |
EXAM II |
|
|
Week 10 (Oct. 31) |
|
Assignment
8 (Due on Nov. 21) |
|
Week 11 (Nov. 5) |
|
|
|
Week 11 (Nov. 7) |
|
|
|
Week 12 (Nov. 12) |
Assignment
9 (Due on Nov. 28) |
|
|
Week 12 (Nov. 14) |
|
[Bonus] Assignment 10 (Hard deadline: Dec. 3) |
|
Week 13 (Nov. 19) |
|
|
|
Week 13 (Nov. 21) |
|
|
|
Week 14 (Nov. 26) |
Nov. 27th, last day to drop courses or
withdraw through the Office of the Registrar |
|
|
Week 14 (Nov. 28) |
|
Student Survey (Please
bring No. 2 pencil with you!) |
|
Week 15 (Dec. 3) |
|
|
|
Week 15 (Dec. 5) |
Q/A |
|
|
Week 16
(Dec. 8-14) |
Final Exam (10:15 am~12
pm, Dec. 14) |
|
1
Academic calendar: http://www.utpa.edu/calendar/academic-calendar/
NOTE: Exam dates are tentative, exact dates
will be announced in class!!!
Drops
and drop passes must be handled by you and the admission office; I will sign
the necessary documents. But, I will not place a drop or drop pass on the final
grade sheet.
Exam I & II …………………. 45%
Final Exam ………………… 25%
Assignments………………… 20%
Attendance
………………… 10%
A
= 90 or higher
B
= 80 - 89
C
= 70 - 79
D
= 60 - 69
F
= <60
GUIDELINES
FOR PROGRAMMING ASSIGNMENTS
ALL
PROGRAMS AND OTHER ASSIGNMENTS ARE DUE AT THE BEGINNING OF THE CLASS
PERIOD (5 minutes grace period).
All assignments turned in after the class begins will be considered late
(even if you come to class late).
Late
Penalty: 5 minutes late to the end
of the day - 10% penalty.
Next
class period 20%
penalty
Two
class periods 30%
penalty
One
week+1 day 50%
penalty
Will
not accept after one week and one day.
Program Identification Section.
All programs should
begin with a comment section that would include the following:
(IF YOU DO NOT INCLUDE
ANY OF THESE YOU WILL BE PENALIZED 2 POINTS).
PROGRAMMERS
NAME:_________________________________________________
STUDENT
ID:___________________________________________________________
CLASS:________________________
ASSIGNMENT #:_________________________
DATE
DUE:__________________ DATE TURNED IN:_________________________
Please upload the
*.zip file you created to the Blackboard. The subject of the assignment must
include the following information:
[CSCI 3328] [Assignment #] [Your Name Here] [Your Student ID Here]
GENERAL DESCRIPTION OF THE PROGRAM
(Program inputs, outputs and summary of what the program does).
Each function should be distinctly
identified (block it off using asterisks).
A brief description of its purpose should be given in comments.
Comments should be inserted as
necessary throughout the program to convey the algorithm of the program. All programs must be tested thoroughly
before submission. You should
include program runs to indicate
that every option of the program has been tested. Programs
turned in without any program run will receive a grade of zero.
WHAT TO TURN IN:
1. Pseudo code, structure chart,
flowchart, etc. as directed.
2. Program listing.
3. Program run.
Turn these in a folder.
GRADING:
Programs that do not run 0
points
Comments as explained above 15
points
program listing 60
points
program run 25
points
Program correction and
re-submission: up to 50% of missed points.
Attendance in the lecture is mandatory. Students are responsible for all materials covered in class, the textbook, tutorials, and homework assignments. Students are expected to attend lectures, study the text, and contribute to discussions. You need to write your name on attendance sheets throughout the course, so please attend every lecture.
No make-up exams will be given except for university sanctioned excused absences. If you miss an exam (for a good reason), it is your responsibility to contact me before the exam, or soon after the exam as possible.
The University expects a student to maintain a high standard of individual honor in his/her scholastic work. Unless otherwise required, each student is expected to complete his or her assignment individually and independently. Although study together is encouraged, the work handed in for grading by each student is expected to be his or her own. Any form of academic dishonesty will be strictly forbidden and will be punished to the maximum extent. Copying an assignment from another student in this class or obtaining a solution from some other source will lead to an automatic failure for this course and to a disciplinary action. Allowing another student to copy one's work will be treated as an act of academic dishonesty, leading to the same penalty as copying.
Students with
disabilities are encouraged to contact the Disability
Services office for a confidential discussion of their individual needs for
academic accommodation. It is the policy of the University of Texas-Pan
American to provide flexible and individualized accommodation to students with
documented disabilities that may affect their ability to fully participate in
course activities or to meet course requirements. To receive accommodation
services, students must be registered with the Disability Services office (DS),
University Center #108, 665-7005 or disabilityservices@utpa.edu.
· An ability to apply knowledge of computing and mathematics appropriate to the discipline
· An ability to analyze a problem, and identify and define the computing requirements appropriate to its solution
· An ability to design, implement, and evaluate a computer-based system, process, component, or program to meet desired needs
· Recognition of the need for and an ability to engage in continuing professional development
· An ability to use current techniques, skills, and tools necessary for computing practice
· An ability to apply mathematical foundations, algorithmic principles, and computer science theory in the modeling and design of computer-based systems in a way that demonstrates comprehension of the tradeoffs involved in design choices
· An ability to apply design and development principles in the construction of software systems of varying complexity
The instructor reserves the right to alter this syllabus as necessary.