CSE308.01/ISE308.01: Software Engineering (Fall 2009)
Scott D. Stoller

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:

The course objectives are: (1) Introduce models of software development and methodologies for project planning, requirements analysis, and system/test design; (2) Provide experience in working as a team to produce software systems that meet specifications while satisfying an implementation schedule; (3) Train students to produce professional quality oral/written presentations of system designs, reviews, and project demonstrations; (4) Expose students to ethical issues in software design and computing in general.


Simon Bennett, John Skelton, and Ken Lunn, Schaum's Outline of UML, 2nd edition, McGraw-Hill, 2004. A copy is on 24-hour reserve in the Science and Engineering Library, but I strongly encourage you to get a copy of your own. Bring it to class (for use during in-class exercises)! Bring it to the open-book exam! Bring it to your team meetings! It will be very helpful in all those cases. Other UML books are OK, too, but I recommend this one for its thorough coverage, abundant examples, and low price. There are some decent on-line UML resources, such as Allen Holub's UML Quick Reference and OMG's UML Resource Page, but they are useful as supplements, not substitutes, for a good UML book like this one.

Scott W. Ambler. Mapping Objects to Relational Databases: O/R Mapping In Detail.

Most software engineering textbooks are fine as a reference for the material on software process models. Feel free to use any of them. Two examples are: Shari Lawrence Pfleeger, Software Engineering: Theory and Practice (on 2-hour reserve in the library), and Ian Sommerville, Software Engineering.


Assignments and Course Documents are posted in Blackboard.

I also use Blackboard to send email to the class, so make sure that your email address in Blackboard is up-to-date.


Class Time: Tue and Thu, 9:50am-11:10am.
Location: Heavy Engineering 201

Office Hours: Monday, 11:00am-12:30pm, and Wednesday, 10:30am-noon, in Computer Science 1429. Also by appointment, and when I am in my office and not unusually busy.

Graduate Teaching Assistant: none
Undergraduate Teaching Assistant: Hung Ngo (Michael) Wu
Office hours: Time TBD. In Computer Science 2110.


Grading. Each assignment is graded relative to some maximum number of points (e.g., 20), which 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. The weights are as follows.


Grading of Teamwork. Each project assignment receives a score reflecting the quality of the work. At the end of the semester, each team member's score for that assignment is 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 semester. Ideally, every team member will contribute equally to the overall effort. In that case, every team member's ICF is 1. A team member who contributes less than his or her fair share will have an ICF less than 1; a team member who contributes more than his or her fair share will have an ICF larger than 1. Everyone should keep track of their contributions throughout the semester. We will evaluate each team member's contributions using all available information, including the team evaluations described next.

Students will periodically evaluate the contributions of all team members to the project. When a student's contribution is significantly below the team's expectations, the student's ICF may be reduced, and in severe cases, the student may be removed from the team. A student removed from a team must complete the remaining assignments as a one-person team.

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.

Submission of Assignments. All assignments (except team evaluations) must be submitted in two ways (yes, both): (1) Submit a printout of the specified material in class on the due date, and (2) Submit an electronic version of the specified material on Blackboard by 11:59pm on the due date, using the appropriate "View/Complete Assignment" link. The printout can also be submitted at the instructor's office (slide it under my door if I am not there) by the end of class on the due date. Any team member can submit the electronic version on Blackboard, but please coordinate so that exactly one team member submits it. If the printout or the electronic version is submitted late, then the assignment is considered to be submitted late, and a lateness penalty may apply. The first page of every printout should contain the team name, section number, and names of all team members. The name of every file uploaded to blackboard should contain the team name (e.g., Dream-Team-hw5.zip).

Team-evaluations must be submitted on Blackboard by 11:59pm on the due date, using the appropriate "View/Complete Assignment" link.

Late Submissions. Assignments submitted after the deadline and within 24 hours of it receive a -3% penalty. Assignments submitted within the next 24 hours receive a -6% penalty, and so on. I am generally not too strict about this if one or two assignments are submitted a few hours late, but chronic offenders and significantly late assignments will be penalized. For assignments that involve presentations (design review, code review, and demo), the penalties are strictly enforced and may be larger (typically 4% per day).

