Difference: CSC121SylF2023 (1 vs. 25)

Revision 252023-11-01 - CathyBareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 78 to 78
 
10/09: Review, testing 10/10: Lab 6 cont. 10/11: Exam 2 10/13: CCSC Board Meeting
no class
10/16: Command line arguments
JBG: Chap 5 		10/17: Inventory: command line arguments 10/18: Secure programming 10/20: CCSC:MW Conference
Lab 8 cont.
10/23: Arrays
LUJ: Chap 11
JBG: Chap 5
OCAJ: Conditions & Arrays 		10/24: Updating inventory: Arrays 10/25: Arrays, searching
JPS: Chap 5 		10/27: Lab 9 cont.
Changed:
<
<
10/30: Sorting 10/31: Just searching or sorting and searching 11/01: Arrays, test drivers 11/03: Lab 10 cont.
>
>
10/30: Sorting
Sorting Homework 		10/31: Just searching or sorting and searching 11/01: Arrays, test drivers 11/03: Lab 10 cont.
 
11/06: 2D arrays 11/07: Packing cargo ships: 2D arrays 11/08: Exam 3 11/10: Lab 11 cont.
11/13: Classes and test drivers
LUJ: Chap 10
JBG: Chap 4 & 6
JPS: Chap 3
JES: Chap 6
OCAJ: Classes & Objects 		11/14: Classes to help with inventory 11/15: Classes 11/17: Lab 12 cont.
11/20: 11/21: Final version of inventory control 11/22: Thanksgiving break 11/22: Thanksgiving break

Revision 242023-08-04 - CathyBareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 17 to 17
 

Course Content

Policies

Added:
>
>
 
Added:
>
>
 
Changed:
<
<

Assignm

>
>

Assignments

 Homework, quizzes, etc. will be made throughout the semester. The quizzes will typically be online. Homework should be turned in via hard copy (and extremely legible) at the start of class on the day assignment unless otherwise specified. Standard late policy applies.

There are two additional assignments involving reactions to current events. Announcements will not be made in class. You are responsible to track these yourself. Standard late policy will apply to these assignments.
You are to react to current events/publications. A reaction to an article includes enough to convince me that you have read the entire article and not just the headline or first paragraph. It should include a summary of what was said and your reaction. Be sure to give a complete reference to the item. These should be turned in as a hard copy in class within one week of the item being published. You may pick when. Each one does have a deadline. The ones you pick must be unique to this course
  1. Write a reaction to one article in the ACM TechNews. It must be programming related. This needs to be completed by midterm.
Line: 40 to 43
 

Extra credit

Added:
>
>
  • 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:

Added:
>
>
  • 50% of the grade is based on the exams. The final exam is worth twice a normal exam and is cumulative
  • 40% is based on the labs
  • 10% is based on homework, quizzes, etc.
 
  • Grade scale
    • 93% <= average <= 100% -> A

Revision 232023-07-31 - CathyBareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 20 to 20
 
Changed:
<
<

Assignments

>
>

Assignm

Homework, quizzes, etc. will be made throughout the semester. The quizzes will typically be online. Homework should be turned in via hard copy (and extremely legible) at the start of class on the day assignment unless otherwise specified. Standard late policy applies.

There are two additional assignments involving reactions to current events. Announcements will not be made in class. You are responsible to track these yourself. Standard late policy will apply to these assignments.
You are to react to current events/publications. A reaction to an article includes enough to convince me that you have read the entire article and not just the headline or first paragraph. It should include a summary of what was said and your reaction. Be sure to give a complete reference to the item. These should be turned in as a hard copy in class within one week of the item being published. You may pick when. Each one does have a deadline. The ones you pick must be unique to this course
  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

Revision 222023-07-28 - CathyBareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 73 to 73
 
11/20: 11/21: Final version of inventory control 11/22: Thanksgiving break 11/22: Thanksgiving break
11/27: 11/28: Lab 13 cont. 11/29 12/01: Lab 13 cont.
12/04: 12/05 12/06: Final Exam
3:30-5:20 		12/08
Changed:
<
<

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards
>
>

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

Education Majors:

Please use the link below to review all appropriate standards. Standards
 \ No newline at end of file

Revision 212023-06-28 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 57 to 57
 

Tentative Schedule

Monday Tuesday Lab Wednesday Friday Lab
8/14 8/15 8/16 8/18: First Program and your environment
Changed:
<
<
8/21: Overview of Java 8/22: Lab 1 cont. 8/23: Selection 8/25: Simple Arithmetic: Selection
8/28: Selection and Repetition 8/29: Lab 2 cont. 8/30: Repetition 901: Calculator: Introduction to repetition
>
>
8/21: Overview of Java
LUJ: Chap 1-3
JBG: Chap 1 & 2
JPS: Chap 1 & 2
JES: Chap 1 & 2
OCAJ: Introduction to Java, Working with Variables 		8/22: Lab 1 cont. 8/23: Selection
LUJ: Chap 4 & 6
JBG: Chap 3
JES: Chap 3
JPS: Chap 2
OCAJ: Operators & Conditionals 		8/25: Simple Arithmetic: Selection
8/28: Selection and Repetition
LUJ Chap 5
LBG: Chap 3
JPS: Chap 2
JES: Chap 3 		8/29: Lab 2 cont. 8/30: Repetition 901: Calculator: Introduction to repetition
 
9/04
Labor Day 		9/05: Lab 3 cont. 9/06: Repetition 9/08: Print a month
Changed:
<
<
9/11: Exam 1 9/12: Lab 4 cont. 9/13: Methods 9/15: Print a month using methods
9/18: Methods 9/19: Lab 5 cont. 9/20: Files 9/22: Inventory Control: Methods and files
9/25: Methods 9/26: Service Day 9/27: Methods, constants 9/29: Lab 6 cont.
10/02: Exceptions, error handling 10/03: Simple quiz engine: Methods and files 10/04: Methods 10/06: Fall Break
>
>
9/11: Exam 1 9/12: Lab 4 cont. 9/13: Methods
LUJ: Chap 7 & 8
JBG: Chap 4
OCAJ: Methods & Conditionals 		9/15: Print a month using methods
9/18: Methods 9/19: Lab 5 cont. 9/20: Files
JBG: Chap 3
JPS: Chap 9 		9/22: Inventory Control: Methods and files
9/25: Methods 9/26: Service Day 9/27: Methods, constants
JES: Chap 1 		9/29: Lab 6 cont.
10/02: Exceptions, error handling
LUJ: Chap 15
JBG:Chap 9
JPS: Chap 6
OCAJ: Working with Exceptions 		10/03: Simple quiz engine: Methods and files 10/04: Methods 10/06: Fall Break
 
10/09: Review, testing 10/10: Lab 6 cont. 10/11: Exam 2 10/13: CCSC Board Meeting
no class
Changed:
<
<
10/16: Command line arguments 10/17: Inventory: command line arguments 10/18: Secure programming 10/20: CCSC:MW Conference
Lab 8 cont.
10/23: Arrays 10/24: Updating inventory: Arrays 10/25: Arrays, searching 10/27: Lab 9 cont.
>
>
10/16: Command line arguments
JBG: Chap 5 		10/17: Inventory: command line arguments 10/18: Secure programming 10/20: CCSC:MW Conference
Lab 8 cont.
10/23: Arrays
LUJ: Chap 11
JBG: Chap 5
OCAJ: Conditions & Arrays 		10/24: Updating inventory: Arrays 10/25: Arrays, searching
JPS: Chap 5 		10/27: Lab 9 cont.
 
10/30: Sorting 10/31: Just searching or sorting and searching 11/01: Arrays, test drivers 11/03: Lab 10 cont.
11/06: 2D arrays 11/07: Packing cargo ships: 2D arrays 11/08: Exam 3 11/10: Lab 11 cont.
Changed:
<
<
11/13: Classes and test drivers 11/14: Classes to help with inventory 11/15: Classes 11/17: Lab 12 cont.
11/20 11/21: Final version of inventory control 11/22: Thanksgiving break 11/22: Thanksgiving break
11/27 11/28: Lab 13 cont. 11/29 12/01: Lab 13 cont.
12/04 12/05 12/06: Final Exam
3:30-5:20 		12/08
>
>
11/13: Classes and test drivers
LUJ: Chap 10
JBG: Chap 4 & 6
JPS: Chap 3
JES: Chap 6
OCAJ: Classes & Objects 		11/14: Classes to help with inventory 11/15: Classes 11/17: Lab 12 cont.
11/20: 11/21: Final version of inventory control 11/22: Thanksgiving break 11/22: Thanksgiving break
11/27: 11/28: Lab 13 cont. 11/29 12/01: Lab 13 cont.
12/04: 12/05 12/06: Final Exam
3:30-5:20 		12/08
 

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards \ No newline at end of file

