CSC 450/CSC 300 – Intro. Software Engineering
This document is an adjunct to the CSC 450 Course Policy Statement.
Instructor: Dr. Peter Sanderson 203B Cheek Hall
Office Hours: 11-12 MW, 3:30-5 T'R, or by appointment.
Meeting Time: By arrangement.
Objective: The purpose of the Service Learning component is for students to provide software development computer system consulting services for a nonprofit or social service organization (hereafter referred to as the community partner). The software engineering practices studied in CSC 450 will be applied to a real-world software development situation, providing a valuable learning opportunity.
Grading Policy: You will receive separate grades for CSC 450 and CSC 300. The grading policy for CSC 450 is in its (separate) course policy statement. Your grade for CSC 300 will be based on: (a) completion of 40 hours of service, (b) feedback from the community partner and CASL administrators, and (c) a series of written reports submitted on specified dates. Part (a) does not affect your grade unless you fail to meet it (see Attendance, below). Part (b) is 20% of your grade and is based on the On-Site Visit report plus the Student Evaluation Form submitted by the community partner. I will translate the ratings and comments into an appropriate numerical score in the range 0-100. Part (c) is the remaining 80% of your grade; each report carries the same weight and is assigned a score in the range 0-100 (see Project Requirements, below). Your grade will be based on the average score according to a 90-80-70-60 scale, subject to completion of the required 40 hours.
Attendance: You are required to complete 40 hours of service above and beyond the time required for your CSC 450 term project. If this requirement is not met, you will receive a failing grade for CSC 300. This is nonnegotiable. You are also required to attend an orientation program prior to beginning your service. Time you spend at the orientation counts as part of the required 40 hours. You are responsible for periodically reporting your hours on a signed time sheet.
Details will be provided at the orientation meeting, which will be held Monday August 30 from 4-5 PM in Plaster Student Union room 3 12. It will be repeated at the same time and place on Tuesday August 3 1. You need attend only one of the two meetings. The Citizenship and Service Learning office is located at 318 Carrington.
Project Requirements: We will determine the Service Learning project during the first three weeks of class. Your input is always appreciated. The project will take one of two forms: either develop a software system, or provide computer consulting services. The former will be a team activity and the latter an individual activity.
If your project is to develop a software system, you will be working as part of a team and the project will serve as your CSC 450 term project. Ideally, members of the team will be Service Learning participants. In addition to fulfilling all the CSC 450 project requirements, you will be expected to submit a series of reports describing your Service Learning experience. I will provide details once the project and set of deliverables is determined. Expect the hours of service to be distributed unevenly through the semester; much time will be spent in the early part of the project becoming familiar with the organization and their software requirements. Specific instructions and guidelines will be provided at the beginning of the project.
If your project is to provide computer consulting services, you will be expected to periodically submit a written report concerning your consulting activities. I will provide specific instructions at the beginning of the project.
The Service Learning course web page is: www.cs.smsu.edu/-pete/csc300
CSC 450 Course Policy Statement – Fall 1999
Instructor. Richard Martin
Office: 201A Cheek Hall
MONDAY 9:00-10:00 TUESDAY NONE
WEDNESDAY1:00-2:00 THURSDAY 1:00-2:00
(other hours by appointment)
Catalog Course Description: Prerequisite: CSC 325. Principles, techniques and tools used to effect the orderly production of medium and large-scale computer programs will be studied. These techniques will be applied to programming projects with students working in teams and managing all phases of a programming project.
Attendance: It is to your advantage to attend class. Completing Problem of the Day exercises on five randomly chosen days will encourage attendance and participation. Late arrival and early departure is discouraged as rude to your fellow computer scientists. It is your responsibility to obtain information presented in your absence.
Academic Honesty: The University has published policies concerning plagiarism, cheating and responsible use of computer resources. See "'Student Rights and Responsibilities"' in the Undergraduate Catalog or check the World Wide Web. Violation of these may result in a failing grade for the course. On assignments or projects assigned to you as an individual, you may discuss design techniques with others, but must work as an individual when the coding stage begins, including hand-written code. Blatant copying of individual assignments will result in zero credit among the persons involved for a first offense and an F in the course thereafter.
Textbooks: The textbook Software Engineering, 5th edition by Ian Sommerville is required.
Computer Use: If you use any University computer then the University·s Policy and Ethics bind you for Computer Use. Any violation of these policies may result in University disciplinary actions.
Midterm exam 10%
Assignments (individual) 25 % (at least 5)
Project (group) 45%
Final exam (Comprehensive) 15%
Problems of the Day 5% (5 days)
For the purposes of determining a grade for the course, the grades from exams, assignments, and projects will be combined as shown above. The course grade will be determined by 90% and above 4 =A, 80% and above = B, 70% and above = C, 60% and above = D, below 60 = F. The numeric requirements for letter grades may be lowered to reflect a curve but will not be raised.
Examinations: Exact dates for exams will be announced in class at least one week prior to the test. The final exam will be comprehensive, and will be on Tuesday, Dec. 14 at 1:15 p.m. – only prior arrangement or exceptional circumstances may make up 3:15 p.m. Missed exam(s) may be made up by prior engagement or exceptional circumstances.
Homework Assignments: Homework will be an assortment of pencil-and-paper and programming problems, and each will have specific instructions on what to turn in. Each assignment will be graded on a 0… 100 scale. Assignments may be turned in late* with a penalty of 10% of the total per calendar day.
Projects: The project will be broken into components, each with its own due date and grade weighting (details later). Components (other than oral presentations) may be turned in late with a penalty of 20% (twenty) per calendar day.
Disability Accommodation: SMSU makes reasonable accommodations for students with disabilities. Please see the instructor.
Nondiscrimination: SMSU is an Equal Opportunity/ Affirmative Action institution. For more information contact Affirmative Action Officer, Office of Human Resources, Southwest Missouri State University, Carrington Hall 128, Springfield, Missouri 65804.
Professor: Dr. Peter Sanderson, Richard Martin
Videos & Presentations
Designing & Delivering a Service-Lea
Connect2Complete Resource Guide
SEMINAR: Dialogue, Discourse, Identity a
More Syllabi Archive
SEMINAR: Dialogue, Discourse, Identity a
Educational Policy – Community Par
Educational Policy – Community Pro