Difference between revisions of "Software Non-functional Assessment Process (SNAP)"
(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.) |
(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.) |
||
| Line 1: | Line 1: | ||
| − | The SNAP sizing process is very similar to the [[Functional_Size_Measurement_(FSM)|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 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 requirement 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 [ | + | The SNAP sizing process is very similar to the [[Functional_Size_Measurement_(FSM)|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 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 requirement 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 [[Functional_Size_Measurement_(FSM)|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 [[Function_Point_Analysis_(FPA)|FPA]].<ref>About SNAP [http://www.ifpug.org/about-ifpug/about-snap/ International Function Point Users Group]</ref> |
Revision as of 06:53, 7 January 2019
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 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 requirement 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]
References
- ↑ About SNAP International Function Point Users Group