Instructor: Rob Hasker (414-277-7326)
Drop-in times (office hours): See my home page: https://faculty-web.msoe.edu/hasker/
| Textbook: | 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 assignments and homework assignments.
Prereq: SE 2800, SE 2832
Format: 3 lecture hours, no lab, 3 credits
Course Outcomes: On successful completion of this course, the student will be able to
Grading:
| Percentage | |||
|---|---|---|---|
| Assignments: | 30% | ||
| Quizzes, Exercises, & Participation: | 15% | ||
| Presentation: | 5% | ||
| Midterm: | 25% | ||
| Final Exam: | 25% | ||
| Total: | 100% |
The MSOE grading scale will be used, though I reserve the right to award higher grades to individuals if it increases fairness. In addition, successfully demonstrating mastery of course outcomes is a prerequisite for a passing grade. This includes being successful on the final exam and, in some cases, completing assignments even if worth zero points.
Most materials will be available on my class web site, https://faculty-web.msoe.edu/hasker/se3800/ or in Canvas. For instance, quizzes will be in Canvas but links to notes will be on the website. I will also communicate to the class on Teams; it is critical you enable notifications for the Teams entries for this class. Many announcements will be made that way and no other. I may also use email at times. I expect you to check for electronic communications at least once a day.
My office hours are listed as "drop-in" times to emphasize that you do not have to have an appointment to come see me. You can come other times as well! I am always glad to help students with challenges. I do expect you to have spent a few minutes checking for answers on the class website and Teams before requesting help, but absolutely would rather you ask for help than spend hours trying to find solutions on your own.
Unless otherwise announced, late solutions will be penalized 2% per day for the first week. Solutions submitted more than one week late will be worth zero points unless there is advance arrangement due to extenuating circumstances. Unless you have written permission, all assignments must be submitted before Monday of finals week. Note that quizzes and exams have a due date and you will not be able to submit after that due date.
Programs in assignments will be graded for both correctness (does it work right?) and presentation (is it maintainable?). See the coding standard for details. Common mistakes are forgetting to write your names in files and inserting hard tabs.
Most implementations will be in C++. If you have not taken CS 2040 before this class, see your instructor for help learning C++.
Assignments, quizzes, and exams are individual unless explicitly stated 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. Making a repository public is also a violation. You will be penalized for violating these standards.
All code should be checked into a Git repository. Backups are critical. Some of the assignments will require you to use Git repositories on specific servers, but you can use BitBucket, GitHub, or other servers for the other code. Just keep any such repositories private. After the end of the term, any repositories created by the instructor may be removed. If you are interested in preserving the project history, you can clone the project with history to a different, private repository.
Missed quizzes cannot be made up, but at least one of the lowest quiz or exercise scores will be dropped. Many quizzes will be online with flexible times. Exams will typically be scheduled during class time.
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, let me know in advance. If you're sick, stay home! 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.
An important part of attending class is the opportunity to discuss issues in small groups; often these groups find answers that are better than mine! No one has all of the answers in software engineering.
If 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 unless the student has been excused in advance.
Please do not record video or audio of lectures without my permission.
Sometimes students wonder why I include discussions of industry experiences in this class. You do not have to memorize the details of these stories (unless those details are in the slides). I include them because they reinforce the material in a way that is more memorable to some students and because they often point to hopefully entertaining mistakes made by experienced people.
All students are expected to follow the procedures specified in the Raider Return Plan. This includes wearing masks in the classroom at all times.
For students with documented disabilities, chronic medication conditions and mental health concerns: MSOE provides services to make reasonable accommodations available. If you are a student who requires or anticipates the need for accommodations, please contact Student Accessibility Services Office at 414-277-7281, by email at moureau@msoe.edu, or in person at K250 to discuss appropriate accommodations and eligibility requirements.