Contact Information

Bruce Bolden

Office Hours:  Posted on web site
Tentative:  MTWTF: 1:30--3:30

Policies and Procedures

Grading

Quizzes will normally be given every Thursday on the material covered since the last quiz. Knowledge of material presented in this class is cumulative!

The final grade will be calculated based on a weighted sum of the points accumulated in each of the categories:

The course will be graded on the basis of 90% and above is an A, 80%--89% a B, 70%--79% a C, etc.

Cheating

Cheating on exams or homework will be heavily penalized.

Computer Usage/Misuse

Misuse of computers and files is a felony in the state of Idaho! See the University of Idaho Computer Use Policy document available from Computer Services for details.

Objectives

• Unqualified personal recommendation.
• Prepare you for more advanced courses.
• Have some fun!

CS 112 Objectives

• Declaring/Using variables
• Basic Input and Output
• Loops
• Functions
• Arrays
• Structures
• Objects
• Basic Sorting and Searching

CS 113 Objectives

• Basic Software Engineering principles
• I/O (standard and file)
• String manipulation
• User defined types:

   struct

  s
• Objects (classes)
• Numbers bases used in computers
• Induction
• Recursion
• Dynamic Memory management---linked lists
• Big-O Notation (Order analysis)
• Sorting and Searching

CS 213 Objectives

• I/O (standard and file)
• String manipulation
• Dynamic Memory management
• Linked lists
• Stacks
• Queues
• Trees
• Hash Tables
• Graphs
• Sorting and Searching

Expectations

• You know the prerequisite material.
• You are willing to do the necessary work.
• You will do your own work!

CS 112 Expectations

• Basic Algebraic manipulation skills
• Willingness to learn and work

CS 113 Expectations

• All CS 112 Expectations
• Basic C++ Syntax
• Basic (primitive) data types
• Decision making (

   if(), switch

  )
• Looping constructs
• File manipulation (open, close, read/write)
• Array manipulation
• Functions (parameter passing)

CS 213 Expectations

• All CS 113 Expectations
• Basic Software Engineering principles
• Data types (primitive and user-defined)
• Functions (recursion)

Tips for Success

General

• Attend class regularly.
• Check the class web site (daily).
• If you have a question, do not wait to ask it.
• Read/Review material regularly.
• Review programs after completion.
• Organize your notes and other material for the class.

Programming Tips

• Read/Review the assignment as soon as possible.
• Think about how you might solve the problem.
• Design a solution to the problem.
• Implement your solution.
• Allow time for problems.
• Review your assignment to make sure that it satisfies the assignment.

Test Tips

• Keep up with the material as it is discussed.
• Start studying early.
• Read/Review material regularly.
• Rewrite and think about the material as necessary.
• Read all problems on the test before starting. Make sure you understand the problem before starting.
• Work as quickly as possible, without going so fast that you make careless errors.
• Review your answers.
• Relax!

General Program Components

Programs can be characterized by the following properties. (Some of them are interconnected.)

• Documentation (Internal/External)
• Messages
• Variables
• Decisions
• Loops
• Functions and Methods
• I/O (Input/Output)
• Error Checking
• User Interface

Documentation

Documentation may be broken into two categories:

1. Internal
2. External

The internal documentation of a program consists of comments intermixed with the program statements.

The external documentation associated with a program typically consists of one or more design documents (specifications) and a user manual.

Messages

Programs send messages (commands) back and forth both internally and potentially to other programs.

Variables

Strongly typed languages require all variables to be declared before they are used. The declaration specifies the type of the data that is/will be stored in the variable.

Decisions

Programs frequently need to make decisions based upon the values of one or more variables. These decisions affect the flow of control of the program.

Loops

Loops allow programs to execute some sequence of statements or instructions repeatedly.

Functions/Methods

Functions or methods allow a programmer to organize a sequence of statements into a unit that may be used many times. Functions/Methods may be thought of as means for passing messages within/between programs. The arguments given to a function typically affect the result of a function/method.

I/O (Input/Output)

I/O allows a program to process different data files, restore settings from a previous session, store results for different reports.

I/O can be done at many different levels:

• Low --- A specific address(es) on a board
• Medium --- Specific operations for reading/writing
• High --- Built-in operations

I/O can be very difficult if the programmer doesn't understand the operations provided by the language being used or the actual/desired format of a data file.

Error Checking

Error checking is necessary to keep programs from performing an operation they cannot do (e.g., divide by zero). The task of error checking/handling is difficult and relies on all the other programming components.

User Interface

The User Interface is what the user sees. The interface can be very simple (e.g., command line oriented) or a very complex GUI (Graphical User Interface). Implementing a robust UI can be a very difficult task and relies on all other programming components and knowledge of the functions/methods to create/interact with the specific environment (e.g., Macintosh, Windows, X, or Java).