RU ENG ECE 16:332:567
Software Engineering I

PDF document of the lecture notes (software engineering book) is available here   PDF icon

Fall 2014


Lecture Schedule and Projects

Ivan Marsic
Office hours:  Friday 1:30 – 2:30 p.m.
Room 711, CoRE Building
Phone: (848) 445-6399

( Appointments other than office hours have to be requested by email with the subject of appointment explained. )

Gabriel Salles-Loustau
Office hours:  Monday and Wednesday 9:00 a.m. – 10:00 a.m.
Room EE-118
Phone: ___

Fridays: 3:20 - 6:20 p.m. in   SEC-202

Course Description:
This is a graduate course in software engineering. The key objective of this course is to learn modular design of software and documenting the design using symbolic representations, i.e., UML diagrams. The course will cover software life-cycle models and different phases of the software development process.
Object-oriented techniques are key to the course. Since the ultimate result of software engineering is a working software package, the course will put a great emphasis on developing a demonstrable software package. However, this is not a programming course.
The key characteristic is having teams of about five students work on a semester-long project. The grading is competitive, with the highest rated project receiving the highest grade and the others being rated relatively to the highest one.

Russ Miles and Kim Hamilton:   Learning UML 2.0
Reilly Media, Inc. 2006.
Book information at:
ISBN-10: 0596009828   |   ISBN-13: 978-0596009823

Robert W. Sebesta: Programming the World Wide Web, 8th edition
Addison-Wesley, 2014.
ISBN-10: 0133775984   |   ISBN-13: 978-0133775983
Book information at:

More relevant books

Course Lecture Notes:
Lecture Notes - Software Engineering · by Ivan Marsic
(Includes solved problems)
Note that only Chapters 1 - 5 and 7 are covered in this course.

Additional papers will be distributed for some topics.

For UML tutorials and reference documents, also check

Click here to get to the optional online readings page.

Course Projects:
Hands-on design projects are the key component of the course. Team work is required for the projects.

Click here for a general project description. All students are urged to examine carefully this document, since the project constitutes the main part of the final grade.

Project deliverables and deadlines are listed here.

Grading: (subject to change)
Class participation:   17 % discussion forum,   17 % peer reviews
Project reports (total 3): 12 % each
Project demos (total 2): 13 % first,   17 % second
Project e-Archive: (*) Can reduce the overall grade by 10 % if missing or inadequate

Observe that about 1/3 of the grade is individual-based (class participation), and about 2/3 is team-based (project deliverables). Please check the detailed project grading policy.

All assignments should be prepared using a word processor and uploaded to Sakai. Handwritten assignments or those containing handwritten material (e.g., figures, tables, etc.) will not be accepted.

Requests for grade review will be considered no later than four weeks after notification of the grade.

See also: Policy on Academic Integrity for Undergraduate and Graduate Students.

Students with Special Needs:
The University policy states that:
“It is the student’s responsibility to confirm with the course supervisor that all arrangements are in place well in advance of the scheduled date of the exam.”

If the student fails to make arrangements before the exams, we may not be able to accomodate the last-moment requests.

See: Office of Disability Services for Students.

We’d be very happy to receive suggestions on how to improve the quality of the course and fairness of the grading process. Email us your suggestions and concerns.
To submit your feedback anonymously, consider

Page Created: Jul 11, 2007      
Last Modified: Mon Sep 24 16:57:12 EDT 2012
Maintained by: Ivan Marsic