Revision 202023-06-27 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 13 to 13
 
    • JBC: Java—A Beginner's Guide, Eighth Edition. ISBN: 9781260440218. Author: Herbert Schildt
    • JES: Java in Easy Steps, 7th Edition. ISBN: 9781840788730. Author: Mike McGrath
    • JPS: Java Programming Simplified—From Novice to Professional - Start at the Beginning and Learn the World of Java. ISBN: 978-93-89845-143. Author: Dr. Muneer Ahmad Dar
Changed:
<
<
    • JCFA: Course: Java Certified Foundations Associate: Basic Elements
>
>
    • OCAJ: Channel: Oracle Certified Associate, Java SE Programmer
 

Course Content

Policies

Revision 192023-06-27 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 8 to 8
 
  • Class Time: 2:00-2:50 MW
  • Lab Time: 2:00-3:20 TF
  • Class Location: S 025
Changed:
<
<
  • Textbook: Student membership in ACM
>
>
  • Textbook: Student membership in ACM. Resources from ACM Learning Center that will be used include:
    • LUS: Let us Java, Fourth Edition. ISBN: 978-93-8817-638-5. Author: Yashavant Kanetkar
    • JBC: Java—A Beginner's Guide, Eighth Edition. ISBN: 9781260440218. Author: Herbert Schildt
    • JES: Java in Easy Steps, 7th Edition. ISBN: 9781840788730. Author: Mike McGrath
    • JPS: Java Programming Simplified—From Novice to Professional - Start at the Beginning and Learn the World of Java. ISBN: 978-93-89845-143. Author: Dr. Muneer Ahmad Dar
    • JCFA: Course: Java Certified Foundations Associate: Basic Elements
 

Course Content

Policies

Changed:
<
<
>
>
 

Assignments

Labs

Line: 32 to 37
 

Extra credit

Grades

Added:
>
>
 Your grades are made up of:

  • Grade scale
Changed:
<
<
    • 93% <= average <= 100% -> A
    • 90% <= average < 93% -> A-
    • 87% <= average < 90% -> B+
    • 83% <= average < 87% -> B
    • 80% <= average < 83% -> B-
    • 77% <= average < 80% -> C+
    • 73% <= average < 77% -> C
    • 70% <= average < 73% -> C-
    • 67% <= average < 70% -> D+
    • 63% <= average < 67% -> D
    • 60% <= average < 63% -> D-
    • 0% <= average < 60% -> F
>
>
    • 93% <= average <= 100% -> A
    • 90% <= average < 93% -> A-
    • 87% <= average < 90% -> B+
    • 83% <= average < 87% -> B
    • 80% <= average < 83% -> B-
    • 77% <= average < 80% -> C+
    • 73% <= average < 77% -> C
    • 70% <= average < 73% -> C-
    • 67% <= average < 70% -> D+
    • 63% <= average < 67% -> D
    • 60% <= average < 63% -> D-
    • 0% <= average < 60% -> F
 

Tentative Schedule

