CS355, Software Engineering
Fall Term, 2011 (3 credits), PHYS 204
Section 1, Wednesdays, 6:30-9:00p.m.
_____________________________________________________________________________
INSTRUCTOR: Dr. Cynthia J. Martincic
OFFICE: 202 Physics Building
PHONE: 724-805-2418 or x2418
EMAIL:cynthia.martincic@email.stvincent.edu
PREREQUISITES:
OFFICE HOURS: Mon., Wed. 10:00am -noon,
Tues., Thurs. 1pm-2pm,
Also by appt. or drop-in.
CS 111
COURSE DESCRIPTION:
This course examines the field of study within computer science known as “software engineering.” Software engineering is similar in some
regards to other engineering endeavors, but there are significant differences. This course will examine means of producing high quality
software, where high quality software is defined as software that is reliable, and reasonably easy to understand, modify and maintain.
Successful completion of this course will require participation in and the completion of a group project, and two exams and a
comprehensive final exam. Topics include both classical and object-oriented software engineering. Successful completion of this course
will require completion of assignments, a group project, short quizzes, and three exams. This is a Writing Designated course. This
semester’s offering of this course will require the completion of several documents, which should be written with the “Six Principles of
Good Writing” introduced in EL 101 in mind. See handout.
LEARNING OBJECTIVES AND ASSESSMENT:
Upon completion of this course the student should be able to describe:

What is encompassed by the field of study within computer science known as “software engineering.” Your understanding of this field
should include its past contributions, a sense of what is understood today about software development, and an overview of important
and promising areas of future research.

What is meant by a “software life-cycle”.

Particular techniques and tools that have been applied to software development, and the circumstances under which they may be more
or less appropriate.

How software projects are planned and managed.

