University System Design Report: Yachts Australia (BCO2041)

This report presents a comprehensive system design for Yachts Australia, a family-owned yacht charter business operating in the Whitsunday Islands. It begins with an executive summary and table of contents, followed by a detailed acquisition strategy based on the agile development model, outlining the system's lifecycle, development platform (ASP.NET MVC 5), and risk assessment. The architectural design visually represents the system's structure, while hardware and software specifications provide minimum and recommended requirements. The report includes interface design elements like structure diagrams and user interface flows, along with wireframe diagrams for the homepage and yacht pages. Program design is illustrated with a structure chart and program specifications for login, payment, and registration functions. The report concludes with a bibliography of relevant sources, providing a complete overview of the proposed system's development and functionality.

Running head: SYSTEM DESIGN
System Design of Yachts Australia
Name of the Student
Name of the University
Author’s note:

1SYSTEM DESIGN
Executive Summary
The report reflects the system design of the Yachts Australia System. The system acquisition
strategy describes how the system will be implemented and maintained in the organization
environment. The architectural design shows how the system will work and in which way
request of the user are transferred from user device to the server. As per the hardware and
software specification, the recommended system should have hardware components that have
been released within three years. The wireframe shows that home page has an image slide as
well as reviews of the customer. The pseudo code describes how the system will do its internal
work or server side script will execute. Ideally, the program design describe the logic

2SYSTEM DESIGN
Table of Contents
Acquisition Strategy:.......................................................................................................................3
Architectural Design:.......................................................................................................................4
Hardware and Software Specification:............................................................................................5
Interface Design:..............................................................................................................................6
Interface Structure Diagram:.......................................................................................................6
User Interface Flow:....................................................................................................................7
Wireframe Diagrams:..................................................................................................................8
Program Design:............................................................................................................................10
Structure Chart:..........................................................................................................................10
Program Specifications:.............................................................................................................11
Bibliography:.................................................................................................................................15

3SYSTEM DESIGN
Acquisition Strategy:
The system acquisition strategy is based on the acquisition lifecycle model. The agile
development model is selected as the lifecycle model for the system acquisition life cycle model.
The agile model has a lot of user intervention for making sure that each system is developed
properly and includes user requirements. In agile development, the system units are developed
simultaneously. This specific development method does not focus primarily on the planning
phase rather it depends on the user feedback to gather essential requirements. As the system will
be developed using ASP.NET MVC 5, the system will be hosted and developed in Windows
operating system. In the initial phase, the basic business and user requirements are collected.
Then in the system design phase, based on the requirements collected, the system design is done.
This design models are class, DFD, ERD, sequence and more. The development team develops
the system based on the designs. In the next phase, the system unit is tested by the end users and
user feedback is collected. New requirements are sent to design team and the rest of the process
follows the same path. After every unit is properly developed, all the units are compiled into a
single system and final products is delivered.
The system development will be done using the Visual Studio 2019 and MS SQL server
2017. The MVC .NetFramwork is used as the system platform. The database will be developed
in SQL Server. The input and output screens will be connected to the database.
Each development process has some risks. This process will have risks like server
incompatibility, high hosting charge, system bugs, improper user feedback and many more. The
risk assessment will have three phases such as risk identification, risk evaluation and risk

4SYSTEM DESIGN
mitigation method development. There will be a risk register to provide good understanding of
risks and risk mitigation strategy.
The system will be deployed in a windows based server. The server will be deployed in
the cloud so that user can access the system easily. This deployment is a part of the agile
methodology. The SAL will be done based on pay-as-use. The organization will pay the hosting
charges based on the resource used. This will allow the organization to reduce the cost of the
system hosting for peak and lean season.
Architectural Design:
Figure 1: Architecture of Yachts Australia System
(Source: Created by Author)

5SYSTEM DESIGN
Hardware and Software Specification:
Minimum Specification: Windows Server 2008, processor pentium-4 or AMD A3, RAM
8GB, Storage 4TB, software based Firewall, windows defender, network monitoring tools and
many more.
Recommended Requirements: Windows Server 2016, MS SQL Server 2017, Processor
intel i78th gen or AMD Ryzen 7 2700x, RAM 64 GB, storage 20TB, hardware firewall,
purchased antivirus, full-functionality network monitoring tool, network bandwidth 130% extra
then required and many more.
The client devices must have modern day web browser and system capability that can
process the front end scripts properly.

6SYSTEM DESIGN
Interface Design:
Interface Structure Diagram:
Figure 2: Interface Structure Diagram of Yachts Australia System
(Source: Created by Author)

7SYSTEM DESIGN
User Interface Flow:
Figure 3: User Interface Flow Diagram of Yachts Australia System
(Source: Created by Author)

8SYSTEM DESIGN
Wireframe Diagrams:
Figure 4: Home Page of Yachts Australia System
(Source: Created by Author)

9SYSTEM DESIGN
Figure 5: All Yatch Page of Yachts Australia System
(Source: Created by Author)

10SYSTEM DESIGN
Figure 6: Page to Show a Selected Yatch
(Source: Created by Author)
Program Design:
Structure Chart:
Figure 6: System Structure of Yachts Australia System
(Source: Created by Author)

