1. REFERRAL DEADLINE MONDAY 12 AUGUST 2013 3:30pm Resubmitted work received late will be counted as a non-submission THIS SHEET MUST BE ATTACHED TO ALL RESUBMITTED WORK FACULTY OF COMPUTING, ENGINEERING & TECHNOLOGY STUDENT’S NAME:__________________________________ REGISTRATION NUMBER:__________________________________ MODULE LEADER: ASSIGNMENT TITLE: MODULE TITLE: MODULE CODE: Any other instructions (eg. VIVA/Demonstrations) Faculty Office Staffordshire University Faculty of Computing, Engineering & Technology K266, Octagon Building Beaconside Stafford, ST18 0AD Work to be marked for the attention of: DO NOT EMAIL WORK Any queries during the Summer period should be made to the Faculty Office: Tel: 01785 353403 Email: fcet.awardsupport@staffs.ac.ukfcet.awardsupport@staffs.ac.uk CE00526-5 Concurrent Programming in C# Airplane Terminal Simulation F Pratt No demo

2. 2 CPICSCE00526-5 Concurrent Programming in C# Referral August '13 Airplane Terminal Simulation You are required to write a C# simulator for an airplane terminal system, with typical geometry as indicated overpage. The simulator is to assist system analysts with looking at dead-locks when the terminal is overloaded with planes. The assignment primarily tests your understanding of concurrent programming concepts from a C# perspective. The graphics required, in the assignment, is required to validate the correct workings and synchronisations of your system. Please hand-in the items requested on page 4, by or on the dead-line stipulated for your referral on the front-sheet. There should be a disc with an executable of your system included with the paper deliverables.

3. 3 CPICSCE00526-5 Below we give a typical set-up for the simulation.Three planes are waiting to take off from “hubs” 1,2 and 3 and a plane is queued for an arrival at the entry hub. The arrival plane is given its hub address of 1,2, 3 or 0 – the latter means it will land and then take off – at the left. Planes must strictly adhere to the indicated one-way system whether landing or taking off. Sections must only ever have at most one plane occupying them. A plane must wait if a section it wishes to enter is occupied. The arrival and hub buttons act as toggles to trigger movement, buttons are either set to "green" or "pink". In “green” mode planes can turn round at hubs. In “pink” mode they are “held” at hubs / landing(s). NB For hub sections the permitted direction of travel may need to “alternate”. Typical Geometry of Airport Terminal hubs take-off section section sectIonsectIon sectIonsectIon sectIonsectIon sectIonsectIon sectIonsectIon arrival hub/stack planes take-off in this direction buttons

4. 4 CPICSCE00526-5 Hand - in The following items are required :- 1 Design Documentation - 2 C# Code - NB The breakdown of the above marks is indicated in square brackets below. 1 Design Documentation [ 20 ] :- This should comprise. i) A front page, followed by table of contents. [3] ii) A clear explanation of the strategy used to ensure that two or more planes never enter the same section of the airport terminal. [7] iii) A diagram / map of all the threads running in the system and how they interact with one another. [10] eg Mascot-like concurrency network diagram. 2 C# Code [ 80 ] :- This should comprise. iv) Paper print-out of C# code [40] v) Executable of C# on disc. [40] 20 paper item 80 paper + disc items