Merge branch 'main' of github.com:neu-se/CS4530-Spring-2024

Assignments/demo-sec235.md

@@ -8,16 +8,20 @@ nav_order: 8
 
 # Specifications for Live Demos / Presentations (Sections 2, 3, & 5 - Prof. Bhutta)
 
-Each group will present a live demo to show the feature that they have added to Covey.Town for the final project (the demo MUST be from hosted website, NOT from localhost). The schedule of these demos will be discussed/finalized during the lecture. You will have 9 minutes maximum (8 minutes to setup and present. 1 minute for questions and everything else). You will lose points if your demo goes over 8 minutes. Please rehearse it and time yourself (best to keep it to 7 minutes or less). Attendance is REQUIRED for these demos.
+Each group will present a live demo to show the feature that they have added to Covey.Town for the final project. The schedule of these demos will be discussed/finalized during the lecture. You will have 9 minutes maximum (8 minutes to setup and present. 1 minute for questions and everything else). You will lose points if your demo goes over 8 minutes. Please rehearse it and time yourself (best to keep it to 7 minutes or less). 
+Please note:
+- The demo MUST be from hosted website, NOT from localhost. 
+- Attendance is REQUIRED for these demos.
 
 Your presentation should include the following:
-- description of feature(s) implemented (no more than 1 slide)
+- Description of feature(s) implemented (no more than 1 slide)
 - Tech stack and/or list of other/external components used (no more than 1 slide)
 - Checklist of all user stories and COS (what was proposed vs what was implemented. Feel free to use percentages to show progress)
-- short summary of overall contributions made by each member (no more than 1-2 sentences per member);
+- short summary of overall contributions made by each member (no more than 1 slide with 1-2 sentences per member);
 - What percentage of overall contribution was made by each member (perhaps using weekly peer contribution scores)
-- estimated number of hours spent on the project by each member (for overall project);
-- what challenges were faced and how did you overcome them? Discuss any deviations from the proposed plan?
+- Estimated number of hours spent on the {overall} project by each member (excluding research tasks);
+- What challenges were faced and how did you overcome them? 
+- Discuss any deviations from the proposed plan?
 
 During your presentation, you might want to consider the following order: introduction of project idea/user stories follow by live demo, then present the checklist and then talk about remaining items from above in any order you find appropriate.
 
@@ -28,4 +32,4 @@ Your final Poster and Demos are worth 4% of the overall course.
 
 Poster will be worth 1% and will be graded based on whether you submitted it on time or not. 
 
-Demos will be worth 3% and will be graded using the following criteria: Each group will evaluate each others' demos and will assign scores (Instructor and TAs will do the same). Your final demo score will be calculated by combining all of these scores (equally weighted). However, you will not receive points for the demo if your group fails to submit copy of the presentation on Canvas or if you are not present for all presentations/demos during class.
+Demos will be worth 3% and will be graded using the following criteria: Each group will evaluate each others' demos and will assign scores (Instructor and TAs will do the same). Your final demo score will be calculated by combining all of these scores (equally weighted). However, you will not receive points for the demo if your group fails to submit copy of the presentation on Canvas, your scores to instructor and if you are not present for all presentations/demos during class.

Assignments/project-grading.md

@@ -52,15 +52,17 @@ We will grade each of these using the following rubric:
 * Implemented feature does not include any eslint-disable or ts-ignore flag
 
 ### Testing (10%)
-The project must include evidence of testing. Ideally, all new features will be accompanied by fully automated tests, but in some circumstances (particularly when engaging with Phaser, the game library, or Tiled, the map editor), this may not be feasible. If automated tests are not possible, include a discussion of your manual testing strategy, including a script that a future developer could use to manually test the feature. There is no explicit requirement to make use of any specific testing technology (e.g. mocks, spies, etc.).
+The project must include evidence of testing (both for front-end and back-end). Ideally, all new features will be accompanied by fully automated tests, but in some circumstances, this may not be feasible. If automated tests are not possible, include a discussion of your manual testing strategy. There is no explicit requirement to make use of any specific testing technology (e.g. mocks, spies, etc.).
 
 #### Satisfactory:
