Revision as of 13:40, 23 April 2016 edit Евгений Мирошниченко (talk \| contribs) 37 edits →Overview: refinement ← Previous edit		Revision as of 13:44, 23 April 2016 edit undo Евгений Мирошниченко (talk \| contribs) 37 edits →Overview: strange and unusual statement being unsourced for a long time Next edit →
Line 17: Such a requirement describes an interaction between an external agent (the [[User (computing)\|user]]) and the software system. When the user provides input to the system by clicking the OK button, the program responds (or should respond) by closing the dialog window containing the OK button. It can be ''informal'', in which case it can be considered as a [[blueprint]] or user manual from a developer point of view, or ''[[Formal specification\|formal]]'', in which case it has a definite meaning defined in [[mathematics\|mathematical]] or programmatic terms. In practice, most successful specifications are written to understand and fine-tune applications that were already well-developed, although [[safety-critical]] [[software systems]] are often carefully specified prior to application development. Specifications are most important for external interfaces that must remain stable. ~~'''~~ == Functional specification topics ==

Functional specification: Difference between revisions