Exam. The exam will cover UML. During the exam, you may use your own notes, printouts of your team's assignments, any software engineering textbook, any book on UML, and printouts of any on-line UML resources. You may not use copies of other people's notes or other team's assignments. Although you are permitted to bring printouts of all of your team's documentation, in the interest of saving trees, I encourage you to bring printouts only of your team's UML diagrams; other material won't be useful. You may not use electronic devices (computers, PDAs, cell phones, etc.) during the exam. Do not miss the exam: make-up exams will be given only in extenuating circumstances (e.g., doctor's note stating that you were ill and unfit to take the exam).

Academic Integrity. In Fall 2006, the Undergraduate Council adopted the following statement and mandated that it be included in all undergraduate course syllabi.

Each student must pursue his or her academic goals honestly and be personally accountable for all submitted work. Representing another person's work as your own is always wrong. Any suspected instance of academic dishonesty will be reported to the Academic Judiciary. For more comprehensive information on academic integrity, including categories of academic dishonesty, please refer to the academic judiciary website at http://www.stonybrook.edu/uaa/academicjudiciary/
If your team submits anything that includes any material created by other people, your team's submission must clearly indicate the sources of that material, otherwise it is plagiarism. Discussing assignments with other people is fine. However, each team must write its own code and documentation independently. Showing your team's code or documentation to other students, giving it to them, or making it accessible to them will be treated as a suspected instance of academic dishonesty.

Disabilities. The Provost requests that the following information be included in the syllabus for every course. If you have a physical, psychological, medical or learning disability that may impact your course work, please contact Disability Support Services, 128 ECC Building (631) 632-6748. They will determine with you what accommodations are necessary and appropriate. All information and documentation is confidential. Students who require assistance during emergency evacuation are encouraged to discuss their needs with their professors and Disability Support Services. For procedures and information go to the following web site: http://www.ehs.sunysb.edu and search Fire Safety and Evacuation and Disabilities.

Critical Incident Management. Stony Brook University expects students to respect the rights, privileges, and property of other people. Faculty are required to report to the Office of Judicial Affairs any disruptive behavior that interrupts their ability to teach, compromises the safety of the learning environment, or inhibits students' ability to learn.

Transaction Lab

Transaction Lab is in rooms 2114 and 2126 of the Computer Science building. Information about Transaction Lab Accounts

If you need to quickly set up an account, please go to room 1309. You will need to provide the CS Systems staff with a student ID and an e-mail address. An e-mail will be sent to you when the account is ready.

File Sharing

Every team is strongly encouraged to use a version control system, such as CVS or Subversion, to manage its project files. Netbeans and Eclipse both support CVS. Or you can use a stand-alone CVS client, such as TortoiseCVS or a command-line version of cvs (e.g., from the cygwin distribution).

A SVN sever is being set up in the Transaction Lab. Details should be available soon.

If your team would like a repository on the Transaction Lab's CVS server, send a request containing the team name and the names and SBU ID numbers of all team members to the instructor, and a repository will be created within a few days. You can then access your team's repository using your Transaction Lab username with your Stony Brook ID as the password. Here are Instructions for Accessing Repositories on the Trans Lab CVS Server.

Database Server

You may use any DBMS for the project. You may run the DBMS yourself, or you may use one of the Transaction Lab's DBMS servers. If your team would like an account on the Transaction Lab's MySQL server or Oracle server, send a request containing the team name and the names and SBU ID numbers of all team members to the instructor, and an account will be created within a few days. For information on using the Transaction Lab's DBMS servers, see the instructions available via the Transaction Lab home page.

Integrated Development Environment

Every team is strongly encouraged to use an Integrated Development Environment (IDE) for software development and debugging. Eclipse and Netbeans are available in the Transaction Lab and can be installed on your own computer.

UML Tools

IBM Rational Software Architect: the market-leading UML-based model-driven development tool. You can use it to draw UML diagrams, generate Java code for interfaces and classes from UML class diagrams, reverse-engineer from code to UML diagrams, etc. I encourage you to try it, despite the learning curve, because it is powerful and widely used. It is installed in the Transaction Lab. A set of 2 DVDs containing the software is available in the North Reading Room of the Melville Library; you can borrow the DVDs and install the software on your own computer. If the person working at the checkout counter doesn't know where these DVDs are, tell them the DVDs are in the rack of "personal copy" discs on top of the taller filing cabinets along the back wall behind the checkout counter. IBM Rational Software Modeler is basically a subset of IBM Rational Software Architect; it is installed in the Transaction Lab and available on DVD from the same place (if your computer has less than 1GB RAM, I suggest you use Software Modeler, otherwise use Software Architect). Other DVDs available from the same place contain IBM Rational Data Modeller, a visual modeling and development environment for database applications, and IBM Rational RequisitePro, a requirements management tool.

Netbeans UML Plugin: This plugin supports drawing most kinds of UML diagrams (Activity diagram, Class diagram, Sequence diagram, State diagram, and Use Case diagram, but not Communication diagram) and forward and reverse engineering.

ArgoUML: an open-source UML modeling tool. It's written in Java, so you must install a Java Run-time Environment (JRE), such as Sun's JRE, before installing ArgoUML.

StarUML: an open-source UML modeling tool. Runs on Windows only.

Diagramming Tools

You are encouraged to use one of the above UML tools to create UML diagrams. You could use one of the following diagramming tools instead. These tools present less of a learning curve when you get started, but they have some disadvantages, namely, they cannot generate code from class diagrams, and they do not check consistency of the diagrams. For example, a UML modeling tool can check that a method used in a sequence diagram is also declared in the appropriate class diagram; a diagramming tool cannot do this.

Microsoft Visio: a diagramming tool, with a library of UML shapes. Visio is available in the Transaction Lab and is available for download through MSDNAA.

Dia: an open-source diagramming tool, with a library of UML shapes.

Microsoft PowerPoint and OpenOffice Draw: These tools can be used to draw UML diagrams, but less conveniently, because they lack libraries of UML shapes, as far as I know.

Lecture Material

The lectures contain material from the Readings listed above and the following books.