SE 3030: Software Development Lab III, 2018-19

Instructor: Rob Hasker

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

There is no textbook for this course.

Course Description: This is the third course in the software development laboratory sequence. Students work on large-scale software projects with a goal of delivering a system that could be deployed by clients. In addition, students gain additional experience at processes assessment and improvement.

Prereq: SE 3020

Format: 2 lecture hours, 2 lab hours, 3 credits

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

Apply software engineering practices and tools to the development of significant software components and systems
Develop deliverable prototypes for evaluation by clients
Plan and track project activities
Identify process improvement opportunities, implement those improvements, and evaluate their success
Communicate project and process information in written and oral form
Research and apply independently learned knowledge and skills to the development of software components and systems

Grading:

		Percentage
	Sprint 1	25%
	Sprint 2	25%
	Sprint 3	25%
	Individual	15%
	Peer evaluation	5%
	Presentation	5%
	Total:	100%

Sprint grades are generally broken down by 40% Process, 40% Software Quality, and 20% Software Product. Absences and tardiness will be penalized as discuss on the SDL Policies page.

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. Failing to meaningfully participate in the project may result in being administratively dropped from the course.

The expectation is that you will spend approximately 10 hours per week (90 hours per term) on the project. But this is sufficient just for a B. To get an A, you must make strong contributions: effective reviews, leadership on a significant portion of the project, ensuring effective verification, etc. Additional hours is not enough to get an A, though you will not be penalized for going above and beyond the minimums. Find positive ways to make your mark on the team and the project.

Communication

Communication is particularly important in SDL. It is expected that your team will establish effective communication channels (Slack, Snapchat, email, or whatever). Discuss with your instructor whether he or she wishes to be included in those communications.

Weekly schedules and instructional materials (including standards for team participation and reports) are generally posted on the SDL Confluence site. Instructors may also communicate by email and other electronic means; it is expected that students will check for electronic communications at least once or twice a day.

Integrity

Students are expected to engage in this course ethically and with integrity. It is expected you will work with your peers, however it is unacceptable to submit the work of your peers as your own. Included in this is an expectation to show respect for fellow students and the instructor.

Fabricating evidence of participation (through misleading time logs, grossly inaccurate status reports, claims to have reviewed documents without examining them, etc.) are forms of academic dishonesty and may result in penalties discussed in the Policy on Student Integrity in the catalog.

Additional Notes

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.