17-313 Syllabus

Units: 12

Prerequisites
No formal prerequisites, but you will get more out of the course if you have experience with some larger development projects, for example, through larger class projects (e.g., 17-214, 15-410), internships, or open-source contributions.

Teamwork
Teamwork is an essential part of this course. Most assignments are done in teams of 2 students. Teams will be assigned by the instructor and stay together for multiple assignments. Guidance on teamwork, reflection, and conflict resolution will be provided throughout the semester and are an essential component of the class. Most assignments have a component that is graded for the entire group and a component that is graded individually. The team policy posted on Piazza applies and describes roles and teams and how to deal with conflicts and imbalances.

Communication
We make announcements through Piazza, including clarifying homework assignments and other interactions. The instructor and TA hold weekly office hours and are reachable by email; see staff page for information on how to contact us. Email us for appointments. We also have an virtual open-door policy: Send us a Zoom meeting request and if we are not currently meeting with somebody else, or with some other work, we will gladly accept your Zoom calls.

Textbook
Various readings throughout the semester available online or through the library; we do not have a single text book but rather assemble readings from different sources. As optional supplementary reading consider Ian Sommerville, Software Engineering. An online version of the book is available here

Attendance Policy

• Attending lecture and recitation is mandatory and will be factored into yor grade.
• Students who arrive late or leave early will be considered absent.
• If you must miss lecture or recitation, let the instructor know beforehand.

Homework Policy

• Homework will not be accepted late, unless you have an extension Extensions require permission from instructor

Collaboration Policy

• Many of the assignments will be done in groups. We expect that group members collaborate with one another, but that groups work independently from one another, not exchanging results with other groups
• Between students in different groups:
• Do not look at another student's code or written answers.
• Do not show another student your code or written answers.
• Do not email, publish, or electronically transfer your code to other students.
• You may not look at or copy code from an online resource or textbook.
• You may not re-use code done in previous semesters.
• No outside assistance on homework from anyone except course staff.

Resources

• Office Hours and Piazza for Homework Help

Grading Policies

• Email srazak@andrew.cmu.edu with regrade requests

Well-being/Happiness

• If you are feeling overly stressed, anxious, or unhappy, we strongly encourage you to seek support. Counseling and Psychological Services (CaPS-Q) is here to help: call 4454-8525. Student Affairs staff are also here to help: call 4454 8526 or send Renee Camerlengo an email at reneec@andrew.cmu.edu.

Official Course Description
Students gain exposure to the fundamental principles of software engineering. This includes both core CS technical knowledge and the means by which this knowledge can be applied in the practical engineering of complex software in real-world settings. Topics related to software artifacts include coding, software architecture, measurement, and quality assurance of various qualities (e.g., robustness, security, performance, maintainability) with static and dynamic analysis, testing, code review, and inspection. Topics related to software process include requirements engineering, process models and evaluation, personal and team development, and supply chain issues including outsourcing and open source. This course has a strong technical focus, a strong focus on developing team skills, and will include both written and programming assignments. Students will get experience with the latest software engineering tools and practices.

Learning Objectives
At the end of the course, students should be able to:

• Understand software engineering as a human activity and business concern; understand involved risks and tradeoffs
• Understand the purpose and need of software engineering
• Understand the need for and difficulty of measurement throughout all SE activities
• Understand basic relevant statistics
• Elicit, describe, and evaluate a system's requirements
• Design a software system and evaluate a design with regard to various quality attributes
• Develop and justify a quality-assurance strategy for a software project
• Plan the process for and manage a software project
• Reason about business models and open source

Lectures :
Sunday and Thursday, 11:30 am - 12:45 pm
Recitation:
Tuesday 11:30 am - 12:45 pm

See the topic list and schedule (includes schedule, notes, video mini-lectures, homework, and other material). Reading quizzes will test topics that are covered in the readings, lectures, and exercises.

Grading Policy

Course Component	Points
Assignments	50
Midterm	2x15
Reading Quizzes	10
Participation	10

Reading Quizzes
You are assigned a reading assignment for almost every class on Gradescope. You are responsible for doing the reading and taking an online Quiz based on the reading before coming to class. The reading quiz are fairly easy if you have done the readings.

Attendance
As indicated in the Grading section, your class participation counts for 10% of your grade. Class participation includes being in class, actively participate in class discussions -- especially for the case studies. A bit part of learning in this course is through presenting your ideas and evaluations and listening to those of other students.

This is a 12-unit course, and it is our intention to manage it so that you spend close to 12 hours a week on the course, on average. In general, 4 hours/week will be spent in class and 8 hours on reading and assignments. Notice that most homework is done in groups, so please account for the overhead and decreased time flexibility that comes with group work. Please feel free to give the course staff feedback on how much time the course is taking for you.

Late work will receive feedback but no credit. Due to heavy reliance on teamwork in this course there are no late days. Exceptions to this policy will be made only in extraordinary circumstances, almost always involving a family or medical emergency---with your academic advisor or the Dean of Student Affairs requesting the exception on your behalf. Please communicate also with your team about timing issues.

Describing tradeoffs among decisions and communication with less technical stakeholders are key aspects of this class. Most homework assignments have a component that require discussing issues in written form or reflecting about experiences.

