Create a diagram using Visio. For example, each Character in the system (either Player or Monster) shares a common attribute of Name. Make sure your classes do not duplicate any code by using Java inheritance to share these common attributes and methods. Upload the Visio diagram as a JPEG or PNG along with your source code.

Some guidelines for the UML diagram:

• All classes in your program (besides Main) should be included in the class diagram.
• Your Character class hierarchy must have at least three levels of inheritance (including Character).
• At least two character types (ex. Warrior, Wizard, etc.) and at least two weapon or armour types must be included. A class for Monster should also be included.
• Your solution must include at least one example of aggregation or composition (has-a, instead of is-a). Suggested classes for aggregation: Weapon or Armour.
• All classes, attributes and methods should follow proper UML class diagram standards and conventions.
• Include constructors and over-ridden methods such as toString().
• Line indicators denoting inheritance, association or aggregation should be included wherever required.

Program Requirements

Create an application using Java and Java Swing to create a simple graphical role-playing game, including an opening splash screen, a simple character creation screen and a battle summary screen.

Screen Descriptions

The splash screen will have a title, and image and a button to progress to the creation screen.

The character creation screen will allow the user to enter a character name, choose a character type (ex. Warrior, Wizard, etc.), randomly reroll the character stats, and select a weapon (ex. Sword, Dagger, etc.). It will also have a button to progress to the battle summary screen.

The battle summary screen will display the selected character's name, class and image, randomly select a monster, then display all stats for both the player and the selected monster.

Program Structure

Your program must use inherited classes for the program Frame and each of the three screens (as Panels), as well as for the different characters, character types, weapons and monsters.

Each of your classes should make proper use of constructors, getter and setter methods, as well as any standard methods you deem necessary.

It needs at least one example of an abstract class and at least one abstract method. Examples of static properties or methods should also be included.

   

OND Game Dragons and Dungeons Build A Character