Email:
Phone: 285-8661
Office: RB 442
See instructor's Web site for office hours.
Instructor: Chris Lüer, PhD
Email:
Phone: 285-8661
Office: RB 442
See instructor's Web site for office hours.
Lecture: Tu, Th 12:30 pm - 1:45 pm, RB 104
Description - Materials - Policies - Schedule
Catalog description:
697 Software Engineering. (3) Software
engineering principles and concepts. The
software life cycle, structured specifications,
design tools and techniques, software
reliability, and verifying program
correctness.
Prerequisite: CS 232 and three graduate
courses in computer science.
Not open to students who have credit in
CS 497.
Course rationale: The course is a required course for the master's program for those students who have not taken it as undergraduates.
Required Textbooks:
Course Web site: http://www.cs.bsu.edu/homepages/chl/697-09S/
Posting of grades: Grades are posted to Blackboard. However, we do not use Blackboard for grade calculations.
Cheating. Consequences of cheating in this class: the course grade is lowered, possibly to F. No team work is allowed in this class unless explicitly stated. Material that is copied from books or Web pages needs to be quoted and the source must be given. It is OK to discuss general solution strategies with your classmates, but it is not OK to copy programs, parts of programs, or other written answers. Be aware of the Ball State University Student Academic Ethics Policy.
Project. The project is done in teams and uses appropraite software engineering tools and processes. Progress on the project is reported in class throughout the semester.
The instructor gives one grade for each project team for each milestone. It will be divided up among the team members through peer evaluations as follows. Each team member divides up 100 percent among all members of the team, giving him- or herself 1/n, where n is the number of team members. The points each team member gets for a milestone is the instructor's grade multiplied with the sum of the team member's peer evaluations. In this way, your team members can influence your grade.
Each time has a Web site, where it publishes all documents related to the project. The team may choose to make the Web site password-protected.
Attendance. There is no grade for attendance; however, there are unannounced quizzes. There is no make-up for missed quizzes.
Email. Emails to the instructor must be sent from a BSU account; this is the only way for us to verify your identity. Emails from other accounts may be ignored.
Grading
Final exam 25%
Midterm exam 10%
Project 50%
Paper presentation 10%
Quizzes 5%
If you receive 93.3% of the total course credit, you will get an A. If you receive 90.0%, you will get an A- or better. If you receive 86.7%, you will get a B+ or better, and so on. The grading scale will be shifted so that the median grade is at least a B+ if there are at least 10 students enrolled.
Tests. There will be a midterm exam plus a comprehensive final exam. Each test will cover both the material presented in class and the related material from the textbook. Missed tests can be made up only for documented medical reasons.
Students with special needs or disabilities. If you need course adaptations or accommodations because of a disability, if you have emergency medical information to share with me, or if you need special arrangements in case the building must be evacuated, please make an appointment with me as soon as possible.
| Week | Topic | Readings | Assignments due |
|---|---|---|---|
| 1 | Introduction | P1 | |
| 2 | Requirements | P7, F9 | MS 1 |
| 3 | Process Models | P2-4, F2 | MS 2 |
| 4 | Analysis and UML Class Diagrams | F1, P8 | MS 3 |
| 5 | UML Interaction and State Diagrams | F3,4,10 | |
| 6 | Analysis | MS 4 | |
| 7 | Analysis | handouts | MS 5 |
| 8 | Test (Th 3/5) | Prepare for test | |
| 9 | Midterm project review | MS 6 | |
| 10 | Intro to Design; Architecture | P9-10 | MS 7 |
| 11 | Class Design; Design Patterns | P11; handouts | MS 8 |
| 12 | Quality Assurance | P13-14 | MS 9 |
| 13 | Project Management, IP Law | P21-22 | MS 10 |
| 14 | Paper presentations. Tu: Mary, Documentation; Amitesh, Agility; Naveen, XP; Teja, Scrum; Ravi, TBA; Logesh, RAD; Soumik, Configuration Mgmt/ISO 9001; Achyuth, Cleanroom Th: Todd, Design Patterns; You, V&V; Keshav, Testing; Deb, CMM and QA; Adam, Management; David, Human Side of Agile; Carrie, Web-based teams; Sirisha, Web engineering |
Presentations; MS 11 | |
| 15 | Project demonstrations; review | Finished project |
Final Exam: Thursday, May 7, 12:00 pm - 2:00 pm.
Slides on UML and unit testing
Slides from test review 3/3
Architecture and class design
Design patterns
Testing