CS211

 

CS211 is my QBasic programming course.

Here is the syllabus:

There is more value in initiative than virtually anything else.

Franklin Pierce College

Computer Science

 

 

Syllabus

Peter D. Hipson

CS211 Introduction to Programming

Office hours: Tues & Thurs late mornings and by appointment

Spring, 1999; 3 credits

Tuesday/Thursday

 15:05 - 16:20

phone: 899-1027

Email: phipson@acm.org

Office: Marcucella MH-130

 

Overview:
This is the introductory course into computer programming using the BASIC language. The version of BASIC being taught is called QBASIC, (short for Quick BASIC), though at the end of the course work will be done with Microsoft’s Visual Basic programming tools as well.

BASIC is probably the most commonly known computer programming languages. Many major applications are written using Visual BASIC. As well, each of the products that make up the Microsoft Office Suite (Word, Excel, and Access) include a version of BASIC called VBA (Visual BASIC for Applications) Note: CS211 must be completed with a grade of C+ or better before other programming courses may be taken

 

Outcomes:
- Working knowledge of programming in BASIC;
- The ability to used Microsoft Windows 95, a DOS Command Prompt, and QBASIC;
- Skills in developing programs, structured programming techniques, and problem solving techniques;
- An understanding of interpreters, compilers, and editors;
- Improved computer usage skills.

 

Methodology:
We will always meet in the lab, you will always be at the machines, generally working along with the course instructor. Much of our time will be spent discussing the class topic for the day, showing techniques by example. I will be putting some concepts, etc., on the blackboard, and you will be taking some notes. We will work very closely with the textbook, so you must always have your copy with you in class. You will have to spend time outside of class reading the text, thinking through problems, and working on your projects and assignments.

Project Assignments:
You will be working on projects/assignments in this course. This effort is very important—it will account for a substantial portion of your grade. You will work on these assignments partly in class in a lab setting; but you must also work on them out of class on your own. At least 75-90% of the time you spend on projects will have to be spent out of class. Please be aware of this and plan your semester accordingly.
Sometimes the project assignments will take the form of quick assignments and sometimes they will take the form of ‘homework’ to be handed in and graded. Assignments will usually be quickly graded at the machine (with a system of +, check, - (zap), and absent), whereas "homework handed in" means that you will print out your project and it will be graded according to the usual scheme of A, B, etc. Late homework will never be accepted, under any circumstances
Reading Assignments:
You cannot just bang away at the machine and expect it to work. You have to read about programming as well as doing it, and it is a very good idea to read about programming away from the machine, before and after trying actually to do it. Reading assignments are given below, by chapter number, and other reading assignments will be announced in class; they should all be finished before the completion date given. Care has been taken to assign only those sections of the approximately 600-page textbook that you really need to read - so really read them! Your knowledge will be assumed.

Attendance:
In the most important sense, all absences, for whatever reason, are equal: you have missed valuable course material, which is always difficult to make up. If you do miss class, for whatever reason, making up the work is your responsibility. All absences, with rare exceptions, will be recorded. It is your responsibility to sign in at the beginning of the class. A phone call explaining why you are absent will not change this. Most everyone has a problem or two during the semester that causes absence. Therefore, avoid frivolous reasons for absences, because real reasons will be coming along.
It is clearly very important for you to come to class. An excessive number of absences will result in lowering your final grade. If your number of absences becomes serious enough, you will be given warning in writing, and if the problem persists, you will be withdrawn from the course with a grade of 'WF' (withdraw fail.)
No requests for withdraw fail will be allowed after December 9.

Final Exam:
You are obligated to take the final exam at the specified time. Exceptions to this rule will be very rare; they will usually be given only to students who have done exceptionally well, and each will be granted on a case-by-case basis, precipitating no 'you-do-it-for-one-you-do-it-for-all' avalanche.
Best idea - put the exam dates on your calendar now.


Final Grade:
Your final grade is based on homework and assignments (30%), quizzes (30%), the final project & and final exam (30%), and attendance, participation, etc. (10%).

Prerequisite: CS101 with a C or better.

Text: QBASIC with an Introduction to Visual Basic 5.0, David I Schneider, Prentice Hall, 1999 (Fourth Edition).

Comment: This book contains many questions and projects at the end of each chapter, working on these questions and projects will enhance your performance in this class.

Classes Tuesday/Thursday

Day

Date

Topic

Reading assignment (chapter)

Tues.

Sept.  7

Introduction to programming

1

Thurs.

Sept.  9

Problem Solving

2

Tues.

Sept. 14

Problem Solving

2

Thurs.

Sept. 16

Fundamentals of programming in QBASIC

3

Tues.

Sept. 21

Fundamentals of programming in QBASIC

3

Thurs.

Sept. 23

Procedures

4

Tues.

Sept. 28

Procedures

4

Thurs.

Sept. 30

Decisions

5

Tues.

Oct.   5

Decisions

5

Thurs.

Oct.   7

Review

6

Tues.

Oct.  12

Premature Mid-term exam

6

Thurs.

Oct.  14

Recovery from Mid-term (no class)

7

Tues.

Oct.  19

Repetition

7

Thurs.

Oct.  21

Arrays

 

Tues.

Oct.  26

Arrays

 

Thurs.

Oct.  28

Sequential files

8

Tues.

Nov.   2

Sequential files

8

Thurs.

Nov.   4

Random access files

9

Tues.

Nov.   9

Random access files

9

Thurs.

Nov.  11

Graphical display

10

Tues.

Nov.  16

Graphical display

10

Thurs.

Nov.  18

Random Numbers

11

Tues.

Nov.  23

Random numbers

11

Tues.

Dec.  30

Visual Basic

12

Thurs.

Dec.   2

Visual Basic

12

Tues.

Dec.   9

Windows Programming

 

Thurs.

Dec.  14

Windows Programming

 

Tues.

Dec.  16

Review

 

 

Dec. 

Final Exam – Date TBA

 

* Complete reading assignments before the class!

Sat., Sun., Mon., Tues., Wed. Dec. 18 - 22 - Final exams


If you need course adaptations or accommodations because of a disability, please make an appointment to see me as soon as possible. If possible, requests for accommodations should be made through Academic Services at least one week prior to when you will need them.

The above schedule and procedures are subject to change in the event of extenuating circumstances.

The version of this syllabus that appears on the Internet is the final word.

Plagiarism… is the unauthorized use by you of the ideas or works of another. This includes copying from others without their permission or consent, using other’s work without crediting the source, or submitting work that is not your original work. This applies for assignments, projects and exams.

Cheating… including plagiarism, and other unethical acts, will not be condoned.