SE 3800: Software Engineering Process II

SE 3800: Software Engineering Process II, Winter 2016-17

Instructor: Rob Hasker (414-277-7326)

Office hours: See my home page: https://faculty-web.msoe.edu/hasker/

Textbooks: Scrum Shortcuts without Cutting Corners, by Ilan Goldstein, Addison Wesley, 2014. ISBN: 978-0-321-82236-9

Course Description: This course provides an more in-depth discussion of agile software development and quality assurance processes including behavior-driven development and continuous integration. It also discusses alternative development models and current software engineering topics. Course concepts are reinforced by classroom exercises and homework assignments.
Prereq: SE 2800, SE 2832

Course Outcomes: On successful completion of this course, the student will be able to

Construct a continuous integration environment meeting the quality goals of a project
Apply behavior-driven development to develop usable, robust, maintainable systems
Identify key activities required to assure systems meet quality goals
Identify the advantages and disadvantages of agile and plan-based methodologies
Describe the key components of the Software Engineering Code of Ethics and Professional Practice

Grading:

		Percentage
	Homework, class exercises:	30%
	Quizzes:	10%
	Presentation:	10%
	Midterm:	25%
	Final Exam:	25%
	Total:	100%

The MSOE grading scale will be used, though I reserve the right to award higher grades to individual students if it increases fairness. In addition, successfully demonstrating mastery of course outcomes is a prerequisite for a passing grade. This includes completing assignments even if worth zero points and taking the final exam.

Communication

Course materials will be posted at my class web site https://faculty-web.msoe.edu/hasker/se3800/. I also use email extensively; I expect you to read your MSOE email at least once a day.

Labs, Assignments, and Quizzes

Late submissions will be penalized, and any work more than a week late will generally be worth zero points. Missed quizzes cannot be made up, but the lowest quiz score may be dropped.

Programs will be graded for both correctness (does it work right?) and presentation (does it look good on the printed page?). I will not be handing out an extensive style sheet for this course, but at a minimum you must do the following:

Use meaningful names for identifiers.
Format your programs consistently and nicely, including ensuring that lines are no longer than about 80 characters, and adding blank lines between sections of code.
Providing enough documentation that another person can understand the modules in your solution.
Ensuring your files contain no hard tabs.
Include your name (prominently) in source files.

Assignments are individual unless we explicitly state otherwise. You are responsible for honestly completing and representing your work, for appropriately citing sources, and for respecting the academic endeavors of others. Electronic tools may be used to identify plagiarism. You will be penalized for violating these standards.

Reasonable accommodations will be provided for students with physical, sensory, cognitive, systemic, and psychiatric disabilities. Please discuss any accommodations you may need with your instructor.

Attendance

Do not skip class! If you do happen to miss, be sure to check for new materials and get the notes you missed from a friend before the next class period. You are responsible for anything missed! If you need to be excused from class for MSOE activities or religious observances, be sure to me know in advance. If you're sick, it's obviously not a good idea to come to class. This includes days on which there are exams; just be sure to contact me as soon as you can get to a phone or computer.

When an exam is missed, I will determine whether to give you a make-up exam or increase the weight of the other exams. All students must take the final exam to receive a passing grade in the course unless the student has been excused in advance.