Matthew Haas
| CSCS2320-001
| haas@corning-cc.edu
| 3 credit hours
| data@lab46.corning-cc.edu
| Fall 2008
| #data
| /var/public/data
| TTh 11:15am-12:30pm / C002
| 59183
|
Course Description:
Data and data structures, linear lists, strings, stacks, queues, linked lists, arrays, and orthogonal lists. Trees, multi-linked structure, table search, sorting techniques, storage allocation, and sequential and random file access.
(3 cr. hrs.) (Fall). Prerequisite: CSCS1320 C/C++ Programming.
Course Objectives:
Upon completion of this course, students will be able to demonstrate:
- Discuss the representation and use of primitive data types and built-in data structures,
- Describe how the data structures are allocated and used in memory,
- Describe common applications for each data structure described in class,
- Implement the user-defined data structures in a high-level language,
- Compare alternative implementations of data structures with respect to performance,
- Write programs that use each of the following data structures: arrays, records, strings, linked lists, stacks, queues, and binary trees,
- Compare and contrast the costs and benefits of dynamic and static data structure implementations,
- Choose the appropriate data structure for solving a given problem.
Required Books:
Grading Policy:
The grading policy is broken down into 4 main areas: Journal, Assessments / Projects, Attendance, and Participation.
Journal:
48%
For the duration of the course I would like for you to keep a journal which details your experiences and revelations of your journey through the course. Each week I would like for you to contribute to your journal, so that a written account can exist to tell your individual story of the course. (Great for looking back on things, and also useful if you are meeting with me).
In some cases, I may present some more structured activities to be done in the journal.
I may have some requirements regarding what form the journal may take. This depends largely upon the class and topics being covered.
In your journal I would like for you to detail your experiences in the course. Do you understand the material? Is it interesting? Anything not making sense? Any parallels to the real world? and general comments and thoughts.
Use the journal to allow me to see the course through your eyes.
Assessments / Projects:
24%
Assessments/Projects constitute the portion of your grade involving Presentations, Exams, Quizzes, Projects, Papers, Labs, Case Studies, and/or Homework assignments- the means by which I will be assessing your understanding of the material through directed explorations of various topics. Such assignments may be comprehensive to one another.
Projects, Labs, Case Studies, and Homework assignments are subject to the pertinent areas of the Submission Policy and will involve further research and exploration of some problem or topic being covered in the course. Projects may encompass a more time-consuming exploration of a topic or problem, whereas Labs will generally be a specific experiment related to the topic. Case Studies may involve the study or focus on particular concepts learned in class and on other assignments; Homework assignments will be more of a drill exercise helping to gain more familiarity with a particular topic.
Exams and Quizzes may also be given during the semester, depending on material covered and preference. Exams will focus on various concepts learned and will generally be essay-based (or rely on a detailed explanation of some process).
There may also exist opportunities for extra credit to be accumulated during the semester. These opportunities will include optional points on labs and case studies that will allow for more in-depth study of a particular topic that goes beyond the general scope of the course.
Such Assessments/Projects as assigned must be well organized (ie easy to read) and contain enough of a written description so I can see the "you" in your responses. Generally, developing your own format and following the guidelines laid out in the Submission Policy will be more than adequate.
Note that I am not interested in "English teacher approved" essays- in some courses and settings that is more important. For this course, I want you to be able to effectively convey your thoughts in words- a crucial ability that can later be applied to "proper English essays".
You can never write too much in my class.
Attendance:
16%
Attendance constitutes a portion of your grade. There are 16 weeks in the entire semester. Dividing the grading percentage by the number of weeks in the class, you will see how much you are able to accumulate each week, in a positive manner towards your grade; or, conversely, how much you can lose should you decide not to attend.
During each class, I will endeavor to pass around an attendance sheet, or deploy some form of attendance-taking mechanism, in which everyone in attendance that day needs to sign or acknowledge so I have that as a record. If you come to class on time each day, and stay throughout the class, you can consider this part of your grade "in the bag".
To calculate the attendance portion of your grade, I will take that week's portion of the grade and divide it by how many class meetings we have. So if you satisfy the above requirements, you will accumulate the full value for the week.
Participation:
12%
Class participation will also play a vital role during the course.
The participation component of your grade deals with how active you are in the class. Do you contribute to class discussions? Pull your weight in group projects? Ask questions? Respond to questions? Turn in work on time? Contribute to the class wiki? Are you a positive addition to the class?
Participation is like the "I care" component of your grade. If you care enough to learn and help enhance the experience, you will have no trouble here. However, if you are disruptive or are not putting forth effort, then it will be duly reflected.
This isn't a "kiss up to the teacher" grade. I don't want people bending over backwards to please me. I want to see people learning and asking questions and growing, not agreeing with everything I say. Sometimes I will specifically ask questions or say things for the sole purpose of getting individual perspectives.
Participation is the contribution of YOU to the overall class, in a positive and harmonious manner to the overall group :)
Submission Policy:
The following guidelines should be used whenever submitting an assignment for this class. If an assignment is submitted that does not conform to these criteria, I reserve the right to deduct points off the assignment. Any exceptions to this policy will be noted.
1 Unless otherwise specified, assignments can be submitted via e-mail, in electronic format, or on paper.
I also accept assignment submissions via singing telegram, airplane banner, crop circles, creative dance, etc. so long that I get to witness such things, and receive something which lets me look back on it later (photos, video, transcription on paper, etc.). Chances are such creative submissions will gain you some bonus points.
In cases where there are multiple sections of the class, be sure to know your particular instructor's e-mail address and section number. Be sure to include all the associated and requested files and data.
Please do NOT submit assignments electronically to me that are in WordPerfect or Microsoft Works formats. I cannot read either of them. If you have and use these programs, please print out your work to hand in.
2 Be sure to include the following information on your assignment submission:
- Name,
- Course and Section,
- Due Date,
- Assignment # and description,
- Short abstract describing the purpose of your program / assignment.
Presentation of this information in a clear and organized fashion will make your assignment all the easier to read. You may come up with your own format for the display of this information.
Any e-mail submissions should have an appropriate subject line. Please use subjects on all e-mails. This is also very important.
Leaving off the subject line is like sending a letter without putting a stamp on it-- it causes someone extra work. And that someone would be me. So don't do it. Please please please use informative subject lines!
3 For any provided questions: identify each question or selection you are answering by listing or paraphrasing the original question.
Do not just give me an answer.
This is important. I mean it. You don't know how frustrating it is to get an assignment that just has the answers on it. It takes so much longer to grade.
I reserve the right to deduct points if you don't do this.
4 Keep your programs and assignments organized and easy to read.
Use a uniform writing style. Messy or unorganized submissions will have points deducted. Think to yourself: does it look good? Would I want to read this? Take pride in your work.
These assignments are not just for me to read and grade- you may wish to incorporate them into a portfolio for use in the future. Making an investment now could pay off later!
5 Turn in assignments on time.
Late assignments will be subject to an appropriate penalty. Circumstances vary, see the Late Policy for details.
If you have submitted an assignment and realized you left something out or can improve upon it: go for it!
I accept resubmissions on assignments, so long as I haven't already graded them.
6 If you encounter an error while performing some assignment (and the directions do not indicate you should be receiving an error), chances are you made a typo. Consult the class mailing list or send me an e-mail.
Assignments containing answers based on the error are subject to points being deducted.
7 Be sure to keep a backup copy of all assignments submitted in the event something is lost in transmission.
It is your responsibility to be able to send another copy of your assignment should the original be lost.
8 Use your own judgment. The world today is increasingly filled with rules and policies dictating what you can and cannot do. I am not about to go and list all the specifics and restrictions regarding assignment submission.
You are here to learn and to grow, and I want to allow you a certain amount of flexibility in that process. Spending all your time formatting an assignment to my specifications isn't my idea of learning. Incorporate these guidelines into your general style, if you miss the mark I'll let you know. But focus more on learning and understanding than worrying about dotting every 'i' or crossing every 't'. There's enough of that elsewhere in the world.
|
Attendance Policy:
Attendance plays an important part in one's educational journey each semester. Missing class deprives you of essential knowledge and hinders understanding towards your eventual mastering of a topic.
Because we are all here to learn (and if learning isn't a priority, I highly suggest you think about making it such), and believe it or not- learning isn't just about one person, but the entire group. So it is important to be present in order to positively contribute to the learning experience.
I also reserve the right to drop students from the course due to excessive absences.
Late Policy:
Sometimes, even though we try our hardest to get everything in on time, the spurious Murphy's Law will make an appearance. Your dog ate your network cable, a burst of cosmic rays damaged your RAM precisely where your work was located... the list goes on.
If due work is not submitted by its respective due date, and no advance attempt has been made to communicate with me, the assignment may be invalidated of any value.
Bottom line.. if something is going to be late: let me know. It happens, just don't make a habit of it. Communication is key.
Network Outages:
In the event that a significant network or computer outage occurs on a network under CCC jurisdiction, an appropriate adjustment will be made to any applicable due dates.
Be aware that if a new virus comes out the default action taken will be to disable all incoming connections on the CCC firewall. This means if you are at home and this action is in effect, nothing on campus will be accessible to you.
If, however, an outage occurs on your end, that shouldn't necessarily be used as an excuse for missing deadlines on work submission. Everyone has a CCC student account, so work can be done while on campus. A certain amount of leniency will typically be granted, if you are usually on-time with your assignments and maintain regular communication with me.
If you experience any sort of problem connecting that does prevent the successful submittal of an assignment or assessment, I expect some notification on your part. Any error messages or diagnostic results will be useful in determining the scope of the problem and consideration regarding due dates.
Collaboration:
Because this course is open resource (ie book, computer, note, etc.) I would like it generally to remain closed person. The reason for this is that the amount of resources available to you are vast, and the goal here is to discover and learn the material through individual initiative. Not to mention that such collaboration on quizzes and tests is CHEATING, and subject to disciplinary action by the school. Individuals are allowed and expected, to assist others through the mailing list (WITHOUT GIVING EXPLICIT ANSWERS) and through personal e-mail and chatting, so long as it does not interfere with a testing situation. If groupwork is required on a particular assignment, it will be stated.
Explicit copying on lab or other course assignments is also forbidden.
Weekly Schedule:
| 1
| Pointers, Classes, Virtual Functions, Abstract Classes, & Lists
| | 2
| Pointers, Classes, Virtual Functions, Abstract Classes, & Lists, cont'd
| | 3
| Overloading, Templates
| | 4
| Exception Handling
| | 5
| Recursion
| | 6
| Linked Lists
| | 7
| Linked Lists, cont'd
| | -
| Break Week
| | 8
| Stacks and Queues
| | 9
| Stacks and Queues, cont'd
| | 10
| Searching and Sorting Algorithms
| | 11
| Searching and Sorting Algorithms, cont'd
| | 12
| Binary Trees
| | 13
| Binary Trees, cont'd
| | -
| Break Week
| | 14
| Graphs
| | 15
| Standard Template Library (STL)
| | 16
| Final Exam/Project
|
* Topics are not set in stone.. they are merely my initial musings as to the flow of the course throughout the semester. Order and presentation may change as deemed necessary.
| 
![[Cover of C++ Programming: Program Design Including Data Structures, 3rd Edition]](http://www.course.com/images/covers/978-1-4188-3640-5.jpg)