CSE308/ISE308: Software Engineering
Fall 2002
Scott Stoller

Other CSE308/ISE308 Pages

Discussion Forum (uses BlackBoard)     (here are Login Instructions for BlackBoard)

Contents of this Page

Course Description
Computers and Accounts
Discussion Forum
Exam Guidelines
Grading Policies
Grading Statistics
Grading Weights
Submission of Assignments
Useful Links
What I Did


SolarSystem Data: Catalog number: 308. Course ID: 203294. Class Number: 3864 for CSE308, 3097 for ISE308. Section: 01 (for CSE308 and ISE308). Term (Fall 2002): 1028.

Instructor: Scott Stoller

TAs: Aili Li, Meher Medida, Arun Ramasamy

Class: Tuesday and Thursday, 8:20am-9:40am. Harriman Hall 137.

Scott's Office Hours: Monday, 1:50pm-2:50pm; Wednesday, 9am-10am. Computer Science 1429.
Aili's Office Hours: Friday, 12pm-2pm, Computer Science 2110.
Meher's Office Hours: Wednesday, 10am-11am, and Thursday, 1pm-2pm, Computer Science 2110.
Arun's Office Hours: Monday and Friday, 9:30am-10:30am, Computer Science 2110.

Course Description

This course covers fundamental topics in software engineering, with an emphasis on requirements and design using the Unified Modeling Language (UML). The main topics are:

There are two "required" textbooks:

Shari Lawrence Pfleeger. Software Engineering: Theory and Practice, 2nd Edition. Prentice-Hall, 2001. ISBN 0-13-029049-1
Perdita Stevens and Rob Pooley. Using UML: Software engineering with objects and components, updated edition. Addison-Wesley, 2000. ISBN 0-201-64860-1
One copy of each book is on 2-hour reserve in the computer science library. You will find it convenient to have both. If your budget limits you to purchasing only one of them, you're probably better off buying the UML book. Note the exam guidelines. The exam will primarily cover UML-related topics but will contain some questions on other topics as well.

Computers and Accounts

You will have access to the computers in the Transaction Lab (Rooms 2126 and 2114).

Information about Account Names and Passwords.

Discussion Forum

The two best ways to get answers to your questions are to post your questions to the discussion forum on Blackboard or come to office hours of the instructor or a TA. If we receive by email a question that apparently should have been asked in one of these two ways, we will simply return your message with the comment "Please post to the discussion forum, come to office hours, or explain why this question is best asked by email".

The advantages of the discussion forum compared to email are: (1) you are more likely to get a prompt response, since the the instructor, the T.A.s, and your classmates all read the discussion forum; and (2) your classmates benefit from seeing all of the questions and answers. If you see a question and know the answer, post it! This shows us that you know what's going on, and it helps your classmates.

The advantages of face-to-face communication (during office hours) compared to email are: (1) almost everyone can talk much faster than they can type, and your hands are much more likely to get repetitive stress injuries than your jaw; and (2) fully clarifying an issue often requires a few rounds of question-and-answer, which can be completed in 5 minutes of conversation but drag on for days when done by email.

To access the discussion forum, (1) click on the link to Blackboard near the top of this page, (2) login, (3) click on cse308, (4) click on Communication (on the left side of the page), (5) click on Discussion Board, and (6) click on General Discussion.

Exam Guidelines

During exams, you may use the course textbooks, your own notes, original printouts or copies of your team's homework assignments, handouts that were distributed in class or posted on the course web page, and a dictionary. You may not use someone else's notes or other teams' homework assignments or mechanical reproductions of all or part thereof. You may not use other textbooks or mechanical reproductions of all or part thereof. You may not use computers (laptop, PDA, etc.).

The instructor may look at materials that students are using during the exam to ensure that these guidelines are being followed. Violations will result in a score of zero on the exam and will be reported to CEAS's Committee on Academic Standing and Appeals (CASA).

Missing an exam is a serious problem. If you miss an exam, you need to have a very strong reason substantiated with convincing evidence (for example, an invoice from the doctor or hospital), otherwise you will get a zero on the exam.

Grading Policies