11SYSTEM DESIGN
Program Specifications:
Login:
function onLogin(user) {
if (user.nihAccountLink.isActive) {
if (user.nihAccountLink.lastLogin < _24HoursAgo &&
user.nihAccountLink.expireTime > _24HoursFromNow) {
user.nihAccountLink.expireTime = _24HoursFromNow;
}
}
}
function onNihAccountLinkSuccess(user) {
user.nihAccountLink.lastLogin = now;
user.nihAccountLink.expireTime = _30DaysFromNow;
if (exists(user.nihAccountLink.username, dbgapAuthorizedWhitelist)) {
addUserToDbgapAuthorizedGroupIfNotExists(user.firecloudUsername);
} else {
removeUserFromDbgapAuthorizedGroupIfExists(user.firecloudUsername);
}
}
function onPeriodicTick() {
// (runs at least once per day)
for (user in getAllDbgapAuthorizedUsers()) {
if (user.nihAccountLink.expireTime >= now) {
removeUserFromDbgapAuthorizedGroupIfExists(user.firecloudUsername);
}
}
}

12SYSTEM DESIGN
function onNewWhitelist() {
for (user in getAllDbgapAuthorizedUsers()) {
if (!exists(user.nihAccountLink.username, dbgapAuthorizedWhitelist)) {
removeUserFromDbgapAuthorizedGroupIfExists(user.firecloudUsername);
}
}
}
Payment:
Description: This logic applies a discount on an item price
Program: applyDiscount
Create variable productPrice as double
Create variable discount as double
Create variable discountedPrice as double
productPrice = get value from user input
discount = get value from user input
discountedPrice = productPrice * (1 – discount)
Display discountedPrice
End program
Registration:
Email field: input type = email, placeholder: “[e-mail]”
Password field: input type = password, placeholder: “Password”
Password confirmation field: input type = password, placeholder: “Password again”
Signup submit: value: “Sign Up”, default state, disabled
##Signup Flow/Logic
###On leave focus of email field
IF email is blank

13SYSTEM DESIGN
Error message: “Please enter an email address.”
ELSE IF email field value is not a valid email address
Error message: “This doesn’t look like an email address. Please try again.”
###On leave focus of password
IF password is not sufficiently strong
Error message: “Please replace with a stronger password.”
###On leave focus of password confirmation
IF password confirmation does not match password
Error message: “Please replace with a stronger password.”
###On leave focus of email, password or password confirmation
IF email AND password AND password confirmation all contain valid values
Enable Signup Submit
##Discussion topics:
What constitutes a sufficiently strong password?
What constitutes a valid email? Eg do we want to allow “[e-mail]”
What should we do if the email already is in use?
eg ELSE IF email field already is in use

14SYSTEM DESIGN
Error message: “This email is already in use. Did you want to [Sign In] instead?”

15SYSTEM DESIGN
Bibliography:
Danielson, C.K., McCauley, J.L., Gros, K.S., Jones, A.M., Barr, S.C., Borkman, A.L., Bryant,
B.G. and Ruggiero, K.J., 2016. SiHLE Web. com: Development and usability testing of an
evidence-based HIV prevention website for female African-American adolescents. Health
informatics journal, 22(2), pp.194-208.
Giuffrida, M., Mangiaracina, R., Perego, A. and Tumino, A., 2017. Cross-border B2C e-
commerce to Greater China and the role of logistics: a literature review. International Journal of
Physical Distribution & Logistics Management, 47(9), pp.772-795.
Jiang, L., Jun, M. and Yang, Z., 2016. Customer-perceived value and loyalty: how do key service
quality dimensions matter in the context of B2C e-commerce?. Service Business, 10(2), pp.301-
317.
Li, S.S. and Karahanna, E., 2015. Online recommendation systems in a B2C E-commerce
context: a review and future directions. Journal of the Association for Information
Systems, 16(2), p.72.
Mambile, C., Machuve, D. and Moebs, S., 2018. UX of a Web based platform for market linkage
between farmers and buyers in Tanzania.
Martin-Kerry, J.M., Knapp, P., Atkin, K., Bower, P., Watt, I., Stones, C., Higgins, S., Sheridan,
R., Preston, J., Taylor, D.H. and Baines, P., 2019. Supporting children and young people when
making decisions about joining clinical trials: qualitative study to inform multimedia website
development. BMJ open, 9(1), p.e023984.

16SYSTEM DESIGN
Parrillo, J.J., 2017. Paleo Journey: An Interactive Paleolithic Cave Art Experience. Using the
User Experience (UX) Design Process to Develop An Interactive and Immersive Paleolithic
Cave Art Exhibit Suitable for Children Between Five (5) and Seven (7) Years Old.
Tran, M., 2018. Visioning of an Generalized Paper Prototyping Framework.
White, B.J. and Kapakos, W.A., 2017. USER EXPERIENCE (UX) IN THE CIS CLASSROOM:
BETTER INFORMATION ARCHITECTURE WITH INTERACTIVE PROTOTYPES AND
UX TESTING. Issues in Information Systems, 18(2).