Acquisition Process for FastFit Web Application

This report discusses the acquisition process for the proposed FastFit web application which will help improve the business process by making it easy for customers to book for classes through the web application. The document discusses the cost and the schedule that will be followed to develop the system and shows models of the system to illustrate data and behavioral requirements of the proposed system.

COVER PAGE

Contents
Introduction.................................................................................................................................................4
Project scope...............................................................................................................................................4
Project cost and Schedule analysis..............................................................................................................5
Modelling....................................................................................................................................................6
Data Flow Diagrams.................................................................................................................................6
Context diagram..................................................................................................................................6
Level 0 Data flow diagram...................................................................................................................6
Entity relationship diagram.....................................................................................................................7
Design..........................................................................................................................................................8
References.................................................................................................................................................11

Figure 1: Project schedule...........................................................................................................................5
Figure 2: Total Cost of ownership................................................................................................................5
Figure 3: Context diagram...........................................................................................................................6
Figure 4: Level 0 DFD...................................................................................................................................7
Figure 5: Entity relationship diagram...........................................................................................................8
Figure 6:Customer login interface...............................................................................................................9
Figure 7: Customer registration interface....................................................................................................9
Figure 8: customer dashboard interface....................................................................................................10
Figure 9: Administrator sales report interface...........................................................................................10

Introduction
This report discusses the acquisition process for the proposed FastFit web application which will help
improve the business process by making it easy for customers to book for classes through the web
application. The document discusses the cost and the schedule that will be followed to develop the
system and shows models of the system to illustrate data and behavioral requirements of the proposed
system.
Project scope
FastFit is a local gym that offers different types of weekly workshops to its customers. These workshops
include Zumba, Pilates and Yoga. The business is in need of a web application that will be used by both
its customers and the staff of the gym. The main aim of developing this system is to make it easy for
customers to book for classes through an online web application and to pay for the booking using the
system. Staff at the gym will also be able to view customers who have registered and their bookings and
from that reports can be generated. The proposed system will have the following functions for both
customers and staff administrators;
Customer
 The system should provide the customer with a registration form for the customer to register
into the system.
 The system should provide the customer with a login form to enable customers to login into
their accounts.
 The system should provide customers with a password recovery function where customers who
already have an account and have forgotten the password can try to recover their passwords by
either using email option or mobile number option.
 The system should provide customers with a page from where they can view classes that are
available for booking. Each class should have all the relevant details.
 The system should provide customers with a page where they can book for a class. The page
should have an option for a single session booking or pre-pay booking.
 The system should provide the customers with a page where they can view their bookings.
 The system should provide registered customers an option of viewing the classes they have
already booked for.
 The system should provide registered customers with an option of updating their profile.
 The system should provide customers who are logged in with an option of logging out in order
to terminate the current session.
Administrator (Staff)
 The system should provide the administrator with a login form to login to their accounts.
 The system should provide the administrator with an option of recovering the password of the
admin has forgotten the password.
 The system should provide the administrator with an option of viewing all customers who have
registered in the system.
 The system should provide the admin with an option of managing classes. Managing classes
involves adding a class, updating a class, or deleting a class.

 The system should provide the admin with an option of viewing all bookings that have been
made. The system should make it possible for the admin to filter the data depending on
different parameters like class type or date.
 The system should provide the administrator with an option of generating reports. The report
can be a weekly sales report, monthly sales report or the sales between two dates.
Project cost and Schedule analysis
The estimated time of completion of the project is 3 months. This is the time it will take from the
beginning of the project up to when a fully working system is deployed and maintenance is done on the
system. The figure below shows the time it will take for each activity.
Figure 1: Project schedule
The total estimated cost of the whole project can be done using Total Cost of Ownership (TCO) analysis
(Reh, 2018)). This will show all the expenses that will be incurred from the beginning of the project to
the end of the project.
Total Cost of
Ownership By Taimoor Rashid Student ID: 102692
Name of product
(equipment / goods/
service): FastFit Information System
Expected lifetime of the
item: 3 Months
EXPENSES
Product / Service Cost items unit cost qty
subtotal
costs $
Fastfit web application requirements engineering $1,000.00 1 $1,000.00
Design and Development $20,000.00 1 $20,000.00
testing $1,000.00 1 $1,000.00
deployment $10,000.00 1 $10,000.00
system changeover/ staff Training $5,000.00 1 $5,000.00
Maintenance $5,000.00 1 $5,000.00
Total $42,000.00
Figure 2: Total Cost of ownership

Modelling
The system can be modelled to show behavioral structure of the system and data structure of the
system (Stephen, 2013). Data flow diagrams are used to show behavioral structure of the system while
an entity relationship diagram is used to show the data structure of the proposed system.
Data Flow Diagrams
Context diagram
A context diagram is used to show interaction of the system with external factors like a customer or an
administrator. The figure below shows the context diagram for the proposed system;
Figure 3: Context diagram
Level 0 Data flow diagram
Level 0 data flow diagram are used to show the flow of information within the system. It shows the
external interactors of the system, processes and data stores that are accessed in order to perform
different functions with the system. The data flow diagram shows the process of login, registration and
booking of a class for a customer.

Figure 4: Level 0 DFD
Entity relationship diagram
The entity relationship diagram is used to model data requirements of the proposed system. It shows
the entities, their attributes and the relationships existing between the entities. The ERD is then used
when implementing the actual database to be used by the system. The figure below shows the ERD for
the proposed system;

Figure 5: Entity relationship diagram
Design
After modelling the system, the design of the system can be done from the specifications of the system.
For the proposed system a few interfaces have been designed to illustrate the design that will be
adopted for the whole system. Some of the interfaces designed are;
 Customer login

Figure 6:Customer login interface
 Customer registration
Figure 7: Customer registration interface
 Customer dashboard consisting of a main menu

Figure 8: customer dashboard interface
 Administrator sales report
Figure 9: Administrator sales report interface

References
Reh, J. (2018). A Guide for Managers to Understand Total Cost of Ownership (TCO). [online] The balance.
Available at: https://www.thebalance.com/total-cost-of-ownership-tco-2276009 [Accessed 17 Oct.
2018].
Stephen, F. (2013). Interviews: Requirements Elicitation Technique. [online] Business Analyst Learnings.
Available at: https://businessanalystlearnings.com/ba-techniques/2013/7/18/interviews-requirements-
elicitation-technique [Accessed 17 Oct. 2018].