MIT113 Spring Breaks 'R' Us (SBRU) System Modeling and Analysis Assessment Answer

Introduction

The travel and tourism industry is not immune to the effects of the fast transformation that technology is having on other fields. The ever-changing nature of the spring break industry is shown in our case study, Spring Breaks 'R' Us (SBRU). SBRU is a website that helps college students plan vacations to various resorts during spring break. Although planning a vacation for spring break is nothing new, the arrival of new technologies has drastically altered the travel industry, calling for new tools and approaches.

SBRU has evolved from using approaches like campus reps handing out leaflets to relying heavily on an online community. SBRU has developed throughout time, adding new technologies and novel features in an effort to better serve its student body. SBRU has negotiated contracts with a wide variety of hotels in popular spring break locations, making their website a one-stop shop for students looking for information on hotels, room rates, and amenities. The website serves as a central hub where students can easily access resources, do research, book rooms, exchange contact information, and make payments. Further, SBRU provides customers with up-to-the-minute information on their bookings, accommodations, and itineraries.

The case study also includes an important new facet: the resorts. SBRU-affiliated hotels need quick and easy access to crucial data including bookings, room types, and rates. The financial component is also crucial, as they need to collect fees for reservations and deal with claims for damages caused by spring breakers. Therefore, SBRU has to set up a reliable system that can meet the requirements of both students and resorts while keeping communication flowing freely.

SBRU is launching an ambitious initiative to further modernize its system in response to the evolving nature of the travel industry and the aim to improve the educational experience for its students. The purpose of this update is to provide students with the opportunity to connect with one another before, during, and after school travels through the use of social networking capabilities. SBRU plans to increase bookings and strengthen its position in the market by taking a comprehensive approach.SBRU has broken down the massive undertaking into four manageable parts: resort relations; student booking; accounting and finance; social networking; and social media. This method facilitates a more organized and systematic development procedure that is tailored to the requirements of each individual subsystem. In the following pages, we will show how well we can translate business requirements into detailed system specifications by using Unified Modelling Language (UML) diagrams (Satzinger et al, 2015). In addition, we will provide a plan for developing and testing this intricate piece of software. Finally, we'll highlight our proficiency in communicating with a wide range of audiences so as to reflect the high standards of professionalism upheld by SBRU.

CRUD Analysis

Using the domain model and the use cases, a CRUD analysis evaluates the system's capacity to handle the four operations of creation, reading, updating, and deletion. Taking into account the domain model and the "Add a New Resort" and "Book a Reservation" use cases, let's do a CRUD analysis of the Spring Breaks 'R' Us (SBRU) system.

• Create

Create a New Resort

This function is used by the system administrators or other authorized users to register a new hotel with the system.

Application: "Add a New Resort"

Entity: Resort

Characteristics That Matter: Details including: name, address, phone number, email address, description, location, capacity, features, and cost

Put in a Request for a Seat

Booking a resort accommodation in advance for a spring break getaway is now possible.

The Case of "Reserving a Table"

Reservation System

Characteristics That Matter: Date of Arrival, Date of Departure, Number of Beds, Payment Amount, Date of Payment, Payment Type, The Terms of Sale

Make a Payment Record

To keep tabs on the money that comes in and goes out, the system creates a new payment transaction every time a user pays for a reservation.

The Case of "Reserving a Table"

Entity: PaymentTransaction

Characteristics That Matter: Amount, Date, Type, and Specifics of Payment

• Read

Resort Information

Resort characteristics, rates, and availability are just some of the details that can be viewed by users.

Entities: Details About the Resort: Where to Find It, How Much It Costs, and What Amenities You Can Expect

View Booking Specifics

The room, dates, and payment details of a user's reservation are all viewable here.

Entity: Reservation

Characteristics That Matter: Date of Arrival, Date of Departure, Number of Beds, Payment Amount, Date of Payment, Payment Type, Payment Details

Examine Details of Financial Transactions

For the purposes of auditing and financial tracking, users, administrators, and accounting staff can obtain payment transaction records.

Substance: FinancialTransaction

Characteristics That Matter: Amount, Date, Type, and Specifics of Payment.

• Update

Refresh Resort Details

Resort specifics, including rates and amenities, are subject to change by authorized staff.

