Due date: 4/09 : 6pm
As promised, software doesn't exist in a vacuum. Customers change their minds; rule designers alter their games. Software developers have no choice but to follow their customers and adapt their software to the new conditions.
In our case, the rules of Squadron Scramble are changing. Specifically, the game designers have decided that players can exchange wildcards from discarded squadrons. If a player discards any squadron using a wildcard (or two), then during a later turn any player who has a corresponding aircraft card in his possession may exchange the aircraft card for one of the wildcards.
For this rule interpret "discard" as "discarded fighter or bomber squadron" or a "fighter squadron used to attack some bomber squadron". Once a bomber squadron with wildcards is shot down, the wildcards are lost for the rest of the battle.
Task 1: [POINTS: 15] Design changes to the interfaces, classes/modules, contracts, cheating detectors, and unit tests. Use class diagrams, sequence diagrams, interface statements with contracts, and prose to describe those pieces.
Task 2: [POINTS: 10] Implement a "tracer bullet" (see "The Pragmatic Programmer") version of your design.
Task 3: [POINTS: 5] Revise the XML-based protocol from Project 10 for testing your new interaction routines.
|last updated on Tue Jun 9 22:03:19 EDT 2009||generated with PLT Scheme|