MSC228 Information Systems Analysis and Design – Assignment

Trimester One, 2012

Case Study Details:

Due Date:

Assignment 2 – Due Monday 21st May by 11.59pm via DSO Marks: 35%

Diagrams and Models – Individual Assignment

===========================================================================

Case Study – Yachts Australia.

Introduction:

Yachts Australia (YA) is a family business operating a charter yacht fleet in the heart of the Great Barrier Reef on the tropical coast of Queensland at the Whitsundays Islands. The Whitsunday group of islands are acclaimed as the best cruising ground in Australia if not the world with access to over 90 National Park Islands plus a choice of 9 different resorts ranging from Wilderness to 5 Star Luxury. All the major central islands lie within 2 to 15 nautical miles of the mainland – from 1 to 3 hours sailing from Airlie Beach and Hamilton Island. They are all within sight of each other, separated by distances from about 0.5 to 5 Nautical Miles. The lesser frequented southern islands extend some thirty miles off shore and are up to 15 miles apart. Delightful secluded mainland bays are within 2 hours cruising north of Airlie Beach. Navigating in this area is therefore extremely easy, usually only by visual means, and therefore does not require a high level of navigation skills.

Background:

The owners Alice and Paul have recently taken over the business from Paul’s parents who have retired. Paul’s parents established the business in the late 70s and originally ran sailing trips from the harbour at Bowen to various islands in the area. Since Alice and Paul have taken over the business they have increased the fleet and the services they are offering the tourists. They are now offering tours that are fully staffed and catered through to self- skippered sailboats.

With the business steadily building Alice and Paul decided to expand the business and YA have now franchised their operations to include outlets in several pristine locations in West Australia and the Northern Territory. The long term intention is to establish self-skippered one-way trips between these outlets across the top end of Australia for the more experienced yachtsmen. As part of several legal franchising agreements, YA receives a set income of 15% of the profits from these operations. Payments are usually transferred quarterly into YA’s bank account.

The fleet currently includes 6 sailing yachts, 4 catamarans and 6 skippered touring boats all varying from 4 berths to 10 berths all with separate cabins and bathrooms.

The staff numbers have also increased and now include 11 staff across all the operations: 1 full time and 1 part time receptionist, 2 cleaning staff, 6 contracted licensed skippers, 1 bookkeeper as well as Alice and Paul who undertake much of the management duties including approving bookings and reservations. They also hire backpackers to help with tasks in peak seasons such as answering phones, bookings, cleaning and crewing on skippered tours.

Furthermore, YA also operates closely with a catering company called Gourmet Picnic Baskets (GPB) which not only delivers lunches and dinners for skippered tours but also stocks chartered boats with essential local produce in readiness for the trips. This arrangement earns YA 10% of their total income.

Alice and Paul can see there are major issues that require solutions. The business has grown to a more complex operation moving from only one operation outlet to four distributed office locations as well as the other activities mentioned. This has meant that the systems for keeping records have become inadequate and they have hired you to improve the reservation and payment systems. Ideally, Alice would like to be able to see how the business is performing on a daily basis. Cheap second-hand yachts often become available at very short notice and she needs to know if the business is in a financial position to take advantage of such situations. Paul has been buying sailboats, refurbishing them and selling them to the franchised operators for a nice profit, something they would like to continue with.

Alice and Paul recently hired a web designer to give them a web presence so they could make use of the internet to advertise their services. Customers who contact YA through the website receive a discount voucher via return email with offers, usually a 5% discount for booking within 30 days.

Paul and Alice have decided to employ you to investigate the business needs and to conduct an initial feasibility study into the possible options for improving their current system.

Description of the current system:

1. Sailboat Charter Rates

Name	Make	Berths	Gourmet Food basket	Mid-season Per day	Peak-season Per day
Lady luck	Catalina	4	$200	$450	$550
Sea change	Beneteau	4	$200	$450	$550
Seasalt	Beneteau	6	$300	$600	$750
Offspray	Hanse	6	$300	$600	$750
Rosea	Beneteau	8	$400	$785	$835
Kurtzie	Beneteau	8	$400	$785	$835