How software process improvement can be achieved.
These objectives will be assessed mainly through a group project, three exams and individual assignments.
TEXT:
Object-Oriented and Classical Software Engineering.(2011) Stephen Schach, McGraw-Hill Publ. ISBN 978-0-07-337618-9
ADDITIONAL RESOURCES: Additional readings may be made available either by hard-copy in-class or files on the network drive for
this course. The content of the readings may be included on exams.
Although you are not required to do so, I recommend that you get a copy of Pocket Book of Technical Writing for Engineers and
Scientists(3rd Ed.) by Leo Finkelstein, McGraw-Hill Pub. ISBN 978-0-07-319159-1
GRADING:
Assignments, Projects and class participation will count for 50% of your grade. The exams count for the other 50%. The project is the
most significant portion of the other 50%. Peer assessment will play a major role in individual project grades. Because roles in the project
will vary throughout the term, peer assessment will be done towards the end of the semester.
The final grading scale may be curved at the discretion of the instructor, but in order to monitor your progress during the term, you should
assume the SVC grading scale as printed in the College Bulletin. Curved grades will result in a higher letter grade than that achieved solely
by the percentages above. For example, an earned ‘B’ may become a ‘B+’. The curve depends upon the performance of the class as a
whole as well as individual class participation and effort. The instructor reserves the right to increase a student’s final grade by up to 5
points in cases in which the student demonstrated efforts beyond the norm.
EXAMS:
There will be three exams, which, in total, will account for fifty percent of the final grade. Exams may cover any topics discussed in class,
in the text, in any additional readings and in the assignments. Exams must be taken when scheduled. No books, notes, electronic devices
or other assistance (including other people) are to be used during exams. Cell phones and pagers must be turned off during exams. Once an
exam has begun, you are not permitted to leave the room until you hand in the exam.
CS355, Software Engineering, Fall 2011
If any students miss one of the first two exams due to extreme verifiable circumstances, the average percent of the other exam and the final
will be used as the grade for the missed exam. No student should miss the final exam. (For a definition of “verifiable extreme
circumstances” see the Section labeled “DEFINITION OF EXTREME VERIFIABLE CIRCUMSTANCES”.) NOTE: Department policy
is that if a student does not attain a passing average in the exam category, that student will receive a failing grade for the course.
COURSE POLICIES:
In most cases, for this class, assignments involve answering questions, using Microsoft Project, Microsoft Visio and an application
development environment, and writing documents. All assignments should be created using the appropriate software. If handwritten, the
handwriting must be clear and legible. It is very natural for students to talk to and confer with other students when having problems with
an assignment. In fact, discussing problems with others is a great way to enhance learning. However, you must do your assignments on
your own except when group projects are explicitly assigned. If two (or more) assignments are unduly similar, they will be considered to
be in violation of the SVC Academic Honesty Policy, and will be treated as such under the guidelines of that policy. “Unduly similar” in
this case means that a prudent individual would reasonably conclude that the assignments were written/completed by the same person. The
first incident will be reported to the Dean of Students and the student(s) will receive only a percent of the value of the assignment or
question. The second incident will result in the student(s) receiving a failing grade for the course.
If you cannot attend a class: Assignments may be placed in the appropriate network drive or emailed to me if you cannot attend a class,
but will not be graded until a paper copy is submitted. The emailed assignment must be received before the start of the class when the
assignment is due and must be in the appropriate application format. The paper copy must be submitted by the next class period or no
points will be awarded for that assignment. Assignments should be emailed only in case of some emergency and emailed assignments will
not be accepted more than twice a term. Do not turn in any exercise or assignment on paper torn from spiral-bound notebooks or on any
size paper other than 8.5x11 inch. Multiple pages must be stapled or paper clipped together or no points will be awarded. For all
assignments and exams, illegible answers will not be graded and no points will be awarded.
Late assignments will only be worth 50% of the points originally assigned for the assignment if turned in within a week of the due date.
Assignments turned in later than one week will not receive any credit.
Students who are participating in sports are expected to follow the College Handbook procedures for excused absences from class and
exams.
Students with documented disabilities should meet with the instructor at the beginning of the semester to discuss reasonable
accommodations. Students with disabilities who require academic accommodations and support services should please consult Mrs. Sandy
Quinlivan. You may contact her by telephone (724-805-2371), SVC email or by scheduling an appointment in Academic Affairs (located
directly above the Post Office). Reasonable accommodations do not alter the essential elements of any courses, programs or activities.
Class attendance is most strongly recommended. Some classes will include in-class assignments, quizzes or computer lab work for which
points will be awarded. Additional points may be added to the final grade based upon class participation. If you miss a class, it is your
responsibility to get any notes, handouts and assignments. If a medical or sport excuse is provided, you will be given the opportunity to
make up missed in-class assignments or quizzes. After 2 unexcused absences, 1 point will be deducted from your final grade points
for each additional missed class.
Cell phones, pagers and beeping watches must be turned off during class and exams.
If a class or office hours must be canceled for any reason, I will try to contact each of you by email and will post an announcement on
BlackBoard as soon as I know of the cancellation. If assignments are due when a class has been canceled, they may be turned in at the next
class without penalty.
Everyone involved in this class is expected to treat others with respect. Respectful behavior includes minimizing distractions during class.
Playing computer games, updating your social networking status and other activities may be distracting. Cell phones, pagers, beeping
watches should be muted during class. If you have a need to keep a cell phone or pager on during class, please let me know.
Students should consult the CIS Department Policies webpage (http://cis.stvincent.edu/policies.html) for additional information regarding
course and department policies.
DEFINITION OF EXTREME VERIFIABLE CIRCUMSTANCES
Examples of extreme circumstances are serious illnesses or the death of a family member. Examples of non-extreme circumstances are
nonrefundable airline tickets, sporting events and concerts. Proof of the extreme circumstance will be required, such as a note from a nurse,
doctor or coach, or an obituary notice. This may seem rather insensitive and tactless, but some students’ excuses verge on the ridiculous
and unbelievable.
2
CS355, Software Engineering, Fall 2011
CS355 Course Syllabus, Fall 2011
(subject to modification as the term progresses)
Week Of
8/29
9/5
9/12
9/19
9/26
10/3
10/10
10/17
10/24
10/31
11/7
11/14
11/21
11/28
12/5
12/12
Readings*
Ch. 1 The scope of software engineering
Ch. 2 Software engineering concepts
Ch. 10 Key Material from Part A
Ch. 11 Requirements
 Monday – Labor Day. Does not affect this class.
Ch. 12 Classical Analysis
Handout on MS Project 2007
Ch. 13 Object-Oriented Analysis
Ch. 17 More on the UML
 Exam 1  Ch. 1, 2, 10, 12, 13
Ch. 14 Design
Ch. 15 Implementation and testing
 Monday and Tuesday – no classes – does not affect this class
Ch. 16 Postdelivery maintenance
Ch. 3 The software proecess
Ch. 4 Teams
 Exam 2  Ch. 13, 17, 14, 15, 16
 Registration for Spring begins Nov. 2
 Withdrawals receive “WF” starting Oct. 31.
I will be at a conference Nov. 3 through Nov. 6.
Ch. 5 Tools of the trade
Ch. 6 Testing
Ch. 7 From modules to objects
Thursday – Founders Day – classes cancelled 3:30-7pm – does not affect this class.
Wed., Thurs, Fri. – Thanksgiving Break – no class this week
Ch. 8 Reusability and portability
Ch. 9 Planning and estimating
Ch. 18 Emerging Technologies
Project Presentations
 Final Exam  comprehensive but mostly Ch. 3 – 9, 18
*Note: You will be expected to do the reading for each week prior to class each week.
3