Business Case And Project Details For Proposed Online Booking System

Business Case and Justification

The aim of the report is to present the business case, and project details for the proposed online booking system design and analysis. In the following sections of the report, there are detailed information about the business case and justifications, project scope statement, cost and schedule, total cost of ownership, ER diagram, dataflow diagrams, screen interfaces etc. All these will help to get some clear idea about the proposed online booking system.

The proposed online booking system will provide the following benefits to the business,

• It will help to streamline the business processes. Compared to the manual process of booking management, the online booking management system will help to collect data from the customers, providing then booking details, passes etc. and then generating reports, receipts etc. All steps can be automated and connected to one another. The information system will help to synchronise the whole process and running it smoothly (Stair & Reynolds 2015).
• It will help in implement automation in the business process. The booking management process will be almost automated. It won’t take any intervention from the humans to run the process. However, human users like customers, staffs, admin etc. can use the system to perform tasks like making booking, checking schedule, checking booking details, generating reports, checking status of a booking and so on. It will make the process faster and agile (Rosenblatt 2013).
• It will make it more convenient for the customers to make booking. They can make the booking from the web or from their mobile devices as per their convenience. The online platform will be available for 24×7 and that will make it more convenient for the customers to place booking whenever they are available (Pokorny et al. 2011).
• It will help to improve the accuracy of the information as all data will be collected directly from the customers and there is no humans involved in the data entry process. So, all data are likely to be accurate and complete. The system will check all data against the data constraints (Lehaney, Lovett & Shah 2011).

The scope of the project is limited within the online booking process for the FastFit Gym. Rest of the business process is out of the scope of the project. The online booking process includes the operations regarding collecting customer details, providing them with the classes, workshops details, generating passes for the customers based on their booking details, reporting and related operations.

The schedule of the project is given below. It shows the details of the activities to perform for the project. It also shows the start and finish dates, predecessors of the activities. The total days has been counted as 103 days to finish the project.

Following human resources like the project manager, system analyst, designer, developer, tester, and trainer will work on the project. The resource chart given below shows the name of the resources and the standard rate of the resources for the project.  

The cost calculation for the project has been given below. It only covers the cost of undertaking and running the project. Mostly it covers the human resource cost for the project. The cost has been calculated as the duration of the activities and the resources allocated to activities. It is assumed that the standard daily working hour is 8 hours.

This is a final estimation of the direct and indirect costs related to the project. It shows the cost of undertaking the project and developing the information system, using the information system, not using the information system and not having the information system (Dennis, Wixom & Roth 2014).

Context diagram is a data flow diagram, where the system is shows as a single process. Rather than digging deeper into the system processes, it covers the external data exchange between the system as a whole entity and the external actors. In this case, the external actors are the customers, staffs and the administrator of the system (Davis 2014). The context diagram is given below. It shows how information is being exchanged between the system and the actors. 

Decomposing the context diagram, the level 0 DFD has been created. It has three primary processes,

• Registration process takes care of the registration of the customers, and how they search for classes before doing the registration.
• The booking process covers the booking and payment options.
• The reporting process covers the reporting activities of the administrator.

In the following DFD, the exchange of data among the actors, processes and data store have been shown in details. 

The Entity relationships diagram is a conceptual schema of the underlying database for the proposed online booking system (Dennis, Wixom & Roth 2014). It shows the entities, the attributes, keys and the relationships between entities.

The identified entities are,

• Customer
• Class
• Workshop
• Booking
• Payment
• Schedule

There are relationships as listed below.

• A class can have several schedules. A schedule will belong to a single class.
• A customer can make one or more booking. A booking belongs to a customer.
• A schedule can have one or more booking. Each booking is related to one schedule.
• A customer can attend many workshops. A workshops may have many customers. So, there is a many to many relationship between these two entities. So, the associative entity Attendance has been created. A customer has one or more attendance. A workshop also has one or more attendance.
• A booking can have one or more payments. A payment is for one booking only.

It is assumed that,

• A customer must make one booking to get registered.
• Customers may make multiple payments against a booking.

The examples of the mockups of the three screen interfaces are given below.

Main Menu

The main menu on the website is given below. Including the home page, the main menu is available on all pages of the website. This is for the navigation through the pages. 

On the home page, there are the header, the main menu with the menu items like home, about, classes, workshops, booking and contact. Below the menu, there is a wide image representing the organisation. And following that there is a heading.

The input screen shows the Booking Form. It asks for customer details and then booking details. There are various controls in the booking form. For example, text box, drop down menu, button etc. After filling the details accurately, a user needs to click on the Book button to make a booking.    

Monthly Sales Report

The monthly sales report is available from the Admin Portal. This is not available from the front end website. This is a special area given access to the admin only. The admin needs to login with his/her details.

The admin first needs to select a month and a year from a drop down menu and then must click on the Show Button. It will show the charts, tables etc. explaining the sales of the selected month on the right side. 

Conclusion 

The report contains system analysis and design details of the proposed online booking information system for the FastFit Gym. It includes information about the project, schedule, cost, total cost of ownership and the details of the system designs including the DFDs, ERD and some of the interface designs. 

References 

Davis, WS 2014, Business Systems Analysis and Design, Wadsworth Publishing Company. 

Dennis, A, Wixom, BH & Roth, RM 2014, Systems Analysis and Design, Wiley. 

Lehaney, B, Lovett, P & Shah, M 2011, Business Information Systems and Technology: A Primer, Taylor & Francis. 

Pokorny, J, Repa, V, Richta, K, Wojtkowski, W, Linger, H, Barry, C & Lang, M 2011, Information Systems Development: Business Systems and Services: Modeling and Development, Springer New York. 

Rosenblatt, HJ 2013, Systems Analysis and Design, Cengage Learning. 

Stair, R & Reynolds, G 2015, Fundamentals of Information Systems, Cengage Learning. 

Order an Essay Now & Get These Features For Free:

Turnitin Report

Formatting

Title Page

Citation

Outline

Place an Order