Differences

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

--- courses:cs335:spring2019:test_wiki:labels [2019/04/26 19:51] – created haywardc
+++ courses:cs335:spring2019:test_wiki:labels [2019/04/27 02:48] (current) – created haywardc
@@ Line 1: / Line 1: @@
-====== Requirements Template ======
+====== Labels for Color Categories ======
-Name of feature should be the top-level heading.
-===== Feature =====
+We will maintain a color-coded legend for the different categories of elements and their states. These categories are: hydrogen (by itself), alkali metals, alkaline earth metals, transition metals, lanthanides, actinides, poor metals, other non-metals, ununseptium (by itself), noble gases. Text colors are based on state of matter.
-Describe the feature -- provide a general overview
+==== Prerequisites ====
-===== Prerequisites =====
+Elements need to be categorized for coloring.
-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.
+A user will see the table with different colors indicating each element's type (category) and state. They will also see a legend with colored boxes for the categories and text for the states.
+==== Example Use Cases ====
-===== What a User Sees =====
+Users will apply color codings to discern information about a given element or group of elements.
-Describe what a user sees: what are the input fields, what are the results displayed, what order are they in
+==== Priority ====
-===== What a User Does =====
+medium priority
-Describe the options for what a user can do.  Be specific.  (May be tied with fields in earlier section.)
-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.)
-===== Behavior of the Application/Feature =====
-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)