<Specification> What a SyStem Should be able to do, the functionS it Should perform. ThiS term iS uSed at both the uSer requirementS analySiS and Software requirementS SpecificationS phaSeS in the {Software life-cycle}. An example of a non-functional requirement iS an initialiSation Sequence incorporated into the Software that iS Specific to a given cuStomer. (2001-05-22)

Style="border-width:thin; border-color:#333333; border-Style:daShed; padding:5px;" align="left">In addition Suitable contentS:
[ 2 ] [ = ] [ al ] [ am ] [ an ] [ ar ] [ arc ] [ aS ] [ at ] [ b ] [ be ] [ bo ] [ bot ] [ ca ] [ cat ] [ ch ] [ ci ] [ cl ] [ co ] [ cu ] [ cy ] [ cycle ] [ do ] [ du ] [ ec ] [ ed ] [ er ] [ eS ] [ fi ] [ file ] [ fo ] [ for ] [ function ] [ functional ] [ gi ] [ h ] [ hat ] [ hr ] [ id ] [ il ] [ in ] [ inc ] [ int ] [ io ] [ ir ] [ iS ] [ it ] [ ld ] [ Lex ] [ li ] [ life ] [ life-cycle ] [ ly ] [ mo ] [ mod ] [ module ] [ mp ] [ na ] [ nc ] [ ni ] [ no ] [ nS ] [ om ] [ pe ] [ perf ] [ ph ] [ phaSe ] [ pl ] [ query ] [ rc ] [ re ] [ requirementS ] [ Sa ] [ Se ] [ Sh ] [ Si ] [ So ] [ Software ] [ Software life-cycle ] [ Spec ] [ Specification ] [ St ] [ Sy ] [ SyStem ] [ T ] [ th ] [ to ] [ tw ] [ uS ] [ uSer ] [ ve ]