Monday Tuesday Lab Wednesday Friday Lab
8/14 8/15 8/16 8/18: First Program and your environment
Changed:
<
<
8/21 8/22 8/23 8/25: Simple Arithmetic: Selection
8/28 8/29 8/30 901: Calculator: Introduction to repetition
9/04
Labor Day 		9/05 9/06 9/08: Print a month
9/11 9/12 9/13 9/15: Print a month using methods
9/18 9/19 9/20 9/22: Inventory Control: Methods and files
9/25 9/26
Service Day 		9/27 9/29
10/02 10/03: Simple quiz engine: More methods and files 10/04 10/06
Fall Break
10/09 10/10 10/11 10/13
CCSC Board Meeting
10/16 10/17: Updating inventory: Methods, files, command line arguments 10/18 10/20
CCSC:MW Conference
10/23 10/24: Updating inventory: Arrays 10/25 10/27
10/30 10/31: Just searching or sorting and searching 11/01 11/03
11/06 11/07: Packing cargo ships: 2D arrays 11/08 11/10
11/13 11/14: Classes to help with inventory 11/15 11/17
11/20 11/21: Final version of inventory control 11/22
Thanksgiving break 		11/22
Thanksgiving break
11/27 11/28 11/29 12/01
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/08
>
>
8/21: Overview of Java 8/22: Lab 1 cont. 8/23: Selection 8/25: Simple Arithmetic: Selection
8/28: Selection and Repetition 8/29: Lab 2 cont. 8/30: Repetition 901: Calculator: Introduction to repetition
9/04
Labor Day 		9/05: Lab 3 cont. 9/06: Repetition 9/08: Print a month
9/11: Exam 1 9/12: Lab 4 cont. 9/13: Methods 9/15: Print a month using methods
9/18: Methods 9/19: Lab 5 cont. 9/20: Files 9/22: Inventory Control: Methods and files
9/25: Methods 9/26: Service Day 9/27: Methods, constants 9/29: Lab 6 cont.
10/02: Exceptions, error handling 10/03: Simple quiz engine: Methods and files 10/04: Methods 10/06: Fall Break
10/09: Review, testing 10/10: Lab 6 cont. 10/11: Exam 2 10/13: CCSC Board Meeting
no class
10/16: Command line arguments 10/17: Inventory: command line arguments 10/18: Secure programming 10/20: CCSC:MW Conference
Lab 8 cont.
10/23: Arrays 10/24: Updating inventory: Arrays 10/25: Arrays, searching 10/27: Lab 9 cont.
10/30: Sorting 10/31: Just searching or sorting and searching 11/01: Arrays, test drivers 11/03: Lab 10 cont.
11/06: 2D arrays 11/07: Packing cargo ships: 2D arrays 11/08: Exam 3 11/10: Lab 11 cont.
11/13: Classes and test drivers 11/14: Classes to help with inventory 11/15: Classes 11/17: Lab 12 cont.
11/20 11/21: Final version of inventory control 11/22: Thanksgiving break 11/22: Thanksgiving break
11/27 11/28: Lab 13 cont. 11/29 12/01: Lab 13 cont.
12/04 12/05 12/06: Final Exam
3:30-5:20 		12/08
 

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards \ No newline at end of file

Revision 182023-06-27 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 26 to 26
 
Changed:
<
<
  • Sorting and searching
>
>
 
Line: 61 to 61
 
10/09 10/10 10/11 10/13
CCSC Board Meeting
10/16 10/17: Updating inventory: Methods, files, command line arguments 10/18 10/20
CCSC:MW Conference
10/23 10/24: Updating inventory: Arrays 10/25 10/27
Changed:
<
<
10/30 10/31: Searching 11/01 11/03
>
>
10/30 10/31: Just searching or sorting and searching 11/01 11/03
 
11/06 11/07: Packing cargo ships: 2D arrays 11/08 11/10
11/13 11/14: Classes to help with inventory 11/15 11/17
11/20 11/21: Final version of inventory control 11/22
Thanksgiving break 		11/22
Thanksgiving break

Revision 172023-06-26 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 28 to 28
 
Changed:
<
<
>
>
 

Extra credit

Grades

Your grades are made up of:
Line: 63 to 63
 
10/23 10/24: Updating inventory: Arrays 10/25 10/27
10/30 10/31: Searching 11/01 11/03
11/06 11/07: Packing cargo ships: 2D arrays 11/08 11/10
Changed:
<
<
11/13 11/14: Classes to help with inventory 11/15 11/17
11/20 11/21: Final lab 11/22
Thanksgiving break 		11/22
Thanksgiving break
>
>
11/13 11/14: Classes to help with inventory 11/15 11/17
11/20 11/21: Final version of inventory control 11/22
Thanksgiving break 		11/22
Thanksgiving break
 
11/27 11/28 11/29 12/01
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/08

Revision 162023-06-26 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 26 to 26
 
Deleted:
<
<
 
  • Sorting and searching
Added:
>
>
 
  • Final version

Extra credit

Grades

Line: 62 to 62
 
10/16 10/17: Updating inventory: Methods, files, command line arguments 10/18 10/20
CCSC:MW Conference
10/23 10/24: Updating inventory: Arrays 10/25 10/27
10/30 10/31: Searching 11/01 11/03
Changed:
<
<
11/06 11/07: Sorting 11/08 11/10
11/13 11/14: Packing cargo ships: 2D arrays 11/15 11/17
>
>
11/06 11/07: Packing cargo ships: 2D arrays 11/08 11/10
11/13 11/14: Classes to help with inventory 11/15 11/17
 
