Spring 2000, CSC 242 00 2, TF 1:00-2:15 PM, Curtis 104

Norm Lippincott, Curtis 105, 610-606-4666 ext. 6197

Mon. 10-11; Tues. 3-6; Wed. 10-11, 1-3; Fri. 10-11.

Cormen, Leiserson, & Rivest; Introduction to Algorithms, McGraw Hill, 1990.

A study of the principles of production and management of software products for computer systems. Topics include analysis of system requirements, techniques and tools for software design, user interfaces, reliability, verification and validation. The use of CASE tools and the software lifecycle will be emphasized. Various professional and ethical issues important for the software engineer also will be discussed. Prerequisite: Programming experience in a high-level language.

The grade for the course will consist of five components weighted as follows:

Project 60%

Tests (2) 20%

Final Exam 15%

Class Participation 5%

During the semester each student will participate in a software engineering project. These projects will be done in groups of 3 or 4 students. Each group will work on a single project for the duration of the semester, with several deliverables throughout the semester. A project will be proposed by each group, and the project may be real world or hypothetical. The project grade will consist of seven components weighted as follows: Requirements Definition, Conceptual Design, Technical Design, Test Plan, and User’s Manual documents, 12% each; final system, 15%; presentations and group participation, 25%.

The tests and final exam will be written and may include problems, short answer questions, and essays. The final exam is comprehensive.

A final grade percentage will be computed according to the weights above and rounded to the nearest full percent. Final grades will be awarded as follows:

93-100 A 77-79 C+

90-92 A- 73-76 C

87-89 B+ 70-72 C-

83-86 B 67-69 D+

80-82 B- 60-66 D

0-59 F

Date Topic / Reading List

1/18 Course Introduction

1/21, 1/25 Ch. 1 – Why Software Engineering?

1/28, 2/1 Ch. 4 – Capturing the Requirements

2/4, 2/8 Ch. 2 – Modeling the Process and Life Cycle

2/11 Presentations – Requirements Definition

2/15, 2/18, 2/22 Ch. 5 – Designing the System

2/25 Presentations – Conceptual Design

2/29 Test 1 – Chapters 1, 2, 4, 5

3/3, 3/14 Ch. 6 – Writing the Programs

3/17 Presentations – Technical Design

3/21, 3/24 Ch. 7 – Testing the Programs

3/28, 3/31 Ch. 8 – Testing the System

4/4, 4/7 Ch. 3 – Planning and Managing the Project

4/11, 4/18 Ch. 9 – Delivering the System

4/14 Test 2 – Chapters 3, 6, 7, 8

4/28 Ch. 10 – Maintaining the System

5/2, 5/3 Final Project Presentations

TBA Final Exam

This schedule is to be used as a guideline for the reading required for the class. You should read the class material in advance of coming to class. This course schedule is subject to change.

Due on

Project Proposal 1/25

Requirements Definition 2/15

Conceptual Design 2/29

Technical Design 3/21

Test Plan 4/4

User’s Manual 4/28

System Delivery 5/3

Attendance will be taken for each class, however record of attendance does not directly affect the student’s grade. The student is responsible for all material covered in class. If a student has excessive absence and is not showing responsibility for the course material, an academic performance notice will be issued to the Advising Center. If a student will be absent on the day of a test, arrangements for a makeup must be made in advance of the test. Failure to do so will result in a grade of zero for the test.

Assignments and projects are due at the beginning of class on the day they are due. By turning in assignments on time your work will be graded and returned in a timely manner (usually by the next class meeting), and with comments as appropriate.

Work turned in late will be subject to any or all of the following:

1. A 1 point penalty (on a scale of 10) will be assessed; 2 points if work is a week late or more.
2. The assignment may be graded without comment.
3. The assignment will be graded and returned at the instructor’s convenience, possibly as late as the end of the semester

The Cedar Crest College Student Handbook, Honor Philosophy (pp. 10-12) part III, Community Standards for Academic Conduct, includes the following:

"As a student at Cedar Crest College, each student shall:

• Only submit work which is his/her own.
• Adhere to the rules of acknowledging outside sources, as defined by the instructor, never plagiarizing or misrepresenting intellectual property.
• Neither seek nor receive aid from another student, converse with one another when inappropriate, nor use materials not authorized by the instructor."

Unless specifically designated by the instructor, assignments for this course are individual assignments, not group projects. It is reasonable and appropriate for students to discuss an assignment outside of class, particularly for programming projects. However, the actual assignment work, whether programming or written, is to be one’s own. It is not appropriate to collaborate on programming assignments, nor is it appropriate to copy another student’s program, alter the program’s appearance (e.g. changing formatting, variable names, output text), and present it as your own individual work. Evidence of such behavior will be considered a violation of the Honor Philosophy and will result in a grade of zero for the assignment. A second offense will result in a grade of "F" for the course.

Appropriate classroom behavior is implicit in the Cedar Crest Honor Code. Such behavior is defined and guided by complete protection for the rights of all students and faculty to a courteous, respectful classroom environment. That environment is free from distractions such as late arrivals, early departures, inappropriate conversations and any other behaviors that might disrupt instruction and/or compromise students’ access to their Cedar Crest College education.