Office Hours
Textbooks
Outcomes
Grading Policy
Schedule
| Mon | 2:00pm | - | 3:00pm |
| Wed | 2:00pm | - | 3:00pm |
| Fri | 10:00am | - | 11:00am |
The Mythical Man-Month: Essays on Software Engineering,
Design Patterns: Elements of Reusable Object-Oriented Software, For those of you interested in curriculum details, this course will correspond to the following components in the Joint ACM / IEEE Computer Society Taskforce report, Computer Science Curricula 2013: Curriculum Guidelines for Undergraduate Degree Programs in Computer Science:
| Knowledge Unit | Core-Tier 1 Hours | Core-Tier 2 Hours |
|---|---|---|
| Software Engineering (SE) | 6 | 21 |
| Goal-Setting Milestones | 20% | Initial Pitch, Detailed Pitch, Feature Selection, Roadmap |
| Agile Sprint Demonstrations | 40% | Bi-weekly check-in presentations demonstrating accountability for sprint goals |
| Final Deliverables | 20% | Formal artifacts documenting the stages of design and development |
| Midterm and Final Exam | 20% | If necessary, written exams. Otherwise, points to be rolled in with Deliverables |
Weekly reading quizzes will be offered automatically through D2L, and will generally consist of one or to problems taken from or motivated by the readings assigned for the following week.
Grades will be assigned using the standard formula: A: [93, 100];
A-: [90, 93); B+: [86, 90); B: [82, 86); B-: [78, 82); C+: [74,
78); C: [70, 74); C-: [66, 70); D+: [62, 66); D: [58, 62); F: [0,
58)
At the instructor's discretion, grades may be "curved"
up; grades will not be curved down.
Grades will be routinely posted in the gradebook on the course D2L site, as they become available.
Student attendance will not be explicitly tracked in this course, and will not directly impact student grades. However, students who routinely miss class discussions and group meetings should expect to be unprepared to complete their projects, or to be downgraded by their team peer evaluations. In short, I don't bother with attendance bean-counting because students who cut class usually fail themselves out of the course before I would need to take any action. Make good decisions.
If you know you will be missing class for a legitimate reason, I appreciate a heads-up, but in accordance with Marquette University Attendance Policies, neither require nor accept documented excuses, except in those specific cases detailed in the policy above. Please try to have a peer in the class take notes in your absence, and get any assignments in ahead of the deadline.
The size and structure of this course will not normally allow me to accept late work under any circumstances. There are enough opportunities for points in the course for most students to miss a few without severe consequences for their grades.
All students are expected to abide by Marquette University's Policy on Academic Integrity, and we will proceed under the assumption that everyone has committed themselves to the University's Honor Pledge:
I recognize the importance of personal integrity in all aspects of life and work. I commit myself to truthfulness, honor, and responsibility, by which I earn the respect of others. I support the development of good character, and commit myself to uphold the highest standards of academic integrity as an important aspect of personal integrity. My commitment obliges me to conduct myself according to the Marquette University Honor Code.
The Honor Code has particular implications for computer scientists and engineers, as well as computing professors, whose course work is so readily duplicated and shared in our modern digital world.
For my part, I will strive to ensure that your assignments and projects are engaging, challenging, and worth your investment in time and energy. For your part, I expect you will work hard, strive to learn, and present your work with honesty and integrity.
Generative artificial intelligence tools for coding assistance have now become ubiquitous. We assume that some students will make use of these tools to assist them with coding, and also for producing some of the text for team written reports. It is expected that any such tools will be listed in the authorship section of the mandatory comment block at the top of any submitted code, or in the author attribution segment of any written documents. Failure to note the contributions of a generative A/I tool will be considered a violation of the academic integrity policy. Consider carefully the implications of showing off your code or written artifacts to a potential employer if a significant portion have been generated by A/I instead of yourselves.
There will be many opportunities for you to collaborate with your peers in this course, and I strongly encourage you both to seek help when you are stuck, and to share your knowledge with your peers when you have achieved understanding. Problems will only occur if you falsely claim work as your own when it is not, or collaborate when an exam or assignment has been specified to be individual work.
In the unlikely event of an academic integrity violation in this course, Marquette University's Procedures For Incidents of Academic Dishonesty will be closely followed.
[Revised 2024 Aug 26 11:20 DWB]
