System Design of Yachts Australia

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

SYSTEM DESIGN1
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

SYSTEM DESIGN2
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

SYSTEM DESIGN3
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