Syllabus for CSCI 152 Visual Basic

Dr. Wildenberg

W-113 585-385-8179

email gwildenberg@sjfc.edu

Home number: 461-3495 (Please use this number if talking to me can save you a lot of grief. Otherwise, please respect my privacy).

Note that my web page may be reached through the sjfc intranet page.

Office hours: See web page: http://sun1.sjfc.edu/~wildenbe/ . If you would like to see me at other times, please make an appointment.

Main goals:

1. Learn basics of programming.

2. Learn the “event driven” programming paradigm.

3. Learn what “Visual programming” is and how it is used.

4. Learn the Visual Basic programming language.

Prerequisites: You need to be comfortable with using Windows. Prior programming experience is NOT necessary for this course. Some acquaintance with the Windows operating system IS essential. However, I will try to answer any questions about Windows that comes up but may sometimes ask you to ask me privately rather than in class.

Text: Introduction to Programming Using Visual Basic 6.0 Update Edition Fourth Edition by David Schneider

ISBN-10: 0131427075 ISBN-13: 978-0131427075

Format: A mix of lecture and lab. Sometimes I talk and you listen and ask questions. Sometimes you try things.

Class Behavior: Here are some do’s and don’ts. Do come to every class. Don’t EVER use the computers in class for anything not directly related to what we are doing. In particular: no web browsing (except for class related topics and at appropriate times), no instant messaging or chat rooms, no reading of your email. I consider all these distracting to others around you and detrimental to the learning process. Do pay close attention to all that I say or project. Do feel free to ask questions – if I don’t know the answer, I will get it for you if I can. Do contact the class representative if you want to bring any general matter to my attention. Do shut off your cell phones and pagers. Don’t answer cell phones or any other devices in class. Do laugh at my jokes (if you feel like it. Do have fun in class, in a serious way – by that I mean that learning is exciting.

First day: Elect a class representative. Pick dates for two exams.

Attendance: Regular attendance is expected. Missing more than 2 days (without excuse) may result in an F. If you have more than two absences, FOR ANY REASON, we will need to discuss your status in the class. (Normally I try to work with anyone who must be out for a very good reason but note that making up the work and getting the class notes is your responsibility. I may require notes from a physician if you claim medical problems.)

Grading: This is based on the following factors: Programs, quizzes, labs, class participation.

Programs and Labs: These come in two groups.

You will often have to write and run and test and print a short program or two during the class. Sometimes these can be completed during the class period -- sometimes you will need to complete them outside of class.

In addition to the in class work, there will be some assignments which need to be done primarily outside of class.

Class participation: This includes such things as: answering the questions that I or others toss out, asking questions, etc. This is a relatively informal item but I often get a feel for who is getting it from this sort of thing.

Quizzes: There will be quizzes (short assessments) and exams (longer assessments) at times to be decided today.

For Spring 2007, by class vote, there will be exams on Feb 13 and Mar 20.

Grading philosophy:

A student who receives a grade is one that displays the qualities described below.

A – Can analyse and solve almost all programming problems. Hands in assignments on time. Programs handed in are well documented and well tested. Programs show good understanding and application of programming principles. Does well on exams.

B – Can analyse and solve many programming problems. Usually completes assignments on time. Occasionally fails to document or test properly. Often uses good programming principles. Usually finishes labs on time. Does fairly well on exams.

C – Can solve very routine programming problems. Has some idea of programming principles. Often can’t complete labs quickly but gets them done. Passes the exams. Often fails to test or document properly.

D, F – Can not solve even routine programming problems. Doesn’t really understand OOP. Seldom completes a lab without lots of help. from myself and/or other students. Does not display much knowledge in exams.

Disabilities:

Students with disabilities may be interested in the colleges policy:

In compliance with St. John Fisher College policy and applicable laws, appropriate academic accommodations are available to you if you are a student with a disability. All requests for accommodations must be supported by appropriate documentation/diagnosis and determined reasonable by St. John Fisher College. Students with documented disabilities (physical, learning, psychological) who may need academic accommodation are advised to make an appointment with the Coordinator of Services in the Student Development Center, K211. Late notification will delay requested accommodations.