| |
| META TOPICPARENT |
name="SyllabiSpring2024" |
CSC 221: Programming 2: Design and Object-Oriented Programming 1: 3 hours
Description
Description
A continuation of Programming 1. Students learn to design more complex larger object-oriented programs. Also includes graphical, event, and concurrent programming.
Goals for CSC 221 are:
- Write non-trivial programs on their own
- Understand and use OO program concepts well
- Improve the security of their program
- Understand the basics of multi-threaded programming
Course outcomes for CSC 221 are:
- Upon complete of CSC 221, students will:
- be able to design and code complex multi-object programs.
- be able to develop graphics based interfaces for programs
- understand the fundamentals of event and concurrent programming.
- understand the fundamentals of additional programming tools and environments including source code version software
Program outcomes for CSC 221 are:
- Analyze a complex computing problem and to apply principles of computing and other relevant disciplines to identify solutions. (Computing student learning outcome 1)
- 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)
- Communicate effectively in a variety of professional contexts. (Computing student learning outcome 3)
- Recognize professional responsibilities and make informed judgments in computing practice based on legal, ethical, and moral principles. (Computing student learning outcome 4)
- Function effectively as a member or leader of a team engaged in activities appropriate to the program’s discipline. (Computing student learning outcome 5)
- Learn new areas of technology. (Computing student learning outcome 6)
- Apply computer science theory and software development fundamentals to produce computing-based solutions. (Computer Science student learning outcome 1)
- Support the delivery, use, and management of information systems within an information systems environment. (Computing and Information Systems student learning outcome 1)
- Apply security principles and practices to maintain operations in the presence of risks and threats. (Cyber Security student learning outcome 1)
Integration
- Self-learning at the introductory level by having some programming assignments that include using some simple features not covered in class
- Note taking at the introductory level by not posting lecture notes and holding students responsible for the content.
- Technical writing at the application level by requiring students to do a formal software development report and requiring quality writing (and grading the quality of the writing), Also by the end of the semester by refusing to accept reports that don't meet a bare min. standard (such as standards, spell check, using bullet lists as appropriate.
- Team work at the introductory level by having at least two assignments where students are working in teams
- Professionalism at the introductory level by having students estimate how long it takes to write programs and then analyze their estimate based on how long it actually took. They will also comment on what they learned and what they would want to to better with a program if they could.
- 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).
- Ethics at an introductory level by having at least one program assigned that could have ethical implications and having the students discuss that in their reports.
|
| |
-
- 60% <= average < 63% -> D-
- 0% <= average < 60% -> F
|
|
< < | Tentative Schedule (needs fixing) (Swap Thursdays and Fridays) |
> > | Tentative Schedule (needs fixing) (Swap Thursdays and Fridays first two weeks)) |
| |
| Monday |
Tuesday Lab<-- --> |
Thursday Lab |
Friday |
| 1/8 |
1/9 |
1/11: Class begin Coding review Lab |
1/12: Testing IST: Chapters 2 & 5 |
| 1/15: School closed: Weather |
1/16: CR cont. |
1/18: Testing design lab |
1/19: Objects WGC: Chapter 6 |
| 1/22: Objects |
1/23: TD cont. |
1/26: Objects |
1/27: Testing code lab |
|
|
< < |
| 1/29: GUI |
1/30: TC cont. |
2/1: |
2/2: |
| 2/5: Exam 1 |
2/6: |
2/8: |
2/9: |
| 2/12: |
2/13: |
2/15: |
2/16: |
| 2/19: |
2/20: |
2/22: |
2/23: |
| 2/26: |
2/27: |
2/29: |
3/1 |
|
> > |
| 1/29: GUI |
1/30: TC cont. |
2/1: GUI |
2/2: Object design lab |
| 2/5: Review |
2/6: Object design Lab |
2/8: GUI |
2/9: Object coding lab |
| 2/12: Exam 1 |
2/13: Object coding Lab |
2/15: Secure programming |
2/16: GUI design lab |
| 2/19: Secure Programming |
2/20: GUI design lab |
2/22: Inheritance |
2/23: GUI Coding lab |
| 2/26: Inheritance |
2/27: GUI Coding lab |
2/29: exam 2 |
3/1: Inheritance design lab |
|
| |
| 3/4: Spring Break |
3/5: Spring Break |
3/7: Spring Break |
3/8: Spring break |
|
|
< < |
| 3/11: |
3/12: |
3/14: |
3/15: |
| 3/18: |
3/19: |
3/20:SIGCSE |
3/21: SIGCSE |
| 3/25: |
3/26: . |
3/28:Easter Break |
3/29: Easter Break |
| 4/1: |
4/2: |
4/4: |
4/5: |
| 4/8: |
4/9: |
4/11: |
4/12: |
| 4/15: |
4/16: |
4/18: |
4/19: |
| 4/22: Classes |
4/23: |
4/25: |
4/26: |
|
> > |
| 3/11: Inheritance |
3/12: Inheritance design lab |
3/14: Linked lists |
3/15: Inheritance coding lab |
| 3/18: Linked lists |
3/19: Inheritance coding lab |
3/20:SIGCSE Exam 3 |
3/21: SIGCSE Inheritance coding lab |
| 3/25: Concurrency |
3/26: Linked list lab . |
3/28:Easter Break |
3/29: Easter Break |
| 4/1: Concurrency |
4/2: Linked list lab |
4/4: Concurrency |
4/5: Concurrency design lab |
| 4/8: Programming languages |
4/9: Concurrency design lab |
4/11: Programming languages |
4/12: Concurrency code lab |
| 4/15: Exam 4 |
4/16: Concurrency code lab |
4/18: Assembly language |
4/19: Project lab |
| 4/22: Assembly language |
4/23: Project lab |
4/25: Compilers |
4/26: Project lab |
|
| |
| 4/29: Finals Week |
4/30: Finals Week |
5/2: Finals week |
5/3: Finals week |
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.
- 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.
- If a second offense should occur, the student will be asked to appear before the professor, the academic dean and the vice president for student development.
The student should realize that at this point continuation in a course and even his/her academic career may be in jeopardy. In the event of a recommendation for dismissal, the matter shall be referred to the Student Development Committee.”
Services
The Americans with Disabilities Act (ADA) is a law which provides civil rights protection for people with disabilities. Bethel University, in compliance with equal access laws, requests that students with disabilities seeking to acquire accommodations make an appointment with the Center for Academic Success—Disability Services. It is located in the Miller-Moore Academic Center, 033. You may also phone 574-807-7460 or email rachel.kennedy@betheluniversity.edu for an appointment.
Education Majors:
Please use the link below to review all appropriate standards.
Standards
\ No newline at end of file |