2 Catamaran Charter Rates

Name	Make	Berths	Gourmet Food stocks	Mid-season Per day	Peak-season Per day
Rocket	Catalina	4	$200	$450	$550
Twilight	Beneteau	4	$200	$450	$550
Wrighteo	Catalina	6	$300	$600	$750
Lillemig	Catalina	8	$400	$785	$835

Skippered Trips Rates

Name	Make	Berths	Mid-season 4 nights	Peak-season 4 nights
Encore	Catalina	6	$4,875.00	$5,350.00
Ruth	Jenneau	8	$5,350.00	$6,725.00
Kurtzie	Beneteau	8	$5,350.00	$6,725.00
Interlude	Catalina	10	$6,725.00	$7,750.00
Intothewind	Jenneau	10	$6,725.00	$7,750.00
Nordlys	Beneteau	10	$6,725.00	$7,750.00

Insurance is charged at 12% of the rates payable by the customer

Bookings:

Most reservations are initiated by a telephone call from a potential customer. When potential customers call, the YA staff member asks a series of questions designed to help them decide which sailboat charter is right for them. Note that all YA staff members, whatever their other duties, are expected to interact with potential customers. Generally, first-time customers want to know what types of boats are available. Even returning customers need to be told about new boats that might have been added to the fleet and their availability.

If the customer decides to book a charter, the YA staff member records general customer information (e.g., name, address, and phone number) on a pre-printed form. Then the staff member requests information about the actual booking (e.g. booking date, number of participants, age). The staff member must check the master calendar to see if a yacht with the right number of berths is available. She or he must also make certain that there are enough employees with the appropriate skills available for fully skippered charters. If there are no conflicts, then the staff member tentatively schedules the charter and asks for more specific details about the particular booking (e.g. linen and Gourmet Food Baskets menus and non-food purchases needed).The staff member calculates an estimated total price and then calculates 20% of the total price as a base deposit and communicates this information to the customer. If the customer agrees, the booking is provisionally scheduled, which means that it is added to the master calendar and the selected staff members are tentatively assigned to it.

Payment:

At this point, the staff person checks on the preferred manner of payment for the deposit and if the customer has a discount voucher. If the customer prefers to pay by credit card, the staff member takes and verifies all payment information. The booking is then changed from provisionally scheduled to “booked,” and YA assumes that a commitment has been made to provide a yacht under the conditions agreed to. Additionally, the staff member prepares an invoice to mail to the customer showing all terms and arrangements regarding the booking as well as the amount paid and the amount remaining for payment. YA also accepts payments in person from clients who use cash and in person or by mail from clients who pay by cheque. All scheduling issues are arranged to accommodate the various payment methods. The scheduling status officially changes from provisional to ‘booked’ following a verbal agreement with the customer and the receipt of the deposit, triggering changes in scheduling status. Normal customers are required to pay the balance of the invoice two weeks before the booked date. Customers wishing to cancel after this date lose their 20% deposit.

Frequent customers, such as the seven largest companies in the region, have accounts with YA. Specific employees at these firms have the authority to book a charter. In these cases, the booking itself is considered sufficient to reserve the yacht, and no deposit is required. Records for all the costs are maintained for these bookings, and a bill is sent to the accounts payable officer at the relevant company about two weeks after the sail trip takes place.

The franchised operations usually pay the 15% of their profit to YA through direct debits every quarter which are confirmed via an email but Alice is not sure if the amounts correspond with the actual profits. As the payments have been declining she feels a better system is needed.

The Gourmet Food Baskets are charged on the YA invoicing and it is therefore easy to calculate the 10% profit YA makes on the sales. Alice usually holds on to the 10% profit and forwards the rest as well as a copy of the invoice to the owner of GFB at the end of each month.

Supply Orders:

YA orders supplies based on the individual booking. Generally on Friday mornings, Alice assesses the bookings scheduled for the next week. She makes sure the crew is available for the skippered tours; she contacts Gourmet Picnic Baskets with the various requests for the catering and picnic hampers as well as organising the linen for each boat.

Issues:

Unfortunately, despite the owners’ years of experience and expertise, the number of double bookings and other mistakes at YA has been too high. Although the number of bookings is still growing Alice and Paul are worried that the increase in competition might see disgruntled customers go elsewhere. Furthermore, they are not too sure if the growth of their business is on par with what the industry is experiencing in general.

The business has grown rapidly over the past years, and the owners want to install a new computer system for managing the booking, staffing and the supply ordering processes. Alice would like the new system to be able to incorporate the following improvements:

Currently sail bookings are made on a pre-printed sheet, cost calculations done by hand and scheduling and staffing availability checked from one master calendar. YA would like to have a computer system to streamline these processes and make checking of details, creating schedules and invoicing much easier.
At present much information about previous customers and staffing is stored in Alice’s head which is frustrating staff and making the business look unprofessional. They would like to be able to have up-to-date details about the yachts, staff and customers.
The receptionist has raised concerns about the security at the organisation with all the backpackers and contracted staff. Although they have passwords for their two computers it is common knowledge that the password is “Alice”.
They have no idea if the business is growing at the same rate as the industry average. They would therefore like to view market movements in the yachting area and be able to perform ‘what-if’ analysis to help both strategic and operational planning.

Your Assignment Submission:

Title Page (including Project Name, student ID number and name, Date)

1. Introduction

Please provide a professional introduction, detailing what will be presented in this document.

2. Contents Page (including Page Numbers)

3. Current Systems Specification:

(Please note: all diagrams in this section should be of the CURRENT system)

3.1 Models

3.1.1 Use Case:

