Case Studies

Case Studies - Systems Analysis and Design in a Changing...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Systems Analysis and Design in a Changing World, Fourth Edition 5-1 Case Studies Case Study: Spring Breaks ‘R’ Us Travel Service Booking System 1. To what events must the SBRU booking system respond? Create a complete event table listing the event, trigger, source, use case, response, and destination for each event. Be sure to consider only the events that trigger processing in the booking system, not the SBRU accounting system or the systems operated by the resorts. List of events and resulting use cases with explanations: 1. Event: Resort submits availability information. Use case: Record resort availability information. This is the information sent to SBRU in the fall indicating what rooms are available and what the rates are for each week. The system records this information. 2. Event: Time to produce brochure information for college representatives. Use case: Produce brochure information. As soon as December arrives, the system takes all of the resort information that has come in and produces the brochure information. Note that the format of the brochure might be a printed document or a Web site. A logical model would not indicate how the brochure was implemented or how it gets to the college representative. 3. Event: Student group requests a reservation. Use case: Book student group. A group of students submits a reservation request for a specific resort during a specific week. Note that the college representative might interact with the students, but that interaction is outside the scope of this system as it is defined. No information is captured until the student group actually makes a reservation. 4. Event: Time to produce booking information for resorts. Use case: Produce booking information for resorts. Before each spring break week begins, the system produces a list for each resort that shows who has booked rooms for that week. Each resort uses the information to check in arriving students. What the resort does is outside the scope of this system. A student paying the resort is also outside the scope of this system. Resorts later send commissions to SBRU accounting, which again is outside the scope of this system.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Systems Analysis and Design in a Changing World, Fourth Edition 5-2 5. Instructors might include an additional event for producing booking reports every week for management of SBRU, although nothing was specifically mentioned in the case. Similarly, reports might be sent to the resorts or to college representatives to indicate how well bookings are going. You might assume that accounting can read data about bookings from the database to reconcile commission checks (accounting is a separate system), or that the booking system can generate a report for accounting at the end of each spring break week or at the end of the spring break season. Event Table and Use Cases
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 15

Case Studies - Systems Analysis and Design in a Changing...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online