-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathJustTheTicket-Requirements.txt
90 lines (76 loc) · 4.45 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
REQ-ID:
Description:
Type:
Rationale:
Originator:
Comments: [M814-ModuleChair] Copy this template below to add new requirements.
REQ-ID: 006
Description: The system shall record every transaction a given customer makes.
Type: Functional
Rationale: A full purchase/refund history is necessary in order to facilitate customer management and future purchase suggestions.
Originator: Leslie Patterson - Business developer
REQ-ID: 007
Description: When ticket(s) are returned, the system shall capture the reason for the return
Type: Functional
Rationale: As part of the fraud prevention process, the reasons for ticket returns will be analyzed.
Originator: Edna Everage — Domestic Ticket Sales
REQ-ID: 008
Description: The system shall require the customer to authenticate themselves when returning a ticket
Type: Functional
Rationale: As part of the fraud prevention process, security measures should be in place to prevent tickets being returned by someone other than the customer who purchased them
Originator: Edna Everage — Domestic Ticket Sales
REQ-ID: 009
Description: The system shall check that the returned tickets belong to the customer making the request.
Type: Functional
Rationale: It must be ensured that the provided identifiers of the tickets to be returned really belong to the identified user.
Originator: Barry McKenzie - Lead business analyst
REQ-ID: 010
Description: The system shall notify the user that the tickets have been revoked and a refund made.
Type: Functional
Rationale: The user must be assured of the successful revoking of the tickets and the refund made.
Originator: Barry McKenzie - Lead business analyst
REQ-ID: 011
Description: The system shall display all valid tickets for upcoming events from the identified customer
Type: Functional, technological requirement
Rationale: The customer need to be able to select the tickets he wants to return
Originator: Lesslie Patterson, Business Developer
REQ-ID: 012
Description: The system shall send refund information to the credit card company
Type: Functional, business requirement
Rationale: The customer wants to have his money back
Originator: Lesslie Patterson, Business Developer
REQ-ID: 013
Description: The system shall store all returned tickets within 24h.
Type: Function, business requirement
Rationale: Unallocated tickets need to be reallocated on a daily basis.
Orginator: Edna Everage
REQ-ID:016
Description:The product shall display terms & conditions and cancellation policy
Type: Functional
Rationale:to be able to state contractual agreement between customer and interested stakeholders before proceeding with the transaction in order to avoid fraud
Originator:Edna Everage
REQ-ID:028
Description: The customer can also return partly tickets. For example a customer has bought 5 tickets of one event and should be able to return any quantity.
Type: Functional
Rationale: The returned ticket Use Case is introduced to prevent fraud. In case a group wanted to join an event but one participant is sick the ticket should be returned. This would reduce the sale of ticket at the games and would prevent unwanted high ticket prices.
Originator: Barry McKenzie
REQ-ID:032
Description: The customer shall be able to navigate easily to 'buy tickets' after the notification of successful returned tickets was shown (REQ10)
Type: Functional
Rationale: The user has shown general interest in the events, but was not able to use the tickets. It should be easy to buy replacement-tickets.
Originator: Barry McKenzie
REQ-ID:033
Description: The system should allow the customer the ability to cancel the return of tickets if these are not yet reallocated.
Type: Functional
Rationale: The user has change its mind regarding the number of tickets to return and the system didn't reallocate them yet to other users. This would reduce the overall number or required reallocations.
Originator: Barry McKenzie
REQ-ID: 034
Description: The system shall identify tickets returned for events that are fully booked
Type: Functional
Rationale: For the mainstream service these returns will require particular attention with regard to reallocation
Originator: Barry McKenzie
REQ-ID: 035
Description: The system shall allow the customer to return any tickets they possess for future events
Type: Functional
Rationale: As tickets are in high demand, we should allow customers who are no longer able to attend an event to return their tickets so that other customers are have the opportunity to attend the event.
Originator: Edna Everage - Domestic Ticket Sales