Functional requirements

1. All Dragon Slayers, Dragon Heads, and Dragon Tails must be able to login and logout of the system.

2. All Dragon Slayers, Dragon Heads, and Dragon Tails must be able to view and edit their user profiles.

3. All Dragon Slayers, Dragon Heads, and Dragon Tails must be able to view previous and upcoming battles, as well as weyrs.

4. Dragon Heads must be able to register/unregister weyrs and tails, and add/remove tails from weyrs.

5. Dragon Heads must be able to message weyrs about battles.

6. Dragon Heads must be able to end current sessions.

7. Dragon Heads must be able to save all updates.

8. Dragon Slayers must be able to assign privileges to Heads/Tails to edit profiles.

9. Dragon Slayers must be able to update Battles/War and recognize winners.

10. Dragon Slayers must be able to accept new tails and assign weyrs.

11. Dragon Slayers must be able to register new heads for weyrs.

12. Dragon Slayers must be able to assign Battle rules.

13. Dragon Slayers must be able to update/create new genres.

22. Dragon Slayers must be able to delete heads, tails, or weyrs, genres, and battles.

14. Dragon Slayers must be able to schedule Battles.

15. Dragon Slayers must be able to create Battles

16. Dragon Slayers must be able to delete weyrs that have not been filled.

17. Dragon Slayers must be able to publish results to social media and the Dragon Con website.

18. Dragon Tails must be able to send/receive messages from weyrs/heads/slayers.

Nonfunctional requirements

1. The system must be user-friendly with screens designed for each part of the systems functions, and show the correct information for each type of user. (Slayer/Tail/Head)

2. The system must be accessible from either (1) server application (Web browser), or (2) client application (windows, mac, mobile).

3. The system must provide multi-user access.

4. The system must authenticate the user by checking their username/password and provide the appropriate access.

5. The system must use a permanent data storage system, such as a database.

6. The system must use accepted standards whenever possible.

7. The system must be coded in Java.

Use Case Diagram

Domain Object Model

Create Battle Use Case Diagram

Create the following sequence diagrams for the following functional capabilities:

creating a genre by DragonSlayer

adding battles with weyrs to a genre by DragonSlayer

creating a weyr by DragonHead

DragonTail update profile

deleting a genre, battle or weyr by DragonSlayer

battle reslts Personal Info New weyers Login/Logout Saves/Updates logout' Loginl View battles view message boards Join Battle:s reply/send battle reslts Personal Info New weyers Login/Logout Saves/Updates logout' Loginl View battles view message boards Join Battle:s reply/send