BCO2041 Systems Analysis and Design Report: Yacht Australia Project

This report details the systems analysis and design for Yacht Australia, focusing on developing an information system to manage the business's activities. It begins with an executive summary outlining the project's goals and scope. The report covers system requests, work plans, and feasibility analyses, evaluating technical and organizational aspects. It defines functional and non-functional requirements, including data storage, request processing, and system availability. Use cases, process models, context diagrams, and data models (including data dictionaries and ERDs) are presented to illustrate the system's design. The report also includes a bibliography of relevant sources used in the analysis and design process. The solution provides a comprehensive overview of the system's architecture and components.

Running head: BCO2041 SYSTEMS ANALYSIS AND DESIGN
BCO2041 Systems Analysis and Design
Name of the Student
Name of the University
Author’s Note

1
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Executive Summary
The report is prepared for Yacht Australia for designing an information system for the
management of the current activity of the business. The request generated from different
levels of the business are evaluated for the development of the report. An analysis is made on
the requirement for the development of the information system and identification of the
workflow of the current system.

2
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Table of Contents
System Request..........................................................................................................................3
Work Plan...................................................................................................................................3
Feasibility Analysis....................................................................................................................3
Technical................................................................................................................................3
Organizational........................................................................................................................4
Requirement Definition..............................................................................................................4
Functional...............................................................................................................................4
Non-Functional......................................................................................................................4
Use Cases...................................................................................................................................5
Process Model............................................................................................................................6
Context Diagram....................................................................................................................6
Level 0 Diagram.....................................................................................................................7
Level 1 Diagram.....................................................................................................................8
Data Model.................................................................................................................................8
Data Dictionary......................................................................................................................8
ERD......................................................................................................................................14
Bibliography:............................................................................................................................15

3
BCO2041 SYSTEMS ANALYSIS AND DESIGN
System Request
Client information recording – The information of the client should be accessed by
the administrator and the other employees working in the organization.
Employee details records – the details of the employees must be stored in the
information system and should be accessible to the administrator.
Data Service – Weekly reports are generated using the service data of the
organization
Sail boat information – The office staffs and the administrators should have all the
records regarding the sailboats and the reservation details.
Work Plan
It includes all the details and sail boat and the employees working in the organisation. The
request of the users must be responded quickly for reducing the waiting time of the user. The
error notification should be recorded and sent to the administrator for creating a response plan
against the errors generated in the information system.
Feasibility Analysis
Technical
The manual work of the employees should be reduced by the deployment of the
information system in the current business process of the organization.
The solution proposed for Yachts Australia (YA) should be evaluated for finding the
errors and handling the requests from the users automatically.

4
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Organizational
The information system should handle more number of customer at a time for
improvement of the relationship with the customer and maintain a records of the customer for
offering them discounts.
Requirement Definition
Functional
Data storage – All the data stored in the information system should be secured and
permission for accessing all the information should be provided to the administrator and the
other users should be restricted to access the sensitive information.
Request Processing – Minimum time should be taken for reserving a sail boat and
allocate it to the user and updating the information system.
Request Response – The sailboat availability should be available to the administrator
such that the details of the boats should be available at the time of reservation.
Payment records – The details of the transaction should be recorded for the future
reference and handling the dispute cases.
Invoice generation – The system should be able to generate invoice and reports
automatically for storing the records for future auditing.
Storage of Employee and client details – The database must be designed to store the
client and the other organizational information.
Non-Functional
Availability – The information system should be available to the users all the time and
the errors in the system must be immediately resolved for increasing the quality of the
project.

5
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Security – Encryption mechanism should be applied for securing the data residing in
the information system.
Scalability – New features must be added in the information system for handling the
changes in the requirement of the users and improve the business performance.
Use Cases

6
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Process Model
Context Diagram

7
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Level 0 Diagram

8
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Level 1 Diagram
Data Model
Data Dictionary
Administrator Table:
Sl. NO. Field name Data Type Constraints Description

9
BCO2041 SYSTEMS ANALYSIS AND DESIGN
01. Admin_ID Int PK It stored the ID
of the admin
02. Admin_Name Varchar(25) NOT NULL It stores the
name of the
admin
03. Password Varchar(15) NOT NULL It stores the
password of
admin
04. Contact Varchar(15) NOT NULL It stores the
contact
information of
the admin
05. Email Varchar(35) NOT NULL It stores the
email of the
admin
Registration Table:
Sl. NO. Field name Data Type Data Type Constraints Description
01. User_ID Int Int PK It stores the
ID of the
user
02. User_Name Varchar(25) Varchar(30) NOT NULL It stores the
name of the
user
03. Password Varchar(15) Varchar(20) NOT NULL It stores the

10
BCO2041 SYSTEMS ANALYSIS AND DESIGN
password for
the user
account
04. Address Varchar(15) Varchar(30) NOT NULL It stores the
address of
the user
05. Contact Varchar(35) Varchar(20) NOT NULL It stores the
contact
information
of the user
06. Email Varchar(30) NOT NULL It stores the
email ID of
the user

11
BCO2041 SYSTEMS ANALYSIS AND DESIGN
Sailboat Table:
Sl. NO. Field name Data Type Constraints Description
01. Sailboat_ID Int PK Stores the Id of
the sailboat
02. Sailboat _Model Varchar(20) NOT NULL Stores the
model of
Saliboat
03. Make Varchar(20) NOT NULL Stores the make
information
04. Berths Varchar(30) NOT NULL Stores the berth
information
05. Seat_Information Varchar(20) NOT NULL Seating capacity
of the boat
06. Rates Varchar(30) NOT NULL Records the rate
of the charter
07. Photo Varchar(50) Not NULL Stores the
image of the
sailboat
08. Fuel Varchar(10) Not Null Stores the fuel
records
Booking table:
Sl. NO. Field name Data Type Constraints Description
01. Customer_ID Int FK Used as a