Case Study: "Add a New Resort" (initial configuration and management)

Place of Stay

Characteristics That Matter: Outline, Unique Functions, and Cost

Make Changes to Your Reservation

Changing the amount of guests staying or the arrival date is just two examples of how a reservation could need to be modified.

Case Study: Making Changes to an Existing Reservation and Making New Ones

Entity: Reservation

Characteristics That Matter: Date of Arrival, Date of Departure, Total Beds

• Delete

Remove a Booking\

To eliminate any trace of cancelled reservations, users can cancel their bookings.

The Case of "Reserving a Table"

Resort Cancellation Request

When a resort no longer works with SBRU, authorized employees can remove their information from the database.

Application: Governmental Procedures

To Remove All Records Of Payments Made To This Resort

Data management considerations need the potential erasure or archiving of previously processed payment transaction records.

Application: Governmental Procedures

Substance: FinancialTransaction

Use Case Diagram

The process of system analysis and design relies heavily on the creation of use case diagrams. Use case diagrams are visual representations that aid in capturing the functional needs of a system by depicting the interactions of various actors with the system to accomplish predefined goals or activities. Here, we'll examine the use case diagrams developed for the Spring Breaks 'R' Us (SBRU) case study and break down its components, importance, and utility in the context of system design and development.

Use Case Diagrams

Use case diagrams are extremely useful in many areas of software engineering, including but not limited to the following:

• Use case diagrams are useful for quickly gaining an overview of a system's capabilities. They clarify the system's intended functionality for all parties involved, including programmers, designers, and business analysts.

• Actors, or external entities that interact with the system, are identified and defined in use case diagrams. An actor may be a human user, another computer system, or a physical object (Shyam & Mukesh, 2020).

• Use cases are defined as the set of possible activities that may be carried out by actors within a system. They provide a detailed account of how the system operates under various conditions.

• Use case diagrams are useful for clarifying system requirements because they show how different actors and use cases interact with one another (Faraj et al, 2020). This facilitates requirement verification and improvement.

• Use case diagrams are a strong communication tool that facilitates discussions and agreements among stakeholders regarding the operation of a system in a visual and readily accessible style.

Use Case Diagram Elements

The following elements constitute a standard use case diagram:

• Stick figures or symbols stand in for the actors in this diagram. They stand in for entities outside the system that have an effect on it. For SBRU, possible roles for outsiders to play include "Student," "Resort Staff," and "Admin."

• Use Cases: Use cases are represented as ellipses or ovals with lines connecting them to actors. The system's capabilities are broken down into discrete "use cases," or tasks, including "Book a Reservation" and "Manage Resort Details."

• Connections Between Actors and Use Cases Associations (shown by lines) demonstrate the connections between actors and the use cases to which they are connected. When an actor is associated with a use case, it means the actor can either trigger or take part in that use case.

• Rectangular in shape, the system border encompasses all participants and use cases. It creates a clear visible barrier between the system and any outside influences.

• One use case or actor may be a more generalized version of another, and generalization relationships can be used to demonstrate this. You may use this to mimic different use-case scenarios.

Diagrams of SBRU Use Cases

Our two major use case diagrams for the SBRU case study are "Add a New Resort" and "Book a Reservation."

• This is the "Add a New Resort" use case diagram.

There are two main people involved in the "Add a New Resort" use case diagram: "Admin" and "Resort Staff." The primary use case is "Add a New Resort," which stands for the process of including a new resort in the system. The connections between the actors and the use case are represented by the associations.

• A Second Use-Case Diagram for "Reserving "

In the "Make a Reservation" use case diagram, the "Student" is the main character. The major use case is "Book a Reservation," which models the steps a student might take to make a reservation at a hotel or other accommodation (Islam, 2020). The associations reveal the student's use of the system to accomplish the goal.

Stakeholders can utilise these use case diagrams to have a better grasp on the SBRU system's fundamental capabilities and the ways in which its many players collaborate to accomplish their goals.

Use Case 1: Add a New Resort Activity Diagram

Use Case 2: "Book a Reservation"

System Sequence Diagrams (SSDs)

