Reference no: EM13337104
Spring Breaks ''R'' Us (SBRU) is an online travel service that books spring break trips to resorts for college students. The head office comprises 6 members of staff, all of whom are involved in the booking process; the manager and assistant manager in his absence, are also responsible for regular administrative duties such as payroll, accounts etc. Students have booked spring break trips for decades, but changes in technology have transformed the travel business in recent years. SBRU 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. SBRU contracts with dozens of resorts in key spring break destinations in Florida, Texas, the Caribbean, and Mexico. Its Web site 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. SBRU provides updated booking information, resort information updates, and travel information for booked students when they log in to the site. The resorts also need access to information from SBRU. 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 SBRU for the bookings, and they need to be able to report and collect for damages caused by springbreakers during their stay. SBRU has recently decided to upgrade its system to provide social networking features for students. It 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. Spring Breaks ''R'' Us (SBRU) requirements includes many use cases that make up the functional requirements. Consider the following description of the Booking subsystem. A few weeks before Thanksgiving break, it is time to open the system to new bookings. Students usually want to browse through the resorts and do some planning. After that, 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 when they leave, they need to check out. For the Social Networking subsystem SBRU is researching. Let us assume you were thinking about a number of potential domain classes that might be involved. For example, there would need to be information about a traveller attending a resort for a particular week. The traveller 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 traveller can associate with in the hopes of connecting to others. The resort has many locations where a traveller might be hanging out at any given time, and a traveller can note whether the location is "liked." People might schedule a party at a location and invite specific friends. It has been decided that the SBRU information system will comprise four subsystems: Resort relations, Student booking, Accounting and finance, and Social networking. The first three are purely Web applications, so access to those will be through an Internet connection to a Web server at the SBRU home office. The Social networking subsystem has built-in chat capabilities. It relies on Internet access for the students, as students compare notes before they book their travel reservations and as they chat while travelling. To function properly, the system obviously requires a wireless network at each resort during the trip. SBRU isn’t responsible for installing or maintaining the resort wireless network; they only plan to provide some design specifications and guidelines to each resort. The resort will be responsible for connecting to the Internet and for providing a secure wireless environment for the students.
• Design plan
• Technical requirements specification based on inputs, process and outputs.
• Hardware/Software Specification & Costing
• Component Diagram
• Package Diagram
• Network diagram
• Design Menu hierarchies and storyboards for the specified use cases