BCO2041 System Analysis and Design: Yacht Australia System Proposal

This report details a system proposal for Yacht Australia, a family business operating in the Whitsundays. The company faces challenges due to its growth, including inefficient booking processes, lack of secure data storage, and inability to track business data effectively. The proposed system aims to address these issues by providing a centralized database for customer and staff information, secure computer usage, automated sales tracking, and improved reporting capabilities. The work plan outlines system planning, analysis, development, installation, and training phases. Feasibility analysis covers technical, economic, and organizational aspects. The report also includes functional and non-functional requirements, use cases for online booking and yacht preparation, context and level 1 diagrams, a data dictionary, and an entity-relationship diagram.

5/13/2018
System Analysis and Design
BCO2041
Assignment 1: System Proposal
Pasang Gurung (s4586773)
Alisha Tamang (s4584387)

Executive Summary
In Whitsundays Island, there is a family business named Yacht Australia. This business serves on the
Whitsundays Island which is the main point of the Great Barrier Reef on the tropical coast of
Queensland. This business established 40 years ago and now provided trips from the Bowen harbor
to various new islands. The fleet and the services are increased by the owners, and it is offered to
tourists. To expand the business, procurement and franchise from a catering company are recently
opened by them. This new company serves I several outlets which include the pristine location of
Northern Territory and West Australia. Because of the growth of the business the company is now
facing some sort of problems in the business system which is restricting the business from reaching
to its business goals. The problems are the:
 One master calendar is used for checking staff and schedule availability.
 The pre-printed sheet is used for making the bookings.
 Information on staffs and customers professionally not stored.
 The computer is not used securely
 Failed to track the reports and data of businesses.
 Computer usage is insecure.
System Request
Name of the project:
Development of a new design system which will manage the payment, staffing, booking and tracking
the growth of the business in the field of marine industry.
Client Company: Yachts Australia
Sponsors: Paul and Alice (Client company owners)
Business Need
 For storing the name, details of payment, address, etc. of the customer in a single database.
 Installing a security system which will restrict the unauthorized persons from access the
database.
 Staff and Yacht availability recording.
 Daily tracking of sales and booking.
 Booking status record.
 Daily based sales report generation.
 Allowance of automatic data entry of boat and staff availability.
 Alert message generation for spam order.
 Avoiding a double booking error.
 Attracting more customers.
 Tracking the other competitors and to compare the business growth.
 Calculation of the cost laterally with invoice copy.

Business Values:
 A system which is able to hold the details of yachts customers and the availability of yachts
and booking status.
 Strong password implementations for a secured system.
 Satisfying the customers and the staffs.
 Resource saving and workload reduction.
 Identifying the growth and the business position.
 Implementing a payment method which is secured and easy.

WORKPLAN
Yachts Australia Working Plan
NO Elements Explanation Allotted To Timeframe Result
1.1 New system
planning
Issue identity,
investigation of
achievability,
obstruction breaking
down, making the
checklist
Project
Manager 25 Days
Identifying issues
separately with a
new technique.
1.2 System analysis
Identify the problems,
creating a demo using
a new framework,
prerequisites
gathering, client
necessity exploration,
proficiency
investigation of new
framework by
comparing with the old
method.
System
Analyzer 21 Days
New framework
recognizing and
identifying
enhancement of
viable exhibitions.
1.3 Allocating the
budget
Spending plan
investigation for entire
task, agenda
influencing to allocate
plan of spending
instance, assets
required spending
plans.
Finance
Manager and
Project
Manager
12 days
Financial plan is
figuring for the
entire venture.
1.4 Development and
Coding Process
The innovation of the
improvement process,
planning the
formatting, demo
system
implementation.
Web Designer
and
Programmer
40 days Genuine framework
creation.

1.5. System Installing
and Debugging
Framework
installation in the
equipment, mistakes
and bugs checking,
upkeep schedule
building.
IT specialist and
Software
Engineer.
7 days
Distinguished error
findings and bug
free framework
representation.
1.6 System training
and handling.
Framework
maintenance and
keeping up. Screening
Well-ordered plan to
use the System.
Qualified
Trainer and IT
Technician
7 Days
Up gradation of the
whole system to
help the user to
learn about the
system.
FEASIBILITY ANALYSIS
The feasibility analysis is used for strength and weakness determination. It is used for determination
of continuation of a project. Besides that, it will also help to upgrade the present project to get the
desired output.
Technical feasibility
In this case, the old staffs will face problems with the new systems as they are not familiarized with
it. Easy navigations and the language will be used for faster learning in this case. As the new system
is manually influenced, staffs will be more comfortable. The main advantage of this system is that
the tasks will be done automatically.
Economic feasibility
In this case, the new system will do more savings for the organization. It will save more money and
time. It will help the staffs by simplifying the tasks and by taking decisions. As the system will
calculate and generate the invoice from the input, the staffs need not calculate anymore.
Organizational feasibility
In this case, the authorised persons are only able to access confidential data before the stored data
is accessed by the random user with a password. In this way, the privacy of the organization will be
improved. A separate login is required for viewing different data from different customers. It helps
the customer to communicate with the organization easily by just providing some information. By
implementing these customers do not need to seek for the boat availability.
Requirement Definitions

