-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathJustTheTicket-Requirements.txt
129 lines (109 loc) · 5.36 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
REQ-ID:
Description:
Type:
Rationale:
Originator:
Comments: [M814-ModuleChair] Copy this template below to add new requirements.
REQ-ID: PJ1
Description: The product shall be able to un-allocate tickets from a customer
Type: Functional Requirement
Rationale: To enable returned tickets to be scheduled for re-allocation
Originator: Polly
REQ-ID: PJ2
Description: The product shall be able to add returned tickets to a re-allocation schedule
Type: Functional Requirement
Rationale: To enable returned tickets to be re-allocated when a schedule runs
Originator: Polly
REQ-ID: SH2
Description: The product will display all tickets a customer currently owns
Type: Functional Requirement
Rationale: The customer will need some record of their currently owned tickets in order to choose one or more for returning, if they want to
Originator: Polly
REQ-ID: DIA1
Description: It must be possible to view all the tickets a customer has returned
Type: Functional Requirement
Rationale: So that it is possible to detect if a customer is returning many tickets / attempting to commit fraud
Originator: Polly
REQ-ID: DIA2
Description: It must be possible for the review staff to view the reason for returning the tickets
Type: Functional Requirement
Rationale: So that it is possible to identify if there are common reasons or causes for returning tickets
Originator: Thomas
REQ-ID: MG1
Description: The product shall check a returned ticket against that customer’s ticket purchases
Type: Functional Requirement
Rationale: To verify that the customer has previously purchased the ticket
Originator: Thomas Shelby - Business Development
REQ-ID: RJE1
Description: The product shall accept the returned ticket(s) selected by the customer.
Type: Functional Requirement
Rationale: The returned ticket(s) are required to enable the appropriate tickets within the real time inventory to be identified and made available for re-sale.
Originator: Thomas Shelby – Business Development Manager
REQ-ID: WD1
Description: The product shall refund customers using original payment method.
Type: Functional Requirement
Rationale: By refunding the original payment method reduces the risk of fraud and restricts black market trading.
Originator: Thomas Shelby, Customer
Comments: [William Donnell] Added as part of TMA02 - Q4b
REQ-ID: AEG1
Description: The product shall allow payments for tickets to be refunded.
Type: Functional Requirement
Rationale: To enable fair dealings with customers who for any reason no longer require their tickets and have already made payments.
Originator: Thomas Shelby
REQ-ID: AEG2
Description: The product shall allow reallocation of tickets every 24 hours.
Type: Functional Requirement
Rationale: To enable reselling returned tickets to enable full venues which generates a good atmosphere and also to enable meeting target revenue.
Originator: Polly Gray
REQ-ID:pj01
Description:The application shall record tickets that have been returned
Type:Functional requirement
Rationale:To be able to reallocate the ticket recorded as once successfully returned
Fit Criterion:The user shall be able to return the valid purchased ticket easily.
Originator:Thomas
Comments: [AmbikaBabu]Added a functional requirement related to the return ticket for reallocation process.
REQ-ID: JG2
Description: The product shall provide reporting on the reasons for return.
Type: Functional requirement
Rationale: Reporting output must be provided to facilitate the analysis and potential as proposed by Polly to understand trends and tackle the potential for fraud.
Originator: Polly Gray
REQ-ID: NW1
Description: The product shall produce Tickets that have a UID (Unique Identifier)
Type: Functional requirement
Rationale: To enable each ticket to be tracked and traced for refund or audit.
Originator: Thomas
REQ-ID: NW2
Description: The product shall be able to find a ticket either by UID or customer details
Type: Functional requirement
Rationale: To enable specific tickets to be refunded.
Originator: Thomas
REQ-ID: RC1
Description: The product shall allow the customer to select the ticket(s) they want to return
Type: Functional Requirement
Rationale: To verify which ticket(s) are to be unallocated.
Originator: Thomas Shelby (Business development)
Comments: [Ryan Cooper] Added as part of TMA02 Question 4b
RQ1 -S.K Description: Reallocate returned tickets
Rationale: To allow the customers on the waiting list to be allocated the returned tickets
Originator: Thomas
REQ-ID:KC1
Description:The product shall create a ticket purchasing waiting list for events viewable by staff.
Type: Functional requirement
Rationale: Allows staff to view order of attempted purchase
Originator: Staff
REQ-ID:KC2
Description:The product waiting list shall display exact number of tickets customers need
Type:Functional
Rationale: When assigning returned tickets, seeing the desired amount will make the process more efficent
Originator: Staff
REQ-ID:TP1
Description: The product shall allow the customer to return the purchased tickets if the customer should not need them.
Type: Functional
Rationale: Customers have to select the correct ticket to be returned from the list of available Tickets.
Originator: Thomas
REQ-ID:TP2
Description: The product shall manage the reassignment of the returned tickets.
Type: Functional
Rationale: To reassign the unused tickets to the inventory to be sold again.
Originator: Polly
Comments: [Tommaso Paci] Added as part of TMA02 Question 4b