| Recovery from remote service failure |
When a remote service fails, reestablish connectivity within 1 minute of its detected availability, under normal store load in a production environment. |
1) Current flexibility- local client-side simplified services are desirable and accepted until reconnected. 2) Evolution- none |
High impact on the scability of the design. |
H |
M |
| Recovery from remote database failure |
As above |
1) Current flexibility- current data is kept in MySQL, but if connection fails then local client-side use of cached information is acceptable until reconnected. 2) Evolution- There will be mass storage and replication solutions. |
As above |
H |
H |
| Support many third-party services (ticket inventory, sports tournaments, ticket prices) They will vary at each installation. |
When a new third-part system must be integrated, it can be almost immediately via front-end or back-end developer. |
1) Current flexibility- adding new sporting events, ticket inventory, and ticket prices. 2) Evolution- Some period of time there should be a system put in place for administrators to input events, tickets, and prices themselves, without developers involvement. |
Low design impact as the data is input into the system, but nothing about the design is changed. |
H |
L |
| Current tax rules must be applied. |
When user is purchasing ticket, all government and state taxe rules should be applied to purchase. |
1) Current flexibility- Current tax rules are not put in place yet. 2)Evolution- Implementing tax rules once system is put out to public |
Failure to comply is a criminal offense. |
H |
L |