-* Any new or modified backend features include tests that validate that the feature works as intended. These tests cover the changed code, and also contain well-written assertions that thoroughly check the expected behaviors.
-* Tests contains no ESLint warnings or errors; does not include any eslint-disable or ts-ignore flags
+* Any new or modified features include tests that validate that the feature works as intended. These tests (which need not be fully automated) cover the changed code and contain well-written assertions that thoroughly check the expected behaviors.
+* Any bugs that the staff detect when evaluating your application are also represented as failing tests (be they manual or automated tests)
+* Tests contain no ESLint warnings or errors; do not include any eslint-disable or ts-ignore flags
 
 #### Meets minimum requirements:
-* Any new or modified backend features include at least one test, which may or may not be an effective test.
-* Tests may contain ESlint warnings (but no errors); does not include any eslint-disable or ts-ignore flags
+* Any new or modified features include at least one test, which may or may not be an effective test.
+* The staff may detect some bugs that are not represented by failing tests. However, a manual evaluation of the test suite indicates a good-faith effort to test the features
+* Tests may contain ESlint warnings (but no errors); do not include any eslint-disable or ts-ignore flags
 
 ### Process (20%)
 The Process grade includes: use of a structured development process, including code reviews, timely completion of sprint progress reports/retrospectives, individual/team surveys, peer evaluations and weekly meetings with TA Mentor (for Week 6, 8, 10-14). It also includes appropriate division of labor within the project. For full credit, each member of the team must have at least 4 commits in the final delivered code. 
@@ -175,4 +177,4 @@ Reflect on your team dynamic: Provide a frank (and ideally, blameless) postmorte
 #### Satisfactory:
 * Is at least 2 paragraphs long;
 * Includes at least 1 paragraph reflecting on your own performance as a team member on this project, including what you would have done differently, given what you know now;
-* Includes at least 1 paragraph reflecting on your overall team dynamic, including strengths and weaknesses. Reflect on how you might have organized your team differently given what you know now.
+* Includes at least 1 paragraph reflecting on your overall team dynamic, including strengths and weaknesses. Reflect on how you might have organized your team differently given what you know now.

Assignments/project-plan.md

@@ -93,8 +93,8 @@ Each work item should contain the following information:
 * Milestone for delivering the task, chosen from one of the following:
   * Sprint 0: Feb 14-Feb 28
   * Sprint 1: Feb 29-Mar 13 (Sprint 1 is just a single week, not including spring break)
-  * Sprint 2: Mar 14-Mar 28
-  * Sprint 3: Mar 29-Apr 10
+  * Sprint 2: Mar 14-Mar 27
+  * Sprint 3: Mar 28-Apr 10
 
 Your work breakdown should take the format of a simple textual list.
 

Assignments/revised-project-plan.md

@@ -72,8 +72,8 @@ Each work item should contain the following information:
 * Milestone for delivering the task, chosen from one of the following:
   * Sprint 0: Feb 14-Feb 28
   * Sprint 1: Feb 29-Mar 13 (Sprint 1 is just a single week, not including spring break)
-  * Sprint 2: Mar 14-Mar 28
-  * Sprint 3: Mar 29-Apr 10
+  * Sprint 2: Mar 14-Mar 27
+  * Sprint 3: Mar 28-Apr 10
 
 Your work breakdown may take the format of a simple textual list.
 

_announcements/week-11.md

