Revision as of 13:33, 23 April 2016 edit Евгений Мирошниченко (talk \| contribs) 37 edits Citation needed ← Previous edit		Revision as of 13:37, 23 April 2016 edit undo Евгений Мирошниченко (talk \| contribs) 37 edits →Overview: False reference: the phrase from the source is about ''а specification'' in general, and does not say a word about "а functional specification" Next edit →
Line 10: == Overview == In [[systems engineering]] a functional specification is a document that clearly and accurately describes the essential technical requirements for items, materials, or services including the procedures by which it can be determined that the requirements have been met. Specifications help avoid duplication and inconsistencies, allow for accurate estimates of necessary work and resources, act as a negotiation and reference document for engineering changes, provide documentation of configuration, and allow for consistent communication among those responsible for the eight primary functions of Systems Engineering. They provide a precise idea of the problem to be solved so that they can efficiently design the system and estimate the cost of design alternatives. They provide guidance to testers for verification (qualification) of each technical requirement.<ref name="SEF01"/> A [[function (engineering)\|functional]] specification does not define the inner workings of the proposed system; it does not include the specification of how the system function will be implemented. Instead, it focuses on what various outside agents (people using the program, computer peripherals, or other computers, for example) might "observe" when interacting with the system. A typical functional specification might state as follows:

Functional specification: Difference between revisions