Requirement Specification

Homepage

• The homepage must display the text "Level" in the top center of the homepage.
• The homepage must display the text "Updating D&D 5e Characters Made Easy" below the text "Level" at the top center of the page.
• The homepage must have two dropdown menus which represent the interaction through which users can select classes and select levels.
• The homepage's "Go button" must change the displayed page to the next page of the application (Step 1 of the level-up process for the given class and level) upon being clicked.

Class Selection

• Users must be able to find and select the class for their search query in the drop-down menu for class selection, and have visual indication that this has been completed.Users must be able to click anywhere on the input form in order to be able to provide input (ex: text box, drop-down menu)
• Users must be able to deselect the class for their search query in the drop-down menu for class selection, and have visual indication that this has been completed.
• Available classes must be sorted in increasing alphabetical order in the drop-down menu for class selection. (i.e, Bard, Druid, Fighter)
• The dropdown menu for class selection must be placed in the mid-center of the page above the dropdown menu for level selection.
• User must be able to click anywhere on the dropdown menu in order to open the dropdown menu and select a class.
• As a default state when initially opening the Level application, the text "Select Option" will be displayed in the dropdown menu's text as a placeholder.

Level Selection

• Users must be able to find and select a level from 1 - 20 for their search query in the drop-down menu for levels, and have visual indication that this has been completed.* Users must be able to deselect the level for their search query.
• Users must be able to deselect the level for their search query in the drop-down menu for levels, and have visual indication that this has been completed.
• Available levels must be sorted in ascending order in the drop-down menu for levels. (i.e, 1, 2, 3, 4, 5, ... 20)
• The dropdown menu for level selection must be placed in the mid-center of the page below the dropdown menu for class selection.
• User must be able to click anywhere on the dropdown menu in order to open the dropdown menu and select a level.
• As a default state when initially opening the Level application, the text "Select Option" will be displayed in the dropdown menu's text as a placeholder.

Go Button

• Users must only be able to navigate to the a new page if a class or level has been selected in the drop-down menu (if there is a class or level displayed in the text of dropdown menu).
• The homepage's "Go button" must be placed below the two dropdown menus in the bottom center of the page.

Reference Pop-Up Window

• The window must open when the user clicks text that is colored green on any "Step" page in the Level application.
• The only text that will be colored green are spell names and Feature names.
• The window must display a description based on the text that is clicked on that is a definition about that text which corresponds with definitions provided by the Dungeons & Dragons 5th Edition handbook for that text. (i.e, green text is "Invisibility", displayed description is "A creature you touch becomes invisible until the spell ends. Anything the target is wearing or carrying is invisible as long as it is on the target’s person. The spell ends for a target that attacks or casts a spell.")

Steps Overview

Organization

• Steps must follow a predefined ordering as follows: Increase Hit Points, Increase Proficiency (every four levels, with the proficiency bonus increasing by one each time it is displayed), Choose Features, Increase Spell Slots (for classes that use spells), Learn Spells, Cantrips, Incantations (for classes that use spells)
• If a Step is not applicable for the class in question, it must not be displayed in the Step level-up ordering (i.e, class, like Fighter, is not a spell user, so Increase Spell Slots and Learn Spells, Cantrips and Incantations should not be displayed)

General Design

• Subheaders
  • On the top of each step page, users must be shown the Class and Level for which they are iterating through a level-up process.
  • On the top of each step page, users must be shown which Step they are on, both number and title, and the purpose of the Step, in terms of what information it provides (Ex: Step 1, Increase Hit Points)
• Next and Back Buttons
  • There must be a next button at the bottom right section of the page
  • Upon clicking the next button, users must be taken to the next step, unless this step is the last (Step 1 to Step 2 / last step to Completed Page)
  • There must be a back button at the bottom left section of the page
  • Upon clicking the back button, users must be taken to the previous step, unless this step is the first (Step 4 to Step 3 / Step 1 to Homepage)
• Progress Bar
  • There must be a progress bar at the bottom of the page, filled to A/B, where A is the current step number, and B is the calculated number of steps this process includes for this specific Class and Level.

Step-Specific Requirements

Increase Hit Points

• User's must be provided with correct, simple Hit Die instructions that give a clear indication of what they must to do calculate Hit Points for their character (Fighter, Step 1: roll a 1d10, then add your character’s constitution modifier)
• Users must be see a visual representation of the correct dice type for their character class (Fighter: illustration of a 10-sided dice)

Proficiency

• This Step must contain content which instructs the user to increase their proficiency to +3 at Level 5, +4 at Level 9, +5 at Level 13, and +6 at Level 17 (cumulatively increasing the added proficiency bonus by 1 for every four levels).

Choose Features

• Users must be provided with all the features for their Level & Class, and the features for no other Levels and/or Classes.
• Users must be provided with Steps that provide instructions on how to add new or adjust old features for their character, as specified by the rules for each specific Class and Level.
• For updating existing Features, users must be shown the correct information for the given level and class. (Change Song of Rest from 1d6 at Level 2 to 1d8 at Level 9)

Organization

• Each Feature must have its own Step, which must be indicated by page separation.
• If a Feature has functions that are separate (in the sense that their functionality is not related to each other), this separation will be visually indicated by breaking up the container that hods the feature into multiple Steps.

Formatting

• If a Feature includes displaying a list, each choice must be shown as a bullet point to avoid implying to the user that they must select choices on Level's interface.

Magic

• Users must be informed as to which spell slots they have just gained, and have the ability to see what their total spell slots are.
• User's must be informed as to how many spells they are able to learn
• If the user’s character has the feature to replace existing spell, they must be prompted that they have that option.
• All possible spells must be shown, for their class and level (only from the Player’s Handbook)
• Spells must be expandable to show detailed effect, properties, constraints; all relevant and correct information as specified in the Handbook
• Once expanded to the Spell page, users must be able to return to the previous Step page with a back button.

Organization

• Spells must be sorted ascending by their spell level, then by alphabetical order, with the spell level sort taking precedence

Completed Page

• The page must display the text "Congratulations! You are now a Level {level} {class}!" with {class} representing the class that the user selected and {level} representing the level that the user selected. (i.e, “Congratulations! You are now a Level 5 Wizard”)
• When the back button is clicked, the user must be able to return to the previous page, which should be the last Step in the level-up process for that specific class-level configuration.
• When the "Level-Up" button is clicked, the application must change from the current page to the home page, and the application must be returned to its default state.