Skip to Content
0 Votes
Version 3.1 by Doug McCord on 2023/05/25 10:05
Show last authors
1 {{toc/}}
2
3
4
5 (% id="HIntroduction" class="western" %)
6 = (% style="font-family:Arial,Helvetica,sans-serif; font-size:16pt" %)Introduction(%%) =
7
8
9 1. (((
10 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Statement of Purpose**
11 )))
12
13 (% style="margin-left:48px" %)
14 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; line-height:115%" %)The goal of the Role-Playing Game Consent Application is to provide players of role-playing games an anonymous way to submit their consent, potential discomfort or opposition to a gamemaster in real-time, during gameplay (see definitions below).
15
16 (% style="margin-left:48px" %)
17 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; line-height:115%" %)This application should make use of mobile technology to be available as a downloadable app, and also be available as a webpage. It should be open source, simple to use and provide anonymous communication to a Consent Group Manager from a group of Participants in the form of a stoplight metaphor with three color options: green, yellow and red.
18
19
20 (% start="2" %)
21 1. (((
22 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Definitions and Abbreviations**
23 )))
24
25 :
26
27 (((
28 (% cellspacing="0" style="border-collapse:collapse; width:722px" %)
29 |(% style="background-color:#d0cece; border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:1px solid #000000; padding:0in 0.08in; width:157px" %)(((
30 (% style="font-family:Arial,Helvetica,sans-serif; font-size:9pt" %)**Term**
31 )))|(% style="background-color:#d0cece; border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:1px solid #000000; padding:0in 0.08in; width:523px" %)(((
32 (% style="font-family:Arial,Helvetica,sans-serif; font-size:9pt" %)**Definition**
33 )))
34 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:1px solid #000000; height:49px; padding:0in 0.08in; width:157px" %)(((
35
36
37 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Consent Group
38 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:1px solid #000000; padding:0in 0.08in; width:523px" %)(((
39
40
41 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Consent Group refers to those users of the Role-Playing Game Consent Application who are all accessing the application using the same Consent Group Code, to either send consent status notifications (for Participants, or PCs) or receive consent status notifications (for the Consent Manager, or CM). In the context of a role-playing game, this might be a single game session’s gamemaster and all of its players, for example.
42
43
44 )))
45 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; height:49px; padding:0in 0.08in; width:157px" %)(((
46
47
48 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Consent Group Code
49 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; padding:0in 0.08in; width:523px" %)(((
50
51
52 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)A unique code that allows a Participants (PC) to join a Consent Group with a single Consent Manager (CM) and other Participants (PCs). These codes are generated and distributed by the Consent Manager (CM).
53
54
55 )))
56 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; height:49px; padding:0in 0.08in; width:157px" %)(((
57
58
59 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Consent Manger (CM)
60 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; padding:0in 0.08in; width:523px" %)(((
61
62
63 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Consent Manager (or CM) refers to the one user per Consent Group that receives all consent notifications (anonymously) from that Consent Group’s Participants (or PCs). While a CM may or may not also be a role-playing game’s gamemaster (or GM), there may only be one CM per Consent Group. Note that this role also generates Consent Group Codes and is responsible for distributing them to invited Participants (PCs).
64
65
66 )))
67 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; height:49px; padding:0in 0.08in; width:157px" %)(((
68
69
70 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Gamemaster (GM)
71 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; padding:0in 0.08in; width:523px" %)(((
72
73
74 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Here used to refer to a role-playing game participant that serves as the game organizer and primary facilitator, often relaying and controlling aspects of the game world which don’t include the players themselves and their actions. Often compared to a storyteller, in the game Dungeons & Dragons this role is called a “Dungeon Master” (or DM), for example.
75 )))
76 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; height:49px; padding:0in 0.08in; width:157px" %)(((
77
78
79 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Open Source
80 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; padding:0in 0.08in; width:523px" %)(((
81
82
83 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Used here to refer to code, or text written in a programming language, that is made freely available for others to utilize and/or modify.
84
85
86 )))
87 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; height:49px; padding:0in 0.08in; width:157px" %)(((
88
89
90 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Participant with Consent (PC)
91 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; padding:0in 0.08in; width:523px" %)(((
92
93
94 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)In this context, the abbreviation ‘PC’ refers to application users in the role of Participant with Consent. While these may or may not also be a role-playing game’s players (which may also be known as ‘PC’ or player character in gaming), in the application, members with this role join a Consent Group with a provided Consent Group Code and may only see their own consent status. Defaulting to green, this status may be changed to yellow or red to notify a Consent Manger (or CM) in the Consent Group that the PC is uncomfortable or opposed to game activities.
95
96
97 )))
98 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; height:49px; padding:0in 0.08in; width:157px" %)(((
99
100
101 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Player
102 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:none; padding:0in 0.08in; width:523px" %)(((
103
104
105 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Here used to refer to role-playing game participants who control single or multiple players within a game, but not the game world or storyline otherwise. Typically, role-playing games consist of a single gamemaster and multiple players. Note that this is sometimes also known as a player character.
106
107
108 )))
109 |(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:1px solid #000000; height:57px; padding:0in 0.08in; width:157px" %)(((
110
111
112 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Role-Playing Game
113 )))|(% style="border-bottom:1px solid #000000; border-left:1px solid #000000; border-right:1px solid #000000; border-top:1px solid #000000; padding:0in 0.08in; width:523px" %)(((
114
115
116 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)A game wherein players take on the roles of separate characters within a fictionalized game world. Note that these games may take many forms, such as with tabletop games (such as with pencils, paper and dice), video or electronic games (such as on a gaming console or computer) or live-action gaming involving movement in the world and costumes.
117
118
119 )))
120 )))
121
122
123
124 (% start="3" %)
125 1. (((
126 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Expected Users**
127 )))
128
129 (% style="margin-left:48px" %)
130 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Consent Application will be free and open source, with expected users being players and gamemasters of role-playing games of all kinds, as well as potentially other gamers (such as video gamers or for other tabletop game types), or members of any organization who wish to share consent anonymously in real time from team members to a single organizer or team manager.
131
132
133 (% start="4" %)
134 1. (((
135 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Scope Limitations and Preconditions**
136 )))
137
138 (% style="margin-left:48px" %)
139 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)This application will be developed and tested to run on the following currently active web browsers only: Firefox, Chrome, Safari and Bing. The application will be developed and tested to run on IOS and Android mobile devices available at the time of release. While simple help documentation may be provided in-app, the application itself will not educate users fully on its use and end goals.
140
141 (% style="margin-left:48px" %)
142 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Consent Manager is responsible for distributing Consent Group Codes to potential users. The application does not provide a means of automatically distributing these codes or searching out potential users.
143
144
145 (% start="5" %)
146 1. (((
147 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Workflow**
148 )))
149
150 (% style="margin-left:48px" %)
151 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**{Diagram/s here}**
152
153
154 (% id="HFunctionalRequirements" class="western" %)
155 = (% style="font-family:Arial,Helvetica,sans-serif; font-size:16pt" %)Functional Requirements(%%) =
156
157 1. (((
158 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Business Requirements**
159 )))
160
161 (% style="list-style-type:lower-alpha" type="a" %)
162 1. (((
163 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The application must have two user modes: Consent Manager (CM) Mode and Participant with Consent (PC) Mode. (**F1**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
164
165 (% style="list-style-type:lower-roman" type="i" %)
166 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)The CM Mode must:
167 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow for the generation of unique Consent Group Codes as part of creating a new Consent Group. Each group will have its own, unique code. (**F2**)
168 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow for up to five different Consent Groups to exist concurrently for a single CM. (**F3**)
169 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow for the deletion or removal of an existing Consent Group. This requires an additional step of verification from the CM, to prevent accidental removals. (**F4**)
170 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow for the entry to and exit from each Consent Group individually in the interface. The status indicators should not be visible outside of the Consent Group. (**F5**)
171 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Within each Consent Group in CM Mode, the application must:
172 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Display the number of users currently registered to this Consent Group. (**F6**)
173 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Display the consent status indicator for the Consent Group consisting of three possible options: red, yellow or green. (**F7**)
174 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow the CM to set the Consent Group status back to green. (**F8**)
175 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow the CM to set a text name for each Consent group. This name is for display purposes only and is shared with a Consent Group’s PCs. (**F9**)
176 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The PC mode of the application must:
177 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Allow users to join an existing Consent Group by entering a Consent Group Code. (**F9**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
178 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow for up to five different Consent Groups to exist concurrently as PC. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F10**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
179 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow entry to and exit from each joined Consent Group individually, one at a time. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F11**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
180 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Provide a message for any Consent Group that the PC was a member of that’s been deleted by the CM. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F12**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
181 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Within each Consent Group in PC Mode, the application must:
182 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Display the Consent Group name as set by the CM. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F13**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
183 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Display the PC’s current status as one of three possible color options: red, yellow or green. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F14**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
184 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow the PC to change their current status by choosing one of the other two status options. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F15**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
185 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Provide the PC visual feedback for any status change that has reached the CM. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F16**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
186 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Provide the PC visual feedback when the CM resets the Consent Group status color back to green if this PC submitted a changed status level. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F17**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
187 111. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)Allow for the quitting from an existing Consent Group, with a verification provided prior to final submission. ((% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**F18**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
188 )))
189
190 (% id="HNonfunctionalRequirements" class="western" %)
191 = (% style="font-family:Arial,Helvetica,sans-serif; font-size:16pt" %)Nonfunctional Requirements(%%) =
192
193 (% start="6" %)
194 1. (((
195 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Access Requirements**
196
197 (% style="list-style-type:lower-alpha" type="a" %)
198 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Game Consent Application must support the following accessibility options:
199 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Single key/input selection option (touch alternative). (**N1**)
200 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)High contrast color scheme. (**N2**)
201 11. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Text zoom. (**N3**)
202 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Only users who have entered a unique Consent Group Code may be allowed to send a consent status update to that group’s CM. It must not be possible for other outsider users to see these indicator updates or the Consent Group status code without first joining a Consent Group with a Consent Group Code. (**N4**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
203
204
205 )))
206 1. (((
207 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Performance Requirements**
208
209 (% style="list-style-type:lower-alpha" type="a" %)
210 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Game Consent Application must be able to run on currently available IOS and Android mobile phones as downloaded from the Apple App Store and the Google Play app store. (**N5**)
211 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Game Consent Application must be able to run on currently available IOS and Android tablets as downloaded from an app store. (**N6**)
212 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Game Consent Application must be able to run on the following available web browsers in their release versions dating from January 2021 to the time of release: Firefox, Chrome, Safari and Bing. (**N7**)
213 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The application must load on all of the above formats with minimal wait times. (**N8**)
214 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Status updates within a Consent Group must move from PC to CM, with visual feedback sent back to PC within ten seconds where a viable internet connection exists. (**N9**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
215 )))
216
217 (% start="8" %)
218 1. (((
219 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Support Requirements**
220
221 (% style="list-style-type:lower-alpha" type="a" %)
222 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Game Consent Application must offer simple, built-in help text. (**N10**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
223 1. (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)The Role-Playing Game Consent Application must be able to refer users to link to online resources, such as FAQ or help sites. (**N11**(% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %))
224 )))
225
226 (% start="9" %)
227 1. (((
228 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Miscellaneous Application Requirements**
229
230 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt; font-weight:normal" %)None.
231 )))
232
233 (% id="HUseCases" class="western" %)
234 = (% style="font-family:Arial,Helvetica,sans-serif; font-size:16pt" %)Use Cases (TBD)(%%) =
235
236 (% start="10" %)
237 1. (((
238 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**User Use Cases**
239
240 (% style="list-style-type:lower-alpha" type="a" %)
241 1.
242
243 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Use Case 1:
244
245 (% style="list-style-type:lower-roman" type="i" %)
246 1.
247 11.
248
249 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Name:
250
251 1.
252 11.
253
254 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Overview:
255
256 1.
257 11.
258
259 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Actors:
260
261 1.
262 11.
263
264 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Preconditions:
265
266 1.
267 11.
268
269 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Postconditions:
270
271 1.
272 11.
273
274 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)Flow of Events:
275
276 1.
277 11.
278 111.
279
280
281 )))
282
283 (% start="11" %)
284 1. (((
285 (% style="font-family:Arial,Helvetica,sans-serif; font-size:10pt" %)**Support Use Cases**
286 )))