Problem Life Cycle
Problem Domain Analysis
Define Project Context
Data Dictionary Advantages
Weak Strong Aggregation
UML Define Cohesion
Use Case Diagram
Use Case Model
Extended Use Case
Project Scope - Exercise
Define the scope of the course project system
Select the user statements that help you define the scope of the course project system.
This exercise is worth a total of 10 points
This is the second exercise in the course project.
No downloadable files are required to complete this exercise.
Review both the problem statement and user statements below. Which of the user statements helps you define the scope of the course project system?
As you read the user statements, keep these questions in mind:
Are there other related projects planned or underway? Where do the different projects intersect?
Are later phases planned? How much do we attempt in each phase?
How much of the functionality will remain manual? Where is the boundary between manual and automated processes?
What aspects of the functionality are more hardware than software dependent?
Should we include (specific feature or requirement)?
Online Ticket Sales System
Our company needs a system to support the sales of tickets for shows at our venue. The venue is a single auditorium facility. The seats are arranged within the venue in sections, rows, and seat numbers so that we can uniquely identify each seat.
We present a wide variety of events such as plays, concerts, and even sporting events. Some of our events are long running with multiple shows each week. Some events have only one show, such as a sporting event.
We use what we call a pricing strategy for each show. A show pricing strategy is made up of one or more price tiers or pricing levels. Each price tier defines a price for each price type that we offer, for example, adult, student, and child prices. Every seat in a show is priced by associating each seat with one of the price tiers for that show.
The pricing strategy can also include a volume discount, but not all shows offer a discount. Also, the same pricing strategy can be used for any number of shows. For example, we use the same pricing strategy for all our Saturday matinees.
Most of our tickets are sold through agents. Agents must have a legal contract with us before we can do business. Once they have a contract, the facilities manager sets up a sales agreement with the agent. The sales agreement gives the agent permission to sell certain seats for a period of time. The agent can sell tickets for the assigned seats for any shows that take place during that period.
Individual customers can also buy tickets directly from us. They can access only the seats that are not assigned to agents. Both customers and agents view the available seats through a seating chart. When a customer or agent selects a seat on the seating chart, he or she effectively puts a hold on the seat so that no one else can select it until he or she either releases it or buys it. Once the customer or agent buys the seat, the ticket is issued and mailed to the customer.
We do not keep track of what agency the agents work for. They move around too often, and it really does not affect their relationship with us.
We already have a database that is working really well for us.
Only the venue manager can set up promotions.
The legal department sets up the agent contracts in their system.
Mailing rates and methods are handled in the mailroom.
Tickets will include the seat location, price, applied discount, and date and time of the event.
We would like eventually to offer season tickets, but we should wait until we have the rest of the system working.
When agents sell the tickets, they basically use the same features as customers would use. The only difference is in what seats they see as available for sale.
Events can be set up without entering any of the performance dates and times.
In phase 2, we plan to let agents see their commissions during each sale.
Submitting your exercise
For each of the user statements above, indicate in the text box below whether or not the statement helps you to define the scope of the course project system. Briefly explain why it does or why it does not.