Details of Submission: Note that all work handed in after the submission date(s) and within 5 working days will be capped at 40% 1 . No marks will be awarded if the assessment is submitted after the late submission date unless extenuating circumstances are applied for and accepted (Advice Centre to be consulted). Work should be submitted as detailed below. You are responsible for checking the method of submission. This is a multi-stage assessment – Stage One: You will be expected to submit a CD on Friday 25 th November 2016 at the lecture. There should be three projects present on the CD – Client (two to run in demo), Middleware and Server (details below). Stage Two: You will be expected to submit a CD on Wednesday 11 th January, 2017 at the lecture. Again there should be at least three projects (details below). IT IS YOUR RESPONSIBILITY TO KEEP A RECORD OF ALL WORK SUBMITTED Part B: Marking and Assessment (to be completed by Module Lecturer) This assignment will be marked out of 100% This assignment contributes to 25% of the total module marks. This assignment is bonded Assignment To develop a three tier system that will simulate a guessing game. Stage One: (to get a basic pass) will expect the passing of a message from the clients to the middleware, to the server, back to the middleware and then back to the correct client. This is the basic framework for the coursework. Stage Two: There will be two clients, one middleware and two servers. 1 Information on exclusions to this rule is available from Campus Advice Shops Each server will hold the number to be guessed and any other relevant data – show via labels or text boxes. Once the two clients have registered to play, the game may commence – the clients will be expected to play in turn. In order to differentiate between a registration and a guess some sort of protocol will need to be devised - will be shown how to split a string in lecture notes. Don't forget that each transaction will expect a response back to the client. The middleware will be responsible for maintaining consistency of data between the servers – the servers will be permitted to talk to each other directly- but only if they are both on-line. We will not actually turn a server off and make it off-line – we will assume that they will not fail – just be busy (not available) sometimes i.e. can still send and receive messages, but that is all if off-line –no game processing or interaction. Complexity: On each server will be a button on/off line. When the button is pressed it will toggle between available and not available. A transaction should be performed if at least one of the servers is active and up to date. This type of system will offer the possibility of having inconsistent data and needs to be resolved. Grading Criteria: Stage One 40-50% -> by the due date to have accomplished message passing from both clients – middleware – server – middleware – appropriate client. Students will be appropriately rewarded for accomplishing the first task by the due date To accomplish stage two i.e. 2 multi-clients, middleware, 2 servers operational 45%-55% To get the basic operations of guessing game working 55-60% To include some form of turning servers on/offline and maintaining game 60-65% To consider and maintain synchronisation and the game continuation 65%>