working on requirements list

tat_requirements/plan.md

@@ -5,19 +5,19 @@ Big questions
 - how is gitlab backed up?
 
 
-Overview
+Overview and order of work
 ---
 
 
-- create tech documents, filling in as much prose as possible
+1. create tech documents, filling in as much prose as possible
 
-- create prototype software to test tech requirements, iterate updating requirements and prototype
+1. create prototype software to test tech requirements, iterate updating requirements and prototype
 
-- create tests for test driven development, and validate prototype
+1. create tests for test driven development, and validate prototype
 
-- refactor or rewrite prototype to match requirements
+1. refactor or rewrite prototype to match requirements
 
-- create version 1 of software
+1. create version 1 of software
 
 
 Code we write

tat_requirements/requirements.md

@@ -78,7 +78,6 @@ only sufficient detail to disambiguate items.
   - ability to issue reminders
   - integrated email notification
   - "watched" records (might be reporting, and not specifically work flow)
-  - 
   
 - reporting
 

tat_requirements/tat_functional_requirements.md

+
+July 16 2015: Do not edit this file. Newer files here supercede the information here.
+
 TAT Functional Requirements
 
 Authors