Content deleted Content added
m Reverted edits by 218.213.76.1 (talk) to last version by 131.203.65.3 |
m →Purpose: Repairing links to disambiguation pages - You can help! |
||
Line 20:
There are many purposes for functional specifications. One of the primary purposes on team projects is to achieve some form of team consensus on what the program is to achieve before making the more time-consuming effort of writing [[source code]] and [[test case]]s, followed by a period of [[debugging]]. Typically, such consensus is reached after one or more reviews by the [[Stakeholder (corporate)|stakeholder]]s on the project at hand after having negotiated a cost-effective way to achieve the requirements the software needs to fulfill.
# To let the [[Software developer|developers]] know what to build.
# To let the [[testers]] know what tests to run.
# To let [[Stakeholder (corporate)|stakeholder]]s know what they are getting.
| |||