-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathassignments.yml
262 lines (257 loc) · 14.2 KB
/
assignments.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
team:
- name: A1 - Team Introduction, Team Setup
worth: 2
file: assignments/a1.md
submission: repo
breakdown:
- section: Company Logo & Name
description: Good logo/name that represents a modern idea
worth: 5.0
- section: Team Profiles
description: Team profiles include photos and profile links of all teammates, clearly lists expertises, and a short biography. This includes all CSC454 members.
worth: 10.0
- section: Leader Selection
description: Tells us who they chose and why, what is their role for your team?
worth: 15.0
- section: Team Principles
description: |
The team principles doc is a 1-page doc that covers: expectations of the team members, expectations for communication, roles and responsibilities, work delegation, etc.
The document will cover the entire team including CSC454/2527 students. An example can be found [here](./a1_example.md)
worth: 55.0
- section: Participation & Teamwork
description: |
Effectively worked as a team member and shared equitable work load during this assignment.
Communication was regular and effective & acted in accordance with team principles.
worth: 15.0
individual: true
due_date: 2025-01-13T23:59:59-05:00
position: 1
number: 1
- name: A2 - Team Exploration - Bias and Diversity Reflection
worth: 4
file: assignments/a2.md
submission: repo
breakdown:
- section: Expertise
description: |
Describes how each team member's existing expertise can benefit the project
Describes areas where your team may not have adequate expertise. This should include areas outside of engineering.
worth: 20.0
- section: Subject Matter Experts
description: |
Students identify areas where they may lack expertise and describes subject matter experts that can help fill those holes.
Areas are more than surface-level deep (e.g. students don't just list out "engineering, will ask instructors to advise" or "industry partners"). Clear thought and care has gone into the rhetoric.
worth: 15.0
- section: Unconscious Bias
description: |
The team has clearly given some thought into potential areas bias may occur and describes the situations.
The writing clearly goes beyond surface level bias and the students have given serious thought about it.
Writing also provides examples of possible solutions to help mitigate these biases.
worth: 20.0
- section: Diversity
description: |
- Explain some areas, which you are comfortable sharing, where the team may lack diversity. You do not need to attribute statements to any individual team member, but you are welcome to do so if you are comfortable.
- You do not need to feel pressured to share or pressure colleagues to disclose anything to the team or publicly, but for the dimensions folks are happy to share, it will give you the opportunity as a team to determine where you may have blind spots on your team.
- Do not feel restrained by the subset listed above as there are many dimensions of diversity, visible and non-visible, that change how you experience the world.
- Teams should aim to go beyond visible dimensions of diversity, though those should be included (e.g. gender, nationality, ethnicity).
- Team gives thoughtful rhetoric on how these areas may impact their team and product
worth: 30.0
- section: Participation & Teamwork
description: |
Effectively worked as a team member and shared equitable work load during this assignment.
Communication was regular and effective & acted in accordance with team principles.
worth: 15.0
individual: true
due_date: 2025-01-20T23:59:59-05:00
position: 2
number: 2
- name: A3 - Tech Choices, Architecture Diagram, Roadmap
worth: 12
file: assignments/a3.md
submission: repo
breakdown:
- section: Use Cases
description: |
- Describes 3-6 use cases that provide adequate complexity to showcase the teams skills
- Use cases are well defined and recorded on the Github team repo
- Illustrates UI with low fidelity sketches where applicable
- Teaching Staff will approve use cases after submission. Use case approval will not affect grade, but students may be required to re-write some use cases if not approved.
worth: 25.0
- section: Stack Decisions
description: |
Team describes the main technologies the team intends to use in the Github team repo. For every technology, there is also a decision record.
Each decision provides thoughtful rhetoric on why this is a good decision for the team, leveraging ideas and concepts presented in lectures.
worth: 20.0
- section: Architecture Diagram
description: |
Incorparting all parts of the technologies in your Stack Decisions and adding adequate detail inside of those technologies (e.g. don't just list React server when there's major components to list), design an architecture diagram in the software of your choice.
Include it in the team repo as an image or a PDF.
Diagram is clean and easily followed. Text can be sparingly leveraged.
worth: 20.0
- section: Roadmap
description: |
Roadmap clearly captures in-depth details of the short term future (next week weeks), some light details about the medium term (towards the end of the term), and high level goals for the future (past the end of the term).
Roadmap is defined in _GitHub Issues_ and labelled using labels, milestones, or projects.
Includes plans for user research.
worth: 20.0
- section: Participation & Teamwork
description: |
Effectively worked as a team member and shared equitable work load during this assignment.
Communication was regular and effective & acted in accordance with team principles.
worth: 15.0
individual: true
due_date: 2025-02-03T23:59:59-05:00
position: 3
number: 3
- name: A4 - UX Research w/Prototype, Roadmap Updates
worth: 8
file: assignments/a4.md
submission: repo
breakdown:
- section: UX Research
description: |
Interview the class instructor _and_ another individual. The other individual should be someone who would use the product you are building.
Includes appendices including notes. These can be rough, but they must show that you asked all individuals approximately the same questions, recorded questions, mistakes, and feedback.
Concisely summarizes the results and does not sugar coat the results.
worth: 75.0
- section: Roadmap
description: |
Update roadmap with the changes related to the UX research.
Explain the changes and things that you have completed in the release body for the assignment.
Paragraph included in release covers progress and answers questions (-100% on this section if not included).
worth: 10.0
- section: Participation & Teamwork
description: |
Effectively worked as a team member and shared equitable work load during this assignment.
Communication was regular and effective & acted in accordance with team principles.
worth: 15.0
individual: true
due_date: 2025-02-15T23:59:59-05:00
position: 4
number: 4
- name: A5 - Dev Env, Test Infrastructure, & Production Setup
worth: 8
file: assignments/a5.md
submission: repo
breakdown:
- section: "`service.yml`"
description: Is present, error-free, and fully filled out. See notes below for more details on how to validate.
worth: 10.0
- section: "`script/bootstrap` or similar"
description: Functions on Unix systems (Linux and/or MacOS). Application is fully ready to run after running the script (dependencies installed, database install and setup, etc). The only exception is when you need to get credentials for something like a 3rd party API, that can be a different step. See Notes Below
worth: 25.0
- section: Testing and CI setup
description: Test harness works and can be run from a single command listed in the service.yml file. CI is running and is passing. If the test command is not listed in the service.yml, 0 pts will be awarded for this section. If the command fails to run before tests are executed, 0 pts will be awarded for this section.
worth: 20.0
- section: Production / Builds
description: |
Application is available from the web (e.g. Heroku, AWS, DigitalOcean, Azure, etc), as a mobile application via Microsoft App Center, or a GitHub Release otherwise.
Exception tracking via Sentry and Logging is set up. See Notes Below
worth: 20.0
- section: Roadmap
description: Roadmap and Stack Decisions are updated with any new decisions and/or changes. Paragraph included in release covers progress and answers questions (-100% on this section if not included).
worth: 10.0
- section: Participation & Teamwork
description: |
Effectively worked as a team member and shared equitable work load during this assignment.
Communication was regular and effective & acted in accordance with team principles.
worth: 15.0
individual: true
due_date: 2025-03-05T23:59:59-05:00
position: 5
number: 5
- name: A6 - Class Demos
worth: 6
file: assignments/a6.md
submission: class
breakdown:
- section: Progress
description: Shows some progress since the last demo. Describes the improvements, if they are on schedule, future plans, etc.
worth: 35
- section: Clarity
description: Shows us their project in a short and clear manner. Describes the area they are scheduled to present clearly and effectively. Is concise and tells a good story.
worth: 35
- section: Participation
description: All members present throughout the term and demos are evenly divided.
worth: 30
due_date: 2025-04-02T23:59:59-04:00
multiple_due_dates: true
has_url: false
position: 6
number: 6
- name: Software
worth: 40
file: assignments/a7.md
submission: repo
breakdown:
- section: "[Product] Applications, Use Cases, and Dynamic Content"
description: |
All applications present in the architecture diagram have a repository and an MVP is implemented.
The product coherently functions (buttons do as expected, a user could reasonably answer questions they want to answer using the app) and achieves the intended goal.
All main use cases/flows have been delivered and are functional.
The majority of the content is functional and dynamic. The app(s) do not rely on hard-coded static data.
Login credentials or registration system provided. Details listed in the release.
worth: 40.0
- section: "[Product] Design & Accessibility"
description: |
The application has a consistent look and feel. You didn't rely on default styles (see below). The flows are not incoherent. This will be a highly subjective area, so feel free to ask for advice before submission (please don't ask the day before, or day of, submission). [Checklist for accessiblity](./accessibility_checklist.md) is filled out and submitted in the team repo
worth: 10.0
- section: "[Infrastructure] Test Coverage"
description: Tests should cover at least 65% of your application and upload to Code Climate.
worth: 15.0
- section: "[Infrastructure] Code Quality"
description: All repositories have at least a "B" Grade on Code Climate.
worth: 10.0
- section: "[Infrastructure] Operational Excellence"
description: CI, Exceptions, Logging, and all other services listed in the requirements & `service.yml` example are all setup. Bootstrap script works. Service.yml is uploaded with no errors.
worth: 5.0
- section: "[Assignment Meta] Video"
description: A short video (~1.5 to 3 min) with a short write up (some bullet points explaining the video) has been provided that indicates the flows that have been implemented. This allows the teaching staff to mark and is often highly valued in a production company. Please note any areas which are still under development, or not fully implemented. Keep in mind the majority of the paths _should_ be implemented.
worth: 5.0
- section: Participation & Teamwork
description: |
Effectively worked as a team member and shared equitable work load during this assignment.
Communication was regular and effective & acted in accordance with team principles.
worth: 15.0
individual: true
due_date: 2025-04-09T23:59:59-04:00
position: 6
user:
- name: Participation, Teamwork, and Communication
worth: 20
file: assignments/participation_teamwork.md
submission: N/A
breakdown:
- section: General
description: |
**Participation on GitHub**
- Participated in GitHub Issues & Submitted GitHub PRs.
- Due as you pass in your software.
**Participation in lectures/courses**
- Participated in and viewed lectures, attended and engaged in-class presentations from guest speakers, demos, etc.
- Online discussions in Slack (#discussions) have engaging, value adding comments to add to the discussion.
- Team formation started/finished on time.
- Due on the last day of classes.
**Teamwork & Communication**
- Participated in all team work
- Answered at least 8 weeks of standups thoughtfully
- Adhered to team principles, communicated regularly/effectively, etc.
- Provided substantial feature development / software to the course
- Paragraph is provided in Quercus (-100% on this section if not provided).
- Due as you pass in your software (April 09, 2025).
worth: 100.0
due_date: 2025-04-09T23:59:59-04:00
multiple_due_dates: true
has_url: false
position: 7
- name: Bonus Assignment
worth: 2
bonus: true
file: assignments/bonus.md
submission: Blog Platform + Link on Quercus
breakdown:
- section: Work
description: General work according to the bonus assignment description
worth: 100.0
due_date: 2025-03-28T23:59:59-04:00
position: 8