Revision as of 09:40, 2 April 2025 edit Nyq (talk \| contribs) Extended confirmed users 5,855 edits m lc per MOS:EXPABBR Tags: Visual edit Mobile edit Mobile web edit Advanced mobile edit ← Previous edit		Revision as of 09:41, 2 April 2025 edit undo Nyq (talk \| contribs) Extended confirmed users 5,855 edits m lc common noun Tags: Visual edit Mobile edit Mobile web edit Advanced mobile edit Next edit →
Line 27: ===Process=== In the ordered industrial software engineering life-cycle ([[waterfall model]]), functional specification describes ''what'' has to be implemented. The next, [[~~Systems~~systems architecture]] document describes ''how'' the functions will be realized using a chosen software environment. In non industrial, prototypical systems development, functional specifications are typically written after or as part of requirements analysis. When the team agrees that functional specification consensus is reached, the functional spec is typically declared "complete" or "signed off". After this, typically the software development and testing team write source code and test cases using the functional specification as the reference. While testing is performed, the behavior of the program is compared against the expected behavior as defined in the functional specification.

Functional specification: Difference between revisions