Reference no: EM133459808
SHOTS is a Student Hospitality Online Travel Service that books spring break trips to resorts for college students. Students have booked spring break trips for decades, but changes in technology have transformed the travel business in recent years. SHOTS moved away from having campus reps with posted fliers and moved to the Web early on. The basic idea is to get a group of students to book a room at a resort for one of the traditional spring break weeks. SHOTS contracts with dozens of resorts in key spring break destinations like Florida, Texas, the Caribbean, and Mexico. Its Website shows information on each resort and includes prices, available rooms, and special features. Students can research and book a room, enter contract information, and pay deposits and final payments through the system.
SHOTS provides updated booking information, resort information updates, and travel information for booked students when they log into the site. The resorts also need access to information from SHOTS. They need to know about their bookings for each week, the room types that are booked, and so forth. Before the spring break booking season starts, they need to enter information on their resorts, including prices and special features. Resorts need to be paid by SHOTS for the bookings, and they need to be able to report and collect for damages caused by spring breakers during their stay.
SHOTS has recently decided to upgrade its entire system to provide better services and to expand its customer base in the future. It also plans to provide social networking features and is currently researching possibilities and collecting information from prospective customers about desirable features and functions. From the business standpoint, the idea is to increase bookings by enhancing the experience before, during, and after the trip.
SHOTS includes many use cases that make up the functional requirements. Consider the following description of the Booking subsystem. A few weeks before Spring break, it is time to open the system to new bookings. Students usually want to browse through the resorts and do some planning. When a student or group of students wants to book a trip, the system allows it. Sometimes, a student needs to be added or dropped from the group or a group changes size and needs a different type of room. One month before the actual trip, it is time for the system to send out final payment requirement notices. Students cancel the booking or they pay their final bills. Students often want to look up their booking status and check on resort details. When they arrive at the resort, they need to check in; and they leave, they need to check out.
Consider the SHOTS Social Networking subsystem, and the potential domain model that might be involved in this subsystem. For example, there would need to be information about a traveler attending a resort for a particular week. The traveler would be assigned to a room along with roommates but might also be connected to other friends. There might be different interests or hobbies a traveler can associate with in hopes of connecting to others. The resort has many locations where a traveler might be hanging out at any given time, and a traveler can note whether the location is "liked". Travelers can also rate or provide comments about the resorts. People might schedule a party at a location and invite specific friends. Many options and features are still being considered.
Complete the following tasks:
1. Provide 10 functional requirements.
2. Provide 10 non-functional requirements.
3. Describe 10 business rules that may affect the system.