Difference between revisions of "Software Non-functional Assessment Process (SNAP)"
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).) |
m |
||
| Line 1: | Line 1: | ||
| − | The SNAP sizing | + | The SNAP sizing process is very similar to the [[Function Point Analysis (FPA)|function point sizing process]]. Within the application boundary, non-functional requirements are associated with relevant categories and their sub-categories. Using a standardized set of basic criteria, each of the sub-categories is then sized according to its type and complexity; the size of such a requirement is the sum of the sizes of its sub-categories. These sizes are then totaled to give the measure of the non-functional size of the [[software]] application. The SNAP model consists of four categories and fourteen sub-categories to measure the non-functional requirements. Non-functional requirements are mapped to the relevant sub-categories. Each sub-category is sized, and the size of a requirement is the sum of the sizes of its sub-categories. While function points measure the functional requirements by sizing the data flow through a software application, SNAP measures the non-functional requirements. It is therefore complementary to FPA.<ref>About SNAP [http://www.ifpug.org/about-ifpug/about-snap/ International Function Point Users Group]</ref> |
| + | |||
| + | |||
| + | ==See Also== | ||
| + | *[[Software Development Effort Estimation]] | ||
| Line 7: | Line 11: | ||
===Further Reading=== | ===Further Reading=== | ||
| − | * | + | *[http://www.research.att.com/techdocs/TD_101164.pptx International Cost Estimation & Analysis Association Conference June 18,2013 -IFPUG] |
| − | * | + | *[http://static1.1.sqspcdn.com/static/f/702523/23063515/1373252379300/201307-Tichenor.pdf A New Software Metric to Complement Function Points -Sqspcdn] |
Revision as of 14:09, 23 December 2022
The SNAP sizing process is very similar to the function point sizing process. Within the application boundary, non-functional requirements are associated with relevant categories and their sub-categories. Using a standardized set of basic criteria, each of the sub-categories is then sized according to its type and complexity; the size of such a requirement is the sum of the sizes of its sub-categories. These sizes are then totaled to give the measure of the non-functional size of the software application. The SNAP model consists of four categories and fourteen sub-categories to measure the non-functional requirements. Non-functional requirements are mapped to the relevant sub-categories. Each sub-category is sized, and the size of a requirement is the sum of the sizes of its sub-categories. While function points measure the functional requirements by sizing the data flow through a software application, SNAP measures the non-functional requirements. It is therefore complementary to FPA.[1]
See Also
References
- ↑ About SNAP International Function Point Users Group