Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml,v diff -u -N -r1.7 -r1.7.2.1 --- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml 7 Aug 2017 23:47:54 -0000 1.7 +++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/requirements-template.xml 9 Aug 2019 20:04:23 -0000 1.7.2.1 @@ -197,7 +197,7 @@ Although in theory coding comes after design, which comes after requirements, we do not, and perhaps should not, always follow such a - rigid process (a.k.a. the waterfall lifecyle). Often, there is a + rigid process (a.k.a. the waterfall lifecycle). Often, there is a pre-existing system or prototype first, and thus you may want to write some thoughts on implementation, for aiding and guiding yourself or other programmers.