Functional requirements:
Functional requirement performs supporting user task which is directly related to a process. These
are two kinds:
1. Information Oriented
2. Process Oriented
Designations Explanation
Bookings This function used for handling the bookings of the
customers and for this data of date and service
availability is required.
Payments These function used for calculating all the costs and for
preparing an invoice for a customer.
Customer Profile This function stores user data with the purchase details
for future reference.
Employees details This function helps to keep track of staffs and help to
distribute the tasks according to the skilled area of
staffs.
Financial Records This can help for a better budget allocation of all the
costs and can predict the total expenses.
Non-functional requirements
Non-functional requirements refer to a specific system which performs a specific set of task
including capacity, speed, external interface design and attributes. This is actually a set of
requirements.
Requirement Description
Security Only authorized persons able to access the data. Others
need a login id and password for accessing the data.
Accessibility The data stored in a familiarized way for the staffs for
quickly accessing those data.
Performance Large sets of data can be handled by the system to serve the
customers better.
Reliability Double booking is prevented and shows an alert message.
List of Event:
Occurrence Generate Root Reaction Destination

Consumer makes
Enquiry
Consumer
needed
Booking
agent
Details of yacht
delivered Administrator
Consumer info
providing
Consumer
delivers details Consumer
Info are
uploaded by the
customer.
Owner and
booking personnel
Yacht booked Yacht booked
by the customer Consumer Booking is done Booking agent
Payments are
received
customer
completed
payment
Customer Bill produced Accounts
Sales are noted payment is
completed Staff Sales info
formed Owner
Report on record
inventory
checking
started
Staff Stock is ordered Owner
Delivery of stock stock ordering
process supplier Stock is received Owner
Bill received of
supplier
Order
purchased accounts Payments Sent Supplier
Use Cases:
Name of use case: Online booking and payment of yacht. Priority : HIGH
Actor: Booking personnel (secondary) and Customer (Primary)
Brief Description: In the online pages all the details about the yacht and respective
payment is given. Customers choose the yacht from there and pay the respective price.
Trigger: Customer wants to book a yacht.
Type: External
Preconditions:
 Customer views the available yachts from the web page.
 The web page should contain details of the yacht and the timings.
 The customer selects a yacht for booking.
Normal Course:
1. Customers select the most suitable yacht for them.
2. The yacht is confirmed, and then the customer needs to provide the details.
3. In the customer details page the customer fill-up personal details.
4. Suitable time and date selected by the customer.
5. The web page redirects to the payment page.

6. Customer completes the payment.
7. The web page displays about the confirmation of the yacht booking and provides a
unique order id.
8. Confirmed order details go to the booking personnel.
9. Available staffs got notified by the booking personnel about the booking.
10. Confirmation details updated in the database by booking personnel.
Postcondition:
 Information related to the customer is saved.
 Accounts department got notified after successful payment.
 All the staffs who are available got notified.
 The system saves the notification about the booking.
 Staffs of the food department also got notified. (When the food service available)
Exceptions:
E1. Step 6 not verifies the payment.
1. "Payment declined" message displayed by the system.
2. Customer needs to choose other payment option or need to exit from the system.
3a. The customer uses other payment system and begins with the step 6.
4a. Step 6 is started again by the system.
3b. Exit option is selected by the user.
4b. Use case terminated by the system.
Name of the use case: Preparation of yacht Priority : HIGH
Actor: Alice (owner)
Brief Description: Yacht preparation and the business progress is reviewed.
Trigger: Owner must view the system of booking.
Type: internal
Precondition:
 Current data must be present in the database.
 Login id and respective password needs to be verified.
Normal Course:
 System login action performed by Alice.
 Desired options are selected by Alice.
 Booking status is shown by the system.
 Orders which do not complete payment marked as a pending order.
 Yacht that is booked is highlighted.
 Passengers, Date and the time is shown in the system.
 Special request selected by Alice.
 Requested beverage and food is setting page given by the system. (If available)
 Staffs selected by Alice.
 Staff rosters inputted by Alice.

 Specific staffs assigned to specific yachts are shown in the system.
 After order confirmation staffs are assigned.
 Report is selected by Alice.
 Sales report and booking report is generated by the system.
Postcondition:
1. Booking preparation is checked by Alice whether it is done as per requests.
2. Business progress report is checked by the Alice.
Exceptions: none
Assumptions: To produce the real time report data must be retrieved from the database.
Use Case Diagram:
Context diagram:

Level 0 Diagram
Process 1 Level 1 Diagram:

Process 2 Level 1 Diagram:

Process 3 Level 1 Diagram: