| Instructor | David Ferry, Homepage |
| Course Web Site | http://cs.slu.edu/~dferry/courses/csci5030/ |
| Course meeting times | Monday, Wednesday - 5:00PM to 7:30PM |
| Final exam period |
Wednesday, August 10th, in class |
| Office hours | By appointment |
| Contact | You may contact me in person during class time, or you may email me at dferry@slu.edu. I am also available to meet during the day by appointment- please send email to schedule. |
Software engineering perhaps stands alone as a technical discipline in which there are no universally accepted techniques (either in academia or industry) that everyone agrees produces good software. Instead, there are a wide variety of practices that have grown up around a diverse set of organizations and philosophies. Rather than cataloguing all these techniques and attempting to prescribe their uses, we will look at succesful case studies, listen to experienced veterans describe their approaches, and try to develop an intuition of how successful software projects are run in practice. We will also get hands-on experience with the tools and techniques of a modern software development ecosystem, and put these into practice in a semester-long team project.
The three elements of this course are class meetings, quizzes, and a project. This course will be taught as a graduate style seminar- some meeting times will be used for lecture, but out-of-class readings will also be the basis for in-class discussions. Quizzes will evaluate the student's understanding of class readings.
The course project will be an exercise in agile software development. Effort on the project will be structured around two week sprints. You will be evaluated at four milestones: prototyping after two weeks, an alpha product around midterms, a beta product at six weeks, and a final version at the end of classes. You will be evaluated on the quality of your product and your group's adherence to process, as well as your individual contributions. Your individual performance will be evaluated by Git commit logs, your participation in code reviews of others' commits, and peer evaluations.
Definite topical outline:
Assessment Objectives- at the completion of this course, students will be able to:
Catalog Description:An overview of software development at a graduate level, including software engineering processes, software design and architecture, testing and quality assurance, and selected other topics of interest to software practitioners.
There are no formal catalog prerequisites for this course, but expectations are commensurate with a graduate computing course:
Please see the instructor if you're missing a prerequisite or uncertain about your preparation for this course.
A tentative course schedule is below. Note that this schedule may change over the course of the semester. When changes occur, students will be given enough advance notice so that readings and other preparation may be accommodated.
The "Readings" field refers to material that will be discussed that day in class, not homework for that day. Readings should be completed prior to coming to class for the day.
| Day | Topic | Readings | Notes |
|---|---|---|---|
| Wed, June 22 | Course Introduction | ||
| Software Development Processes | "Real Software Engineering" by Glenn Vanderburg | Class 1 | |
| Mon, June 27 | Agile and Scrum | Review the basic concepts of Agile development: https://www.agilealliance.org/agile101/ The Agile Manifesto Principles of the Manifesto Introduction to the Scrum Methodology: What is Scrum Then watch the "Introduction to Scrum" and "Sprint Planning Meeting Videos" at the next link: Agile E-Learning |
Class 2 Agile and Scrum Slides |
| Project Introduction | Project Prompt |
Project Slides | |
| Sprint 1 Planning Meeting | Quiz 1 | ||
| Wed, June 29 | The Dark Side of Scrum | How agile software developers saved healthcare reform in America. Never says Agile/Scrum, but read and create a list of commonalities with Scrum methodology: Obama's Trauma Team Watch and/or read also: Daily Scrum Meeting Training "Dark Scrum" "The State of Agile Software in 2018" Scrum Anti-Patterns |
Dark Scrum Slides |
| Version Control and Git | Git Slides Workflow Exercise |
||
| Wed, July 6 | Branching Models for Git |
A Successful Git Branching Model Git Workflows |
Git Branching Slides Rebasing Exercise |
| Intro to Test Driven Development Sprint Reviews and Retrospectives |
Intro to Test Driven Development TDD: The Bad Parts |
Quiz 2 | |
| Sprint 1 Review and Retrospective | Sprint Retrospective Slides | ||
| Mon, July 11 | More on Testing | Uncle Bob on Test Doubles | Unit Testing in Python |
| Sprint 2 Planning Meeting | |||
| Wed, July 13 | Continuous Integration TDD in Gitlab |
Gitlab CI/CD Quiz 3 |
|
| Mon, July 18 | Test Types | Twitter-Text Feedback & Telemetry (13:55 thru 18:10) Unit Testing vs. Feature (Behavior) Testing |
Testing Slides |
| Wed, July 20 | Git Deep Dive | ||
| Sprint 2 Review and Retrospective | Quiz 4 | ||
| Mon, July 25 | Code Reviews | Code Review Exercise The Human Side of Code Reviews: Part 1 Part 2 Optional: They Write the Right Stuff, a look at how high-stakes software is created for space missions (and which is actually a passionate defense of the waterfall model- remember to read critically!) |
Code Reviews |
| Software Architecture | Software Architecture | ||
| Sprint 3 Planning | |||
| Wed, July 27 | Engineering Case Study: Mozilla | Mozilla Case Study | |
| Engineering Case Study: Twitter | Quiz 5 Twitter Case Tudy |
||
| Mon, August 1 | Archiecture Discussion | For lack of a better term, "pro" architecture articles: There's No Conflict Between Architecture and Agile An Agile Approach to Software Architecture Articles critical of "Architecture Astronauts": Don't Let the Architecture Astronauts Scare You Architecture Astronauts Take Over A personal account of wrestling with architecture: The Hard Things About Simple Things |
Archiecture Discussion and Sprint 3 Retrospective |
| Technical Debt | Technical Debt Slides | ||
| Wed, August 3 | Refactoring | Quiz 6 Refactoring Slides |
|
| Sprint 3 Review and Retrospective | |||
| Mon, August 8 | Sprint 4 Planning | Sprint 4 Planning Form | |
| Course Conclusion | Course Conclusion Slides | ||
| Wed, August 10 | Sprint 4 Review and Retrospective | Quiz 7 |
Version control software is used to track changes to all artifacts related to this course. Most importantly this means project source code, but you should track absolutely all of your work using version control: data files, config files, build scripts, test code, documentation, READMEs, licence files, project websites and other resources, and so on.
Some things should not be tracked: generated files such as intermediate compilation products and binary executable files bloat the repository, and can't be used unless the server environment is totally replicated by the user. Dependencies such as libraries should be indicated and not replicated, unless you're willing to take on the challenge of regularly updating and maintaining those libraries as well.
There are many reasons why version control is a universal software development tool:
A short guide to using SLU's git resources
In lieu of a textbook, we will have online readings and other media throughout the semester.
Readings are a crucial part of this course. The goal of our readings is to hear from successful, real-world practitioners and ground our dicussions in current industrial practice. Readings are frequently written articles, but will also include videos and other media.
If the schedule has a reading listed for a given date then you should consume that material prior to that class period and come ready to discuss it on that date. Please be thoughtful and reflective about our readings, as the quality of the discussion (and in turn, what you and your peers get from the course) is directly related to your preparation.
A great general-purpose way to respond to any content (in this course or in any other course) is to answer the following questions:
Please feel free to go further than this in responding to any of the course material, but if you can answer these questions for yourself then you are probably adequately prepared for our class discussions.
The semester schedule for quizzes is known well in advance. Make up quizzes will only be given for severe and documented reasons.
Your grade will be determined as follows:
| Activity | Grade Percentage |
|---|---|
| Project | 50% |
| Quizzes | 35% (5% each) |
| Class Participation | 15% |
Grading is done on a straight scale (uncurved). The following scores are guaranteed. The grading scale may be curved upwards (in your favor) at the discretion of the instructor.
Project work assigned for this course is generally expected to be completed collaboratively. However, the sharing of written work or code between teams is strictly prohibited. Quizzes are individual assignments and collaboration is strictly prohibited. Occasionally, the readings for classes may include non-credit exercises designed to inform or enhance your understanding of the material. These non-credit exercises may be completed collaboratively.
Some specific guidelines for this course:
Successful students attend all or mostly all class sessions. This is true in my experience and has been demonstrated in large scale studies as well. In that study, even students who attended nine out of ten class periods had measurably lower class performance than those who attended all classes. However, there is no attendance requirement for this class, and you do not need to get permission when you do miss class. You are an adult and have the freedom to manage your time in whatever way you feel is most useful. Job interviews, conferences, tests in other courses, etc. are all reasonable cases for being absent.
Note that in-class assignments such as tests or quizes cannot be made up outside of class without prior approval from the instructor. All such activities will be listed course schedule with ample time to prepare (i.e. there are no "pop quizes").
If you do miss class you should refer to the course schedule to see what was missed and arrange to get course notes from another student. I am always happy to answer questions but I do not repeat full class periods in office hours.
Throughout the COVID-19 pandemic, key safeguards like face masks have allowed SLU to safely maintain in-person learning. If public health conditions and local, state, and federal restrictions demand it, the University may require that all members of our campus community wear face masks indoors.
Therefore, any time a University-level face mask requirement is in effect, face masks will be required in this class. This expectation will apply to all students and instructors, unless a medical condition warrants an exemption from the face mask requirement (see below).
When a University-wide face mask requirement is in effect, the following will apply:
Students who attempt to enter a classroom without wearing masks will be asked by the instructor to put on their masks prior to entry. Students who remove their masks during a class session will be asked by the instructor to resume wearing their masks.
Students and instructors may remove their masks briefly to take a sip of water but should replace masks immediately. The consumption of food will not be permitted.
Students who do not comply with the expectation that they wear a mask in accordance with the University-wide face mask requirement may be subject to disciplinary actions per the rules, regulations, and policies of Saint Louis University, including but not limited to those outlined in the Student Handbook. Non-compliance with this policy may result in disciplinary action, up to and including any of the following:
dismissal from the course(s)
removal from campus housing (if applicable)
dismissal from the University
To immediately protect the health and well-being of all students, instructors, and staff, instructors reserve the right to cancel or terminate any class session at which any student fails to comply with a University-wide face mask requirement.
When a University-wide face mask requirement is not in effect, students and instructors may choose to wear a face mask or not, as they prefer for their own individual comfort level.
ADA Accommodations for Face Mask Requirements
Saint Louis University is committed to maintaining an inclusive and accessible environment. Individuals who are unable to wear a face mask due to medical reasons should contact the Office of Disability Services (students) or Human Resources (instructors) to initiate the accommodation process identified in the University's ADA Policy. Inquiries or concerns may also be directed to the Office of Institutional Equity and Diversity. Notification to instructors of SLU-approved ADA accommodations should be made in writing prior to the first class session in any term (or as soon thereafter as possible).
2021-2022 Mandatory Syllabus Statement on In-Person Class Attendance and Participation
The health and well-being of SLU's students, staff, and faculty are critical concerns, as is the quality of our learning environments. Accordingly, the following University policy statements on in-person class attendance are designed to preserve and advance the collective health and well-being of our institutional constituencies and to create the conditions in which all students have the opportunity to learn and successfully complete their courses.
Students who exhibit any potential COVID-19 symptoms (those that cannot be attributed to some other medical condition the students are known to have, such as allergies, asthma, etc.) shall absent themselves from any in-person class attendance or in-person participation in any class-related activity until they have been evaluated by a qualified medical official. Students should contact the University Student Health Center for immediate assistance.
Students (whether exhibiting any of potential COVID-19 symptoms or not, and regardless of how they feel) who are under either an isolation or quarantine directive issued by a qualified health official must absent themselves from all in-person course activities per the stipulations of the isolation or quarantine directive.
Students are responsible for notifying their instructor of an absence as far in advance as possible; when advance notification is not possible, students are responsible for notifying each instructor as soon after the absence as possible. Consistent with the University Attendance Policy, students also are responsible for all material covered in class and must work with the instructor to complete any required work. In situations where students must be absent for an extended period of time due to COVID-19 isolation or quarantine, they also must work with the instructor to determine the best way to maintain progress in the course as they are able based on their health situation.
Consistent with the University Attendance Policy, students may be asked to provide medical documentation when a medical condition impacts a student's ability to attend and/or participate in class for an extended period of time.
As a temporary amendment to the current University Attendance Policy, all absences due to illness or an isolation/quarantine directive issued by a qualified health official, or due to an adverse reaction to a COVID-19 vaccine, shall be considered "Authorized" absences
Academic integrity is honest, truthful and responsible conduct in all academic endeavors. The mission of Saint Louis University is "the pursuit of truth for the greater glory of God and for the service of humanity." Accordingly, all acts of falsehood demean and compromise the corporate endeavors of teaching, research, health care, and community service via which SLU embodies its mission. The University strives to prepare students for lives of personal and professional integrity, and therefore regards all breaches of academic integrity as matters of serious concern.
The governing University-level Academic Integrity Policy was adopted in Spring 2015, and can be accessed on the Provost's Office website at: https://www.slu.edu/provost/policies/academic-and-course/policy_academic-integrity_6-26-2015.pdf.
Additionally, each SLU College, School, and Center has adopted its own academic integrity policies, available on their respective websites. All SLU students are expected to know and abide by these policies, which detail definitions of violations, processes for reporting violations, sanctions, and appeals. Please direct questions about any facet of academic integrity to your faculty, the chair of the department of your academic program, or the Dean/Director of the College, School or Center in which your program is housed. Specific College of Arts and Sciences Academic Honesty Policies and Procedures may be found here.
Saint Louis University and its faculty are committed to supporting our students and seeking an environment that is free of bias, discrimination, and harassment. If you have encountered any form of sexual harassment, including sexual assault, stalking, domestic or dating violence, we encourage you to report this to the University. If you speak with a faculty member about an incident that involves a Title IX matter, that faculty member must notify SLU's Title IX Coordinator and share the basic facts of your experience. This is true even if you ask the faculty member not to disclose the incident. The Title IX Coordinator will then be available to assist you in understanding all of your options and in connecting you with all possible resources on and off campus.
Anna Kratky is the Title IX Coordinator at Saint Louis University (DuBourg Hall, room 36; anna.kratky@slu.edu; 314-977-3886). If you wish to speak with a confidential source, you may contact the counselors at the University Counseling Center at 314-977-TALK or make an anonymous report through SLU's Integrity Hotline by calling 1-877-525-5669 or online at http://www.lighthouse-services.com/slu. To view SLU's policies, and for resources, please visit the following web addresses: https://www.slu.edu/about/safety/sexual-assault-resources/index.php and https://www.slu.edu/general-counsel.
IMPORTANT UPDATE: SLU's Title IX Policy (formerly called the Sexual Misconduct Policy) has been significantly revised to adhere to a new federal law governing Title IX that was released on May 6, 2020. Please take a moment to review the new policy and information on the following web address: https://www.slu.edu/about/safety/sexual-assault-resources/index.php. Please contact the Anna Kratky, the Title IX Coordinator, with any questions or concerns.
In recognition that people learn in a variety of ways and that learning is influenced by multiple factors (e.g., prior experience, study skills, learning disability), resources to support student success are available on campus. The Student Success Center, a one-stop shop, which assists students with academic and career related services, is located in the Busch Student Center (Suite 331). Students can visit https://www.slu.edu/life-at-slu/student-success-center/ to learn more about tutoring services, university writing services, disability services, and academic coaching.
Students with a documented disability who wish to request academic accommodations must contact Disability Services to discuss accommodation requests and eligibility requirements. Once successfully registered, the student also must notify the course instructor that they wish to access accommodations in the course.
Please contact Disability Services, located within the Student Success Center, at Disability_services@slu.edu or 314-977-3484 to schedule an appointment. Confidentiality will be observed in all inquiries. Once approved, information about academic accommodations will be shared with course instructors via email from Disability Services and viewed within Banner via the instructor's course roster.
Note: Students who do not have a documented disability but who think they may have one are encouraged to contact Disability Services.
Students are encouraged to take advantage of University Writing Services in the Student Success Center; getting feedback benefits writers at all skill levels. Trained writing consultants can help with writing projects, multimedia projects, and oral presentations. University Writing Services offers one-on-one consultations that address everything from brainstorming and developing ideas to crafting strong sentences and documenting sources. For more information, visit https://www.slu.edu/life-at-slu/student-success-center/ or call the Student Success Center at 314-977-3484.
Students in personal or academic distress and/or who may be specifically experiencing challenges such as securing food or difficulty navigating campus resources, and who believe this may affect their performance in the course, are encouraged to contact the Dean of Students Office (deanofstudents@slu.edu or 314-977-9378) for support. Furthermore, please notify the instructor if you are comfortable in doing so, as this will enable them to assist you with finding the resources you may need.