-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathJustTheTicket-Requirements.txt
227 lines (185 loc) · 11.3 KB
/
JustTheTicket-Requirements.txt
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
REQ-ID: AF-001
Description: The product shall check if the ticket is already expired
Rationale: To avoid unrightful refund claims
Originator: Customer
Comments: [AF-001] Created and committed 11th Feb 2019.
REQ-ID: AF-002
Description: The product shall updates DMS (live ticket information database) about returned ticket statuses according to the decision of the “Ticket Review Team”.
Rationale: To make returned tickets available again
Originator: Ticket Review Team
Comments: [AF-002] Created and committed 11th Feb 2019.
REQ-ID: AM-001
Description: Find the tickets and ensure validity
Rationale: to verify that the tickets haven’t already been returned, refunded, or reallocated.
Originator: Polly Gray
Comments: [AM-001] Created and committed 02-FEB-2019.
REQ-ID: AM-002
Description: Capture the reasons for customer return
Rationale: to monitor a potential pattern of fraud
Originator: Polly Gray
Comments: [AM-002] Created and committed 02-FEB-2019.
REQ-ID: CS-002
Description: The system will ensure that tickets are returned to a reallocation pool, not back to the general inventory.
Rational: To ensure that tickets are reallocated to those on the waiting list and not purchased as a general sale.
Originator: Polly Gary
REQ-ID: JF-001
Description: The product shall check that the tickets belong to the customer
Type: Functional
Rationale: To ensure that the customer who wants to return the tickets is the owner of them
Fit Criterion: The system fulfils this requirement if it only allows to return tickets that the customer bought
Originator: Polly Gray
Comments: [JF-001] Created and committed 13-FEB-2019
REQ-ID: OH-001
Description: The website should allow the customer to enter ticket number(s) to initiate a ticket return.
Rationale: Entering the ticket numbers would allow the system to track down the related event and the customer who initially purchased the ticket(s).
Originator: Thomas Shelby.
Comments: [OH-001] Created and committed 10th Feb 2019.
REQ-ID: OH-002
Description: The website should allow a customer to login with a personal combination of username and password.
Rationale: Allowing customers to login with their individual username and password would enable the application to identify and verify the customer identity that initiated the ticket(s) return.
Originator: Thomas Shelby.
Comments: [OH-002] Created and committed 10th Feb 2019.
REQ-ID: PC-001
Description: The product shall allow the user to specify any concessionary requirements
Rationale: The system must be able to prioritise the re-allocation of returned tickets in a fair way.
Originator: Thomas Selby
Comments [PC-001] Created and committed 13-FEB-2009
REQ-ID: PC-002
Description: The system shall allow a user to accept or reject a ticket allocated via the reallocation process
Rationale: As these tickets will be allocated via an automated process, the new customer should be able to consent before the system takes payment.
Originator: Polly Gray
Comments [PC-002] Created and committed 13-FEB-2009
REQ-ID: RB-001
Description: The system shall search for the customer registration to identify the customer returning ticket
Rationale: To check if the person intending to return the ticket is a registered customer and the same who made that ticket purchase
Originator: Thomas Shelby
Comments: [RB-001] Created and committed 09-FEB-2019. Recommited to take scree shot for the solution document 15-FEB-2019.
REQ-ID: SAB-001
Locate Ticket purchased
Description: The system will access copy of ticket stored.
Rationale: To ensure the authenticity of returned ticket(s).
Originator: Thomas Selby
REQ-ID: SS-002
Description: The product shall calculate the correct refund amount for returned ticket(s).
Rationale: To avoid legal and reputational consequences, the customer must receive the correct refund based on the ticket(s) original purchase price despite potential variations in price since original purchase.
Originator: Polly Gray
Comments: [SS-002] Created and committed 12-FEB-2019.
REQ-ID: TC-001
Description: The software must be able to identify specific bookings using information provided by the user who made the booking
Rationale: To allow a user to collect tickets or amend the booking.
Originator: Polly Gray
Comments: [TC-001] Created and committed 10-FEB-2019.
--Removed Duplicates--
Duplicates of AF-001:
REQ-ID: CC-001.
Description: The system shall only allow a ticket refund if the sporting event associated with the ticket has not taken place yet.
Type: 9
Rationale: Once a sporting event has taken place a customer cannot request a refund because the event is now in the past.
Originator: Thomas Shelby.
Comments: [CC-001] Created and committed 01-FEB-2019.
REQ-ID: CS-001
Description: The system will ensure that the event for which the tickets are being returned is in the future.
Rational: Refunds cannot be issued for events that are in the past.
Originator: Polly Gray
Duplicate of AF-002:
REQ-ID: DJT-002
Description – Returning a ticket will increase the number of tickets available for an event
Rationale – A ticket return will reduce ticket allocation for an event and hence increase the number of tickets available for sale
Originator - Polly Gray - responsible for domestic ticket sales for the XXII Commonwealth Games
Comments: [DJT-002] Created and committed 09th Feb 2019
Duplicate of AM-001:
REQ-ID: JF-002
Description: The product shall check that the tickets are valid for return
Type: Functional
Rationale: To ensure that the tickets can be returned
Fit Criterion: The system fulfils this requirement if it only allows to return tickets that are accepted to be returned
Originator: Polly Gray
Comments: [JF-002] Created and committed 13-FEB-2019
Duplicate of AM-002:
REQ-ID: SS-001
Description: The product shall allow the customer to specify a reason for return for each ticket to be returned.
Rationale: The customer may return multiple tickets (for same event or different events) with each return having a different reason.
Originator: Thomas Shelby
Comments: [SS-001] Created and committed 12-FEB-2019.
Duplicates of CS-002:
REQ-ID: LA-001
Description: The system shall keep track and keep visible any tickets that are refunded.
Rationale: To ensure that any black market activity is reduced or eliminated and to ensure fair allocation of tickets issued.
Originator: Thomas Selby
REQ-IQ: LA-002
Description: The system shall ensure that any returned tickets are allocated to a fair reallocation pool.
Rationale: To ensure that tickets are fairly reallocated to a transparent waiting list so that return reasons are tracked and that return patterns are identified in order to eliminate fraudulent activities.
Originator: Polly Gray
REQ-ID: RB-002
Description: The system shall add the ticket to the reallocation list to be reallocated every 24 hrs
Rationale: To make any seats that has now become available to be reallocated to those on the waiting list in a manageable and consistent manner
Originator: Polly Gray
Comments: [RB-002] Created and committed 09-FEB-2019. Recommited to take scree shot for the solution document 15-FEB-2019.
Duplicate of JF-001:
REQ-ID: SAB-002
Confirm customer is the returned ticket Owner.
Description: The system will compare customer's identity to the accessed ticket customer,s identity.
Rational : To ensure decision to return is that of the original customer to avoid redudiation.
Originator : Thomas Selby
Duplicate of SS-002:
REQ-ID: TC-002
Description: The software must be capable of refunding money that paid for unwanted tickets to the user who originally paid.
Rationale: If a user does not get their money back it is likely to cause legal problems
Originator: Thomas Shelby
Comments: [TC-002] Created and committed 10-FEB-2019.
--Removed Out Of Scope --
REQ-ID: CC-002.
Description: The system shall support ticket requests originating from the general public, sponsor companies, sports officials from Commonwealth countries and competitor guests.
Type: 9
Rationale: The Commonwealth Games encourages attendance by the public, but must also fulfil an obligation to sponsors, officials and competitors by making a share of tickets available to all types of spectator.
Originator: Thomas Shelby.
Comments: [CC-002] Created and committed 01-FEB-2019.
REQ-ID: DR-001
Description: The system shall meet not exceed the revenue target by more than 5%.
Rationale: The system needs to make a profit but not to generate criticism.
Originator: Polly Gray
REQ-ID: DR-002
Description: The system must be transparent in its operation
Rationale: There must be no impression that any person or organisation has received preference ticket allocation.
Originator: Thomas Shelby
REQ-ID: DJT-001
Description – The Product should allocate a number of tickets to each event
Rationale – The product should determine a maximum allocation for each event so that ticket sales can be monitored for appropriate levels of sales to maintain a full stadium
Originator - Polly Gray - responsible for domestic ticket sales for the XXII Commonwealth Games while
REQ-ID: OH-001
Description: The website should allow the customer to enter ticket number(s) to initiate a ticket return.
Rationale: Entering the ticket numbers would allow the system to track down the related event and the customer who initially purchased the ticket(s).
Originator: Thomas Shelby.
Comments: [OH-001] Created and committed 10th Feb 2019.
REQ-ID: OH-002
Description: The website should allow a customer to login with a personal combination of username and password.
Rationale: Allowing customers to login with their individual username and password would enable the application to identify and verify the customer identity that initiated the ticket(s) return.
Originator: Thomas Shelby.
Comments: [OH-002] Created and committed 10th Feb 2019.
REQ-ID: JF-001
Description: The product shall check that the tickets belong to the customer
Type: Functional
Rationale: To ensure that the customer who wants to return the tickets is the owner of them
Originator: Polly Gray
Comments: [JF-001] Created and committed 13-FEB-2019
REQ-ID: JF-002
Description: The product shall check that the tickets are valid for return
Type: Functional
Rationale: To ensure that the tickets can be returned
Originator: Polly Gray
Comments: [JF-002] Created and committed 13-FEB-2019
REQ-ID: SS-002
Description: The product shall calculate the correct refund amount for returned ticket(s).
Rationale: To avoid legal and reputational consequences, the customer must receive the correct refund based on the ticket(s) original purchase price despite potential variations in price since original purchase.
Originator: Polly Gray.
Comments: [SS-002] Created and committed 12-FEB-2019.
REQ-ID: RB-002
Description: The system shall add the ticket to the reallocation list to be reallocated every 24 hrs
Rationale: To make any seats that has now become available to be reallocated to those on the waiting list in a manageable and consistent manner
Originator: Polly Gray
Comments: [RB-002] Created and committed 09-FEB-2019. Recommited to take scree shot for the solution document 15-FEB-2019.
REQ-ID: SS-001
Description: The product shall allow the customer to specify a reason for return for each ticket to be returned.
Rationale: The customer may return multiple tickets (for same event or different events) with each return having a different reason.
Originator: Thomas Shelby.
Comments: [SS-001] Created and committed 12-FEB-2019.