CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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.

• Introduction to Objects: Finite State Machines
• Objects and Interfaces: Neurons for a neural network
• Inheritance: and team work: Multiple Games

Extra credit

• Extra credit will only be made available based on the entire class needs. Such as an exam that most people did poorly on despite a good effort.

Grades

Campus Integrity Policy

1. A student found guilty of plagiarism or cheating will receive an “F”(zero) for that particular paper, assignment or exam. Should this occur, the professor will have an interview with the student and will submit a written report of the incident to the academic dean.
2. If a second offense should occur, the student will be asked to appear before the professor, the academic dean and the vice president for student development.
   
   

The student should realize that at this point continuation in a course and even his/her academic career may be in jeopardy. In the event of a recommendation for dismissal, the matter shall be referred to the Student Development Committee.”

AI Use Policy

It is expected that any coursework (including, but not limited to, essays, papers, exams, projects, and lab reports) submitted by a student will be a product of their own creation, demonstrating their achievement of the learning outcomes related to the assigned task. With this in mind, note that submitting work that includes unauthorized or undocumented use of Artificial Intelligence (AI) may be considered as cheating or plagiarism. If you are unsure about appropriate use of AI on a given assignment, talk with your professor.

Services

Education Majors:

Standards

CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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.

Grades

Your grades are made up of:

• Labs are worth 45%. * Each lab is worth as follows: (for the labs that have four parts)

• Homeworks, quizzed, etc. are worth that last 5%

• Grade scale

CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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. Write a reaction to one article in XRDS. It must be programming related. This needs to be completed before the final.

Labs

• Introduction to Objects: Finite State Machines

• Inheritance: and team work: Multiple Games

Extra credit

• Extra credit will only be made available based on the entire class needs. Such as an exam that most people did poorly on despite a good effort.

CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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.

• Lab time: 2:00-2:50 T, 1:00-1:50 F
• Class Location: S 025
• Textbook: Student membership in ACM. Resources from ACM Learning Center that will be used include:

Course Content

Policies

CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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.

Labs

• Introduction to Objects: Finite State Machines
• Objects and interfaces: Tic Tac Toe

Extra credit

• Extra credit will only be made available based on the entire class needs. Such as an exam that most people did poorly on despite a good effort.

Grades

CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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. Write a reaction to one article in the ACM TechNews. It must be programming related. This needs to be completed by midterm.
2. Write a reaction to one article in XRDS. It must be programming related. This needs to be completed before the final.

Labs

Extra credit

• Extra credit will only be made available based on the entire class needs. Such as an exam that most people did poorly on despite a good effort.

Grades

Your grades are made up of:

• Grade scale
  • 93% <= average <= 100% -> A

Tentative Schedule (needs fixing)

CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours

Description

Description

Goals for CSC 221 are:

1. Write non-trivial programs on their own
2. Understand and use OO program concepts well
3. Improve the security of their program
4. Understand the basics of multi-threaded programming

Course outcomes for CSC 221 are:

• Upon complete of CSC 221, students will:
  • be able to design and code complex multi-object programs.
  • be able to develop graphics based interfaces for programs
  • understand the fundamentals of event and concurrent programming.
  • understand the fundamentals of additional programming tools and environments including source code version software

Program outcomes for CSC 221 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)
7. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
8. Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
9. Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)

Integration

1. Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
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 teams
5. Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also 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. Write a reaction to one article in the ACM TechNews. It must be programming related. This needs to be completed by midterm.
2. Write a reaction to one article in XRDS. It must be programming related. This needs to be completed before the final.

Extra credit

• Extra credit will only be made available based on the entire class needs. Such as an exam that most people did poorly on despite a good effort.

Grades

Tentative Schedule (needs fixing)