CSC 4110 Introduction to Software Engineering (Call No.: 26452)
Spr/Sum 1998, Dept. of Computer Science, Wayne State University
Day/Time: M W 1:00pm-2:35pm
Location: 235 State Hall
Instructor: ChanJin Chung, Ph.D.
- Office Room: 448 State Hall
- Phone: (313)577-2831; Fax: (313)577-6868
- Web: http://www.cs.wayne.edu/~jcc (announcements, lecture notes, etc.)
Office Hours: M W 2:35pm-3:35pm
Prerequisite
- CSC220 <- CSC211 <- CSC110 <- CSC101
- Comfortable in using IBM PCs/Windows95/Dos or Unix/Xwindows.
- Familiarity with Object-Oriented concepts (Classes and Objects,
Inheritance, Polymorphism, and Templates) and OO programming languages
(C++, Java, etc.) is required.
- Students without the prerequisites must get the approval from the
instructor.
Required Text : Software Engineering: A Practitioners Approach,
by R. Pressman, 4th edition McGraw Hill, 1997
Additional References
Course Objectives
- The student will have a working knowledge of a framework within
which to develop large-scale software products.
- The student will be able to develop right software right.
- The course will focus on Object-Oriented software engineering
methodologies.
Important Dates and Grading: Total 300 points
- Exam 1 (Mon. June 1): 50 points
- Exam 2 (Wed. July 1): 50 points
- 2 Homework Assignments: (20x2=) 40 points
- Project Presentation and Prototype Demo (in July): 40 points
- Final Project (Wed. July 29): 60 points (including demo.)
- Final (Mon. Aug. 3): 60 points
This score will be translated into a letter grade based upon the
percentages given below.
|
A |
90-100% |
|
A- |
88-89% |
|
B+ |
85-87% |
|
B |
80-84% |
|
B- |
78-79% |
|
C+ |
75-77% |
|
C |
70-74% |
|
C- |
68-69% |
|
D+ |
65-67% |
|
D |
60-64% |
|
D- |
58-59% |
|
E |
0-57% |
Class Policies
- Attendance is essential to doing well in the course. The exams
will focus primarily (but not exclusively) on material presented in the
lectures.
- If you are unable to attend a meeting, it is your
responsibility to obtain the material from other students or instructor.
Usually, it will be in an envelop on the instructor's office door.
Exam. Policies
- There will be no makeup exams will be given without an excuse
from a physician stating why the student was
incapacitated on a given date or range of dates.
- Closed books, closed notes
Project Policies
- Each project will be conducted by a team of 2-3 individuals.
- Teams must be formed by Wed. June 3.
- Each member of a team must present topics in charge
during the project presentation in July.
- Each member of a team may not receive the same project grade.
- Each project must follow the methodologies explained in class.
Special Notes
- Students are supposed to use the Computer in the open lab. (308 State),
Graduate Lab. (437 State), or may develop programs on their own computer.
Please check the posted schedules for the labs.
- Homework Assignments must be done individually.
Late submission penalty is 30%.
No submission will be accepted beyond a week after the due date.
- No grades of I(incomplete) will be given without an excuse
from a physician stating why the student was
incapacitated on a given date or range of dates.
- Plagiarism is a serious academic offense. DO NOT COPY THE WORK OF
OTHERS. Failure to observe this will result in zero point for the
assignment.
- Cheating during exams is also a very serious academic offense
and will be handled in accordance with University Policy.
Course Contents
- The software product and software process models (life-cycles)
- Managing Software Projects
- Project Management and Scheduling
- Project Metrics
- Software Configuration Management
- Software Quality Assurance
- Conventional Methods for Software Engineering
- System Engineering
- Software Requirements Analysis and Modelling
- Software Design Methods
- Software Testing and Maintenace Methods
- Software Metrics
- Object-Oriented Requirements Analysis
- Object-Oriented Design
- Object-Oriented Programming
- Introduction to Java
- Comparing Java to C++
- Developing GUI programs
- Object-Oriented Testing
- Formal Methods and Cleanroom Software Engineering
- Software Engineering for Real-time Systems
- Client-Server Software Engineering
- Reuse, Reengineering, and Tools for SE
- The Year 2000 (Y2K) problem and how to fix it
5/10/98