CSC 122: Programming 2: Data Structures: 3 hours.

Description

Goals for CSC 122 are:

1. Enhance the ability to program
2. Understand different data structures
3. Be able to use different data structures well

Course outcomes for CSC 122 are:

• Upon completion of CSC 122, students will know:
  • how to use and build different data structures including stacks, queues, trees, graphs, and lists
  • a number of different searches and sorts (including O(nlogn) sorts)
  • how to identify Big-O for given algorithms
  • how to completely document code and programs
  • how to thoroughly test a program (including most error conditions)
  • how to identify some potential security issues with code being developed
  • the importance of designing before coding and practice it when warranted.

Program outcomes for CSC 122 are:

1. Analyze a complex computing problem and to apply principles of computing and other relevant disciplines to identify solutions. (Computing student learning outcome 1)
2. Design, implement, and evaluate a computing-based solution to meet a given set of computing requirements in the context of the program’s discipline. (Computing student learning outcome 2)
3. Communicate effectively in a variety of professional contexts. (Computing student learning outcome 3)
4. Recognize professional responsibilities and make informed judgments in computing practice based on legal, ethical, and moral principles. (Computing student learning outcome 4)
5. Function effectively as a member or leader of a team engaged in activities appropriate to the program’s discipline. (Computing student learning outcome 5)
6. Learn new areas of technology. (Computing student learning outcome 6)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class (such as using a pre-defined data type)
2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
3. Technical writing at the application level by requiring students to do a formal software development report and requiring quality writing (and grading the quality of the writing), Also by the end of the semester by refusing to accept reports that don't meet a bare min. standard (such as standards, spell check, using bullet lists as appropriate.
4. Team work at the introductory level by having at least two assignments where students are working in pairs with one developing the data structure and the other using it. Students need to take on both roles during the semester. Students also might have a third assignment where they are assigned one of the two roles and they have a partner that they don't know and must only communicate via the interface.
5. Professionalism at the introductory level by having students track how long it takes to write programs (so that they are better equip to estimate this in the future) and comment on what they learned and what they would want to to better with a program if they could.
6. Cybersecurity at an introductory level by requiring students to document possible invalid input what happens for all programs. By the end of the semester, they should handle some of the invalid input (i.e. secure programming).
7. Ethics at an introductory level by having at least one program assigned that could have ethical implications and having the students discuss that in their reports.

1. Hashing
2. Using a binary tree to do Huffman codes
3. Own data structure

Homework, Assignments, Quizzes, etc.

1. 1. Write a reaction to one article in the ACM TechNews. This needs to be completed by midterm.
   2. Write a reaction to one article in XRDS. This needs to be completed before the final.
   3. Write a reaction to one article in the Communication of the ACM. This needs to be completed before the final

Extra credit

1. 1. There may be events that I give extra credit for attending. To earn this, you must attend the event (in person unless otherwise stated) and write a 1/2 page summary of what was said. This is to be turned in as a hard copy within 3 working days of the event.
   2. Do a second reaction to an article in the Communications of the ACM
   3. Do a second reaction to an article in the ACM TechNews.