Index: openacs-4/packages/acs-core-docs/www/requirements-template.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/requirements-template.adp,v diff -u -r1.4 -r1.5 --- openacs-4/packages/acs-core-docs/www/requirements-template.adp 25 Apr 2018 08:38:28 -0000 1.4 +++ openacs-4/packages/acs-core-docs/www/requirements-template.adp 3 Sep 2024 15:37:32 -0000 1.5 @@ -1,7 +1,11 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {System/Application Requirements Template} +{/doc/acs-core-docs/ {ACS Core Documentation}} {System/Application Requirements Template} System/Application Requirements Template +

System/Application Requirements -Template

<authorblurb>

By You -

</authorblurb>
+Template
+

By You +

+OpenACS docs are written by the named authors, and may be edited by +OpenACS documentation staff.

Introduction

Briefly explain to the reader what this document is for, whether it records the requirements for a new @@ -103,9 +110,9 @@ Optional: Implementation Notes

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 pre-existing system or -prototype first, and thus you may want to write some thoughts on +should not, always follow such a rigid process (aka 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.

@@ -124,8 +131,8 @@ 0.1Created8/21/2000Josh Finkler, Audrey McLoghlin -

($‌Id: requirements-template.xml,v 1.7 -2017/08/07 23:47:54 gustafn Exp $)

+
($‌Id: requirements-template.xml,v 1.7.2.2 +2020/07/02 08:39:25 gustafn Exp $)