Software Engineering and Senior Project

Textbook:

• Sommerville, Software Engineering, 10th ed., Pearson, 2016.

Course Summary: Students successfully completing the course will understand the fundamentals of software engineering, including requirements analysis, design, disciplined and coordinated implementation and evaluation. The course consists of three components: a team-based, semester-long software project, an oral presentation (a lecture) concerning a topic of software engineering, and homeworks concerning those presentation topics.

On-line Access:

You must be registered for the online component of this course at canvas.emich.edu. This is the official mechanism for distributing information about the course, including changes to assignments (such as due dates). All students in the class are required to attend to Canvas.

Graduate Students: Students registered for the 500-level version of this class will be expected to complete more difficult projects, and their homeworks will be graded on a separate scale.

Course Structure:

This is a student-oriented and -implemented course.

Students will work in a number of different groups. One of the groups (4-5 students each) will be for the entire semester and will design, implement, and analyse a major software project. The projects will be developed with and for clients either on or off campus. Each group will demonstrate their completed project at the end of the semester.

Students also will work within a different group (the membership of each students' two groups should be mutually exclusive) to develop and provide an oral presentation (a lecture) on one of the software engineering topics listed below. Each of these groups will also be responsible for writing and grading a homework assignment for their topic. (The groups will provide the grades to me so I can place them in the Canvas grading records.)

Topics:

1. Waterfall development process
2. Agile development process
3. Use case diagrams
4. Collaboration through software repositories
   1. Subversion
   2. Git and Github
5. UML
   1. Introduction to UML
   2. UML tools, especially free and open source
6. Testing
   1. Testing in general
   2. JUnit testing
7. Refactoring
8. Software Patterns
9. Other topics that you can convince me to include

Presentations/Lectures:

Each presentation team is responsible for

• Teaching the material to the class
• Providing references
• Making reading assignments
• Assigning homework and grading it (I will help with developing the rubrics)

Course Calendar:

Grading Policy:

The final course grade will be a weighted average of the grades received in each of the following categories, as specified:

• Homework grades, class participation, 30%
• Topic presentation and the quality of the topic's assigned homework 30%
• Semester sofware project 40% (three components: outline (20%), requirements specification (20%), implementation (60%)
  

Tardiness Policy: Programming and other homework assignments will be due at the beginning of class. After that, assignments will be accepted through the start of the next scheduled class, but will suffer a full grade penalty. E.g., if a late programming assignment is worthy of an 'A', we will mark it a 'B'. Assignments more than one class late will not be accepted, and will receive a grade of 'F'.

Attendance Policy: We're all grown-ups, when and whether you attend class is up to you. However, missed assignments shall only be excused by a doctor's written note, verifying that the student was medically indisposed to attend class that day.

Grading of Programs: Grading of the semester-long project will be explained in class.

Announcements and the Web Page:

Academic Irregularities: