Function points and SNAP cover the entire spectrum of the requirements from a software system. 

While function points size the functional user requirements per ISO guidelines, SNAP takes into consideration things which are: a) Non-functional as per ISO guidelines & are b) Not counted under the function point method. 

• The two methods complement each other and provide complete coverage of both functional and non-functional requirements.
• It improves the correlation of effort and size, as the development of a software includes tasks to meet both functional and non-functional requirements.
• It improves estimation and the ability to predict the effort and time required to deliver a software project.
• Developers are not penalized for investing effort in the non-functional aspects of the requirements.
• Users can better understand the benefits of an application to their organization.
• Customers can better realize (and quantify) the values for their money. Both function points and SNAP points are assets added to the software.
• Software development productivity calculations are more accurate; any variations in measuring “effort/function points” metric may be better explained.
• Projects that are non-functional only can now be sized.
• Differences in values of Key Performance Indicators (KPIs) between projects are better explained.

Login as a member to access this resource.

Non-Members: $20.00, purchase the publication here: https://ifpug.memberclicks.net/bpm