1. By Daniel O’Brien and Scott MacDougall

2. Daniel O'Brien and Scott MacDougall comprised the development team and shared an equal distribution of roles and responsibilities. Story (Narrative) The office sells tickets to the customers in the city of Toronto, Ontario. The customers can order tickets online, on the phone, or in person. The ticket price is based on the event and the seat location. The ticket is delivered via walk in pickup, mailed, or printed from online. The customer can also ask for a refund if necessary. The office accepts membership cards or coupons for discounts. The office sells tickets to many types of events including sport, theatre, and concert. The office also keeps a record of sales in case of a sellout.

3. We used this diagram, provided by Igor Pustylnick, as template in tracking requirements in our project.

4. Use Case Context Diagram

5. FULL FUNCTIONAL SPECIFICATIONS FOR ORDER PLACEMENT (It is written in Stimulus-Response Format, IF Statements) 1.1 when customer places order 1.1.1 office checks database for Seating Availability in the Event Info 1.1.2 if the seats for the event are full, cancel transaction 1.1.3 if seats are available, accept order 1.2 upon accepting the order: Update Seating Availability when customer picks seat 1.2.1 customer can only pick from available seating, they can choose Number and Location of Seats 1.2.2 determine the Ticket Price based on Location and Number of Seats, using Event Info in Sales Records 1.2.3 charge the fee 1.2.4 determine, using the Customer's Info, if he/she is a Member and / or validate discounts/coupons

6. FULL FUNCTIONAL SPECIFICATIONS FOR ORDER PLACEMENT (It is written in Stimulus-Response Format, IF Statements) 1.2.5 calculate and charge the Ticket Price after discounts/coupons/memberships are taken into account 1.3 confirm whether or not the total final price has been fully paid: 1.3.1 if customer decides not to pay, cancel transaction and undo the update on seating availability 1.3.2 if paid, record the amount and method of payment used by the customer (debit, credit, cash) as well as Customer Info in the Order Info 1.3.3 if overpaid, also calculate the change due to the customer 1.3.4 if the fee is not fully paid, calculate and charge the remaining fee 1.3.5 if debit / credit card not approved, recharge the fee 1.3.6 if customer decides not to pay, cancel transaction and refund customer via method of payment, record all info on this interaction

7. FULL FUNCTIONAL SPECIFICATIONS FOR ORDER PLACEMENT (It is written in Stimulus-Response Format, IF Statements) 1.3.6.1 if customer wishes to dispute the interaction call for manger and / or security confirmation 1.3.7 if the customer pays via 2 methods of payment (ex: half debit and half cash), the 2 payment methods and their respective amounts are recorded in the Order. 1.4 after the Fee has been fully paid and the Order recorded in the Sales Records Database 1.4.1 print receipt

8. SPECIFICATIONS FOR ORDER PLACEMENT FOR USER INTERFACE

9. Ticket Office Payment Gateway External Interface Name CREDIT AUTHORIZATION INTERFACE Description Enables the system to send requests to the Credit Union Institution for authorization of credit card numbers Source Theatre Ticket Office System [TTOS] Destination The credit institution Timing On Demand Composition Source + Destination + Message_Number + credit_card_number + merchant_number + amount Units Dollars Limit/Range 1-999 Precision 2 decimal places Protocol IPX/SPX Name CREDIT CONFIRMATION INTERFACE Description Enables the system to receive confirmation of credit card numbers from the Credit Union Institution Source The credit institution Destination Theatre Ticket Office System [TTOS] Timing On Demand Composition Source + Destination + Message_Number + credit_card_number + merchant_number + amount+union_authorization Units Dollars Limit/Range 1-999 Precision 2 decimal places Protocol IPX/SPX Authorization Approved/Unapproved The external interface for Debit would be practically the same

10. Report Specifications

11. Report Mockup

12. User Interface: Order Input

14. Actors and Roles ONLINE ORDER TAKER: The Online Order Taker is a system created / purchased by the ticket office that places and modifies customer orders in the Sales Records Database of the Ticket Office. The Requests that require responses are: - Taking Orders - Cancelling Orders - Modifying Orders & Refunds - Entering & Updating Order Data - Identify Sales Method (visa and debit)(cash cannot be accepted online) - Enters & Updates Customer Data (Customer gets a card with a pin that they enter to record & verify their membership) - Enters & Updates Event Info i.e. Seating Availability - Prepares & delivers orders through print-out receipts and tickets (Which are emailed)

15. Actors and Roles BOX OFFICE TELLER: The Box Office Teller is a person employed by the ticket office that places and modifies customer orders in the Sales Records Database of the Ticket Office. The Requests that require responses are: - Taking Orders - Cancelling Orders - Modifying Orders & Refunds - Entering & Updating Order Data - Identify Sales Method (cash, visa, and debit) - Verifies Customer Data (for Memberships) - Enters & Updates Event Info i.e. Seating Availability - Prepares & delivers orders through print-out receipts and tickets

16. Actors and Roles TICKET OFFICE MANAGER: The Manager is a part of the Ticket Office Management Team that places and modifies customer orders in the Sales Records Database of the Ticket Office in the absence of employees. The Requests that require responses are: - Taking Orders - Cancelling Orders - Modifying Orders & Refunds - Entering & Updating Order Data - Identify Sales Method (visa, debit, and cash) - Enters & Updates Customer Data (Customer gets a card with a pin that they enter to record & verify their membership) (Manager is only person with authority who can modify this) - Enters & Updates Event Info i.e. Seating Availability - Prepares & delivers orders through print-out receipts and tickets

17. Actors and Roles BOX OFFICE CALL TAKER: The Box Office Call Taker is a Box Office Teller or Manager who can also take orders over the telephone. The Requests that require responses are: - Taking Orders - Cancelling Orders - Modifying Orders & Refunds - Entering & Updating Order Data - Identify Sales Method (cash, visa, and debit) - Verifies Customer Data (for Memberships) - Enters & Updates Event Info i.e. Seating Availability - Prepares & delivers orders through print-out receipts and tickets (Which are emailed)

18. Role Matrix

19. TellerCallerManagerOnline System

20. Work Session & Role Matrix

22. Workflow Diagram Part 1

23. Workflow Diagram Part 2

24. Workflow Diagram Part 3

25. Most of this was already covered in functional specifications

27. Software System Attributes: -Reliability: as reliable as a SQL database -Availability: 24/7 - security and maintainability: automatic backups, and data input monitoring (only managers can edit data such as a customer's membership status by entering a verification code).

29. Component Reusability Matrix

31. Order Components Diagram

32. Order Activity / Component Model (Process Flow)

33. Refund Components Diagram

34. Delivery Components Diagram

35. Technical Requirements and Architecture Considerations HARDWARE & SOFTWARE -system requires 4-way processor, 8GB of RAM -500GB of disk space, TCP/IP over Wireless & Wired LAN NETWORKS & DATABASES -written using ASP.NET, C#, and Microsoft SQL Server