COMP 480 Problem Solving with Computing


Things you should be able to explain

A list of items you should be able to explain or provide examples for. Not an exhaustive list - check for updates regularly.

You should always look through the whole list, not just the last few lines. Aside from being a great strategy for reviewing material, please note that not all changes happen in the last few lines.

Please stop by during office hours with questions, I'll be glad to try answer any questions you may have.


IDE
FAQ
source code
hardware 
peripherals
CPU
Cores
motherboard
volatile vs persistent memory
RAM
GUI
CLI command line
Diskdrive/Harddrive
Optical Storage
directory/folder/file/extension/type
bit/byte/kb/Mega-byte/Giga-byte
software
application software
system software
OS, Operating System
Programming languages
editor
edit/compile/run-cycle
algorithm
design
program
source code
compiler
executable
binary
interpreter
browser
URL
domain name
country code
HTML/CSS
DNS
IP address
positional notation
binary - base 2
bug
logic/semantic bug
syntax bug 
USB
run time bug
identifiers
variables (scope:local and global, lifetime)
key- or reserved words
data types, string, float, integer (truncation)
character, string
functions (calling, defining)
arguments/parameters for functions
Conditional execution, decision structures
short-circuit evaluation
Boolean expression
and, or, not
==, !=, <=, >=, <, >
Boolean comparison vs assignment
relational expression
compound expression
if, if-else, if-elif-else
decimal - base 10
nested if statements
while-loop
for-loop
range + lists
sentinel
infinite loops
'off-by-one' error
stack trace
API
lists (indexing/index values)
modules
files (input file, output file, end-of-file)
buffering/buffer
exception/execption handler/"thowing/catching" exceptions
Know what causes these exceptions: IndexError, NameError, IOError and how to handle them.
pixel
RGB
mutable vs immutable
slices
lists vs strings
basic list/string methods (see notes on slides)




Mail me at ansaria@franklin.edu with comments and/or questions.