System Design and Analysis

This report deals with the case study of Yachts Australia dealing with different types of boats in the tropical region of Queensland. The report consists of different conceptual diagrams that state the working process of the company.

Running head: SYSTEM DESIGN AND ANALYSIS
System Design and Analysis
Name of Student-
Name of University-
Author’s Note-

1SYSTEM DESIGN AND ANALYSIS
Executive Summary
This report deals with the case study of Yachts Australia dealing with different types of boats in
the tropical region of Queensland. The business operates with different types of boats in the fleet
having all of different number of berth and have different prices. There are 11 total staffs who
works for the company. This report consists of different conceptual diagram that states the
working process of the company. There is a use case diagram shown in the report that states the
activities that are carried out by different actors associated with the working process of Yachts
Australia.

2SYSTEM DESIGN AND ANALYSIS
Table of Contents
System Request................................................................................................................................4
Work Plan........................................................................................................................................4
Feasibility Analysis.........................................................................................................................5
Requirement Definition...................................................................................................................6
Functional Requirement:.............................................................................................................6
Non-Functional requirement:.......................................................................................................6
Use case:......................................................................................................................................7
Process Model..................................................................................................................................8
Context Diagram:.........................................................................................................................8
Level 0 Diagram:.........................................................................................................................9
DFD Level 1:.............................................................................................................................10
Data Model....................................................................................................................................11
Data Dictionary:.........................................................................................................................11
Entity Relationship Diagram:....................................................................................................12
Bibliography..................................................................................................................................13

3SYSTEM DESIGN AND ANALYSIS
System Request
The system that is requested in this report is making the working system of the company
automatic so that the system runs smoothly. The information system that is to be designed for the
Yachts Australia will do most of the works automatically. For carrying out the system manually,
many working issues are associated with the system and thus to change the working procedure of
the system, this information system is to be built for the organization (Crane, Matten and Spence
2016). New computer system is to be installed in the working process of the Yachts Australia so
that the processes in the company are streamlined. The system that is proposed in this report
mainly streamlines the booking process, the staffing process and the supply ordering process of
the company.
Work Plan
The work plan that is being included in the information system of the Yachts Australia
includes the following sub-systems.
1. Taking bookings from customer: The Customer books Yachts as their choice and the
bookings are to be made after seeing the availability of boats. There are different types of boats
that are served by Yachts Australia and all the types of boats are to be shown to the customer.
2. Payment process: The customer pays required amount of money for booking the boats and at
the time of booking, the customer needs to pay the base amount to book the boat. The payment
process is carried out in three ways, it might be done either in cash payment, credit card payment
or cheque payments.

4SYSTEM DESIGN AND ANALYSIS
3. Contract with Franchisee: The Yachts Australia has an extra business of refurbishing old
second hand yachts and resell them to the franchise with whom they have contact.
Feasibility Analysis
1. Technical Feasibility – There can be some risks with the hardware and software that
are to be used while developing the system (Laplante 2017). The hardware associated with the
development of the information system in the software might not arrive within the system in
proper time or the hardware that arrived might have faults within the system. The software and
the technologies related to the software should be new and should be highly advanced so that all
the security system of the application is satisfied (Cioffi-Revilla 2017). All the procured systems
in this information system should be tested properly before procuring them from technical
supplier.
2. Economic Feasibility – There might also be a risks from the financial point of
implementing the project. The cost of implementing the project is to be determined at the
beginning of the project and the total cost that would be required in the development phase of the
project (Pohl 2016). For determining the economic feasibility of the project, the break even
analysis of the project is to be calculated, along with the net present value as well as return on
investment so that there is no loss in the project (Mall 2018). To develop a proper feasibility in
terms of economy will be very helpful for understanding the total revenue that can be earned in
the company after the development of the website.
3. Behavioural Feasibility – In the behavioural feasibility, some of the new people are to
be included in the system to develop a new website for university. The persons should be
included for developing the information system of Yachts Australia (Dick, Hull and Jackson

5SYSTEM DESIGN AND ANALYSIS
2017). The people for developing the information system should be hired on a contractual basis
and they are to be paid on the basis of their needs. For conducting the behavioral feasibility,
there should be proper meeting held for developing the information system in Yachts Australia.
Proper actions are to be taken only after holding meetings.
Requirement Definition
Functional Requirement:
Non-Functional requirement:

6SYSTEM DESIGN AND ANALYSIS
Use case:
Figure 1: Use Case Diagram of Yachts Australia
(Source: Created by Author)

7SYSTEM DESIGN AND ANALYSIS
Process Model
Context Diagram:
Figure 2: Context Level Diagram of Yachts Australia
(Source: Created by Author)

8SYSTEM DESIGN AND ANALYSIS
Level 0 Diagram:
Figure 3: Level 0 Data Flow Diagram of Yachts Australia
(Source: Created by Author)

9SYSTEM DESIGN AND ANALYSIS
DFD Level 1:
Figure 4: Level 1 Data Flow Diagram of Yachts Australia
(Source: Created by Author)

10SYSTEM DESIGN AND ANALYSIS
Data Model
Data Dictionary:

11SYSTEM DESIGN AND ANALYSIS
Entity Relationship Diagram:
Figure 5: Entity Relationship Diagram of Yachts Australia
(Source: Created by Author)

12SYSTEM DESIGN AND ANALYSIS
Bibliography
Dick, J., Hull, E. and Jackson, K., 2017. Requirements engineering. Springer.
Pohl, K. (2016). Requirements engineering fundamentals: a study guide for the certified
professional for requirements engineering exam-foundation level-IREB compliant. Rocky Nook,
Inc..
Mall, R., 2018. Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Cioffi-Revilla, C., 2017. Computation and social science. In Introduction to computational
social science (pp. 35-102). Springer, Cham.
Laplante, P.A., 2017. Requirements engineering for software and systems. Auerbach
Publications.
Dennis, A. and Wixom, B.H., 2018. Systems analysis and design. Wiley.
Crane, A., Matten, D. and Spence, L. eds., 2019. Corporate social responsibility: Readings and
cases in a global context. Routledge.
Dickerson, C. and Mavris, D.N., 2016. Architecture and principles of systems engineering. CRC
Press.
Afreen, N., Khatoon, A. and Sadiq, M., 2016. A taxonomy of software’s non-functional
requirements. In Proceedings of the second international conference on computer and
communication technologies (pp. 47-53). Springer, New Delhi.

13SYSTEM DESIGN AND ANALYSIS
Sarrab, M., Baghdadi, Y., Al-Shihi, H. and Bourdoucen, H., 2016. A model for mobile learning
non-functional requirement elicitation. International Journal of Mobile Learning and
Organisation, 10(3), pp.129-158.
Aziz, Y., Aziz, T., Malik, M.I., Baig, M.K., Ali, M.Z. and Baqer, M., 2017. Non Functional
Requirement in Agile Software Development. University of Engineering and Technology Taxila.
Technical Journal, 22(1), p.107.
Sachdeva, V. and Chung, L., 2017, January. Handling non-functional requirements for big data
and IOT projects in scrum. In 2017 7th International Conference on Cloud Computing, Data
Science & Engineering-Confluence (pp. 216-221). IEEE.