"2.2 Design the processes using Activity diagrams."

We require a few of these which model the most important processes in the system (think war engine, how war theatres play out, how a country decides and acts out a turn, etc.)

2.3 Decide on the patterns to address the functionality defined by the functional requirements and processes.

2.4 Design the classes for each of the identified patterns taking their interrelationships into account.

2.5 Draw a class diagram of your system.

This diagram will likely change over time

"2.8 Provide at least two object diagrams showing the state of the objects active in the war simulation at a specific point in time."

Please take note of the submission instruction for the 'Report' task.

4.1 You are required to write a brief about your research, ensuring that you reference all sources. Your brief
should include what you understand about warfare as well as associated entities, phases, etc. that you
will be using as part of you warfare engine. Make sure to document any further assumptions or decisions
you made. Lastly ensure to include relevant definitions and explanations where required.

4.2 A report stating how you applied the design patterns to address the functionality required by the system.
This report should include UML diagrams to augment the explanation. This Task goes hand-in-hand
with the Design task. Much of the design must be reported on in this task.

"2.7 Design state diagrams showing how an object (which could also be a composite) changes state"

There is a lot of opportunity in our system to create these.

This involves creating and implementing all the classes involved in the ArmyComponent hierarchy. This involves the Abstract Factory and Composite

"2.6 Draw Sequence and communication diagrams showing the message passing between objects."

This will involve the fundamental mechanisms of certain design patterns as well as the interaction between patterns.

"2.1 Identify the functional requirements."

A page or so long document describing the functional requirements of our system (ie: an overview of what our system does and how it, what aspects of war it includes, what is the overall driver of the simulation, etc) should suffice