11/20 11/21: Final lab 11/22
Thanksgiving break 		11/22
Thanksgiving break
11/27 11/28 11/29 12/01
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/08

Revision 152023-06-22 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 27 to 27
 
Changed:
<
<
  • bin packing (2D)
>
>
 
  • Sorting and searching
  • Final version

Extra credit

Line: 63 to 63
 
10/23 10/24: Updating inventory: Arrays 10/25 10/27
10/30 10/31: Searching 11/01 11/03
11/06 11/07: Sorting 11/08 11/10
Changed:
<
<
11/13 11/14: 2 D array 11/15 11/17
>
>
11/13 11/14: Packing cargo ships: 2D arrays 11/15 11/17
 
11/20 11/21: Final lab 11/22
Thanksgiving break 		11/22
Thanksgiving break
11/27 11/28 11/29 12/01
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/08

Revision 142023-06-20 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 24 to 24
 
Changed:
<
<
  • update counts of file create new file (X)
  • adapt previous to arrays (arrays)
>
>
 
  • searching 2nd file (not in order) (searching)
  • bin packing (2D)
  • Sorting and searching
Line: 59 to 59
 
9/25 9/26
Service Day 		9/27 9/29
10/02 10/03: Simple quiz engine: More methods and files 10/04 10/06
Fall Break
10/09 10/10 10/11 10/13
CCSC Board Meeting
Changed:
<
<
10/16 10/17: Lab X 10/18 10/20
CCSC:MW Conference
10/23 10/24: Arrays 10/25 10/27
>
>
10/16 10/17: Updating inventory: Methods, files, command line arguments 10/18 10/20
CCSC:MW Conference
10/23 10/24: Updating inventory: Arrays 10/25 10/27
 
10/30 10/31: Searching 11/01 11/03
11/06 11/07: Sorting 11/08 11/10
11/13 11/14: 2 D array 11/15 11/17

Revision 132023-06-20 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 23 to 23
 
Changed:
<
<
  • Quizzer (files)
>
>
 
  • update counts of file create new file (X)
  • adapt previous to arrays (arrays)
  • searching 2nd file (not in order) (searching)
Line: 57 to 57
 
9/11 9/12 9/13 9/15: Print a month using methods
9/18 9/19 9/20 9/22: Inventory Control: Methods and files
9/25 9/26
Service Day 		9/27 9/29
Changed:
<
<
10/02 10/03: Lab X 10/04 10/06
Fall Break
>
>
10/02 10/03: Simple quiz engine: More methods and files 10/04 10/06
Fall Break
 
10/09 10/10 10/11 10/13
CCSC Board Meeting
10/16 10/17: Lab X 10/18 10/20
CCSC:MW Conference
10/23 10/24: Arrays 10/25 10/27

Revision 122023-06-19 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 22 to 22
 
Changed:
<
<
  • methods -> inventory control (find location in file 1, use number to find amount in file 2 and limit in file 3 -> same method, called twice), decide if we need to re-order (method), error method
>
>
 
  • Quizzer (files)
  • update counts of file create new file (X)
  • adapt previous to arrays (arrays)
Line: 55 to 55
 
8/28 8/29 8/30 901: Calculator: Introduction to repetition
9/04
Labor Day 		9/05 9/06 9/08: Print a month
9/11 9/12 9/13 9/15: Print a month using methods
Changed:
<
<
9/18 9/19 9/20 9/22: Methods 2
>
>
9/18 9/19 9/20 9/22: Inventory Control: Methods and files
 
9/25 9/26
Service Day 		9/27 9/29
10/02 10/03: Lab X 10/04 10/06
Fall Break
10/09 10/10 10/11 10/13
CCSC Board Meeting

Revision 112023-06-19 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 21 to 21
 
Changed:
<
<
  • methods -> print month with methods (7 numbers per line, number of days in a month, month name)
>
>
 
  • methods -> inventory control (find location in file 1, use number to find amount in file 2 and limit in file 3 -> same method, called twice), decide if we need to re-order (method), error method
  • Quizzer (files)
  • update counts of file create new file (X)
Line: 54 to 54
 
