CSSE2002/7023作业代写

In this assignment, and continuing into the second assignment, you will build a simple simulation of an air traffic control (ATC) system. The first assignment will focus on implementing the classes that provide the core model for the system.

An ATC system manages the movement of aircraft around an airport, including assigning aircraft to terminals and gates, and managing situations such as emergencies. An ATC system also maintains various queues including a landing queue, and takeoff queue (more about this in assignment 2).

Terminals each contain a number of Gates, and can be designed to only cater to specific types of aircraft, such as Airplanes or Helicopters.

An aircraft can be either an Airplane or a Helicopter. An Aircraft can have two primary purposes; they can either be a Passenger aircraft, or a Freight aircraft.

Each aircraft has various characteristics which are known to the ATC system including the aircraft’s empty weight, fuel capacity, passenger capacity, and freight capacity. These characteris- tics can determine how long it can take to complete various actions such as boarding passengers or freight, or refueling the aircraft. The total weight of an aircraft can change depending on the occupancy level (passengers or freight) of the aircraft (for example, more passengers means the aircraft will be heavier).

Each aircraft also has a list of tasks that it completes. Tasks represent the actions or states that an aircraft can take including: being away from the airport (for assignment simplicity we only care the aircraft is in an away state, we do not care what it might be doing in this time), waiting to land, waiting to take off, loading (i.e. passengers or freight), and waiting idle at the gate. Tasks can take different amounts of time depending on characteristics of the aircraft, and the requirements of each recorded task (for example, loading takes longer when there are more passengers or freight).

The list of tasks which an aircraft has must follow a strict set of requirements. The tasks can only occur in a specific order (for example, it would not make logical sense to be waiting in the air in a landing queue, and then takeoff – the aircraft must land first). Aircraft also complete a task list in a circular manner. Once the aircraft has completed the last task in the list, it will then commence the first task in the list again. This behaviour will go on forever (this simplification of aircraft behavior is for assignment simplicity. A real aircraft would have much more complex schedules, but this is way beyond the scope of this course).

留学生CS代写

Code specifications are an important tool for developing code in collaboration with other peo- ple. Although assignments in this course are individual, they still aim to prepare you for writing code to a strict specification by providing a specification document (in Java, this is called Javadoc).

You will need to implement the specification precisely as it is described in the specification docu- ment.

The Javadoc can be viewed in either of the two following ways:

1. Open https://csse2002.uqcloud.net/assignment/1/ in your web browser. Note that this will only be the most recent version of the Javadoc.

2. Navigate to the relevant assignment folder under Assessment on Blackboard and you will be able to download the Javadoc .zip file containing HTML documentation. Unzip the bundle somewhere, and open doc/index.html with your web browser.

留学CS作业代写

1. Fully implement each of the classes and interfaces described in the Javadoc. 2. Write JUnit 4 tests for all the methods in the following classes:

Gate (in a class called GateTest)

TaskList (in a class called TaskListTest)

CS编程代写

Conformance is marked starting with a mark of 10.

Every single occurrence of a conformance violation in your solution then results in a 1 mark de- duction, down to a minimum of 0. Note that multiple conformance violations of the same type will each result in a 1 mark deduction.

Conformance violations include (but are not limited to):

Placing files in incorrect directories.

Incorrect package declarations at the top of files.

Using modifiers on classes, methods and member variables that are different to those specified in the Javadoc. Modifiers include private, protected, public, abstract, final, and static. For example, declaring a method as public when it should be private.

Adding extra public methods, constructors, member variables or classes that are not de- scribed in the Javadoc.

Incorrect parameters and exceptions declared as thrown for constructors. Incorrect parameters, return type and exceptions declared as thrown for methods. Incorrect types of public fields.