Revision as of 14:13, 26 September 2014 edit Thebster (talk \| contribs) 1 edit m Noted a minor (and ironic) typo in the image. SI&T is System Integration and Test not System Integration and TEXT. Tag: gettingstarted edit ← Previous edit		Revision as of 11:25, 21 January 2015 edit undo Deb (talk \| contribs) Administrators 216,848 edits m clarify Next edit →
Line 5: {{software development process}} A '''functional specification''' (also, ''functional spec'', ''specs'', ''functional specifications document (FSD)'', ''functional requirements specification'', or ''Program specification'') in [[systems engineering]] and [[software development]] is the documentation that describes the requested behavior of an engineering system. The documentation typically describes what is needed by the system user as well as requested properties of inputs and outputs (e.g. of the [[software]] system). A functional specification is the more technical response ~~onto~~to a matching requirements document, e.g. the [[Product requirements document\|Product Requirement Document]] "PRD". Thus it picks up the results of the [[requirements analysis]] stage. On more complex systems multiple levels of functional specifications will typically nest to each other, e.g. on the system level, on the module level and on the level of technical details. == Overview ==

Functional specification: Difference between revisions