8/21 8/22 8/23 8/25: Simple Arithmetic: Selection
8/28 8/29 8/30 901: Calculator: Introduction to repetition
9/04
Labor Day 		9/05 9/06 9/08: Print a month
Changed:
<
<
9/11 9/12 9/13 9/15: Methods 1
>
>
9/11 9/12 9/13 9/15: Print a month using methods
 
9/18 9/19 9/20 9/22: Methods 2
9/25 9/26
Service Day 		9/27 9/29
10/02 10/03: Lab X 10/04 10/06
Fall Break

Revision 102023-06-19 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 20 to 20
 
Changed:
<
<
  • simple calculator (repetition)
  • print a month (repetition)
>
>
 
  • methods -> print month with methods (7 numbers per line, number of days in a month, month name)
  • methods -> inventory control (find location in file 1, use number to find amount in file 2 and limit in file 3 -> same method, called twice), decide if we need to re-order (method), error method
  • Quizzer (files)
Line: 53 to 52
 
Monday Tuesday Lab Wednesday Friday Lab
8/14 8/15 8/16 8/18: First Program and your environment
8/21 8/22 8/23 8/25: Simple Arithmetic: Selection
Changed:
<
<
8/28 8/29 8/30 901: Repetition 1
9/04
Labor Day 		9/05 9/06 9/08: Repetition 2
>
>
8/28 8/29 8/30 901: Calculator: Introduction to repetition
9/04
Labor Day 		9/05 9/06 9/08: Print a month
 
9/11 9/12 9/13 9/15: Methods 1
9/18 9/19 9/20 9/22: Methods 2
9/25 9/26
Service Day 		9/27 9/29

Revision 92023-06-15 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 19 to 19
 

Labs

Added:
>
>
 
  • simple calculator (repetition)
  • print a month (repetition)
  • methods -> print month with methods (7 numbers per line, number of days in a month, month name)

Revision 82023-06-09 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 18 to 18
 

Assignments

Labs

Changed:
<
<
  • perform operation and check answer (selection)
>
>
 
  • simple calculator (repetition)
  • print a month (repetition)
  • methods -> print month with methods (7 numbers per line, number of days in a month, month name)
Line: 51 to 51
 

Tentative Schedule

Monday Tuesday Lab Wednesday Friday Lab
8/14 8/15 8/16 8/18: First Program and your environment
Changed:
<
<
8/21 8/22 8/23 8/25: Selection
>
>
8/21 8/22 8/23 8/25: Simple Arithmetic: Selection
 
8/28 8/29 8/30 901: Repetition 1
9/04
Labor Day 		9/05 9/06 9/08: Repetition 2
9/11 9/12 9/13 9/15: Methods 1

Revision 72023-06-02 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 62 to 62
 
10/16 10/17: Lab X 10/18 10/20
CCSC:MW Conference
10/23 10/24: Arrays 10/25 10/27
10/30 10/31: Searching 11/01 11/03
Changed:
<
<
11/06 11/07: 2 D array 11/08 11/10
11/13 11/14: Sorting 11/15 11/17
>
>
11/06 11/07: Sorting 11/08 11/10
11/13 11/14: 2 D array 11/15 11/17
 
11/20 11/21: Final lab 11/22
Thanksgiving break 		11/22
Thanksgiving break
11/27 11/28 11/29 12/01
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/08

Revision 62023-05-30 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 18 to 18
 

Assignments

Labs

Added:
>
>
  • perform operation and check answer (selection)
  • simple calculator (repetition)
  • print a month (repetition)
  • methods -> print month with methods (7 numbers per line, number of days in a month, month name)
  • methods -> inventory control (find location in file 1, use number to find amount in file 2 and limit in file 3 -> same method, called twice), decide if we need to re-order (method), error method
  • Quizzer (files)
  • update counts of file create new file (X)
  • adapt previous to arrays (arrays)
  • searching 2nd file (not in order) (searching)
  • bin packing (2D)
  • Sorting and searching
  • Final version
 

Extra credit

Grades

Your grades are made up of:

Revision 52023-05-18 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 6 to 6
 
  • Professor: Dr. Cathy Bareiss
  • Office SB 31
  • Class Time: 2:00-2:50 MW
Changed:
<
<
  • Lab Time: 2:00-3:20 TR
>
>
  • Lab Time: 2:00-3:20 TF
 
  • Class Location: S 025
  • Textbook: Student membership in ACM
Line: 37 to 37
 
    • 0% <= average < 60% -> F

Tentative Schedule

