Actions

Difference between revisions of "Functional Size Measurement (FSM)"

(Functional Size Measurement (FSM) is a technique for measuring software in terms of the functionality it delivers. The ISO/IEC standard for Functional Size Measurement 14143-1:2006 defines FSM as a means of quantifying the Functional User Requirements)
 
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).)
 
Line 1: Line 1:
Functional Size Measurement (FSM) is a technique for measuring software in terms of the functionality it delivers. The ISO/IEC standard for Functional Size Measurement 14143-1:2006 defines FSM as a means of quantifying the Functional User Requirements i.e. functions that the user has required to be delivered. Functional Size can be used for many purposes however; it is primarily used at the planning stage for input into project resource estimation calculations for cost, effort and schedule.At the completion of a project it is used to compare performance in terms of the cost effectiveness and efficiency of the development and support teams. FSM measures the functional requirements of the software. This means that it can be applied before development commences, rather than retrospectively as is the case with other forms of software measurement, such as counting lines of code and/or other physical objects. This capability to measure early enables accurate estimates to be made, risks to be evaluated, and project scope to be negotiated, before final commitments are made. FSM also enables comparison of applications and projects based on their size. Productivity rates for applications of a similar attribute profile can be compared for benchmarking support ratios and improvement purposes. Productivity rates from past projects can also be used to predict effort, once a project’s Functional Size has been determined.<ref>What is Functional Size Measurement? [http://www.totalmetrics.com/webhelp2-2/Background_and_Articles_on_Functional_Size/Introduction_to_Function_Point_Analysis/What_is_Functional_Size_Measurement_.htm Totalmetrics.com]</ref>
+
Functional Size [[Measurement]] (FSM) is a technique for measuring [[software]] in terms of the functionality it delivers. The ISO/IEC [[standard]] for Functional Size Measurement 14143-1:2006 defines FSM as a means of quantifying the Functional User Requirements i.e. functions that the user has required to be delivered. Functional Size can be used for many purposes however; it is primarily used at the planning stage for input into project resource estimation calculations for cost, effort and schedule.At the completion of a project it is used to compare performance in terms of the cost effectiveness and [[efficiency]] of the development and support teams. FSM measures the functional requirements of the software. This means that it can be applied before development commences, rather than retrospectively as is the case with other forms of software measurement, such as counting lines of code and/or other physical objects. This capability to measure early enables accurate estimates to be made, risks to be evaluated, and project scope to be negotiated, before final commitments are made. FSM also enables comparison of applications and projects based on their size. [[Productivity]] rates for applications of a similar attribute profile can be compared for [[benchmarking]] support ratios and [[improvement]] purposes. Productivity rates from past projects can also be used to predict effort, once a project’s Functional Size has been determined.<ref>What is Functional Size Measurement? [http://www.totalmetrics.com/webhelp2-2/Background_and_Articles_on_Functional_Size/Introduction_to_Function_Point_Analysis/What_is_Functional_Size_Measurement_.htm Totalmetrics.com]</ref>
  
  
 
===References===
 
===References===
 
<references />
 
<references />

Latest revision as of 16:01, 6 February 2021

Functional Size Measurement (FSM) is a technique for measuring software in terms of the functionality it delivers. The ISO/IEC standard for Functional Size Measurement 14143-1:2006 defines FSM as a means of quantifying the Functional User Requirements i.e. functions that the user has required to be delivered. Functional Size can be used for many purposes however; it is primarily used at the planning stage for input into project resource estimation calculations for cost, effort and schedule.At the completion of a project it is used to compare performance in terms of the cost effectiveness and efficiency of the development and support teams. FSM measures the functional requirements of the software. This means that it can be applied before development commences, rather than retrospectively as is the case with other forms of software measurement, such as counting lines of code and/or other physical objects. This capability to measure early enables accurate estimates to be made, risks to be evaluated, and project scope to be negotiated, before final commitments are made. FSM also enables comparison of applications and projects based on their size. Productivity rates for applications of a similar attribute profile can be compared for benchmarking support ratios and improvement purposes. Productivity rates from past projects can also be used to predict effort, once a project’s Functional Size has been determined.[1]


References

  1. What is Functional Size Measurement? Totalmetrics.com