Explore chapters and articles related to this topic
System and Software Measurement Programs
Published in Ron S. Kenett, Emanuel R. Baker, Process Improvement and CMMI® for Systems and Software, 2010
Ron S. Kenett, Emanuel R. Baker
In determining “size,” we need a measure that is standardized across projects and independent of the methodology, technology, or development tools used to create the systems or software. Commonly cited measures of size include pages of documentation, number of objects, lines of code or function points, and number of manufactured units. For software, lines of code are typically measured without counting embedded comments in the source code and without special-purpose code used only for testing and debugging. The SEI guideline [5] for measuring lines of code is a standard that can be used to ensure that consistent definitions are used within the organization. As noted in Chapter 2, we emphasize again the importance of operational definitions, in this case to ensure that a line of code means the same thing to everyone involved. A function points is a dimensionless number that is representative of the extent of the functionality of the software—hence, a size measure. Guidelines for counting function points are provided in publications available from the International Function Points User Group (IFPUG). Function points also enable consistent size definitions within an organization, or within the software industry, for that matter, because they are independent of the programming language used for any project.
SWAQ: a Semantic Web Application Quality Evaluation Framework
Published in Journal of Experimental & Theoretical Artificial Intelligence, 2018
The function point metric effectively measures the functionality delivered by a system (Abrahao & Pastor, 2003). Authors define how Web application and hence SWAs will differ from software in terms of their definition of the components of Unadjusted Function Point Count (UFC) (Abrahao & Pastor, 2003). The goal is to attain a rich set of functional constructs of SWA, while the question to be asked is how much functionality is supplied by SWA to its user. Since, UFC and Value Adjustment Factor (VAF) are real and positive, normalisation of functionality, , is performed as in Equation (2).