move sections between files, section heads updated in outout.md, fix section heads.

tat_requirements/co-op_background.md

@@ -21,9 +21,9 @@ Robbie Hott
 
 [Co-op Background](co-op_background.md)  (This document) 
 
-[Introduction ](introduction.md) (Was an introduction, but shaping up to be the requirements)
+[Introduction ](introduction.md) (Was an introduction, but shaping up to be requirements part one)
 
-[Requirements](requirements.md) (Tech requirements from Rachael's spreadsheets)
+[Requirements](requirements.md) (Requirements part two, includes requirements from Rachael's spreadsheets)
 
 #### Introduction to SNAC
 

tat_requirements/introduction.md

 #### TAT Functional Requirements
 
-Before reading this you should have read:
 
-[Plan](plan.md) (External, broad view roadmap)
+[Plan](plan.md) (Read this first. External, broad view roadmap)
 
-[Co-op Background](co-op_background.md)  (Currrent state and background explanations)
+[Co-op Background](co-op_background.md)  (Currrent state and SNAC background)
 
-[Introduction ](introduction.md) (This document. The technical requirements)
+[Introduction ](introduction.md) (This document. The technical requirements part one)
 
-[Requirements](requirements.md) (Tech requirements from Rachael's spreadsheets)
+[Requirements](requirements.md) (Tech requirements part two, includes requirements from Rachael's spreadsheets)
 
 #### Introduction to Planned Functionality
 

tat_requirements/outline.md

@@ -61,6 +61,10 @@ Documentation
 
 Required new features
 
+Web application overview
+
+Web application output via template
+
 Data background
 
 What is "normal form" and what informs the database schema design?
@@ -78,3 +82,46 @@ Brian’s API docs need to be merged in or otherwise referred to:
 Not sure where to fit these topics into the requirements. Some of them may not be part of technical requirements:
 
 
+requirements.md
+----
+
+List of requirements
+
+Requirements from Rachael's spreadsheet
+
+List of Application Programmer Interfaces (APIs)
+
+Maintenance Functionality
+
+Functionality for Discovery
+
+User interface for Discovery
+
+Functionality for Splitting
+
+User interface for Splitting
+
+Functionality for Merging
+
+User interface for Merging
+
+Functionality for Editing
+
+User interface for Editing
+
+Admin Client for Maintenance System
+
+User Management
+
+Web Application Administration
+
+Reports
+
+System Administration
+
+Community Contributions
+
+Ability to Open/Close the Site during Maintenance
+
+Sandbox for Training, perhaps as a clone of the QA system?
+

tat_requirements/readme.md

 
 These documents are organized in the following order:
 
-[plan.md](plan.md) gives the big overview.
+[plan.md](plan.md) Big overview.
 
-[introduction.md](introduction.md) covers the current state and gives some historical background.
+[outline.md](outline.md) An outline of sections in the documents
 
-[co-op_background.md](co-op_background.md) covers broad expectations for the co-op software.
+[co-op_background.md](co-op_background.md) Broad expectations for the co-op software.
 
-[requirements.md](requirements.md) are the technical requirements.
+[introduction.md](introduction.md) Requirements part one
+
+[requirements.md](requirements.md) Requirements part two, includes tech requirements from Rachael's spreadsheets