CSci 5180: Software Engineering I :: Summer 1998 Syllabus

792129; Tu, Th 10am-1230pm; Mech. Eng. 108
Role:NameOffice & HoursPhoneEmail
Instructor: Prof. S. Shekhar EE/CS 5-203, Tu Th 1230-130pm 624-8307, shekhar@cs.umn.edu
TA: Badrul Sarwar, EE/CS 2-209, Tu W 4-5pm 626-7512, sarwar@cs.umn.edu
TA: D. Kim, EE/CS 2-209, M F 11am-12noon 626-7512, dkim@cs.umn.edu
Schedule:lecture, homework and examination schedule
Homeworks:homework descriptions and recommended exercises
Web Pages: Main (http://www.cs.umn.edu/~shekhar/5180),
TA-Announcements , Instructor-Announcements ,
Copy Shop: Copies on Campus, Coffman Union Basement.
Textbook: S. R. Schach, Classical and Object Oriented Software Engineering, 3rd Ed., Irwin, ISBN 0-256-18298-1.

Topics:

Software- the process and its management (metrics, estimation, project management), system and software requirement analysis (structured analysis, object-oriented analysis, formal methods), the design and implementation of software (data-flow oriented design, object-oriented design, other design methodologies), Ensuring, verifying and maintaining software integrity (quality assurance, testing, maintenance, configuration management), the role of automation (CASE, CASE environments), current topics (e.g. Y2K problem).

Examinations and Assignments:

Submission of all assignments and scoring >= 50% on the final examination are the two necessary conditions for passing this class. The weighting scheme used for grading is: Midquarter exam - 25%, Final exam - 40%, Assignments - 35%.
Assignments are due at the beginning of the lecture on designated days. UNITE students should have their homeworks postmarked by this date and pursuade their site coordinators to fax it to Dongsoo Kim at 625-0572 the same day. However, assignments put in the Dongsoo Kim's office (EE/CS 6-225G) by 5:00 pm will be counted as having been submitted that day. DO NOT submit assignments in EE/CS 5-203. All assignments must have your name, student ID and course name/ number. There would be four assignments, some of which may require programming.
Late submission policy: Assignments submitted late will be penalized at the following rate, 1 day - 30%, and >= 2 days - 70%. Weekend days will be counted.
For assignments, you are encouraged to type or typeset your answers. For programming assignments you are encouraged to use pretty printers to make your listings more readable. Following is (roughly) the weight distribution for case-study/project problems: Correctness - 60%, Test Results Summary - 10%, Style and Documentation - 15%, Approach - 10%, and Report - 5%.

Exams:

Students are responsible for all material covered in lectures, as well as that specifically mentioned as part of the supplementary reading assignments. Examnations will heavily emphasize conceptual understanding of the material. Sample examinations in postscript form are available at following links: (i) Sample Final, and (ii) Sample Mid-Quarter.

Cheating/ Collaboration:

Getting help from services like general debugging service (GDS), web-sites (e.g. cheaters.com), or copying someone else's assignment, or the common solution of written or programming assignments will be considered cheating. The purpose of assignments is to provide individual evaluation as well as a tool to get you thinking. Interaction for the purpose of understanding a problem is not considered cheating and will be encouraged. However, the actual solution to problems must be one's own.

Helpful Comments:

This class is Very Interesting (for your personal understanding of software development process) and useful. Practitioners may be invited as guest lecturer during discussion of topics such as object oriented requirement analysis and design. To get full benefit out of the class you have to work regularly. Read the textbook regularly and start working on the assignments soon after they are handed out. Plan to spend at least 10 hrs a week on this class doing assignments or reading.
Good Luck, and Welcome to CSci 5180!
Shashi Shekhar

The views and opinions expressed in this page are strictly those of the page author.
The contents of this page have not been reviewed or approved by the University of Minnesota.