CSCI
3327
Object
Oriented Programming in Visual Basic
Fall
2009
Professor: Dr. John P. Abraham Office: ENGR 3.276
Phone: 381-3550 E-mail: jabraham@panam.edu
Email is the best way to contact me.
Email:
jabraham@utpa.edu. Tele: 381-3550
|
My
TA: Eduardo Garcia. Email: eddielgarcia@gmail.com
Text & Materials:
|
Deitel & Ditel, Visual Basic 2008
How to Program, Fourth Ed. Prentice Hall 2009. ISBN-10: |
013605305X |
References:
Richard Johnson,
Diane Zak, Microsoft Visual Basic 2008: RELOADED,
2008.
Shelly, Cashman, Qusney, Visual Basic. Net Comprehensive
Concepts and Techniques. Thomson.
Catalog Description: The visual Basic programming language and environment will be introduced with an emphasis on window-based programming and the use of objects in Visual Basic. Topics will include control structures, graphical use interface concepts, classes, methods, inheritance and visual basic interface and libraries.
Prerequisites: CSCI 1380 or Programming Experience in another language and Ability to develop algorithms.
Learning outcomes:
1. Use the .NET IDE environment
2. Declare and use various data types in the VB environment.
3. Properly use the different looping structures available in VB.
4. Write an amortization schedule or the future value of monthly investment program to demonstrate the capabilities of looping.
5. Use procedures and functions.
6. Write programs involving single and multi dimensional arrays.
7. Write object based programs showing proper use of inheritance and polymorphism.
8. Use GUIs available in VB.
9. Write multi-form programs.
10. Write multi-threaded programs
11. Write programs using sequential access and random access file structures.
12. Link VB to a database.
Visual Basic 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 1. Introduction to Visual Basic. Microsoft site.
2. Introduction to Visual Basic
Programming.
3. Introduction to Classes and Objects.
4. Control Statements: Part 1.
5. Control Statements: Part 2. EXAM I
6. Methods: A Deeper Look.
7. Arrays.
8. Introduction to LINQ and Collections
9. Classes and Objects: A Deeper Look. EXAM II
10. Object Oriented Programming
11. Graphical User Interfaces with Windows
Forms.
12. Strings, Characters and Regular
Expressions.
13. Files and Streams.
14. Extensible Markup Language (XML) and LINQ
to XML. FINAL EXAM
NOTE: Exam dates are tentative, exact dates will be announced in class !!!
Grading: 60% Exams, 40% Lab Assignments.
A = 90 or higher
B = 80 - 89
C = 70 - 79
D = 60 - 69
F = <60
Exam 1 &2 . 45%
Final Exam 25%
Assignments 20%
Attendance & notebook binder 10%
Drops must be handled by you and the admissions office; I will sign the necessary documents. But, I will not place a drop or drop pass on the final grade sheet.
Visual programming requires you to demonstrate programs in class so that others can see how you handled a particular problem. Please make sure that the programs are always available to you.
Final Note: If you have a documented disability which will make it difficult for you to carry out the work as I have outlined and/or if you need special accommodations/assistance due to the disability, please contact the Office of Services for Persons with Disabilities (OSPD), Emilia Ramirez-Schunior Hall Room 100 immediately. Appropriate arrangements/accommodations can be arranged.
Lab Project Policies:
Unless stated otherwise, all projects are individual assignments and are expected to be the student's own work. The student may seek help with identifying syntax and runtime errors. General discussions regarding the solutions are encouraged, but giving or receiving major sections of code will be considered cheating and will be dealt with on an individual basis.
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:________________________
CLASS AND SECTION:________________________ assignment #:________
DATE DUE:_____________ DATE TURNED IN:__________________
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. Psuedocode, 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.