The fields of software engineering and system analysis rely heavily on System Sequence Diagrams (SSDs). They offer a graphical depiction of the system's interactions with its environment (often people or other systems). SSDs are priceless for gaining insight into the core features of a system, elaborating on requirements, and setting the stage for system design and development. The relevance of SSDs, the components that make them up, and their function in the software development lifecycle will be discussed.

System's Sequence Diagram

In the sometimes convoluted realm of system requirements, SSDs provide a connecting role between the next phases of design and development. The inputs and outputs of each interaction are highlighted, and the core sequences of user interactions with the system are captured. Cases like Spring Breaks 'R' Us (SBRU) demonstrate the value of these kinds of diagrams in situations where user-system interactions are complex and multifaceted.

Elements of Sequence Diagrams for Computer Systems

• In SSDs, "actors" stand in for entities outside of the system. Users, other systems, and physical devices all fit into this category. Actors trigger system reactions by their own behaviors. Actors in SBRU might be anybody from students to resort owners to third-party payment processors.

• Functions and services provided by the system to its users are referred to as "use cases." In state transition diagrams (SSDs), use cases are represented as rectangular containers and linked to actors by lines that show who triggers the use case. As an illustration, "Book a Reservation" and "Add a New Resort" are two examples of frequent actions in the SBRU scenario.

• The border between the system under study and its surrounding environment. It contains all the system's use cases and actors. Defining what is and isn't included in the SSD's purview with this limit.

• Messages are the directional arrows that connect the various participants and applications. They stand in for requests and interactions between actors and the system. Labels in messages explain what kind of exchange it is, for "Request to Book Reservation" or "Confirm Receipt."

Role:

• Requirements analysis is a crucial part of the software development process, and SSDs play a crucial role in this process. They aid in visualizing the system's future interactions with its environment, which is useful for engineers and clients alike (Suhirman et al, 2021). SSDs guarantee that no necessary user-system communication is missed by graphically showing the important sequences of interactions.

• SSDs are helpful for verifying that criteria have been met. They provide a chance for interested parties to assess whether or not the proposed system will fulfill their requirements. SSDs can also be utilized to ensure the system responds appropriately to different inputs.

• SSDs provide a foundation upon which to build a well-designed system. They are useful for designers because they reveal what parts, interfaces, and features need to be added to support the interactions shown. The SBRU reservation and management systems, for instance, would be shaped by the SSDs.

• Clear communication between all parties involved in a project is made easier by SSDs. They allow everyone on a project team, from developers to designers to project managers, to speak the same visual language. This helps ensure that everyone has a common understanding of the system's behaviour and reduces the likelihood of confusion.

Use Case 1: Add a New Resort SSD

Use Case 2: Book a Reservation SSD

State Machine Diagram

The State Machine Diagram is a graphical depiction of the possible states and transitions of a system or entity. The "Make Booking" use case for the SBRU system describes the sequence of actions and decisions that users go through when reserving a hotel for spring break. The State Machine Diagram provides a graphical representation of the relationships between different states, illuminating the system's actions in this context.

Checking Out the Room for Changes and States:

• This is the first step in making a reservation. The process of finding vacant rooms at a resort is started by the user.
• The user moves from this state to the "Room Selected" stage when they choose a room.

Choice of Room:

• The user has decided on a room and is ready to make a reservation. They can either carry on with making a payment, or they can give up.
• The user moves to the "Payment Made" state once they have made the decision to complete the payment.
• When a user cancels without paying, they have two options:
• Change to "Payment Not Approved" if the transaction was declined.
• Proceed to "Transaction Completed" if the payment was processed without error.

Amount Paid:

• The user has entered this condition when they have paid for the specified accommodation.
• Once the payment is verified, the user's status will change to "Room Confirmed" in the system.

Confirmed Room:

• When this happens, the user's reservation is finalized and the room is set aside for them.
• The user is then sent to the "Room Report Emailed to Student" status, where they will remain until the next confirmation is received.

Emailing a Student a Room Status Report:

• In this mode, users receive an in-depth report of their booking through email.
• To get to the "End Process" state, users must first confirm their email address, and then they can opt to cancel the process.

Quit:

• This is a hybrid state composed of two states that each indicate a distinct user interaction:
• This sub-state is entered by the user if their payment is declined.

Agreement Reached:

This sub-state is reached if the user's payment was processed successfully.

