Please observe the continual changes in the course outline. This weeks important information will be in BLACK below. Please DO complete the reading assignments. If you have any questions, email me. The class syllabus information is listed below. Final Exams for Beginning Pascal will be held on Tuesday, September 23. Assignment information is listed below:
If you are looking
for class information for Intermediate Pascal then you must go here.
Beginning Pascal
COP 2210 Section 0007
Fall 1997
CLASS 11:30-13:10 Tues. in PC II 108 LAB 12:30-13:20 Thurs. in PH 310 TEXT Turbo Pascal, Walter J. Savich INSTRUCTOR Maysa Peterson OFFICE Room 255 Computer Science Building OffHrs 10:00-11:00 Tues., 11:00-12:00 Thurs. PHONE 823-2929 PHONE 522-8550 (home) call only in emergencies PAGER 807-5921 (10:00 - 23:00 Tues. - Thurs.) EMAIL bschnell@www.scranton.com HOMEPAGE http://www.kneehighs.com/
Beginning Pascal (COP 2210) is a 1-hour programming course using Borland Turbo Pascal 7.0. It is offered the first 5 weeks of Fall Term at the same time and room that is used for the 1-hour course Intermediate Pascal (COP 2211) in the second 5 weeks and for Advanced Pascal (COP 2212) the last 5 weeks of the Term.
There will be 4 assignments and one test in Beginning Pascal. See the Topical Outline on page 2 (the back) for the estimated topical coverage. A test makeup is highly unlikely!! An honest effort will be made to provide an opportunity for makeup, only if a student must miss it for a documented, truly unavoidable reason. The test is open book, open notes and you may use a calculator. It includes material from the lectures, the assigned text (see the parentheses in the Topical Outline) and the assignments.
The Topical Outline gives the assignment due dates. Each assignment is due on or before class begins on the given due date. You may hand them in at the start of that lab or anytime prior at the Computer Science Office, Rm. 220. Any assignment received late will automatically be docked 10 points on a 100 point scale.
For each assignment, you must turn in a clean 9x12, or slightly larger, envelope with:
1) your name,
2) your student number,
3) the assignment number
4) the class and section (COP2210 Section 07) hand printed on the outside.
Inside the envelope you must have:
1) a 3.5" floppy containing only the source file(s) for the assignment with
same identification as on the envelope (name etc.) on the floppy label.
2) two easy-to-read listings of your source code with the identification
(name etc.) on a comment line of the program.
The course grade will be:
50% (100 points) from the test scores
50% (25*2 points) from the assignment scores.
Plus (10 points)for getting assignment 2 running
It is recommended that you do NOT miss class. Programming, like mathematics, builds on previously learned material. Miss a class and you are lost! If you have to miss a class, please let me know in advance, by phone or email, and make arrangements with a fellow student to get a copy of the notes and assignments. Programming assignments are due by the specified due date regardless of circumstances, no excuses except death!
Topical Outline for COP 2210 Thurs. 8/21 introduction, read chapters 1-2 Tues. 8/26 program syntax, program style, write, read, data types Assignment 1 Thurs. 8/28 LAB PH310 Tues. 9/2 read chapter 3, chapter 7 pg. 236-253 operator precedence, if, compound, while, repeat Assignment 2 Thurs. 9/4 LAB PH310, Assignment 1 due Tues. 9/9 read chapter 4, chapter 5 pg. 158-175, chapter 12 pg. 463-489 robust input, debugger, text files, procedures, local identifiers Assignment 3 Thurs. 9/11 LAB PH310, Assignment 2 due Tues. 9/16 read chapter 6, the rest of chapter 5 and 7, Section 8.2 and 9.1 for, case, type declarations, redefined functions, arrays Assignment 4 Thurs. 9/18 LAB PH310, Assignment 3 due Tues. 9/23 TEST Thr. 9/25 LAB PH310, Final Version of Assignment 2 due Tues. 9/30 Intermediate Pascal Begins
|
Introduction to Pascal Programming COP 2210-0007 Assignment Information |
|
|
Week 1
8/26/97
8/28/97
|
Assignment 1:
Due: 9/4/97 Write an extended version of the "Hello World" program. Ask the user for his name and any other information you wish to add and have it fully displayed on the screen along with any type of text art as defined in class. Be creative with it.
For example text art |
Text Art:
-----------------------uuu-u---------u-uuu-------------------------- - \ / \ / - - Hangin' on by a | | MMMMM | | thread!!!! - - | | ' ' | | - - Overworked... | | | 0 0 | | | Underpaid... - - \ \ \ @ / / / - -------------------------------------------------------------------- -------------------------------------------------------------------- - Maysa Maria Peterson Internet Cafe - - bschnell@www.scranton.com 717-344-1969 - -------------------------------------------------------------------- |
| Week 2: Information | |
|
Week 2
9/2/97
9/4/97
|
Assignment 2: ATM
Due: 9/11/97 Create a program that will balance your checkbook.Have it ask the user for the beginning balance, then allow the user to withdraw, deposit, and get balance information. Keep the program simple and easy to read so a non-programmer can follow the code without difficulty. Analyze the problem first. Use flow charts to help you design the program flow. You will write THREE (3) versions of the same program:
2.) Use only the WHILE DO looping structure. 3.) Use only the REPEAT UNTIL looping structure. until the user indicates that he wishes to terminate the process. Observe how the different constructs facilitate or hinder logical flow? Under what conditions is one construct better than another? |
| Week 3: Information | |
|
Week 3
9/9/97
9/11/97
|
Assignment 3: Advanced ATM
Due: 9/18/97 Build on your existing work for the previousATM assignment. This time, use whatever looping structures you feel fit best. Allow the user to use the ATM until they have completed all their transactions. This system will read and write all data to a text file. In this way, it will be a "smart" system, always retaining current balance information. Use procedures to streamline your code. You will write a minimum of THREE (3) procedures for the same program:
2.) Procedure Withdrawal(account_num, amount); 3.) Procedure Deposit(account_num, amount); account number validity, transfers between accounts, etc. See how the usage of procedure makes the code of the main program body more legible and easy to follow. Don't forget to properly document each procedure as you would individual programs and looping structures. |
| Week 4: Information | |
|
Week 4
9/16/97
9/18/97
|
Assignment 4: ATM
Due: 9/25/97 REDO and Complete Assignment #2Have it running correctly. REMEMBER: Keep it simple! AND I DON'T want to see a bunch of programs that look like mine. |
|
Here is an example source of a user-defined function. OR...
Download the executable Here is an example source of a FOR loop. OR... Download the executable |
|
The test will cover everything on this site and in the class notes except: