Index: openacs-4/packages/acs-core-docs/www/requirements-template.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/requirements-template.html,v
diff -u -r1.49.2.15 -r1.49.2.16
--- openacs-4/packages/acs-core-docs/www/requirements-template.html	11 Jun 2017 08:42:13 -0000	1.49.2.15
+++ openacs-4/packages/acs-core-docs/www/requirements-template.html	15 Jun 2017 13:56:42 -0000	1.49.2.16
@@ -59,9 +59,9 @@
 	    any module using a single methodology with minimal exposure to
 	    code.
 	  </p></blockquote></div></li></ul></div><p>
-      For guidelines writing requirements, take a 
-      <a class="ulink" href="http://www.arsdigita.com/ad-sepg/process/requirements-quality.html" target="_top">look
-	at the quality standards</a>, along with a good example, such as <a class="xref" href="apm-requirements.html" title="Package Manager Requirements">Package Manager Requirements</a>.
+      For guidelines writing requirements, take a look at <a class="ulink" href="http://www.utm.mx/~caff/doc/OpenUPWeb/openup/guidances/guidelines/writing_good_requirements_48248536.html" target="_top">
+	quality standards</a> or <a class="ulink" href="https://ep.jhu.edu/about-us/news-and-media/writing-good-requirements-checklists" target="_top">requirements
+	checklist</a>, along with a good example, such as <a class="xref" href="apm-requirements.html" title="Package Manager Requirements">Package Manager Requirements</a>.
     </p><p>
       Besides writing requirements in natural language, consider using the
       following techniques as needed: