2018 Spring Semester
Tuesdays and Thursdays, 2:00-3:15 PM w/ Prof. Mark Sherriff - Rice 130
- Mondays, 2:00-3:15 PM - Rice 120
- Mondays, 3:30-4:45 PM - OLS 009
- Mondays, 5:00-6:15 PM - OLS 009
Instructor: Prof. Mark Sherriff
Office: Rice 401
Office Hours: Tuesdays and Wednesdays, 9:00-10:30 AM
- 2:00 Lab (Rice 120) - Zach Danz and Bobby Hails
- 3:30 Lab (OLS 009) - Marissa Lee and Daniel Hoerauf
- 5:00 Lab (OLS 009) - Danny Brown and Sam Weber
- Support - Divya Karuturi
Message boards: Piazza @ https://piazza.com/class/j9sondoq2lu2es
Login to Piazza and use the threads for quick questions, assignments, and for discussion with other students and staff. You can also post private messages here that will only be seen by staff members. This includes regrade requests for homework assignments.
All office hour times are posted on the course calendar at the bottom of the Schedule page on the course website. TA office hours are held Rice 340. Professor office hours are held in Rice 401. Note that we will update this calendar for any and all office hour changes due to the changing needs of the course. Students should refer to this calendar before going to any office hours.
Textbook: An Introduction to Software Engineering - Laurie Williams
Edition: 1st (2013)
- ASIN: B00E8NEKN8 (Kindle Edition – http://www.amazon.com/An-Introduction-Software-Engineering-ebook/dp/B00E8NEKN8/)
- ISBN-10: 0989864014 (Paperback Edition - http://www.amazon.com/Introduction-Software-Engineering-Laurie-Williams/dp/0989864014/)
Cost: Kindle Edition $9.99; Paperback - $29.99
Analyzes modern software engineering practice for multi-person projects; methods for requirements specification, design, implementation, verification, and maintenance of large software systems; advanced software development techniques and large project management approaches; project planning, scheduling, resource management, accounting, configuration control, and documentation. Prerequisite: CS 2150 with a grade of C- or higher.
Upon completion of this course students will:
- Develop an understanding of how to specify, design, and implement a complex software entity that involves many aspects of modern software systems.
- Master a number of modern tools and a number of difficult technical fields.
- Acquire experience of working on a large software system as a member of a team working on system development and as a member of a team that has to interact with other teams and customer representatives.
Course Topics: The topics to be covered in the course include:
- Software quality, including testing and inspections
- Project management, scheduling, planning, with an emphasis on the Scrum agile method
- Requirements elicitation, analysis and specification
- Architecture and design principles
- Security in the development of software applications
- Programming and team-based development practices
- Professional ethics
You should meet the following requirements to take this class:
- Have taken CS 2150 with a C- or better. We’ll assume you have mastered the material in the courses leading up to CS 2150 also, which includes software developments skills in Python, Java, and C++.
- Can attend class and lab regularly (attendance will be taken in lab each week and occasionally in lecture)
- You will be expected to learn programming languages and platforms on your own in this class! If you don’t feel comfortable with this, please talk to Prof. Sherriff as soon as possible!
Course Project - 50% - Includes all milestones, final product, team evaluations/performance, and demo
Lab Grade - 15% - Includes lab assignments, attendance, and participation
Midterm Exam - 15% - Thursday, February 22, During lecture
Final Exam - 15% - Thursday, May 10, 9:00 AM
Class Activities - 5% - Includes in-class quizzes, attendance checks on required days, participation
Participation/Professionalism Penalty - up to -100% - Excessive missed classes, rude behavior toward instructor or classmates, not participating fully with your partner, etc. can be held against a student when final grades are calculated.
Your final grade will be calculated as follows:
Rounding: By default, grades will not be rounded in this course.
Pass/Fail: A course average of 65.00 or higher with at least one completed mobile project is required for successful completion.
- I have an "open door" policy, in that if my door is open (or cracked), by all means stop on in and say hi or ask a question. If my door is closed, then I'm heads down on some task, on the phone, in a meeting, etc. It's always a good idea to email me before coming to make sure I'm here.
- I can’t stress enough that email is the best way to get in touch with me.
- If you email me, please put 3240 somewhere in the subject. Failure to do so makes it much harder to keep up with your email and reduces the chance of a timely reply.
- Please don’t hesitate to contact me if you have any problems, concerns, questions, or issues regarding the course, material, or anything else in the class.
You are expected to work as a member of your group in this course and cooperate with your colleagues. Cooperation means attending group meetings, completing your assignments properly and on time, letting your group know if you will be out of town, responding to e-mail from your group, and so on. If there is a lack of cooperation by any group member, it must be brought to the attention of the instructor as soon as it happens. If the lack of cooperation is serious, the offending group member’s semester grade will be lowered. More information on group composition will be provided with the project material.
- Attendance in lecture is vital to learning the material and making a good grade in this class.
- There will be specific, announced class days in which attendance will be taken. These are mainly for guest speakers and in-class activities. These activities cannot be made up if you miss them, regardless of the reason.
- Students can miss one lab with no penalty. The second miss incurs a small penalty, with the penalty size increasing with each missed lab.
- The required classes will be noted on the course schedule calendar.
Homework Assignments / Exams
- Homework assignments will not be handed out in class. Everything will be available online at http://cs3240.cs.virginia.edu or in Collab.
- Partners/groups/teams may not collaborate with any other set of partners/groups/teams unless specified as part of the assignment.
- There will be one midterm and a final exam during the course of the semester.
- Any test that is missed due to any absence that is not a University Excused Absence will result in a zero (0) for that grade.
- Any test that is missed due to a University Excused Absence or due to circumstances that are approved by me beforehand must be made up within a week of the missed test.
Grading Concerns and Appeals
- All grading appeals must be submitted as a private post on Piazza, tagged with the regrade folder option.
- All regrade requests must be made within one week of the assignment being returned to the student. After that point, no regrades will be considered.
- We will regrade serious errors in judgement; we will not regrade partial credit judgement calls.
- When regrading, we reserve the right to regrade the entire exam or assignment, which may result in either an increase or a decrease in your grade. We are not trying to scare off students whose exams or assignments were graded incorrectly, but we are trying to avoid frivolous requests.
- What should be regraded?
- Your answer is the same as what is on the key, but the grader didn’t realize it.
- Your answer is different, but is also correct (code that compiles and runs correctly, but is different than the key).
- What should not be regraded?
- “Most of what I wrote is correct, so I think I deserve more partial credit.”
- “I wrote so much, and the grader didn’t notice that the correct answer is buried somewhere within this long paragraph.”
- “I’m just 1 point away from an A, so I thought it was worth scrounging around to find an extra point somewhere.”
- The regrade procedure is intended to correct serious errors in grading. It is not intended as a opportunity to argue about each judgment call made by the graders. We agree that graders sometimes take off 1-2 points too many here and there, but we believe that they also give you 1-2 points too many just as often. When we regrade exams, we sometimes disagree with the exact points awarded on each question by the graders, but the total grade usually comes out the same.
- However, significant mistakes in grading do occur. If you sincerely feel that your exam or assignment was unfairly graded, we will look it over carefully. In that case, we reserve the right to regrade the entire exam or assignment, which may result in either an increase or a decrease in your grade. We are not trying to scare off students whose exams or assignments were graded incorrectly, but we are trying to avoid frivolous requests.
- What should be regraded? 1. Your answer is the same as what is on the key, but the grader didn’t realize it. 2. Your answer is different, but is also correct (code that compiles and runs correctly, but is different than the key) What should not be regraded? 1. “Most of what I wrote is correct, so I think I deserve more partial credit.” 2. “I wrote so much, and the grader didn’t notice that the correct answer is buried somewhere within this long paragraph.” 3. “I’m just 1 point away from an A, so I thought it was worth scrounging around to find an extra point somewhere.”
This syllabus is to be considered a reference document that can and will be adjusted through the course of the semester to address changing needs. This syllabus can be changed at any time without notification. It is up to the student to monitor this page for any changes. Final authority on any decision in this course rests with the professor, not with this document.
In this course, there will be a focus on working well together and learning about the development process. A large portion of that process involves interpersonal skills and conflict management. Students and staff are all expected to treat each other with respect. This includes, but certainly is not limited to:
- Excessive web browsing during class
- Disrespectful language
- Promptness for all deadlines and class meetings
- Quality work
- Not working well with your partner
- Collaborating with other teams
The number one problem with professionalism in class is the overuse of laptops and mobile devices. Taking notes on a laptop and following along with the slides is welcome and encouraged. Doing work for other classes, watching videos, chatting, or anything else that distracts from your ability to learn and follow along (or anyone around you), will result in a professionalism penalty.
If you need to do work for another class during our class meeting, do so somewhere else and listen to the podcast, rather than disrupt the class itself.
Students can and will be penalized for unprofessional behavior.
Your class work might be used for research purposes. For example, we may use anonymized student assignments to design algorithms or build tools to help programmers. Any student who wishes to opt out can contact the instructor or TA to do so after final grades have been issued. This has no impact on your grade in any manner.
- Know the honor code
- Work with your team, but not any other team
- Using code from other students (from any semester) is an honor violation
- Using publically-available example code and libraries is fine, but you must cite them
- More information on what is allowed will be included with each assignment
- It never hurts to ask the staff what is allowed or not allowed!
The School of Engineering and Applied Science relies upon and cherishes its community of trust. We firmly endorse, uphold, and embrace the University’s Honor principle that students will not lie, cheat, or steal, nor shall they tolerate those who do. We recognize that even one honor infraction can destroy an exemplary reputation that has taken years to build. Acting in a manner consistent with the principles of honor will benefit every member of the community both while enrolled in the Engineering School and in the future.
Students are expected to be familiar with the university honor code, including the section on academic fraud (http://www.virginia.edu/honor/what-is-academic-fraud-2/). Each assignment will describe allowed collaborations, and deviations from these will be considered Honor violations. If you have questions on what is allowable, ask! Unless otherwise noted, exams and individual assignments will be considered pledged that you have neither given nor received help. (Among other things, this means that you are not allowed to describe problems on an exam, assignment, or project to a student who has not taken it yet. You are not allowed to show exam papers to another student or view another student’s exam papers while working on an exam.) Sending, receiving, or otherwise copying or describing the contents of electronic files that are part of course assignments are not allowed collaborations (except for those explicitly allowed in assignment instructions).
For CS3240, using code developed by previous students in the course or code written for your use by someone outside the course is not allowed and will likely be an honor violation. This does not apply to the use of publicly available frameworks and libraries, unless indicated in the assignment instructions. Such uses must be documented in the submitted work. If you have any questions, talk to a TA or the instructor in advance.
Assignments or exams where honor infractions or prohibited collaborations occur will receive a zero grade for that entire assignment or exam. Such infractions will also be submitted to the Honor Committee if that is appropriate. Students who have had prohibited collaborations may not be allowed to work with partners on remaining homeworks.
How to Cite Code
Use the following format for citing code you use. Order by title of the software package. Use the appropriate commenting format for the programming language of your source code.
/*************************************************************************************** * REFERENCES * Title: <title of program/source code> * Author: <author(s) names> * Date: <date> * Code version: <code version> * Availability: <where it's located> * * Title: .... * ***************************************************************************************/
SDAC and Other Special Circumstances
If you have been identified as an SDAC/LNEC student, please let the Center know you are taking this class. If you suspect you should be an SDAC/LNEC student, please schedule an appointment with them for an evaluation. We happily and discretely provide the recommended accommodations for those students identified by the LNEC. Please contact us one week before an exam so we can make accommodations. Website: http://www.virginia.edu/studenthealth/sdac/sdac.html
If you have other special circumstances (athletics, other university-related activities, etc.) please contact your instructor and/or Head TA as soon as you know these may affect you in class.
Frequently Asked Questions
Q: How do I get off the waitlist?
A: Here is how we are going to pull people (or not pull people) off the wait list:
- I will NOT be using the permission of instructor information found in SIS. (Long story...)
- Fill out the form here if you feel you have a special case for getting in: https://goo.gl/forms/vgAO8nXCTjfkqmmV2
- 4th and 3rd year BSCS and CPE majors have the highest priority (assuming they did not add to the waitlist within the last few days/weeks).
- After those students get in (or at least are given the opportunity to), then I will consider 2nd years and BACS students.
- If you are not a declared BSCS major, BACS major, CPE major, or CS minor, you have lower decidely lower odds at getting into the course.
- After this, the wait list ordering comes into play and we will follow the order that appears in the SIS wait list.
- No course action forms will be signed.
Q: Can we pick our own teams?
A: No. Simply put, you're not going to get to pick your teams in industry, so why should you here? :-)