Your classmates are your colleagues. This is particularly true in this course, where we aim to provide you with principles, practices, tools, and paradigms that will enable you to be an effective, real-world Software Engineer. We ask that you treat one another like the professionals you are and that you are preparing to be. To that end, we will not tolerate harassment in this class. We define harassment as unwelcome or hostile behavior of an ad hominem nature, i.e., that focuses not on ideas but on people and identity. This includes offensive verbal or written comments in reference to gender, disability, physical appearance, race, or religion; sexual images in public spaces; deliberate intimidation, stalking, following, harassing photography or recording, and sustained disruption of class meetings. Harassment is against the law and we have no tolerance for it, and neither does the university. Even when behavior does not rise to the level of harassment (even if you think you're "just joking!"), it can still make people very uncomfortable, and harm their educational and professional career by forcing them to devote mental energy to something other than the material they are trying to learn or the professional successes they are trying to achieve. However, we expect that we do not need to threaten you to earn your respect on this matter: we simply ask that you treat one another like professionals, in the most positive sense. This has two implications:

• If you feel someone is violating these principles (for example, with a joke that could be interpreted as sexist, racist, or exclusionary), and you feel you have the standing to do so, speak up! Do not be a bystander to unprofessional behavior.
• If you do not feel comfortable doing so, and/or if the behavior persists, send a private email to the course instructor or set up a meeting with us to discuss the matter. We will preserve your anonymity.

We, the course staff, are committed to affording you the same respect we ask you to afford one another. If you feel that we are not doing so, we hope you will feel comfortable either telling us so directly, or approaching another one of the course staff with your concerns.

The usual policies apply, especially the University Policy on Academic Integrity. Many of the assignments will be done in groups. We expect that group members collaborate with one another, but that groups work independently from one another, not exchanging results with other groups. Within groups, we expect that you are honest about your contribution to the group's work. This implies not taking credit for others' work and not covering for team members that have not contributed to the team. Otherwise, our expectations regarding academic honestly and collaboration for group work are the same as for individual work, substituting elevated to the level of "group." The course includes both individual assignments and individual components of group assignments. Although your solutions for individual parts will be based on the content produced for the group component (e.g., written reflections on lessons learned), we treat individual component of group assignments as equivalent to individual assignments overall, and expect you to complete such components independently of your groupmates. The rest of this academic honesty and collaboration content is taken from the policy used in 15-214, which we reuse almost directly (with minor modifications, and attribution). "You may not copy any part of a solution to a problem that was written by another student, or was developed together with another student, or was copied from another unauthorized source such as the Internet. You may not look at another student's solution, even if you have completed your own, nor may you knowingly give your solution to another student or leave your solution where another student can see it. Here are some examples of behavior that are inappropriate:

• Copying or retyping, or referring to, files or parts of files (such as source code, written text, or unit tests) from another person or source (whether in final or draft form, regardless of the permissions set on the associated files) while producing your own. This is true even if your version includes minor modifications such as style or variable name changes or minor logic modifications.
• Getting help that you do not fully understand, and from someone whom you do not acknowledge on your solution.
• Writing, using, or submitting a program that attempts to alter or erase grading information or otherwise compromise security of course resources.
• Lying to course staff.
• Giving copies of work to others, or allowing someone else to copy or refer to your code or written assignment to produce their own, either in draft or final form. This includes making your work publicly available in a way that other students (current or future) can access your solutions, even if others' access is accidental or incidental to your goals. Beware the privacy settings on your open source accounts!
• Coaching others step-by-step without them understanding your help.

If any of your work contains any statement that was not written by you, you must put it in quotes and cite the source. If you are paraphrasing an idea you read elsewhere, you must acknowledge the source. Using existing material without proper citation is plagiarism, a form of cheating. If there is any question about whether the material is permitted, you must get permission in advance. We will be using automated systems to detect software plagiarism. It is not considered cheating to clarify vague points in the assignments, lectures, lecture notes; to give help or receive help in using the computer systems, compilers, debuggers, profilers, or other facilities; or to discuss ideas at a very high level, without referring to or producing code. Any violation of this policy is cheating. The minimum penalty for cheating (including plagiarism) will be a zero grade for the whole assignment. Cheating incidents will also be reported through University channels, with possible additional disciplinary action (see the above-linked University Policy on Academic Integrity). If you have any question about how this policy applies in a particular situation, ask the instructor or TA for clarification."

Note that the instructors respect honesty in these (and indeed most!) situations.

Accommodations for Students with Learning Disabilities

Carnegie Mellon University is committed to providing reasonable accommodations for all persons with disabilities. To access accommodation services, you are encouraged to initiate the request directly with the Office of Disability Resources in Pittsburgh or through the Office of Health & Wellness or CaPS-Q. The Office of Disability Resources will review the information you provide. All information will be considered confidential and only released to appropriate persons on a need to know basis. Once the accommodations have been approved, you will have access to your Summary of Accommodations Memorandum describing the approved accommodation(s). You are responsible for sharing the Memorandum with your professors at the beginning of each semester. For more information on policies and procedures, please visit here or here

Take Care of Yourself:

This semester is unlike any other. We are all under stress and uncertainty. Attending online classes all day can take its toll on our physical and mental health. Do your best to maintain a healthy lifestyle by eating well, exercising, getting enough sleep and taking some time to relax. This will help you achieve your goals and cope with stress. Always remember that you are not alone. There are many helpful resources available on campus and an important part of the college experience is learning how to ask for help. Asking for support sooner rather than later is often very important. If you or anyone you know experiences any academic stress, difficult life events, or feelings like anxiety or depression, we strongly encourage you to seek support. Student Affairs staff are here to help: call 4454 8526 or send message to Renee Camerlengo (reneec@andrew.cmu.edu). Consider reaching out to a friend, faculty, staff or family member you trust for help. If you or someone you know is feeling suicidal or in danger of self-harm, call someone immediately, day or night at 5554 7913, which is staffed by trained mental health care providers. If the situation is life threatening, call 999.