Software Non-functional Assessment Process (SNAP) - Revision history

User at 16:26, 3 January 2023

2023-01-03T16:26:25Z

User at 14:09, 23 December 2022

2022-12-23T14:09:15Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T18:26:42Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User: 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.

2019-01-07T06:53:09Z

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.

User: 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.

2019-01-07T06:51:43Z

New page

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-Method|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>

===References===
<references />

===Further Reading===
*International Cost Estimation & Analysis Association Conference June 18,2013 [http://www.research.att.com/techdocs/TD_101164.pptx IFPUG]
*A New Software Metric to Complement Function Points [http://static1.1.sqspcdn.com/static/f/702523/23063515/1373252379300/201307-Tichenor.pdf Sqspcdn]

@@ Line 1: / Line 1: @@
-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>
+The '''Software Non-functional Assessment Process (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 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 to 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.
 ==See Also==
-*[[Software Development Effort Estimation]]
+*[[Function Point Analysis (FPA)]]

@@ 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 [[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>
+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>
@@ Line 7: / Line 11: @@
 ===Further Reading===
-*International Cost Estimation & Analysis Association Conference June 18,2013 [http://www.research.att.com/techdocs/TD_101164.pptx IFPUG]
+*[http://www.research.att.com/techdocs/TD_101164.pptx International Cost Estimation & Analysis Association Conference June 18,2013 -IFPUG]
-*A New Software Metric to Complement [[Function Points]] [http://static1.1.sqspcdn.com/static/f/702523/23063515/1373252379300/201307-Tichenor.pdf Sqspcdn]
+*[http://static1.1.sqspcdn.com/static/f/702523/23063515/1373252379300/201307-Tichenor.pdf A New Software Metric to Complement Function Points -Sqspcdn]

@@ 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 [[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>
+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>
@@ Line 8: / Line 8: @@
 ===Further Reading===
 *International Cost Estimation & Analysis Association Conference June 18,2013 [http://www.research.att.com/techdocs/TD_101164.pptx IFPUG]
-*A New Software Metric to Complement Function Points [http://static1.1.sqspcdn.com/static/f/702523/23063515/1373252379300/201307-Tichenor.pdf Sqspcdn]
+*A New Software Metric to Complement [[Function Points]] [http://static1.1.sqspcdn.com/static/f/702523/23063515/1373252379300/201307-Tichenor.pdf Sqspcdn]

← Older revision		Revision as of 06:53, 7 January 2019
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 [~~Functional-Size-Measurement-~~FSM~~-Method~~\|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>	+	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>