Before revision: Process |chapter=Chapter 6: Software requirements|title=Applied Software Project Management |first1=Andrew |last1=Stellman |first2=Jennifer |last2=Greene |publisher=O'Reilly Media |pages=97–130 |year=2005 |isbn=9780596553821 |access-date=15 June 2018 </ref> A typical functional requirement will contain a unique name and number, a brief summary, and a rationale.
After revision: Process A typical functional requirement will contain a unique name and number, a brief summary, and a rationale.