If you have questions about the grading of an assignment, first see the T.A. who graded it, preferably during their office hours. This helps ensure consistency of grading. The name of that TA should be written on the graded assignment. If you still have questions after talking to the TA, then come talk to the instructor.

Each assignment is graded relative to some maximum number of points (e.g., 20 or 100). The maximum number of points is unrelated to the weight of the assignment in the course grade. Each score is normalized into a number between zero and one (e.g., 19/20 -> 0.95) and then multiplied by the weight of the assignment to obtain a weighted score. Course grades are based primarily on the sum of the weighted scores.

Each assignment submitted by a team (as opposed to an individual) will receive a score reflecting the quality of the work. At the end of the project, each team member's score for that assignment will be computed, by multiplying that score by an individual contribution factor (ICF) that reflects the team member's overall contribution to the team effort for the entire project. Ideally, every team member will contribute equally to the overall effort. In that case, every team member gets an ICF of 1, and every team memver receives the same scores for all team assignments. If some team member's overall contribution was, for example, only 90% of what was expected, then that team member's score for each team assignment will be computed by multiplying the original score for the assignment by that member's ICF of 0.9. A team member who contributes more than his or her fair share will get an ICF larger than 1. We will evaluate each team member's contribution using all available information, including the "What I Did" sections of homeworks, the summary of contributions in the complete project, and discussions during project meetings and demos. Everyone is encouraged to keep track of their contributions carefully throughout the semester.

Each team member is responsible for ensuring that he or she contributes. If you believe that your teammates are preventing you from contributing, discuss the situation with the instructor immediately; if you wait until near the end of the project, it will be too late to remedy the situation, and you will receive low scores for the project.

Grading Statistics

The following information may be slightly inaccurate, due to score adjustments, late submissions, etc.

Item Out Of Mean Std.Dev. Histogram
hw0 40 39.2 3.0
hw1 75 65.5 10.5
hw2 120 94.8 22.5
hw3 90 77.9 10.9
hw4 80 71.6 7.6
hw5 20 19.5 1.2
hw6 100 97.1 5.0
exam 100 79.0 13.4 histogram
hw7 100 100 0
hw8-avg 5 2.95 1.2
hw9-documentation 100 103.0 9.1
hw9-implementation 100 101.8 9.2
presentation 100 92.8 3.7
ICF N/A 1.01 0.19

hw8-avg is the average for hw8.1-hw8.8. If you did not submit a hw8.x, your score for that hw8.x is a zero in computing this average.

Grading Weights



All students are expected to follow CEAS's
policies governing academic dishonesty. Suspected academic dishonesty will be reported to CEAS's Committee on Academic Standing and Appeals (CASA).

If your submission includes any material (text, diagrams, code, etc.) created by other people, your submission must clearly indicate the sources of such material. Failure to indicate the sources will be treated as plagiarism.

Discussing assignments with other people is fine. However, each person (or team, as appropriate) must write its own submission independently. This applies to all submitted materials: text, diagrams, code, etc. Showing your own (or your team's, as appropriate) work to other students (or members of other teams, as appropriate), giving it to them, or making it accessible to them (e.g., by making the files world-readable, whether intentionally or through carelessness) will be treated as academic dishonesty.

Submission of Assignments

All assignments should be submitted as printouts in class on the due date, unless the assignment specifies otherwise. Assignments submitted after the end of class on the due date are late and receive a -3% penalty. Assignments submitted the next day receive a -6% penalty, and so on.

Useful Links

OMG UML Resource Page
Java 1.3 Documentation
Java 1.4 Documentation

What I Did

Summary of cse308's "hwn: what I did" mail folder

If you are concerned about the reliability of email, you can check whether we received your "what I did" messages by looking for them in the above mail folder summary, which is updated once a week, on Mondays.

Students with Disabilities

The Provost requires that the following statement be included in syllabus handouts:
If you have a physical, psychological, medical or learning disability that may impact on your ability to carry out assigned course work, I would urge that you contact the staff in the Disabled Student Services office (DSS), Room 133 Humanities (moved to ECC Bldg during renovation of Humanities), 632-6748/TDD. DSS will review your concerns and determine, with you, what accommodations are necessary and appropriate. All information and documentation of disability is confidential.