Changed:
<
<
Monday Tuesday Lab Wednesday Thursday Lab
8/14 8/15 8/16 8/17: Class begin
First Program and your environment
8/21 8/22 8/23 8/24
8/28 8/29 8/30 8/31
9/04
Labor Day 		9/05 9/06 9/07
9/11 9/12 9/13 9/14
9/18 9/19 9/20 9/21
9/25 9/26
Service Day 		9/27 9/28
10/02 10/03 10/04 10/05
Fall Break
10/09 10/10 10/11 10/12
CCSC Board Meeting
10/16 10/17 10/18 10/19
10/23 10/24 10/25 10/26
10/30 10/31 11/01 11/02
11/06 11/07 11/08 11/09
11/13 11/14 11/15 11/16
11/20 11/21 11/22
Thanksgiving break 		11/23
Thanksgiving break
11/27 11/28 11/29 11/30
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/07
>
>
Monday Tuesday Lab Wednesday Friday Lab
8/14 8/15 8/16 8/18: First Program and your environment
8/21 8/22 8/23 8/25: Selection
8/28 8/29 8/30 901: Repetition 1
9/04
Labor Day 		9/05 9/06 9/08: Repetition 2
9/11 9/12 9/13 9/15: Methods 1
9/18 9/19 9/20 9/22: Methods 2
9/25 9/26
Service Day 		9/27 9/29
10/02 10/03: Lab X 10/04 10/06
Fall Break
10/09 10/10 10/11 10/13
CCSC Board Meeting
10/16 10/17: Lab X 10/18 10/20
CCSC:MW Conference
10/23 10/24: Arrays 10/25 10/27
10/30 10/31: Searching 11/01 11/03
11/06 11/07: 2 D array 11/08 11/10
11/13 11/14: Sorting 11/15 11/17
11/20 11/21: Final lab 11/22
Thanksgiving break 		11/22
Thanksgiving break
11/27 11/28 11/29 12/01
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/08
 

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards \ No newline at end of file

Revision 42023-05-18 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 16 to 16
 

Assignments

Added:
>
>

Labs

 

Extra credit

Grades

Your grades are made up of:
Line: 36 to 38
 

Tentative Schedule

Monday Tuesday Lab Wednesday Thursday Lab
Changed:
<
<
8/14 8/15 8/16 8/17: Class begin
>
>
8/14 8/15 8/16 8/17: Class begin
First Program and your environment
 
8/21 8/22 8/23 8/24
8/28 8/29 8/30 8/31
9/04
Labor Day 		9/05 9/06 9/07

Revision 32023-05-18 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 36 to 36
 

Tentative Schedule

Monday Tuesday Lab Wednesday Thursday Lab
Changed:
<
<
8/14 8/15 8/16 8/17
8/21 8/15 8/16 8/17
8/28 8/15 8/16 8/17
9/04 8/15 8/16 8/17
9/11 8/15 8/16 8/17
9/18 8/15 8/16 8/17
9/25 8/15 8/16 8/17
10/02 8/15 8/16 8/17
10/09 8/15 8/16 8/17
10/16 8/15 8/16 8/17
10/23 8/15 8/16 8/17
10/30 8/15 8/16 8/17
11/06 8/15 8/16 8/17
11/13 8/15 8/16 8/17
11/20 8/15 8/16 8/17
11/27 8/15 8/16 8/17
12/04 8/15 8/16 8/17
>
>
8/14 8/15 8/16 8/17: Class begin
8/21 8/22 8/23 8/24
8/28 8/29 8/30 8/31
9/04
Labor Day 		9/05 9/06 9/07
9/11 9/12 9/13 9/14
9/18 9/19 9/20 9/21
9/25 9/26
Service Day 		9/27 9/28
10/02 10/03 10/04 10/05
Fall Break
10/09 10/10 10/11 10/12
CCSC Board Meeting
10/16 10/17 10/18 10/19
10/23 10/24 10/25 10/26
10/30 10/31 11/01 11/02
11/06 11/07 11/08 11/09
11/13 11/14 11/15 11/16
11/20 11/21 11/22
Thanksgiving break 		11/23
Thanksgiving break
11/27 11/28 11/29 11/30
12/04 12/05 12/06
Final Exam: 3:30-5:20 		12/07
 

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards \ No newline at end of file

Revision 22023-05-16 - cathybareiss