@@ -0,0 +1,8 @@
+---
+title: Information about Project Final Deliverables, and Posters/Demos
+week: 11
+date: 2024-03-26
+---
+Please don't forget to review [final project deliverables](https://neu-se.github.io/CS4530-Spring-2024/assignments/project-deliverable) page published on course website. This include [grading rubrics](https://neu-se.github.io/CS4530-Spring-2024/assignments/project-grading) and other details related to the submission of the final project (i.e., code/testing, report, posters and demos). Canvas assignments for these are also published now.
+
+In addition, each instructor has provided a list of [expectations for the final demos / presentations](https://neu-se.github.io/CS4530-Spring-2024/assignments/project-grading#posters-and-demo-10). Please be sure to review these quickly.

_data/modules.yml

@@ -69,7 +69,7 @@ guest-pm:
   name: Work on Project
 12b:
   name: Ethics
-  page: 
+  page: /modules/17-ethics
 12c:
   name: Work on Project / Mini-Demo
 13a:
@@ -106,7 +106,7 @@ tp3:
 tp4:
   name: Project Final Deliverable
   type: deadline
-  page: 
+  page: /assignments/project-deliverable
 veteransday:
   name: Veteran's Day (No class)
   type: holiday

lectures/l17.md

@@ -0,0 +1,32 @@
+---
+layout: module
+title: "17 - Ethics"
+permalink: /modules/17-ethics
+parent: Modules
+nav_order: 17
+lessons: 
+  - title: "Ethics"
+    ppt: "Module 17 Ethics.pptx"
+    pdf: "Module 17 Ethics.pdf"
+
+---
+### Learning Objectives:
+In this week of the course, you will learn about ethical problems in Software Engineering. You will learn about some of the many unintended consequences of the software we build, and about ways to analyze the ethical problems that are associated with that software
+
+{% include lesson.html %}
+
+### Resources
+* [Software Engineering @ Google](https://learning.oreilly.com/library/view/software-engineering-at/9781492082781/), Chapter 4 (Engineering for Equity)
+* Coverage of Google Photos auto-tagging bug [WSJ](https://www.wsj.com/articles/BL-DGB-42522), and more recent from [Wired](https://www.wired.com/story/when-it-comes-to-gorillas-google-photos-remains-blind/)
+* COMPAS coverage: [The Atlantic](https://www.theatlantic.com/technology/archive/2018/01/equivant-compas-algorithm/550646/), [ProPublica](https://www.propublica.org/article/machine-bias-risk-assessments-in-criminal-sentencing), [ProPublica data](https://www.propublica.org/article/how-we-analyzed-the-compas-recidivism-algorithm)
+* Price discrimination: [WSJ](https://www.wsj.com/articles/SB10001424127887323777204578189391813881534), [FairTest](https://arxiv.org/abs/1510.02377)
+* Climate considerations: [in NLP](https://arxiv.org/abs/1906.02243), [in content delivery networks](https://www.sciencedirect.com/science/article/abs/pii/S2210537916301196)
+* Robles v Domino's Pizza coverage: [Eater](https://www.eater.com/2019/7/25/8930669/dominos-supreme-court-website-accessible-blind-users), [Columbia Journal of Law & Social Problems](http://jlsp.law.columbia.edu/2020/02/13/inaccessible-pizza-delivery-and-the-future-of-the-ada/)
+* [Citicorp Center Design case study](https://www.theaiatrust.com/whitepapers/ethics/study.php)
+* [Therac-25 case study](https://ethicsunwrapped.utexas.edu/case-study/therac-25)
+* [Value Sensitive Design @ Khoury](https://vsd.ccs.neu.edu)
+* [ACM software engineering code of ethics](https://ethics.acm.org/code-of-ethics/software-engineering-code/), [IEEE code of ethics](https://www.computer.org/education/code-of-ethics)
+* Web accessibility resources from W3C: [WCAG 2.0 specification](https://www.w3.org/TR/WCAG20/), [evaluating web accessibility](https://www.w3.org/WAI/test-evaluate/)
+* On the origins of the ADA: [Judy Heumann memoir](https://www.penguinrandomhouse.com/books/621090/being-heumann-by-judith-heumann/), [Crip Camp: A Disability Revolution](https://www.netflix.com/title/81001496) (Netflix)
+* Podcast: [Margaret Burnett on Gender, Cognitive Styles, and Usability Bugs](https://www.se-radio.net/2019/09/episode-380-margaret-burnett-on-gender-cognitive-styles-usability-bugs/)
+* [Solutions to AI image bias raise their own ethical questions](https://www.marketplace.org/2023/10/10/solutions-to-ai-image-bias-raise-their-own-ethical-questions/)