Differences

This shows you the differences between two versions of the page.

--- courses:cs335:spring2019:test_wiki:addoptions [2019/04/26 19:51] – created haywardc
+++ courses:cs335:spring2019:test_wiki:addoptions [2019/04/26 20:51] (current) – haywardc
@@ Line 1: / Line 1: @@
-====== Requirements Template ======
+====== Add Options to Display Colors and Names ======
-Name of feature should be the top-level heading.
-===== Feature =====
+We will (potentially) create checkboxes for displaying colors and/or displaying names of elements. If we discover an easier way to do this, we will change the methodology but not the end result.
-Describe the feature -- provide a general overview
+==== Prerequisites ====
-===== Prerequisites =====
+The categories must already be **[[labels|color-coded]]**.
-What had to happen before someone reaches this page, e.g., user must be logged in and have certain authorization privileges.
+==== What a User Sees ====
-Link to earlier feature as appropriate, so that we can easily reference the requirements for that feature.
+There are four different variations of the table the user can see based on their choices: one is without names and colors, one is with names and without colors, one is without names and with colors, and the last is with both.
+==== What a User Does ====
-===== What a User Sees =====
+The user checks and unchecks checkboxes to display or remove colors and names.
-Describe what a user sees: what are the input fields, what are the results displayed, what order are they in
+==== Behavior of the Application/Feature ====
-===== What a User Does =====
+When a box is checked or unchecked, a different html page will be loaded with the only difference being the cosmetic difference sought by their action. This will require four different permutations of the page and table. By default, the table will be displayed with colors and without names.
-Describe the options for what a user can do.  Be specific.  (May be tied with fields in earlier section.)
+==== Example Use Cases ====
-What is required of the user?  Any input that needs to validated?  Any constraints?  (Perhaps a user must fill in two fields or only one of two fields.)
+A user can change these display options to learn more information or to quiz themselves. Exercises can use this property to display a customizable amount of information.
-===== Behavior of the Application/Feature =====
+==== Priority ====
-When a user enters input or clicks a button, what are the possible outcomes?
-Examples: if user enters erroneous input, what happens?  if user does one of three options, what happens in each of those cases?
-===== Example Use Cases =====
-Describe some typical situations of what a user can/will do.
-May want to put this earlier, but may not make sense unless you explain the other stuff.
-===== Priority =====
-Relative priority of feature (high, medium, low)
+medium-high