System: Online Ticket Sales System
Objective: Identify which stakeholder statements define the project context—that is: who interacts with the system, which external systems/devices it depends on, and what information flows in and out.
This exercise is worth 10 points. Your score is based on whether your reasoning correctly distinguishes context from internal design details.
This is the first exercise in the course project. Before you define features, you define the boundary:
Review the problem statement and the user statements. For each user statement, decide whether it helps define the project context. Then explain briefly why.
A quick rule: a statement helps define context if it answers one of these questions:
Our company needs a system to support the sale of tickets for shows at our venue. The venue is a single-auditorium facility. Seats are organized by section, row, and seat number so each seat can be uniquely identified.
We present a variety of events (plays, concerts, sporting events). Some events run multiple times per week; some have a single show. Each show uses a pricing strategy with price tiers and price types (adult, student, child, etc.). Seats are priced by associating each seat with a price tier. Pricing strategies may include optional volume discounts and can be reused across multiple shows.
Most tickets are sold through agents. Agents must have a legal contract with us before doing business. After a contract exists, the facilities manager sets up a sales agreement allowing agents to sell certain seats for a time window. Customers can also buy directly, but only seats not assigned to agents. Both customers and agents view availability through a seating chart. Selecting a seat places a temporary hold; purchasing issues a ticket that is mailed to the customer.
For each statement (1–10), write either Context or Not Context, then explain why in 1–2 sentences.
Tip: “Context” usually points to actors, external departments/systems, interfaces, or information handoffs. “Not Context” is usually an internal rule, pricing algorithm detail, or a design decision you would address later.