CTI Course Syllabus

Software Engineering I (465-96-501)

Quarter: Times: Location: Summer 2002  Tuesdays and Thursdays  Loop Campus Thomas Long  M.S.  Class Web Page Lecturer tlong@cs.depaul.edu

Summary of the course:

Survey the fundamental principles and concepts in Software Engineering  Study and understand the Software Engineering processes for various phases in the software development life-cycle  Apply the knowledge to a case study  No programming required

Textbooks and printed resources:

Required  Software Engineering, Ian Sommerville, Addison-Wesley (6th Edition),

Grading:

The course grade will be based on:    Appraisal Item % of Final Grade Case 1 30 Case 2 30 Class Presentation 5 Class Notes 5 Final Exam 30 Grading Scale  Grade Score A 90 and above B 80-89 C 70-79 D 60-69 F Below 60

Weekly Schedule:

Date Lecture Topic Reading 6th Edition Class #1 Introduction Chapters 1-3 Software Engineering Overview Software Development Lifecycles Class #2 Analysis Chapters 4-7 Requirements Class #3 Design Chapters 10-12 Class #4 Design Chapters 14-15 Class #5 Implementation Chapters 8, 16-18 Class #6 Validation & Verification Chapters 19-21 Class #7 Estimating Chapters 4,22-23 Project Management Class #8 Configuration Management Chapters 27,29 Change Control Class #9 Quality Management Chapters 24-25 Capability Maturity Model Case Study 2 Due  Finals Week Final Exam - take home

University policies:

Plagiarism:  The university and school policy on plagiarism can be summarized as follows: Students in this course, as well as all other courses in which independent research or writing play a vital part in the course requirements, should be aware of the strong sanctions that can be imposed against someone guilty of plagiarism. If proven, a charge of plagiarism could result in an automatic F in the course and possible expulsion. The strongest of sanctions will be imposed on anyone who submits as his/her own work a report, examination paper, computer file, lab report, or other assignment which has been prepared by someone else. If you have any questions or doubts about what plagiarism entails or how to properly acknowledge source materials be sure to consult the instructor.  Incomplete:  An incomplete grade is given only for an exceptional reason such as a death in the family, a serious illness, etc. Any such reason must be documented. Any incomplete request must be made at least two weeks before the final, and approved by the Dean of the School of Computer Science, Telecommunications and Information Systems. Any consequences resulting from a poor grade for the course will not be considered as valid reasons for such a request.