The user can exit the process from either "Quit" branch and arrive at the final "End Process" state.

End Process:

• When you reach this status, your reservation is complete. Users have either completed a successful reservation, faced payment troubles, or abandoned their booking altogether.
• From this point forward, no more changes can be expected.

Detail Description of States:

Exact Search Terms Used in the States Room:

• Users have started looking for vacant rooms at this point. They have not made a reservation yet since they are still considering their choices.
• To advance to the next level, users can pick a different room.

Choice of Room:

• At this point, the user has chosen a room and may either continue with the booking or abandon the process.

• The next stage is determined by the option to proceed to "Payment Made" or to cancel.

Amount Paid:

• After successfully paying for the chosen room, the user transitions to this state.
• Once payment is verified, they will be upgraded to a "Room Confirmed" status.

Confirmed Room:

• The user's reservation has been approved, guaranteeing a comfortable stay.
• The "Room Report Emailed to Student" screen then loads to give the student access to supplementary materials.

Emailing a Student a Room Status Report:

• A user's booking status is reported to them through email.
• At this point, the user has the option to cancel the current action.

Quit:

• There are two possible outcomes, both of which depend on the amount of money exchanged, hence this is a hybrid state.
• If the user's payment is declined, they will transition to the Payment Not Approved state.
• Agreement Reached: If the transaction is successful, they will transition into this substate.

End Process:

• This status indicates that all reservations have been processed.
• It's possible that the user has either completed the booking procedure, run into trouble with the payment, or abandoned their efforts.

Importance and Usefulness

The SBRU system's State Machine Diagram for the "Make Booking" use case is a useful visual representation for comprehending the customer's flow from start to finish in making a reservation (Wang & Park, 2021). It helps those involved in designing and implementing the system to understand the many states a user might be in and the transitions between them.

In conclusion, the "Make Booking" use case State Machine Diagram is an essential part of building the SBRU system. It not only helps you learn more about the booking procedure, but it also helps you plan and execute tests. This graphic is critical to SBRU's efforts to simplify the booking process for spring break trips for college students.

Conclusion

In conclusion, the Spring Breaks 'R' Us (SBRU) system's behavior and data management are illuminated by the State Machine Diagram and CRUD analysis shown for the "Make Booking" use case. The State Machine Diagram details the complex actions and choices made during the booking procedure, providing an all-encompassing perspective of user input and system output.

Data manipulation and management essentials for the SBRU system are highlighted via an examination of the CRUD procedures of create, read, update, and delete. It emphasizes the fundamental resort, reservation, and financial transaction procedures that are foundational to smooth operations and positive guest experiences.

System designers, developers, and stakeholders can benefit greatly from the combination of these modeling and analytic methodologies. They provide support in areas such as system architecture, user experience, error management, and process enhancement. They also allow for more organized testing and better communication between team members.These resources are essential in helping SBRU achieve its goal of providing a first-rate spring break booking experience for college students, as they contribute to the development of a reliable and straightforward system that meets the needs of the company and facilitates an easy planning process.

References

Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2015). Systems analysis and design in a changing world. Cengage learning.

Islam, A. (2020). Resort Management System (Doctoral dissertation, United International University).

Wang, T., & Park, J. (2021). Design and implementation of intelligent sports training system for college students' mental health education. Frontiers in psychology, 12, 634978.

Suhirman, S., Hidayat, A. T., Saputra, W. A., & Saifullah, S. (2021). Website-Based E-Pharmacy Application Development to Improve Sales Services Using Waterfall Method. International Journal of Advances in Data and Information Systems, 2(2), 114-129.

Shyam, A., & Mukesh, N. (2020). A Django based educational resource sharing website: Shreic. Journal of scientific research, 64(1), 138-152.

Faraj, A., Alzahrani, S., Almumtin, R., Alrajhi, D., Alshyban, S., Alshabanah, M., ... & Almarashdeh, I. (2020). Developing and implementing an online learning platform for children with autism. International Journal of Scientific Research in Science and Technology.
You Might Also Like:

Business Tourism Management Assignment Help

HAT203 Hospitality and Tourism Management Assignment

Current Sustainability Issues Facing the Tourism Industry Assignment Sample

Looking For Complete Assignment Sample Get It On WhatsApp