RU ENG ECE 14:332:452 Software Engineering PDF document of the lecture notes (software engineering book) is available here   Spring 2012 HOME PAGE http://www.ece.rutgers.edu/~marsic/Teaching/SE/

Instructor:

Ivan Marsic Office hours: Tuesday, Friday 3 (12:00 - 1:20 p.m.) Room 711, CoRE Building Phone: (732) 445-6400, extension 218 URL: http://www.ece.rutgers.edu/~marsic/

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

TA:

Parneet Kaur Office hours: Tuesdays from 1:30pm to 2:30pm or by appointment Room 118, EE Building URL: TBA Email: parneet@eden.rutgers.edu

Lectures:

Tuesday, Friday: 2 (10:20 a.m. - 11:40 a.m.) in SEC-118

Course Description:

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 five to seven students work on developing complex software systems over a course of one semester. The grading is competitive, with the highest rated project receiving the highest grade and the others being rated relatively to the highest one.
The issue of which programming language to use often arises, and here is an interesting view: If programming languages were religions...   (or try this). You can also find some great comments at Slashdot here.

According to the US Bureau of Labor Statistics, software engineers are projected to be one of the fastest growing occupations from 2006 to 2016... READ MORE >>

Prerequisites:

14:332:351, Programming Methodology II.
If you do not have a solid knowledge of a programming language, preferably an object-oriented language, then you should not take this course.

Lecture Notes:

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

Textbooks:

Bernd Bruegge and Allen H. Dutoit: Object-Oriented Software Engineering: Using UML, Patterns and Java, Third Edition,
Prentice Hall, Upper Saddle River, NJ, 2010.
ISBN 0-13-6061257
Book information is available at
Pearson: http://www.pearsonhighered.com/educator/academic/product/0,4096,0136061257,00.html
Amazon: http://www.amazon.com/Object-Oriented-Software-Engineering-Using-Patterns/dp/0136061257
Check also the book’s WebHome < OOSE < TWiki http://wwwbruegge.in.tum.de/OOSE/

Russ Miles and Kim Hamilton: Learning UML 2.0,
O’Reilly Media, Inc., Sebastopol, CA, 2006.
ISBN 10: 0-596-00982-8  |  ISBN 13: 9780596009823
Book information is available at
O’Reilly: http://www.oreilly.com/catalog/9780596009823/index.html
Amazon: http://www.amazon.com/Learning-UML-2-0-Russ-Miles/dp/0596009828

Online Materials:

Click here to get to the 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 the description of how to work on team projects. All students are urged to examine this document carefully, since the project constitutes the main part of the final grade.

Click here for the list of class projects and their descriptions.

Project deliverables and deadlines are listed here.

Grading: (subject to change)

Questions from reading assignments:	10 %
Exams (two, in-class):	14 % each
Project reports (total 3):	10 % first two,   12 % third
Project demos (total 2):	15 % each
Project e-Archive:	(*) Can reduce the overall grade by 10 % if missing or inadequate

Observe that 38 % of the grade is individual-based (questions and exams), and 62 % is team-based (project deliverables). Please check the detailed project grading policy.

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

All exams are open book, meaning that the students can have access to the textbook or any other paper-based materials.
No cell phone, laptops, or other networked devices are allowed at the exams for two reasons:

1. to avoid student collaboration during the exam
2. to deny unfair advantage for students using a digital textbook to do quick searches for the exam topics.

Please do not inquire about exceptions, because none will be allowed.
No discussion is allowed among the students during the exam. Such students shall be asked to leave the classroom.

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 last-moment requests.

See: Office of Disability Services for Students.

Feedback:

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.

Adoption: University of Arkansas - CSCE 3513.

Page created: Oct 27, 1997      
Last modified: Wed Jan 18 16:05:29 EST 2012
Maintained by: Ivan Marsic