Difference: CSC121SylS2022 (1 vs. 13)

Revision 132022-03-11 - cathybareiss

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

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: 29 to 29
 
Added:
>
>
 

Homework

Line: 61 to 66
 
Feb 21: Methods Feb 22: Calendar next step Feb 23: Methods Feb. 24: Calendar (part b cont.)
Feb 28: Methods Mar 1: Calendar step 3 Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Changed:
<
<
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception
Mar 21: Arrays Mar 22: Arrays A Mar 23: Arrays Mar. 24: Arrays A
Mar 28: Arrays: 2D and more Mar 29: Arrays B Mar 30: Searching and Sorting Mar. 31: Arrays B
Apr 4: Searching and Sorting Apr. 5: Search/Sort Apr. 6: Exam 3 Apr. 7: Search/Sort
Apr 11: Classes Apr. 12: Class A Apr. 13: Classes Apr. 14:
Easter Break
Apr 18: Classes Apr. 19: Class A Apr. 20: Classes Apr. 21: Class B
Apr 25: Classes Apr. 26: Class B: Calendar part C Apr. 27: Exam 4 Apr. 28: Class B
>
>
Mar 14: Files Mar 15: Files/Exceptions: Calendar (part 3 cont.) Mar 16: Exceptions Mar. 17: Files/Exception: Calendar (part 3 cont.)
Mar 21: Arrays Mar 22: Counting key words Mar 23: Arrays Mar. 24: Key words (cont.)
Mar 28: Arrays: 2D and more Mar 29: Bin Packing Mar 30: Searching and Sorting Mar. 31: Bin packing (cont.)
Apr 4: Searching and Sorting Apr. 5: When to sort first Apr. 6: Exam 3 Apr. 7: Search/Sort (cont.)
Apr 11: Classes Apr. 12: Classes for project Apr. 13: Classes Apr. 14:
Easter Break
Apr 18: Classes Apr. 19: Project classes (cont.) Apr. 20: Classes Apr. 21: Final Calendar Project
Apr 25: Classes Apr. 26: Final project (cont.) Apr. 27: Exam 4 Apr. 28: Final project (cont.)
 
May 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:

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

Revision 122022-02-28 - cathybareiss

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

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

Homework

Line: 58 to 59
 
Feb 7: For and Do loops Feb 8: Arithmetic tables (nested loops) Feb 9: Exam 1 Feb. 10: Arithmetic tables (cont.)
Feb 14: Loops Feb 15: Starting a calendar Feb 16: Methods Feb. 17: Calendar (part a cont.)
Feb 21: Methods Feb 22: Calendar next step Feb 23: Methods Feb. 24: Calendar (part b cont.)
Changed:
<
<
Feb 28: Methods Mar 1: Method B & Files/exceptions Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
>
>
Feb 28: Methods Mar 1: Calendar step 3 Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
 
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception
Mar 21: Arrays Mar 22: Arrays A Mar 23: Arrays Mar. 24: Arrays A

Revision 112022-02-08 - cathybareiss

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

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

Homework

Line: 56 to 57
 
Jan 31: While loops Feb 1: Grades continued Feb 2: Snow day! Feb. 3: Snow day!
Feb 7: For and Do loops Feb 8: Arithmetic tables (nested loops) Feb 9: Exam 1 Feb. 10: Arithmetic tables (cont.)
Feb 14: Loops Feb 15: Starting a calendar Feb 16: Methods Feb. 17: Calendar (part a cont.)
Changed:
<
<
Feb 21: Methods Feb 22: Method A: Calendar part b Feb 23: Methods Feb. 24: Method A
>
>
Feb 21: Methods Feb 22: Calendar next step Feb 23: Methods Feb. 24: Calendar (part b cont.)
 
Feb 28: Methods Mar 1: Method B & Files/exceptions Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception

Revision 102022-02-08 - cathybareiss

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

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: 56 to 56
 
Jan 31: While loops Feb 1: Grades continued Feb 2: Snow day! Feb. 3: Snow day!
Feb 7: For and Do loops Feb 8: Arithmetic tables (nested loops) Feb 9: Exam 1 Feb. 10: Arithmetic tables (cont.)
Feb 14: Loops Feb 15: Starting a calendar Feb 16: Methods Feb. 17: Calendar (part a cont.)
Changed:
<
<
Feb 21: Methods Feb 22: Method A Feb 23: Methods Feb. 24: Method A
>
>
Feb 21: Methods Feb 22: Method A: Calendar part b Feb 23: Methods Feb. 24: Method A
 
Feb 28: Methods Mar 1: Method B & Files/exceptions Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception
Line: 65 to 65
 
Apr 4: Searching and Sorting Apr. 5: Search/Sort Apr. 6: Exam 3 Apr. 7: Search/Sort
Apr 11: Classes Apr. 12: Class A Apr. 13: Classes Apr. 14:
Easter Break
Apr 18: Classes Apr. 19: Class A Apr. 20: Classes Apr. 21: Class B
Changed:
<
<
Apr 25: Classes Apr. 26: Class B Apr. 27: Exam 4 Apr. 28: Class B
>
>
Apr 25: Classes Apr. 26: Class B: Calendar part C Apr. 27: Exam 4 Apr. 28: Class B
 
May 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:

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

Revision 92022-02-03 - cathybareiss

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

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: 53 to 53
 
Jan 10: Jan 11: Jan 12: Jan. 13: Classes begin
First program: Getting things to work
Jan 17:
No class: MLK Day 		Jan 18: First lab continued Jan 19: Lot's of details (Let Us: 1-3)
(Beginner: parts of 1 & 2)
(Easy: 1-2.5) 		Jan. 20: Selection: Making decisions
Jan 24: Quality code, selection Jan 25: Selection continued Jan 26: While loops Jan. 27: Grades and loops
Changed:
<
<
Jan 31: While loops Feb 1: Grades continued Feb 2: For and Do loops Feb. 3: Arithmetic tables (nested loops)
Feb 7: Exam 1 Feb 8: Arithmetic tables (c.) Feb 9: Loops Feb. 10: Starting a calendar
Feb 14: Loops Feb 15: Calendar (c.) Feb 16: Methods Feb. 17: Method A
Feb 21: Methods Feb 22: Method A Feb 23: Methods Feb. 24: Method B
Feb 28: Methods Mar 1: Method B Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
>
>
Jan 31: While loops Feb 1: Grades continued Feb 2: Snow day! Feb. 3: Snow day!
Feb 7: For and Do loops Feb 8: Arithmetic tables (nested loops) Feb 9: Exam 1 Feb. 10: Arithmetic tables (cont.)
Feb 14: Loops Feb 15: Starting a calendar Feb 16: Methods Feb. 17: Calendar (part a cont.)
Feb 21: Methods Feb 22: Method A Feb 23: Methods Feb. 24: Method A
Feb 28: Methods Mar 1: Method B & Files/exceptions Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
 
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception
Mar 21: Arrays Mar 22: Arrays A Mar 23: Arrays Mar. 24: Arrays A

Revision 82022-01-25 - cathybareiss

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

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: 53 to 53
 
Jan 10: Jan 11: Jan 12: Jan. 13: Classes begin
First program: Getting things to work
Jan 17:
No class: MLK Day 		Jan 18: First lab continued Jan 19: Lot's of details (Let Us: 1-3)
(Beginner: parts of 1 & 2)
(Easy: 1-2.5) 		Jan. 20: Selection: Making decisions
Jan 24: Quality code, selection Jan 25: Selection continued Jan 26: While loops Jan. 27: Grades and loops
Changed:
<
<
Jan 31: While loops Feb 1: Grades continued Feb 2: Exam 1 Feb. 3: Arithmetic tables (nested loops)
Feb 7: For and Do loops Feb 8: Arithmetic tables (c.) Feb 9: Loops Feb. 10: Starting a calendar
>
>
Jan 31: While loops Feb 1: Grades continued Feb 2: For and Do loops Feb. 3: Arithmetic tables (nested loops)
Feb 7: Exam 1 Feb 8: Arithmetic tables (c.) Feb 9: Loops Feb. 10: Starting a calendar
 
Feb 14: Loops Feb 15: Calendar (c.) Feb 16: Methods Feb. 17: Method A
Feb 21: Methods Feb 22: Method A Feb 23: Methods Feb. 24: Method B
Feb 28: Methods Mar 1: Method B Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD

Revision 72021-12-27 - cathybareiss

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

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
 

Assignments

Changed:
<
<
>
>
 

Homework

Grades

Line: 47 to 51
 

Tentative Schedule

Monday Tuesday Lab Wednesday Thursday Lab
Jan 10: Jan 11: Jan 12: Jan. 13: Classes begin
First program: Getting things to work
Changed:
<
<
Jan 17:
No class: MLK Day 		Jan 18: Continuation of Intro Jan 19: Lot's of details (Let Us: 1-3)
(Beginner: parts of 1 & 2)
(Easy: 1-2.5) 		Jan. 20: Selection: Making decisions
Jan 24: Review of selection, good code Jan 25: Continuation of lab 2 Jan 26: While loops Jan. 27: Loop A
Jan 31: While loops Feb 1: Loop A Feb 2: Exam 1 Feb. 3: Loop B
Feb 7: For and Do loops Feb 8: Loop B Feb 9: Loops Feb. 10: Loop C
Feb 14: Loops Feb 15: Loop C Feb 16: Methods Feb. 17: Method A
>
>
Jan 17:
No class: MLK Day 		Jan 18: First lab continued Jan 19: Lot's of details (Let Us: 1-3)
(Beginner: parts of 1 & 2)
(Easy: 1-2.5) 		Jan. 20: Selection: Making decisions
Jan 24: Quality code, selection Jan 25: Selection continued Jan 26: While loops Jan. 27: Grades and loops
Jan 31: While loops Feb 1: Grades continued Feb 2: Exam 1 Feb. 3: Arithmetic tables (nested loops)
Feb 7: For and Do loops Feb 8: Arithmetic tables (c.) Feb 9: Loops Feb. 10: Starting a calendar
Feb 14: Loops Feb 15: Calendar (c.) Feb 16: Methods Feb. 17: Method A
 
Feb 21: Methods Feb 22: Method A Feb 23: Methods Feb. 24: Method B
Feb 28: Methods Mar 1: Method B Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception
Mar 21: Arrays Mar 22: Arrays A Mar 23: Arrays Mar. 24: Arrays A
Changed:
<
<
Mar 28: Arrays: 2D and more Mar 29: Arrays B Mar 30: Arrays: Searching and Sorting Mar. 31: Arrays B
Apr 4: Arrays: Searching and Sorting Apr. 5: Search/Sort Apr. 6: Exam Apr. 7: Search/Sort
>
>
Mar 28: Arrays: 2D and more Mar 29: Arrays B Mar 30: Searching and Sorting Mar. 31: Arrays B
Apr 4: Searching and Sorting Apr. 5: Search/Sort Apr. 6: Exam 3 Apr. 7: Search/Sort
 
Apr 11: Classes Apr. 12: Class A Apr. 13: Classes Apr. 14:
Easter Break
Apr 18: Classes Apr. 19: Class A Apr. 20: Classes Apr. 21: Class B
Changed:
<
<
Apr 25: Classes Apr. 26: Class B Apr. 27: Exam 1 Apr. 28: Class B
>
>
Apr 25: Classes Apr. 26: Class B Apr. 27: Exam 4 Apr. 28: Class B
 
May 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:

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

Revision 62021-12-27 - cathybareiss

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

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: 46 to 46
 

Tentative Schedule

Monday Tuesday Lab Wednesday Thursday Lab
Changed:
<
<
Jan 10: Jan 11: Jan 12: Jan. 13: Classes begin
Jan 17:
No class: MLK Day 		Jan 18: Jan 19: Jan. 20:
Jan 24: Jan 25: Jan 26: Jan. 27:
Jan 31: Feb 1: Feb 2: Feb. 3:
Feb 7: Feb 8: Feb 9: Feb. 10:
Feb 14: Feb 15: Feb 16: Feb. 17:
Feb 21: Feb 22: Feb 23: Feb. 24:
Feb 28: Mar 1: Mar 2: Mar. 3:
>
>
Jan 10: Jan 11: Jan 12: Jan. 13: Classes begin
First program: Getting things to work
Jan 17:
No class: MLK Day 		Jan 18: Continuation of Intro Jan 19: Lot's of details (Let Us: 1-3)
(Beginner: parts of 1 & 2)
(Easy: 1-2.5) 		Jan. 20: Selection: Making decisions
Jan 24: Review of selection, good code Jan 25: Continuation of lab 2 Jan 26: While loops Jan. 27: Loop A
Jan 31: While loops Feb 1: Loop A Feb 2: Exam 1 Feb. 3: Loop B
Feb 7: For and Do loops Feb 8: Loop B Feb 9: Loops Feb. 10: Loop C
Feb 14: Loops Feb 15: Loop C Feb 16: Methods Feb. 17: Method A
Feb 21: Methods Feb 22: Method A Feb 23: Methods Feb. 24: Method B
Feb 28: Methods Mar 1: Method B Mar 2: SIGCSE
Exam 2 		Mar. 3:SIGCSE
TBD
 
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Changed:
<
<
Mar 14: Mar 15: Mar 16: Mar. 17:
Mar 21: Mar 22: Mar 23: Mar. 24:
Mar 28: Mar 29: Mar 30: Mar. 31:
Apr 4: Apr. 5: Apr. 6: Apr. 7:
Apr 11: Apr. 12: Apr. 13: Apr. 14:
Easter Break
Apr 18: Apr. 19: Apr. 20: Apr. 21:
Apr 25: Apr. 26: Apr. 27: Apr. 28:
>
>
Mar 14: Files Mar 15: Files/Exceptions Mar 16: Exceptions Mar. 17: Files/Exception
Mar 21: Arrays Mar 22: Arrays A Mar 23: Arrays Mar. 24: Arrays A
Mar 28: Arrays: 2D and more Mar 29: Arrays B Mar 30: Arrays: Searching and Sorting Mar. 31: Arrays B
Apr 4: Arrays: Searching and Sorting Apr. 5: Search/Sort Apr. 6: Exam Apr. 7: Search/Sort
Apr 11: Classes Apr. 12: Class A Apr. 13: Classes Apr. 14:
Easter Break
Apr 18: Classes Apr. 19: Class A Apr. 20: Classes Apr. 21: Class B
Apr 25: Classes Apr. 26: Class B Apr. 27: Exam 1 Apr. 28: Class B
 
May 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:

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

Revision 52021-12-07 - cathybareiss

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

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
 
Apr 11: Apr. 12: Apr. 13: Apr. 14:
Easter Break
Apr 18: Apr. 19: Apr. 20: Apr. 21:
Apr 25: Apr. 26: Apr. 27: Apr. 28:
Changed:
<
<
Apr 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:
>
>
May 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:
 

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

Revision 42021-12-06 - cathybareiss

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

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
 

Assignments

Added:
>
>
 

Homework

Grades

Revision 32021-12-02 - cathybareiss

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="WebHome"
>
>
META TOPICPARENT name="SyllabiSpring2022"
 

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 031
Changed:
<
<
  • Class Time: MW 12:00-12:50 (section 02) or 2:00-2:50 (section 01) MW
>
>
  • Class Time: MW 12:00-12:50 (section 02) or 2:00-2:50 (section 01)
 
  • Lab Time: TR 1:00-1:50 (section 01) or 2:00-2:50 (section 02)
  • Class Location: S 025 or zoom
Changed:
<
<
  • Textbook:
>
>
  • Resources: All resources (textbook, lessons, etc.) are found in SkillSoft of the Learning Center available to any member of ACM (go to acm.org)
  • Textbooks:
    • Let Us Java, Fourth Edition by Yashavant Kanetkar. ISBN: 978-93-8817-638-5
    • Java -- A Beginner's Guide, Eighth Edition by Herbert Schildt. ISBN 9781260440218
    • Java in Easy Steps, 7th Edition by Mike McGrath. ISBN 9781840788730
  • Additional Resources: Course Series: Getting Started with Java Programming
 

Course Content

Policies

Line: 17 to 22
 

Assignments

Added:
>
>
 

Homework

Grades

Line: 58 to 64
 
Apr 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:

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
Added:
>
>
META TOPICMOVED by="cathybareiss" date="1638458484" from="CenterForComputing.CSC121SylF2021" to="CenterForComputing.CSC121SylS2022"

Revision 22021-11-23 - cathybareiss

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

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 031
Changed:
<
<
  • Class Time: MW 12:00-12:50 or 2:00-2:50 MW
  • Lab Time: TR 1:00-1:50 or 2:00-2:50
>
>
  • Class Time: MW 12:00-12:50 (section 02) or 2:00-2:50 (section 01) MW
  • Lab Time: TR 1:00-1:50 (section 01) or 2:00-2:50 (section 02)
 
  • Class Location: S 025 or zoom
  • Textbook:

Course Content

Line: 39 to 39
 

Tentative Schedule

Monday Tuesday Lab Wednesday Thursday Lab
Changed:
<
<
Jan 10: Jan 11: Jan 12: Jan. 13:
>
>
Jan 10: Jan 11: Jan 12: Jan. 13: Classes begin
 
Jan 17:
No class: MLK Day 		Jan 18: Jan 19: Jan. 20:
Jan 24: Jan 25: Jan 26: Jan. 27:
Jan 31: Feb 1: Feb 2: Feb. 3:
Line: 55 to 55
 
Apr 11: Apr. 12: Apr. 13: Apr. 14:
Easter Break
Apr 18: Apr. 19: Apr. 20: Apr. 21:
Apr 25: Apr. 26: Apr. 27: Apr. 28:
Changed:
<
<
Apr 2: Apr. 3: Apr. 4: Apr. 5:
>
>
Apr 2: Final at 10:30-12:30 for section 02
1:00-3:00 for section 01 		Apr. 3: Apr. 4: Apr. 5:
 

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 12021-10-25 - cathybareiss

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

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 031
  • Class Time: MW 12:00-12:50 or 2:00-2:50 MW
  • Lab Time: TR 1:00-1:50 or 2:00-2:50
  • Class Location: S 025 or zoom
  • Textbook:

Course Content

Policies

Assignments

Homework

Grades

  • Homework, etc. is worth 10% of the final grade
  • Programs are worth 40% of the final grade
  • Exams are worth 50% of the final grade with the cumulative final being worth twice a normal exam
  • 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

Monday Tuesday Lab Wednesday Thursday Lab
Jan 10: Jan 11: Jan 12: Jan. 13:
Jan 17:
No class: MLK Day 		Jan 18: Jan 19: Jan. 20:
Jan 24: Jan 25: Jan 26: Jan. 27:
Jan 31: Feb 1: Feb 2: Feb. 3:
Feb 7: Feb 8: Feb 9: Feb. 10:
Feb 14: Feb 15: Feb 16: Feb. 17:
Feb 21: Feb 22: Feb 23: Feb. 24:
Feb 28: Mar 1: Mar 2: Mar. 3:
Mar 7:
Spring Break 		Mar 8:
Spring Break 		Mar 9:
Spring Break 		Mar. 10:
Spring Break
Mar 14: Mar 15: Mar 16: Mar. 17:
Mar 21: Mar 22: Mar 23: Mar. 24:
Mar 28: Mar 29: Mar 30: Mar. 31:
Apr 4: Apr. 5: Apr. 6: Apr. 7:
Apr 11: Apr. 12: Apr. 13: Apr. 14:
Easter Break
Apr 18: Apr. 19: Apr. 20: Apr. 21:
Apr 25: Apr. 26: Apr. 27: Apr. 28:
Apr 2: Apr. 3: Apr. 4: Apr. 5:

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: r13 < r12 < r11 < r10 | 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