Differences

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

--- courses:cs335:spring2019:test_wiki:beautify [2019/04/26 19:52] – created haywardc
+++ courses:cs335:spring2019:test_wiki:beautify [2019/04/26 21:04] (current) – haywardc
@@ Line 1: / Line 1: @@
-====== Requirements Template ======
+====== Make it Prettier ======
-Name of feature should be the top-level heading.
-===== Feature =====
+We can make improvements to the table's appearance such as changes to borders, font, etc.
-Describe the feature -- provide a general overview
 ===== Prerequisites =====
-What had to happen before someone reaches this page, e.g., user must be logged in and have certain authorization privileges.
+In order to ensure the table looks just as desired, all features listed prior to this except for integration into multiple exercises and the line separating metals and non-metals need to be completed.
-Link to earlier feature as appropriate, so that we can easily reference the requirements for that feature.
 ===== What a User Sees =====
-Describe what a user sees: what are the input fields, what are the results displayed, what order are they in
+A better, more attractive display of the table.
-===== What a User Does =====
-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)
+low