An overall use case diagram.
Detailed description for any 1 use case which is of high priority to “Yacht Australia” (include name, id, importance level, primary actor, stakeholders and interests, trigger, relationships, normal flow of events, subflows, alternate/exceptional flows.

3.1.2 Structural model:

An overall structural (class) diagram showing attributes and methods of each class and the relationships between classes.

3.1.3 Activity Diagram:

Activity Diagram of the main business processes

3.1.4 Structured Design Models

A Context Diagram
The Level 0 DFD
One Level 1 DFD

4. Proposed System Specification:

(Please note: all diagrams in this section should be of the PROPOSED system)

4.1 UML Model

4.1.1 Use Case:

An overall use case diagram of your proposed solution.
Detailed description for any 1 use case which is of high priority to “Yachts Australia” (include name, id, importance level, primary actor, stakeholders and interests, trigger, relationships, normal flow of events, subflows, alternate/exceptional flows.

5. Comparison and analysis

Write a 500 word analysis of the major differences and similarities between the two sets of diagrams that you have produced in Section Three (3) for the current system (i.e. Which model do you consider to be more effective and why? Does the type of project make a difference? Does the design model address the requirements? etc.).

6. References/Bibliography

Include any materials you have used to assist in the completion of the assignment. This is a report style so academic citations are not expected.

Submitting the Assignment:

Your work must be submitted as follows;

The final report file (created in Microsoft Word) will be submitted electronically via DSO.

Assignment submission rules

The assignment is to be submitted online in DSO in the area provided. No paper copy is required
Assignments are on time if they are submitted online on (or before) the due date.
No extensions will be considered for this assignment unless a written request (email is fine) is submitted and negotiated with one of the teaching staff.
Assignments submitted late without an extension being granted will not be marked.
It is your responsibility to keep backups of the assignment.

Getting Help

All students can obtain help by posting messages to the Assignment Discussion folder in DSO.

Please note: An overall word limit is not specified for this assignment due to significant marks being allocated to the diagramming of requirements. The Marking Guide should give you an idea of the relative effort you need to apply to each section of your assignment.

MSC228 Information Systems Analysis and Design – Assignment Marking Guide 2012

Student Name:	Comments:	Mark Assigned:


Current System Models:
-High Level Use Case Diagram.		/5
-Use Case Description.		/5
-Class Diagram		/15
-Activity Diagram		/10

-Context Diagram.		/10
-Level 0 DFD.		/15
-Level 1.		/10

Proposed System Model:
-High Level Use Case Diagram.		/5
-Use Case Description.		/5

Comparison and Analysis:		/10
Presentation		/10
Total:		/100

SOLUTION

INFORMATION SYSTEM AND ANALYSIS DESIGN

YACHTS AUSTRALIA

Table of Contents

CURRENT SYSTEM SPECIFICATIONS: 2

Models: 2

Use case description: 2

Use case diagram: 3

Structural model: 3

Activity diagram: 4

Structure design models: 5

Context diagram: 5

Level ODFD diagram: 6

Level 1DFD diagram: 6

PROPOSED SYSTEM SPECIFICATIONS: 7

UML model: 7

Inception phase: 8

COMPARISION AND ANALYSIS. 11
REFERENCE: 12

INTRODUCTION

This entire report gives a detail description of Yachts Australia and various specifications that are involved in a system. This report deals with current requirement specifications, proposed system and, comparison and analysis of a model. Current requirement specifications deal with the models and use case description of a system and how the officers communicate with staff; it also consists of structural model which is divided in several classes. The activity diagram helps to know the process of the current system. The structural models give brief description of the context diagram and data flow diagrams of levels 0 and 1. Then proposed system specification gives a UML description of models with the help of use case diagram. Comparison and analysis gives a result related to best model that is suitable to system.

CURRENT SYSTEM SPECIFICATIONS:

Models: The below diagram gives an idea about structured analysis use case of a current system.

Use case description:

Sailors enter in to the boat prior to the race and the officer takes the race sheet on the committee boat to start race. Some race officers allow entire race at start of the day and at the end RO entry finish times of boat on the race sheet. The detail on the particular race sheet includes boat name, id, class, helm name. The details are partially required, but require sail numbers and different classes. When the boats are back to the club, they are entered in the result sheet and these classes are sent to captain. Some races are conducted for one type of boats and others are conducted for different types (Kaplan and Nick, 2009). Handicapped is multiplier to entire elapsed time and these are tedious towards handicapped classes. RO refers towards list but usually starts at 12 and finishes at 13:14. These results conducted are noticed and written in a sheet to post it on race board. RO collect these details and enter them in to the system to take a print of it. This works as a result of the current system race.

Use case diagram:

Use case name:	Scheduling class
Scenario
Triggering event:	Officer takes a race sheet
Brief description:	Officer search for the driver than takes the race sheet on the committee before the start of race and he enters all the details of the speed with different specifications such as boat name, id, and helm name.
Actors:	Officer, RO
Stake holders	All officer
Pre condition	Race sheet must exist
Flow of events	Race sheet must be filled by the officer and RO who are actors
Exception conditions	If the race sheet doesn’t exist elapsed time must be given in detail

Structural model:

The class diagram given brief idea about division of class as per the services.

The classes are mainly known as neolex 25. The intensions of these classes are to identify the speed of boat as per the racing which depends on the skills of screw. The rules conducted can be conjunction with official measurement diagram. All parts of boats, spars, sails and equipment will be compiled towards the class rules (Michael, 2009). These rules are based on neolex 25 racing activities in national basis. Custodian of these class rules shall be of a Yacht association of Australia. There is no variation between the class rules as scheduled in neolex 25. The scheduled neolex 25 racing event can be conducted according to class rules which are not recognized. The class rules present are not amendment at anytime expecting. Notification did to the proposed amendment can be noticed in custodian (Marc, 2004). The proposed amendment can be circulated among all the members and these amendments are to be accepted or rejected only by custodian in general meeting. The amendment takes the effect of commencement in next financial year.

Activity diagram:

Aiming towards the requirements, each use case is modified towards activity diagram or a use case that points out the activities performed by the system. Use case descriptions are created for every use case and as needed for various scenarios or activity processing options for particular use case (Tim, 2005). Then next is the final description diagram activity diagram by using use case description. This design is called as system sequence design, this model the time independent behavior of system as a sequence of system from one object to other object. The unified process helps in identification of system. This unified methodology is accepted by best practices such as mitigation, iteration and model driven development. The focus and risk is grounded in curtained design framework. .

This particular design helps in formation of course for particular customer in sequence form. This process of details is done by processor; first determination of location is done to identify the details of customer. The course number and display of this course number can be seen by the proposer to verify the availability of system specifications. The course offering should be done as per the requirement of customer and availability. This course offering can be displayed in particular form of sequence through which customer can under detail easily.

Structure design models:

Context diagram:

This design specifies the use case realization through software; three layer designs provide a framework for adding the details of user interface and the data access. The data design classifies in to certain classes which provide details of modeled as requirements. Therefore this design classifies problems that are faced by different classes. This design even focuses upon the interface design and database design (Michael, 2008). The difference between analysis and design cannot be focused but the detailed focus will be done towards the domain classes. This context diagram gives brief description about the actor till database. One of the main importance of this approach is design models are simple and they are extension of analysis models. In a structured technology there is big connect between data flow models and flow chart structure chart. Structured design technology necessitated the difficult and amorphous process. This helps in formation of chart that helps to bring data flow diagram in detail. A detailed interaction diagram is extraction of system sequence diagram.

The owner acts as an actor in particular system and transfer of information is done by owner till the course offering is booked. The user interface helps in planning the proper design that has to be executed by system. Properly planned and modified data can be designed, if any problem faced by design they can be solved in next stage of cycle. These error free data can be sent to the data access system where only authorized users can use information. Database system can help them in finding of certain levels of data for huge number of sail reports or race. All the data that are collected in this system are totally stored in database system which retain for long period of time.

Level ODFD diagram:

The data flow diagram gives a brief description about adding a customer with the help of a collaboration diagram. The find course message should be sent to internal source of courses and find the right one and return it to the reference (Judith, 2003). The process of showing multi object is called as a sail course. The double boxes present at the top indicate the sail course S or internal array. The ac indicate the specific object located as ac sail course which is found based upon the course number.

This point is not considered how internal arrays are populated and transfer to get new micro station. The message format includes the return value to illustrate the found course of ac. Information about this actor is indicated by dashed output message arrow. Finally the input message is transferred giving the input message add course offering. This source is originated from owner actor and is sent to the controller object (Margo, 2003). The course object should be maintained to control the course offering objects and in this case it is designed that course offering objects. The final results of this are add course offering will send message to the course objects. The create message indicates that customer will be invoked during execution of a system. The messages can be returned back saying that they indicate and displayed back to the actor.

Level 1DFD diagram:

In this data flow diagram schedule window is created where owner enter in to the course ID of offering . The scheduler sends an request to the new course object where multi sailcourseC is replaced by mechanism that creates one new course instnce from data to the requested course. The course id information is revelaed by constructor o course (Lee, 2005). The access of datalayer class, course DA, to get read the data base to represent the course as per needed. The course DA contains all logics that are connected to databse system as SQL statements. This helps in extraction o information and plcing it in a empty course object that is provided. The data access layer contains all logics to access database and convert it back to the results (Rob, 2002). When the correct offering enters the system then the owner enters the information to start with new offering. That information goes to windows, then control objets, then to course object when they are responsible for creating new course offering. The course offering object is responsible for course offering DA to save the data to access information from the database.

This point of design process is scheduled towards the course offering where it is essential to complete except for any exception process and error messages. As previous one we can design the information in course diagram. Here each layer of this system is specified as a design class diagram (Dave, 1999). This layer can be identified as a separate UML package with three separate design diagrams. To recall the phase that has been worked previously sail world course will require many more iterations to complete course offering.

PROPOSED SYSTEM SPECIFICATIONS:

UML model:

The UML models shown are the elaboration of each phase of iteration as per requirements. The remembrance of the disciplines involves in creation of requirement models. This model helps in capturing and documents as per the requirements in proper discipline. This diagram helps to identify the diagram and help to understand business process which is not used directly by system design.

Inception phase:

The inception phase deals with the initial investigation into proposed system with key deliverables. The inception model is brief and key models are to be started but not completed in any detail. Some of prototypes give brief idea about proof of concept (John, 1998).

Inception iteration:

Business case:

High intensity visualization of system:

Benefits of business:

Estimation of cost to develop

Planned iterations

Specific deliverables planned

Use cases to include:

List of all use cases

Description for some use cases

Prototypes:

Proof of concept prototype

Vision prototype

Development environment prototype

Potential project risks:

Risk assessment planning

Most of the use case should be identified, but only few of them are described to intermediate level of detail. The use case for complete system includes the following:

Add customer
Add sail course
Schedule course offering
Register customer for course offering
Book lodging
Process final payment
Check in customer
Cancel customer registration
Process certification
Sell merchandise
Staff course offering
Assign boat
Maintain boats
Maintain staff
Maintain course
Maintain course offerings
Maintain customers

The project moves to the elaboration phase of iteration when inception phase of iteration is completed. The first iteration would address the subset requirements of a system and business model. These are chosen based upon the risk assessment plan and preliminary schedule plan. The elaboration phase not only includes requirement and analysis but it also includes design and implementation for this subset of requirements. In this particular iteration there is involvement of four iterations two of such are employees and customers (Dave, 2008). These people interact with system through internet, these use case model and domain model are limited comparing to other sail requirements. The domain model of iteration gives the brief idea about UML model diagram which includes four classes. The limited scope is used for first iteration.

Registered

Date registered after payment

Focusing upon requi

Every use case diagram is focused towards modeling the use case description that highlights the activities that is completed by system. The below diagram is a use case diagram for inception phase. The final diagram that is used is the variation with UML sequence diagram which is called as system sequence diagram. These sequence diagram works on behavior of the system from one object to another object. The rectangles represent the objects and verticals lines represent as the lifeline that represent time and horizontal represents the arrow messages. The system sequence diagram represents the model requirements rather than the design details because of its limited actors and one object that represent software construction. These details of a software system are not addressed and only input messages, output data are included.

Use case name:	Schedule course
Scenario
Triggering event:	Owner decides to schedule a class
Brief description:	Owner search for course in a system using course descriptor, when it is displayed , he/she enters the details of the course that is offered, then the system builds a new course offer. This process continues till course is offered
Actors:	Owner, manager
Stake holders	All office managers
Pre condition	Course must exist
Flow of events	Course offering must be created by actors and system by certain event
Exception conditions	If the course is not offered than owner must enter description

The purpose of the design is to add further clarifications to make user understand about the products. Those who perform modeling at requirement level and design level have scope of understanding the modeling activities which have scope to raise the questions about the current system. The major solution for this activity can be high quality and more robust (Edwin, 2000). Good design and modeling techniques can be applied to design diagrams that enables the design issues and to apply best standards solutions. This identification is basis of work done in development of particular system. Taking time for designing takes time however, the process can be done quickly without any circumstance.

COMPARISION AND ANALYSIS

The comparison between two levels gives the idea about better process through which future system can be performed. Level 0 data flow diagram shows the better quality in course offering for the customers. Here the owner is one who gathers information which is related to customers and ultimate output is ac course offering. This process followed is a multi object which comes under sail course. The major destination of this is to develop the course offering system that is processed for future system (Robert, 2008). Level 1 dataflow diagram starts with owner and output of this system is ac controller. This system is a repetitive system where huge number of iterations is taken until course offered is conformed and then it moves back to owner for next course offering. The data access layer in this system can recover data in to proper format which can be understood. When the current access the data it can be used by controller to access course offering of a system. In level o dataflow diagram owner is originated towards the controller object and this data can be stored in course offerings (Jimmy, 2009). Level 1 data flow consist of database context SQL statements through which data can be processed but the access of this can be done by the users having knowledge on the database systems. This output of this system can be a micro station which can be used for transfer of data in to course offering system. The context diagram in system can be used for transfer of data from one particular system to other with the help of three layer architecture. This diagram helps to find the problems that are accessed during the starting point of data transfer. Level 1 diagram is used to find the error messages and transfer the information related to that through course offering objects. This can even be identified as a unified model with separate level of diagrams that give brief of design diagrams. This phase is use to recall the previous work of the sail course with number of cycles or iterations. The last stage of this will be course offering of objects in iterations. In level 0 data flow the information is revert back towards the actors to inform that current course offering has been completed and this is complete process (George, 2009). The design of data can be classified in to different classes which provide information that is modeled towards the requirements o a system. Therefore this data design classifies and focuses towards the interface and database design which is necessary for a particular system to run successfully. The difference between design and analysis can be focused towards different domain classes. By comparing both the levels of data flow diagram we can conclude that level 0 data flow helps in finding and documenting the specifications as per requirements.

REFERENCE:

Kaplan H, Nick B, Heather B, 2009, Cima Official Learning System Test of Professional Competence in Management Accounting. Elsevier, ISBN 1856178595, 9781856178594.
Lee M, 2005, Formers portable Australia Great Barrier reef, John Wiley and sons.
Mobile Reference, 2007, Travel Sydney, Australia: Illustrated Travel Guide and Maps, Mobile Reference publishers.
Robert M, 2008, Great Australian Sporting Moments, The Miegunyah Press, ISBN 0522855474, 9780522855470.
George M, 2001, Australian Legends. R.I.C. Publications, ISBN 1863116753, 9781863116756.
Jimmy C, 2010, II World Cruising Destinations: An Inspirational Guide to All Sailing Destinations, A&C Black, ISBN 1408114011, 9781408114018.
Michael W, 2009, Australian offshore laws, Federation Press.
Marc L, Lee M, 2004, Frommer’s Australia from $50 a Day, John Wiley & Sons.
Tim U, 2005, Australia: The Backpackers Ultimate Guide, BUG Backpackers Guide, 2005.
Former’s Shortcuts, 2011, Queensland and the Great Barrier Reef, Australia: Former’s Shortcuts, John Wiley & Sons.
Michael L, 2008, The Encyclopedia of Tourism and Recreation in Marine Environments, CABI.
Judith R, 2003, More Yachting Yarns from South Australia: The Tales and History of Ten Extraordinary Yachts, Sea view Press.
Margo D, and Anne D, 2003, Rough Guide to Australia, Rough Guides.
Rob Van Driesum, 2002, Outback Australia Lonely Planet.
Australia Bureau of Meteorology, 2001, Australian meteorological magazine, Volume 50 Bureau of Meteorology.
Dave G, 1999, The Elements of Boat Strength: For Builders, Designers, and Owners, McGraw-Hill Professional.
American Society of Civil Engineers, Task Committee on Marinas, 2000 Planning and Design Guidelines for Small Craft Harbors, American Society of Civil Engineers, 1994.
John C, P, 1998, The Marine Electrical and Electronics, Bible Sheridan House, Inc.
Dave G, 2008, Boat Mechanical Systems Handbook: How to Design, Install, and Recognize Proper Systems in Boats, McGraw-Hill Professional.
Edwin R, 2000, Power boater’s Guide to Electrical Systems: Maintenance, Troubleshooting, and Improvements, McGraw-Hill Professional.

LD35

“The presented piece of writing is a good example how the academic paper should be written. However, the text can’t be used as a part of your own and submitted to your professor – it will be considered as plagiarism.

But you can order it from our service and receive complete high-quality custom paper. Our service offers INFORMATION SYSTEM essay sample that was written by professional writer. If you like one, you have an opportunity to buy a similar paper. Any of the academic papers will be written from scratch, according to all customers’ specifications, expectations and highest standards.”

Please Click on the below links to Chat Now or fill the Order Form !

INFORMATION SYSTEMS AND ANALYSIS DESIGN