Add example table to functional requirements section
authorPatrick Adler <patrick.adler@chi.frb.org>
Fri, 17 Apr 2015 08:21:46 -0500
changeset 704 e364989e179b
parent 703 9dfe5be845f8
child 705 49399a3ec70a
Add example table to functional requirements section
latest/payment-agent/index.html
--- a/latest/payment-agent/index.html	Fri Apr 17 01:23:27 2015 -0500
+++ b/latest/payment-agent/index.html	Fri Apr 17 08:21:46 2015 -0500
@@ -123,7 +123,33 @@
 	 <li><b>WA</b> - Wallet and Paymnet Instrument Provisioning and Administration</li>
 	 <li><b>SA</b> - Security and Auditing</li>
  </ul>
-  <p class="note">Following the introduction of categories above, this section will include a categorized table of mandatory list of core/functional requirements that the architecture must support </p>
+  <p class="note">Following the introduction of categories above, this section will include a categorized table of mandatory list of core/functional requirements that the architecture must support.
+	  <p id="summary_functional_requirements"></p>
+	  <table>
+	   <caption>Summary Functional Requirements</caption>
+	   <thead>
+	    <tr>
+	     
+	     <th id="category"> Category
+	     <th id="requirement_id"> ID
+	     <th id="requirement">Requirement	
+	     <th id="use_case_ref">Use Cases
+	   <tbody>
+	    <tr>
+	     <td>IA
+	     <td> 1
+	     <td> Payer and payee should not need to know each other’s account numbers to make a web payment
+	     <td> Payer Privacy
+	    <tr>
+   	     <td>IA
+   	     <td> 2
+   	     <td> Payer and payee account data should not be disclosed at any point throughout the lifecycle of the payment
+   	     <td> Payer Privacy
+	  </table>
+  
+  </p>
+  
+  
 </section>
   
 <section><h3>Role Based Contextual Requirements</h3>