Line: 1 to 1
 
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.
Line: 35 to 35
 
    • 0% <= average < 60% -> F

Tentative Schedule

Added:
>
>
Monday Tuesday Lab Wednesday Thursday Lab
8/14 8/15 8/16 8/17
8/21 8/15 8/16 8/17
8/28 8/15 8/16 8/17
9/04 8/15 8/16 8/17
9/11 8/15 8/16 8/17
9/18 8/15 8/16 8/17
9/25 8/15 8/16 8/17
10/02 8/15 8/16 8/17
10/09 8/15 8/16 8/17
10/16 8/15 8/16 8/17
10/23 8/15 8/16 8/17
10/30 8/15 8/16 8/17
11/06 8/15 8/16 8/17
11/13 8/15 8/16 8/17
11/20 8/15 8/16 8/17
11/27 8/15 8/16 8/17
12/04 8/15 8/16 8/17
 

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards \ No newline at end of file

Revision 12023-04-20 - cathybareiss

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="Syllabi"

CSC 121: Programming 1: Control Structures. 3 hours

Description

An introduction to computer application development using a high level, object oriented, GUI based language. Emphasis is on the use of problem solving methods, algorithms, control structures, documentation and debugging. Lab: CSC 121L. Prerequisites: CSC 102 or permission of the instructor

Goals for CSC 121 are:

Upon completion of the course, students will
  1. Be able to write small (two pages) programs independently of outside help
  2. Begin to develop technical writing skills
  3. Have developed simple habits of secure programming

Course outcomes for CSC 121 are:

Upon completion of CSC 121, students will know:
  • how to write 2 - 3 page programs in a high level language
  • how to document code and a program
  • how to come up with a simple testing plan that includes input, output, and some error conditions
  • how to work with a simple IDE to debug a program

Program outcomes for CSC 121 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. Understand and use appropriate cloud technologies in specified areas (Computing student learning outcome 8)
  6. Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
  7. 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 (such as simple math function, formatting, string functions that are easy to understand and covered by the textbook)
  2. Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
  3. Technical writing at the introductory level by requiring students to understand and properly express a problem summary and requirements and the steps of a program and a complete (but somewhat informal) testing report.
  4. 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.
  5. 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).
  6. Ethics at an introductory level by having at least two programs assigned that could have ethical implications and having the students discuss that in their reports.

Details

  • Professor: Dr. Cathy Bareiss
  • Office SB 31
  • Class Time: 2:00-2:50 MW
  • Lab Time: 2:00-3:20 TR
  • Class Location: S 025
  • Textbook: Student membership in ACM

Course Content

Policies

Assignments

Extra credit

Grades

Your grades are made up of:

  • Grade scale
    • 93% <= average <= 100% -> A
    • 90% <= average < 93% -> A-
    • 87% <= average < 90% -> B+
    • 83% <= average < 87% -> B
    • 80% <= average < 83% -> B-
    • 77% <= average < 80% -> C+
    • 73% <= average < 77% -> C
    • 70% <= average < 73% -> C-
    • 67% <= average < 70% -> D+
    • 63% <= average < 67% -> D
    • 60% <= average < 63% -> D-
    • 0% <= average < 60% -> F

Tentative Schedule

Campus Integrity Policy

The student handbook (p. 156) states: “Any act of deceit, falsehood or stealing by unethically copying or using someone else’s work in an academic situation is strictly prohibited.

  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.”

Covid Policy

Everyone should follow the current Bethel University covid policy. See: https://www.betheluniversity.edu/intheknow for details

Services

The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.

DEI Statement

During this particularly difficult time, this statement momentarily underscores and deepens what is expressed in the Lifestyle Covenant regarding the dignity of all humans. The statement will remain in all Bethel Faculty syllabi until spring 2023 and then be remanded back to the Faculty. Bethel University respects the dignity of all God’s image-bearers, and stands against racism, prejudice, and discrimination. Because Christ calls us to love our neighbor as ourselves, Christian discipleship includes pursuing the good of those who suffer injustice due to their color, race, or ethnicity. Therefore, we aim to continually transform our classrooms into safe and hospitable spaces where we listen to one another with mercy, learn from and value each other with tenacity, and commit to pursuing justice for the most vulnerable in our community.

Education Majors:

Please use the link below to review all appropriate standards. Standards
View topic | History: r25 < r24 < r23 < r22 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback