Difference: CSC121SylF2026 (1 vs. 2)

Revision 22026-06-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.

Details

Changed:
<
<
  • Professor:
  • Office:
  • Class Time: 11:00-1:50am MF
  • Lab Time: 11:00-11:50pm TR
  • Class Location:
  • Textbook:
>
>
  • Professor: Dr. Cathy Bareiss
  • Office SB 31
  • Class Time: 2:00-2:50 MW
  • Lab Time: 1:00-1:50 TF
  • Class Location: S 025
  • 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
    • OCAJ: Channel: Oracle Certified Associate, Java SE Programmer
 

Course Content

Policies

Changed:
<
<

Programs

>
>
 

Assignments

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

Extra credit

Extra credit

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

Grades

Your grades are made up of:

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
Line: 35 to 70
 

Tentative Schedule

Monday Tuesday Lab Thursday Friday Lab
Added:
>
>
8/18: 8/19: 8/21: Classes begin
Overview of Course and 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: First Program and your environment
8/25: Selection
LUJ: Chap 4 & 6
JBG: Chap 3
JES: Chap 3
JPS: Chap 2
OCAJ: Operators & Conditionals 		8/26: Lab 1 cont. 8/28: selection
LUJ: Chap 4 & 6
JBG: Chap 3
JES: Chap 3
JPS: Chap 2
OCAJ: Operators & Conditionals 		8/29: Selection: Guessing a number
9/01
Labor Day 		9/02: Lab 2 cont. 9/04: Repetition
LUJ Chap 5
LBG: Chap 3
JPS: Chap 2
JES: Chap 3 		9/05: Repetition: Factoring a number
9/8: Repetition
LUJ Chap 5
LBG: Chap 3
JPS: Chap 2
JES: Chap 3 		9/9: Lab 3 cont. 9/11: Repetition and Files
Class notes are the best because
most resources are doing I/O a different way 		9/12: Repetition and Files: Language quiz
9/15: Exceptions, Review
JUB Chap 9 		9/16: lab 4 cont. 9/18: Repetition: Counting Letters 9/19: CCSC:MW conference
Exam 1
9/22: Methods 9/23: Lab 5 cont. 9/25: Methods 9/26: Lab 5 cont.
9/29: Methods 9/30: Service Day 10/2: Methods 10/3: Methods: Better counting letters
10/06: Arrays 10/7: Lab 6 cont. 10/9: Fall Break 10/10: Fall break
10/13: arrays 10/14: Methods: Mastermind game 10/16: Exam 2 10/17: Lab 7 cont.
10/20: Programming Review 10/21: Lab 7 cont. 10/23: Arrays 10/24: Mastermind with arrays
10/27: Arrays 10/28: Lab 8 cont. 10/30: Secure Programming 10/31: Language Quiz redo with arrays.
11/03: Exam 3 11/04: Lab 9 cont. 11/06: Searching and sorting 11/7: Searching/Sorting Lab
11/10: Searching and sorting 11/11: Lab 10 cont. 11/13: Ethics 11/14: 2D Arrays: packing
11/17: Classes 11/18: Lab 11 cont. 11/20: Classes 11/21: Lab 11 cont.
11/24: Intro to Classes 11/25: Classes 11/27: Thanksgiving break 11/28: Thanksgiving break
12/01: Exam 4 12/02: Lab 12 cont. 12/04: Review 12/05: Lab 12 cont.
12/08: Finals Week 12/10: WEDNESDAYFinal Exam: 3:30-5:30 12/11: 12/12: Finals Week

Tentative Schedule

Monday Tuesday Lab Thursday Friday Lab
 
8/17: 8/18: 8/20: 8/21:
8/24: 8/25: 8/27: 8/28:
8/31: 9/01: 9/03: 9/04:

Revision 12026-04-17 - 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:
  • Office:
  • Class Time: 11:00-1:50am MF
  • Lab Time: 11:00-11:50pm TR
  • Class Location:
  • Textbook:

Course Content

Policies

Programs

Assignments

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

Monday Tuesday Lab Thursday Friday Lab
8/17: 8/18: 8/20: 8/21:
8/24: 8/25: 8/27: 8/28:
8/31: 9/01: 9/03: 9/04:
9/07: Labor day 9/06: 9/10: 9/11:
9/14: 9/15: 9/17: 9/18:
9/21: 9/22: 9/24: 9/25:
9/28: 9/29: Service Day 10/01: 10/02:
10/05: 10/06: 10/08: Fall Break 10/09: Fall Break
10/12: 10/13: 10/15: 10/16:
10/19: 10/20: 10/22: 10/23:
10/26: 10/27: 10/29: 10/30:
11/02: 11/03: 11/05: 11/06:
11/09: 11/10: 11/12: 11/13:
11/16: 11/17: 11/19: 11/20:
11/23: 11/24 11/26: Thanksgiving Break 11/27: Thanksgiving Break
11/30: 12/01: 12/03: 12/04:
12/07: Final 10:30-12:30pm 12/08: 12/10: 12/11:

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

AI Use Policy

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

Services

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
View topic | History: r3 < r2 < r1 | 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